Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I know I keep saying this - but this _really_ reminds me of the way Eiffel puts things together (although they keep the class metaphor rather than calling them roles).

    • Except that you still have MI (but with explicit method resolution) and you still can have behavior buried in inherited classes rather than explicitly stated in the preamble to your code (though I love that you must explicitly override them). Also, because it's class based, it's not as easy to share behavior amongst classes which are not structurally related -- one of the design goals of roles.

      That being said, Eiffel looks really nice and if more than 3 people were using it ... ;)

    • This book [amazon.com] is actually one of my all time favorites. Eiffel has a nice concept of partial classes which themselves can require methods to be implemented, but it does not have conflict resolution like roles do so you are still susceptible to some of the issues that traditional MI/mixins has. But actually, if you throw in the rename and redefine keywords in Eiffel and you can actually manually fix that if you want. TIMTOWTDI I guess :)

      - Stevan