Henrik Gedenryd <h.gedenryd at open.ac.uk> wrote:
> danielv at netvision.net.il wrote:
> 
> > After that, I needed to move MailNotifier into this new module. I tried
> > to edit the class definition, as I would to change categories. This
> > didn't work, it offered to create a new class.
> > Q2: Why, is that the most common thing to do? when would I do that?

> Since there are  (multiple) namespaces the effect is to create a new
> definition of that name in the module that is specified. That is the natural
> interpretation of a definition message.

Well, it's breaking a very comfortable habit, but I guess it makes sense
in the new world.

> > I accepted, it worked, the class disappeared. In the ModuleExplorer,
> > however, the entry was still there, with the following printString:
> > '#(''stray-Module'' ''bad parent, #2857'')'. It still has it's neighbour
> > refs, the other variables are emptied.
> > Q4: Huh? what happened, how do I fix it, how do I avoid it, or should I
> > just start reading code now?
> 
> The ModuleExplorer itself is holding on to the last reference to the object,
> which has been removed from the module hierarchy.
Aha! yes, this worked. Collapsing enough of the explorer made it go away
(though not just collapsing the top level, for some reason). 

> Henrik