[MLton-devel] new basis library

[Matthew Fluet]

> Another option is to put in the calls to STRING_CONST (or something
> slightly less bold) by hand into the library source.

I think that would be too obfuscating in the library source.

I got a sed hack to work, and I extended the check-basis script to append
an optional .sml or .cm file to the end of the basis to type-check that
file under the basis.  This makes it easier to verify whether or not the
right opaque signature matches are being observed.  The only thing I can't
figure out is how to jettison SML/NJ's environment so that the program is
check just under MLton's exported basis.

> > And, the above switch doesn't work for string constants used in
> > pattern matches, but I didn't see any in my perusal of the basis
> > library and they would be easy enough to desugar if need be.
> 
> I saw a few in system/path.sml.

I replaced the ones in date.sml.  There are some left in
system/{file-sys.sml,path.sml} and posix/file-sys.sml.  SML/NJ complains,
but continues with the type-checking.



-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel