multiple classes with the same name, namespaces

[Brent Pinkney]

> 	Spoon currently still has the old system dictionary, but I'd like to 
> remove it. I think we should just rewrite users of "Smalltalk at:" 
> (probably in some automated fashion, both in situ and during method 
> transfer). Instead of a system dictionary, I'd rather have some class 
> take responsibility for each former non-class "global" variable, and use 
> messages for access. Or just use shared pools for such variables. (Heh, 
> shared pools is another topic that gets some people riled up. :)

Is the existing 'self class environment' not the palce to start?