http://www.perlmonks.org?node_id=1033279


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

I think concrete means well-defined in this context.

Isn't it also a way to specify an interface only?

Both Perl 6 and Moose allow that, yes.

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

Replies are listed 'Best First'.
Re^2: what means concrete in perlglossary/role - a concrete set of behaviors?
by Corion (Patriarch) on May 13, 2013 at 11:53 UTC

    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.

      Am I missing something ... the glossary says "interface without inheritance." Not sure where you're getting "interface without implementation."

      -derby

        Yeah - so it doesn't even run counter to that.

        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.