nested modules proposal (was: packages proposal)

[Fergus Henderson]

On 13-Feb-1998, Andrew Bromage <bromage at cs.mu.OZ.AU> wrote:
> > > This way, the empty module name is sort
> > > of the "root module".  However it doesn't work when using "__" as
> > > a module qualifier.
> > 
> > Actually it *does* work with "__": you could just write "__m1__m2__foo".
> 
> No you can't.  That's a variable.

Doh! ;-)

> > > The only part of the
> > > compilation process that needs to understand this mapping, of course,
> > > is `mmake depend'.
> > 
> > The compiler also needs to know where to find the `.int' file
> > when it sees `:- import_module foo', or where to find the parent module's
> > `.m' file when a module begins with `:- module foo.bar'.
> 
> My point was that the .int files don't necessarily have to bear any
> filename relationship with the source file that they come from.

I guess they don't.

Mmake currently assumes that they do, but I guess `mmake depend'
could spit out hard-coded rules rather than relying on pattern
rules for creating the `.int' files.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3         |     -- the last words of T. S. Garp.