Yes I thought about that after my post if the superclass get the method removed... So I think that we should remove the explicit requirement since it is too static in a world like Smalltalk. Stef On Jan 21, 2009, at 11:08 PM, Adrian Lienhard wrote:
On Jan 21, 2009, at 22:57 , Stéphane Ducasse wrote:
Adrian why this is not simply that when you compute the composition and the method that you should add in B that you do not add f if it is an explicit requirement and defined in the superclass?
Its not that simple because the situation can change at any time. Lets say, class A does not implement #doSomething when you define B. When you add the trait T1, #doSomething sending #explicitRequirement is added to B. Later you implement #doSomething in A. At this moment the #doSomething has to be removed from B.
Adrian
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project