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'm waiting to see what shakes out of A12 before I do much more work on it. Very few people really understand the point of roles; I hope that Larry will explain it far better than I've been able to do.

    • by Ovid (2709) on 2004.02.14 21:42 (#28464) Homepage Journal

      I forgot to mention that since I don't know how Perl 6 roles are to be implemented, my design goals were driven by my understanding of the original traits document. That's one of the reasons why I call them "traits" instead of "roles". I've thought about uploading this to the CPAN, but I have two concerns. First, I don't want to cause potential confusion when Perl 6 comes out. Second, since there are already beginning implementations of roles, I don't necessarily want to provide competing modules unless I am very confident in what mine can do.

      Also, I've discovered that when I write weird stuff like this, I get very little feedback. Very few people understand what traits do (I'm not entirely sure that I've got it right), so I suspect that few, if any, would use my module. Further, I base my idea on the idea of composite runtime interfaces. That's a bizarre concept, so I don't know if it's a good idea.