On Tue, 2005-04-26 at 10:49, Aaron Sherman wrote:
> Quoting S12:
> A class's method definition hides any role definition of the
> same name, so role methods are second-class citizens. On the
> other hand, role methods are still part of the class itself, so
> they hide any methods inherited from other classes, which makes
> ordinary inherited methods third-class citizens, as it were.
Oops, I was quoting A12, not S12. S12 says:
A class's explicit method definition hides any role definition
of the same name. A role method in turn hides any methods
inherited from other classes.
which is pretty much the same thing.
Aaron Sherman <[EMAIL PROTECTED]>
Senior Systems Engineer and Toolsmith
"It's the sound of a satellite saying, 'get me down!'" -Shriekback