Panu Viljamaa wrote:

> Ok. So if I understand this correctly, selector namespaces mean that:
> 
> We can add or modify a method in an existing class but have the change affect only selected parts of the system - because a given method can have several implementations that co-exist simultaneously and get  used in different parts of the system.  Thus: " '50' asMoney"  could cause the execution of different implementations of #asMoney, depending on where the method call appears.
> 
> I believe this has been a feature of  VisualAge Smalltalk for a long time already ("Extended classes").  Right ?


No, as with ENVY for VW or StORE for VW, a only one extension of a given 
method may exist in force at a time.  In VW, I have a history log of 
overrides and can roll back to previous ones, but I still can't have 
more than one in force at the same time.  Selector namespaces would fix 
that.


> Making it standard would be cool naturally, if it can be done simply.
> 
> -Panu Viljamaa
> 
> 
> 
>