Re: Proposal: An OOC Package Tool

[Dirk Muysers <dmuysers@capgemini.fr>]

>   We are currently thinking about adopting Java's naming convention for
>"packages" in Lagoona. This would (in essence) still constitute a "flat
>namespace" however the compromise of settling for "reverse domain names"
>prefixing the actual module name seems to be the best one to make in terms
>of transparency and utility.


Definitely a good idea. I would even go one step further  --now this will
make scream--,
and separate again the interfaces from the modules, as it has been done for
example
in the Inferno project. In the latter you could have the following:

include "GuiModule.m"
gui: GuiModule;
if (motif_wanted) {
    gui = load "gui/modules/motif";
} else {
    gui = load "gui/modules/notif";
}
gui->Init();
......

This allows to import different implementations of the same module
interface.

There are also good ideas in the Xerox Parc ILU projects, particularly a
very good
algorithm for module footprinting, that gives a globally unique identifier
to a module
which may also be used as a module import key.

Just my 2 c.

Dirk Muysers