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 the Role Debacle 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Regrettably, the warning is now getting pulled from roles and people who don't want silent "action at a distance" are now penalized.

    I have to agree with perigrin, this is a rather unfair characterization of the situation. We initially enabled the warning because it is useful and helpful, however the big downside that we all saw was that for people who were well versed in Roles and knew well how they worked were forced to add code to silence the warning. After considerable debate, both in the use.perl t

    • Additionally some work has been done (not sure how final/releasable it is) on making it actually easier for you to write something like MooseX::Roles::Strict, which would be quite painful with the current codebase.

      Actually the basic hook you need I think has been released. I went about doing this when this whole discussion started because it *should* have been possible, and Sartak made it work the right way (as opposed to my ugly hack). You can now say: use Moose::Role -metaclass => 'MyRole::Metaclass' and MyRole::Metaclass will replace Moose::Meta::Role and override the necessary Role composition bits to compose with your own custom composition rules. This is a lot more work than it should be, but it *is* possible now, as opposed to before when it wasn't even possible without replacing Moose::Role entirely.

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