[MLton-devel] new basis library
Matthew Fluet
fluet@CS.Cornell.EDU
Wed, 24 Jul 2002 17:28:08 -0400 (EDT)
---------- Forwarded message ----------
Date: Wed, 24 Jul 2002 15:59:33 -0500
From: Henry Cejtin <henry@sourcelight.com>
To: fluet@CS.Cornell.EDU
Subject: RE: [MLton-devel] new basis library
You guys are way way ahead of me in this stuff, but when I write my own code
I almost always use opaque constraints, and what I find myself doing all the
time, mainly to avoid having to write datatype definitions more than once, is
to first have the structure with no signature constraint, then to define the
signature, and finally to re-bind the structure name to the same structure,
but with the opaque constraint.
E.g.,
structure Zulu =
struct
datatype t = ...
...
end
signature ZULU =
sig
datatype t = datatype Zulu.t
...
end
structure Zulu = Zulu:> ZULU
My point is that couldn't something like this be done with the current basis.
You first build everything as it is now, then you re-bind all the structures
with opaque constraints. This way everything is in scope when you need it.
The disadvantage is that the constraints aren't imposed until the end, which
might not be the really right way to think about things.
-------------------------------------------------------
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