Re: Moose role with requirement consuming another role

Replies are listed 'Best First'.
Re^2: Moose role with requirement consuming another role by Boldra (Curate) on Jul 20, 2011 at 12:49 UTC
I can see how my simplified example matches that description of an interface role, but in reality the Logger Role has six attributes and 200 lines of code, it's not just a list of 'requires'. "this type of usage doesn't seem to be (officially) supported" == "I can't find it in the doc either" ? - Boldra	[reply]
Re^3: Moose role with requirement consuming another role by Arunbear (Prior) on Jul 20, 2011 at 14:16 UTC
Role::App being used like an abstract base class is what is at odds with the documentation (regardless of whether or not the Logger Role is an interface type role).	[reply]
Re^4: Moose role with requirement consuming another role by Boldra (Curate) on Jul 21, 2011 at 08:38 UTC
No, none of my roles are abstract base classes, they all provide additional functionality. Role::App reads the config file, creates objects based on its contents, and provides methods for fetching these objects. Anyway, I can't see how a class which inherits from another class (or a role) could be called an abstract base class - it's not at the base. But perhaps you are using a different definition. - Boldra	[reply]
Re^5: Moose role with requirement consuming another role by Arunbear (Prior) on Jul 21, 2011 at 10:53 UTC
Re^6: Moose role with requirement consuming another role by Boldra (Curate) on Jul 21, 2011 at 11:12 UTC
Some notes below your chosen depth have not been shown here
Re^5: Moose role with requirement consuming another role by Anonymous Monk on Jul 21, 2011 at 11:08 UTC
Re^6: Moose role with requirement consuming another role by Boldra (Curate) on Jul 21, 2011 at 11:20 UTC