Re: Moose role with requirement consuming another role

I don't quite understand your approach. If role Role::App requires the attribute gazpacho that role App::FixIt provides, why not not simply compose App::FixIt into Role::App?

Perl 6 - second systems done right

Comment on Re: Moose role with requirement consuming another role Select or Download Code

Replies are listed 'Best First'.
Re^2: Moose role with requirement consuming another role by Boldra (Curate) on Jul 20, 2011 at 10:21 UTC
My second example (with gazpacho), was really just meant to show that I understand the importance of the with/has order when a class consumes a role. Perhaps I over-emphasized it. The real problem is not with class<-role(requirement), but, similar to my first example, class<-role<-role<-role(requirements). Or to go into yet more detail, I have about 30 app classes which consume one of two specialized App roles, these both consume a generic App role, which consumes three further roles, MooseX::Getopt, MooseX::SimpleConfig plus our own app-logger role. I can easily drop the requirement in the app-logger role and everything works fine. I'm just curious if there is a better solution. - Boldra	[reply]

Replies are listed 'Best First'.

Re^2: Moose role with requirement consuming another role
by Boldra (Curate) on Jul 20, 2011 at 10:21 UTC

The real problem is not with class<-role(requirement), but, similar to my first example, class<-role<-role<-role(requirements). Or to go into yet more detail, I have about 30 app classes which consume one of two specialized App roles, these both consume a generic App role, which consumes three further roles, MooseX::Getopt, MooseX::SimpleConfig plus our own app-logger role.

I can easily drop the requirement in the app-logger role and everything works fine. I'm just curious if there is a better solution.

- Boldra

[reply]