Stephen Pair wrote:

> Is it settled then?  Let's at least allow aliases for external modules
> for now and change the module def file to accomodate that.  Allowing
> 
> So, I'm studying the code and I see that ModuleReference has a method
> called #alias.  Which is exactly where I would have put a method to look
> up the alias for a neighbor module in the definedNames.  What is the
> indentended use for this alias?

As you found, the code already allows for aliases, and the module def file
supports it already too.

goran.hultgren at bluefish.se wrote:

> I would like to add support for the "minimal module metainfo" I was
> talking about earlier.
> I looked at the Annotations stuff but as I see it, these things does not
> get written to the external representation of the module.
> 
> Henrik - should/could we add this to the definition file or should we
> put it somewhere else, perhaps in a third, "noncompulsory" file? Was the
> annotations only meant to live in the image?
> 
> And since noone reacted on my list of fields I will go for what I
> posted. :-)

I think we can keep it in the def file for now, as in "keep it simple". I
posted a few comments about some fields being redundant, otherwise the list
was fine IMO.

Henrik