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
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Mechanism vs Policy (Score:1)
If Moose developers won't change the default behaviour (I don't know the issues well enough to argue either way) then I'd hope they'd be open to providing a mechanism to let you do it yourself.
Perhaps you already can by sub-classing Moose::Role.
Re: (Score:2)
I'm pretty sure I can subclass Moose::Role, but I've never tried. Sounds like the way to go.
And at this point, even if they did agree this behavior is wrong (I don't believe they do), this has been part of the interface long enough that I doubt they would change it (kind of like how Perl 5's SUPER:: bug has never been fixed).
Re:Mechanism vs Policy (Score:1)
Okay, after much discussion on #moose (soon to be summarized on the mailing list) we will be adding a warning so that when a class method silently overrides the role method it will warn you that this is happening. In order to silence the warning you will have to explictly exclude the method from the role (see Moose::Cookbook::Roles::Recipe2 [cpan.org] for information on this feature).
For more details, watch for my summary mail on the mailing list.
- Stevan
Reply to This
Parent
Re: (Score:1)
And here's the mailing list summary [perl.org].
Re: (Score:2)
You've made me a ridiculously happy man right now :)