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
--Larry Wall
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)
Note I am not pretending to even play a Moose core developer on TV. I'm just giving my two cents being an active part of the Moose developer community.
If it was decided that this was the right decision it would be changed with a long deprecation cycle. The Moose team isn't above deprecating bad features. However something like this would need to be "proven" in a MooseX:: class for a while I would think.
The right answer I think would be to override the Moose::Meta::Role::Application::ToClass class to add the preferred behavior. I've not dug into those bits directly so I'm not sure how easy or hard that would be. But I'd be happy to help, as would anybody on #moose on irc.perl.org.
Reply to This
Parent