Re: Issue 1717 in pharo: Object and Class should have simple testing methods for trait use

Updates:
        Cc: [hidden email]
        Labels: Type-Enh Milestone-2.0

Comment #3 on issue 1717 by [hidden email]: Object and Class should  
have simple testing methods for trait use
http://code.google.com/p/pharo/issues/detail?id=1717

While there are no occurrences of that violation of demeter law in current  
system, I agree it should be test methods for traits.
But surely isKindOf: is not the appropriate message, because a trait is a  
composition, not an inheritance... maybe somethink like #isComposedBy: is  
better.
Also same for #includesBehavior:, that's for inheritance.  
#includesComposition: should be better

(oh, well... maybe some better names than that, but you get my point)

in favor of this approach, I'd say that it is an easy addition, and not a  
fundamental change (like it would be if we change #isKindOf: or  
#includesBehavior:)



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker