goran.hultgren at bluefish.se wrote:
> 
> Doug Way <dway at riskmetrics.com> wrote:>
> 
> > Göran also refers to "neighbor" modules, which sounds vaguely familiar from long-ago discussions on this list.
> 
> Thanks for bothering with my dots! My name sounds so much better then!
> :-) :-) (ö like in "k(E)rnel" and G like in "(Y)ikes")

No problem.  I have no idea how to type in an ö, but I do know how to cut & paste. :)

> > (I may be oversimplifying, but it sounds like neighbor modules could be considered the required (imported, prerequisite, etc.)
> > modules for a particular module?  If so, I wonder if a term like "prerequisite" might more accurately describe
> > this one-way relationship.  The term "neighbor" implies a two-way sibling-like relationship to me.)
> 
> It is actually explained in the class comment of Module. Don't you have
> a 3.3alpha image up and running?! :-)
> In short it says:
> 
> "All "neighbor modules"--external modules, submodules, module
> parameters, delta modules--are held in an OrderedCollection to strictly
> define the order of lookup for names defined outside this module."
> 
> ...and that is actually also the name of the instance variable. Henrik
> had probably a hard time to come up with a name for this because a
> Module sees exported names for both external modules (what you would
> call typical "imports" or "prefrequisites"), submodules, module
> parameters and deltamodules.
> 
> So the neighbors are simply ALL other Modules that the Module "sees". We
> might come up with a better name but the name "prerequisite" does not
> seem to cover more than perhaps the external modules.

Ah, that makes sense then.  "Neighbor" sounds like a reasonable name in that context.

- Doug Way
  dway at riskmetrics.com