Here is a RT ticket to Mouse:
https://rt.cpan.org/Public/Bug/Display.html?id=61312
Applying roles after the fact changes the flow of method modifiers. It
seems that application order takes precedence over the actual modifier
type.
This issue he reported occurs not only on Mouse, but also on
On Tue, 14 Sep 2010 20:45:55 +0900, Fuji, Goro g.psy...@gmail.com wrote:
Here is a RT ticket to Mouse:
https://rt.cpan.org/Public/Bug/Display.html?id=61312
Applying roles after the fact changes the flow of method modifiers. It
seems that application order takes precedence over the actual
- Original Message
From: Fuji, Goro g.psy...@gmail.com
Here is a RT ticket to Mouse:
https://rt.cpan.org/Public/Bug/Display.html?id=61312
Applying roles after the fact changes the flow of method modifiers. It
seems that application order takes precedence over the actual
On Sep 14, 2010, at 9:15 AM, Ovid wrote:
- Original Message
From: Fuji, Goro g.psy...@gmail.com
Here is a RT ticket to Mouse:
https://rt.cpan.org/Public/Bug/Display.html?id=61312
Applying roles after the fact changes the flow of method
modifiers. It
seems that application order
I wasn't aware of this module. It worked like a charm! Thanks!
On Tue, Sep 14, 2010 at 2:15 PM, Karen Etheridge p...@froods.org wrote:
On Tue, Sep 14, 2010 at 02:05:29PM -0400, Marcos Barbeitos wrote:
Hi! I just started using Moose in this project I've been working on.
I am preparing a
If it is actually warnings that you want to suppress, then Adam Kennedy's
Test::NoWarnings module may help you. It is used somewhere by the DBD::SQLite
test suite, which is how I know about it. -- Darren Duncan
