[MLton-devel] Fwd: Mark Tuttle
Matthew Fluet
fluet@cs.cornell.edu
Thu, 1 May 2003 19:19:36 -0400 (EDT)
> 1. Use IntInf
> 2. Use Int64
> 3. Use Word
>
> (1) is probably to costly performance-wise, but maybe we could try and
> see?
We'd also need to mediate all of the places where Position.int's are
passed to C; we won't be able to hand off an IntInf.
> (2) will take a while to implement, but is the way we should go long
> term.
Agreed.
> (3) would have as good a performance as we have now, and would allow
> up to 4G, but I don't think it's allowed by the Basis Library
> spec, which requires Position:> INTEGER
Depends on what you consider :> INTEGER implying. Certainly we can export
Word as INTEGER (just need to implement a few missing values and
functions). The fact that it is an opaque signature match means we will
never be able to confuse them with Int.ints. It's just a question of
whether or not:
(Position.fromString "~123") + (Position.fromString "123")
necessarily equals (Position.fromString "0").
In any event, I don't think it would affect end users that much. But,
certainly #2 is the way to go.
> Hmmm. In thinking about it further, maybe (2) isn't so bad if we go
> with the FFI library for Int64.
Maybe not.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel