in reply to Re^2: Solving compositional problems with Perl 6 roles
in thread Solving compositional problems with Perl 6 roles

I'm not sure what you mean by "That..."?

... does Program, Manage, FirstAid;

was meant to imply the equivalent of

... does Program does Manage does FirstAid;

with $individual stops FirstAid; removing the latter Role when appropriate.

Unless your referring to the last bit about the compiler mapping $individual does Thieving; to $individual isn't Employee;, in which case, my attempt at humour failed completely.

Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon

Replies are listed 'Best First'.
Re^4: Solving compositional problems with Perl 6 roles
by dragonchild (Archbishop) on Aug 23, 2004 at 12:16 UTC
    Actually, I think that your attempt at humor was actually a good idea, in disguise. I can see where one would like roles to be exclusionary - if $foo does X, that means you cannot have $foo does Y, so there should be a way of specifying that in the definitions of X and Y. But, as I said earlier, this is starting to sound like Prolog. (Not necessarily a bad thing, mind you ...)

    We are the carpenters and bricklayers of the Information Age.

    Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

    I shouldn't have to say this, but any code, unless otherwise stated, is untested