Nathanael Schärli wrote:

>>But the programmer has to remember not only 
>>the selectors but different objects as receivers - more complicated, 
>>and something new to learn. 

In that case you should stick with C ;-)

> Even with the new approach, you can still see all these classes as one
> virtual object. As you know, objects/classes can be built with
> aggregation and if it is important to you, we can design it so that you
> can type:
> 
> - "Smalltalk image" instead of "Image"
> - "Smalltalk changes" instead of Changes"
> - etc.

I like this one, or least having all the methods be instance methods of 
Image current, Changes current etc. This way you could actually have 
multiple objects representing e.g. another image or changes of another 
image etc. Same for SystemVersion, you name it.
Moving methods to the class side hardwires the concept of there only 
being one interpretation of the respective concept.

Just MTCW

Michael