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.

Solving compositional problems with Perl 6 mixins 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Because interfaces are not used, you don't have the problem with duplicate code, but you do get the benefit of knowing the methods are implemented (and that required methods are available.)

    Also, unlike Java's interfaces, role names and type names share a namespace. That's all of the goodness of allomorphic type checking in signatures.

    • I thought I had posted a response, but apparently I had not :(

      First, can you give a clear definition of "allomorphism"? Try as I might, I can't quite understand it. It seems like allomorphism [c2.com] is similar to polymorphism, except you can override behavior on an instance level instead of a class level and all that's relevant is that the interface is consistent. Is that correct? I think not because it's too simple.

      Also, I'm not sure what you mean by "role names and type names share a namespace." What benefit does that provide?

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.