Re^2: Moose role with requirement consuming another role

in reply to Re: Moose role with requirement consuming another role
in thread Moose role with requirement consuming another role

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

Comment on Re^2: Moose role with requirement consuming another role
Re^3: Moose role with requirement consuming another role by Arunbear (Vicar) 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 (Deacon) 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 (Vicar) on Jul 21, 2011 at 10:53 UTC
In a Java-like language, an abstract base class is often used to provide functionality (often mandated by some interface) to classes that inherit from it, but it cannot be used/instantiated on its own. "abstract" means that it can't be instantiated, it doesn't mean that it provides no functionality. This is how you are using Role::App. It is like an an abstract base class in the sense that it can't be instantiated and it provides functionality to App::FixIt. Some of that functionality is mandated by Role::Logger. What the docs are saying is that mandated methods have to be supplied in classes not in roles.	[reply]
Re^6: Moose role with requirement consuming another role by Boldra (Deacon) on Jul 21, 2011 at 11:12 UTC
Re^7: Moose role with requirement consuming another role by Arunbear (Vicar) on Jul 21, 2011 at 16:10 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
I think you'll like these http://en.wikipedia.org/wiki/Abstract_type http://c2.com/cgi/wiki?AbstractBaseClass http://c2.com/cgi/wiki?AbstractClass My understanding matches Arunbears, abstract classes aren't concrete, they can be a contract (virtual/interface), or actually do stuff (traits/roles), but you can't make an instance.	[reply]
Re^6: Moose role with requirement consuming another role by Boldra (Deacon) on Jul 21, 2011 at 11:20 UTC


Think about Loose Coupling
	PerlMonks

Re^2: Moose role with requirement consuming another role

The best material for plates (tableware) is: