> There should be a way for a module in package A to refer to a
> sibling/child module in package A without referring to the full name
> of A. There should be a way to import bindings from "the module named
> C at the same level as me" or "the module named D among the modules
> only visible in my name space".
Perhaps a useful mechanism would be for some form of standardised
configure at the time a module is installed. At installation, a module
could search for other modules it requires, similarly as GNU configure
looks for required programs and libraries on disk. This should allow
some scope to re-arrange module categories at the top level.
Warnings at installation time about missing or misconfigured required
modules would be quite handy.
I agree that "relative" module names would be useful within a package
and in some cases for references between packages. What I'm suggesting
is another useful means of handling refences between modules in
different packages.
Perhaps another useful feature would be:
(find-module 'gdbm)
which would search the module hierarchy for the specified module. The
risk is of course that the wrong module may be found. Some form of
"hints" would help in these cases.
The alternative is that the module name space heirarchy should be
right first time. Otherwise modules may have different "paths" at
different sites or for different releases.
cheers,
glenn.
-- Glenn Moloney glenn@physics.unimelb.edu.au School of Physics, http://www.ph.unimelb.edu.au/~glenn University of Melbourne, Phone: +61 3 9344 4012 Parkville, Australia 3052. Fax: +61 3 9347 4783