Re: Moose role with requirement consuming another role

[Arunbear]

in reply to Moose role with requirement consuming another role

Your Role::Logger role looks like an "interface role" in the sense described in Roles Versus Abstract Base Classes, and your Role::App is being used like an abstract base class.

But this type of usage doesn't seem to be (officially) supported

[Boldra]

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"

?

[Arunbear]

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).

[Boldra]

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.