Re^2: what means concrete in perlglossary/role - a concrete set of behaviors?

http://qs321.pair.com?node_id=1033280

in reply to Re: what means concrete in perlglossary/role - a concrete set of behaviors?
in thread what means concrete in perlglossary/role - a concrete set of behaviors?

Maybe concrete is also meant as the opposite of abstract, which would somewhat run counter to the idea of "interface without implementation". But I don't follow Perl6 and the various incarnations of the M* modules and theories behind them.

Comment on Re^2: what means concrete in perlglossary/role - a concrete set of behaviors?

Replies are listed 'Best First'.
Re^3: what means concrete in perlglossary/role - a concrete set of behaviors? by derby (Abbot) on May 13, 2013 at 12:32 UTC
Am I missing something ... the glossary says "interface without inheritance." Not sure where you're getting "interface without implementation." -derby	[reply]
Re^4: what means concrete in perlglossary/role - a concrete set of behaviors? by Corion (Patriarch) on May 13, 2013 at 12:33 UTC
Yeah - so it doesn't even run counter to that.	[reply]
Re^4: what means concrete in perlglossary/role - a concrete set of behaviors? by Anonymous Monk on May 13, 2013 at 20:19 UTC
I took it to mean: abstract : Interface without implementation normal : Interface, implementation, and inheritance if you feel like it concrete : Implementation in stone, no inheritance allowed.	[reply]
Re^4: what means concrete in perlglossary/role - a concrete set of behaviors? by Anonymous Monk on May 13, 2013 at 13:08 UTC
See requires in Role::Tiny/Moose::Role, and Re: Howto create a Moose baseclass/superclass/contract? Moose equivalent of Module::Pluggable? Favorite way to create base/super class?	[reply]

In Section Seekers of Perl Wisdom