[MLton-devel] integrating multiple basis libs

[Matthew Fluet]

> > Then, depending on which basis is being used, process the bind-basis
> > and suffix-basis at compile time.
>
> This still leaves the choice of whether to keep the bind-basis and
> suffix-basis file contents in lib/mlton or in the world.  I think the
> latter will be simpler.

Right now, the bind-basis file is a list of files to be evaluated in the
environment produced by build-basis.  If we delay processing this file
until compile time, then we will be delaying reading in those files until
compile time.  But, in a binary distribution, we don't include the
basis-library source code.  So, we really need to lex and parse all those
files and suspend that in the world.

So, basisLibrary would have a type like:

unit -> {build: Decs.t,
         {name: string,
          bind: Ast.t,
	  suffix: Ast.t}} list

I guess that's reasonable.



-------------------------------------------------------
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