Re: how to trigger actions on Role use

2009-04-23 Thread Hans Dieter Pearcey
On Thu, Apr 23, 2009 at 02:43:37PM +0100, Mark Morgan wrote: Based on the above, the adding of the attributes should be done for the entire class once, when the role is first used. I don't like having to wrap constructor creation to handle this, better that there should be an

Re: Moose Talks at YAPC::NA

2009-04-23 Thread Sachin Sebastian
Wish I could watch those talks. Will it be available at http://yapc.tv/ or some other site? Thanks, Sachin. On Tue, Apr 21, 2009 at 1:55 PM, Sartak sar...@gmail.com wrote: I believe the Moose talks (with varying degrees of Moose focus) that have been submitted are: * Introduction to Moose

Unfun with roles.

2009-04-23 Thread Elliot Shank
Call me confused about what's going on with multiple roles with methods having the same name. I thought exclude should resolve this situation. However, this complains about Baz having to implement foo(); what am I not understanding? package Foo; use Moose::Role; sub foo {}; package Bar;

Re: Unfun with roles.

2009-04-23 Thread Sartak
On Thu, Apr 23, 2009 at 11:13 PM, Elliot Shank p...@galumph.com wrote: with  Foo = { exclude = 'foo' },  Bar = {}; The key is actually excludes not exclude. Moose really needs to use Params::Validate and MooseX::StrictConstructor. :( Shawn