> Precisely because everything that used to reference Smalltalk now 
> sends #environment, I think we should be careful about using it.  For 
> now, the #environment of any code *is* Smalltalk; returning anything 
> else is effectively lying and is bound to get you into trouble.

Yes but the first thing is to get rid of Smalltalk because we have 
problem even to play with dan's environment because a class cannot 
decide where to live, the browsers and all the tools
are doing the worng assumption that this should be Smalltalk.

>  I think Göran was mostly using it because it's a spare instance 
> variable on Class, not because Namespace provides all the semantics an 
> #environment should (no doubt he'll correct me if I'm wrong).
>
> Eventually, we may well find a use for that extra indirection, but I 
> don't think this is it.

I do not understand may be I'm tired as usual. But Smalltalk is an 
environment so I do not understand why we need an extra namespace 
class? Dan introduced Environment but environment were nested.
Goran what is the difference between Namespace and SystemDictionary 
(besides the fact that (1) SystemDictionary was a black hole attarcting 
all kinds of dirt and (2) that the name was not so well-chosen)

Stef