FYI, I was able to work around Alice ML's special use semantics by using a queue and a stack of queues to simulate the use process. The UseLib has now been revised and works with Alice ML as well as Poly/ML, SML/NJ, and Moscow ML.
Note that I also had to work around Alice ML's lack of a couple of functions in the OS.FileSys structure: http://mlton.org/cgi-bin/viewsvn.cgi/*checkout*/mltonlib/trunk/org/mlton/vesak/use-lib/unstable/detail/ml/alice/workarounds.sml -Vesa Karvonen On Nov 15, 2007 11:36 PM, Vesa Karvonen <[EMAIL PROTECTED]> wrote: [...] > Yeah, that is pretty much what I suspected. The reason why I'm asking > about this is that I recently wrote a simple "Use Library" > (http://mlton.org/cgi-bin/viewsvn.cgi/*checkout*/mltonlib/trunk/org/mlton/vesak/use-lib/unstable/README) > to help with porting my libraries and programs to multiple SML > implementations. The point is that by writing a single set of "use" > -files for a library/program (e.g. > http://mlton.org/cgi-bin/viewsvn.cgi/*checkout*/mltonlib/trunk/com/ssh/generic/unstable/lib.use), > one can more quickly try/get an initial port to most interactive SML > implementations. Fortunately, I think that it is possible to work > around Alice ML's more restricted use function in this case. I'll > have to try it tomorrow. (BTW, currently SML# has an even more > restricted form of use. SML#'s use is a new form of declaration and > not a first-class function.) _______________________________________________ alice-users mailing list [email protected] http://www.ps.uni-sb.de/mailman/listinfo/alice-users
