It appears that many subclasses of Model's implementation want to override with their own, exactly equivalent of the Object implementation.
Open Inheritance browser on Model>>#perform:orSendTo: and see.
Seems like we could get rid of Models and the dups. Does anyone know why Model's is like that?
On 1 October 2013 20:50, Chris Muller asqueaker@gmail.com wrote:
It appears that many subclasses of Model's implementation want to override with their own, exactly equivalent of the Object implementation.
Open Inheritance browser on Model>>#perform:orSendTo: and see.
Seems like we could get rid of Models and the dups. Does anyone know why Model's is like that?
There are a lot more Model subclasses using Model's implementation than there are using the redundant ones, at any rate.
frank
squeak-dev@lists.squeakfoundation.org