Here is a report of traits use in perl and this sounds really cool. I think that smalltalkers did not get totally the power of traits.
Stef > > I gave a presentation on this at a Lisbon conference. I have brief > slides at: > > http://www.slideshare.net/Ovid/inheritance-versus-roles > > And a longer write-up at (you can download the PDF if you have a > free account with them): > > http://www.slideshare.net/Ovid/inheritance-versus-roles-1799996 > > > However, those are rather introductory and target a Perl audience. > > For specific write-ups on the "class silently wins" issue: > > http://use.perl.org/~Ovid/journal/38809 > > Much of the debate has focused around our seeing (loosely) traits as > fulfilling two needs: interface *and* implementation. If you > primarily use roles as Java-style interfaces, then silently > discarding the role methods is a win. However, if you're like the > BBC and you use roles to provide implementation, silently discarding > the role methods is a loss. So just as classes used for two > different purposes (responsibility and code reuse) causes a bit of a > problem, roles used for two different purposes causes another issue > -- albeit, one not as severe as the problem they're intended to solve. > > Cheers, > Ovid > -- > Buy the book - http://www.oreilly.com/catalog/perlhks/ > Tech blog - http://use.perl.org/~Ovid/journal/ > Twitter - http://twitter.com/OvidPerl > Official Perl 6 Wiki - http://www.perlfoundation.org/perl6 > > _______________________________________________ > Traits mailing list > [email protected] > https://www.iam.unibe.ch/mailman/listinfo/traits _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
