ducasse <ducasse at iam.unibe.ch> wrote:

> For ellipse := (Module path: #(Squeak Morphic Core Basic)
>                      class: #EllipseMorph) new
> 
> this could be better
> as 
>     ellipse := (Module class: #EllipseMorph inPath: #(Squeak Morphic Core
> Basic) new
>     because we are interested in the class
> 
> Or we can have something new to refer to class in namespace


Are you and/or the other module people saying that with a modularized
Squeak system, everytime we wish to refer to a class that is in a
module, we would need to use something like one of the above examples? 
I hope I have misunderstood!  I think that would be horrible.

I am suspicious of "name spaces" altogether.  Look at VW and the costs
and delays involved in its move to name spaces.  It cost the use of the
refactoring browser for *years*.  It added a new complexity, and
therefore barrier, to anyone moving to VW or even just upgrading to the
the VW 5i series.  It made subclassing look much uglier.  Etc.  And all
for what?  Solving a problem of name clashes?  A problem that doesn't
really exist.

I hope my comments are moot because I have misunderstood completely. 
Otherwise, I can only hope the madness stops before it is too late.


-- Frank