In a message dated Sun, 1 Oct 2006, Aaron Sherman writes:
Trey Harris wrote:
In a message dated Fri, 29 Sep 2006, Aaron Sherman writes:
[snip]
However, that's not to say that a class can't be abstract, just that a
class that does an interface (a role with nothing but abstract methods)
must
Trey Harris wrote:
It sounds like the assumption thus far has been that the existance of
roles imply that abstract classes are disallowed, so you'd write:
role Dog { method bark { ... } #[ ... ] }
class Pug does Dog { method bark { .vocalize($.barkNoise) } }
S12 says: Classes are
In a message dated Wed, 4 Oct 2006, Jonathan Lang writes:
In Perl 6, the abstract SystemMonitor could be a role, and a concrete
ScriptedMonitor could be a class that does SystemMonitor, but it's not at
all clear to me what HardwareMonitor would be, since classes can't be
abstract and roles can't
Trey Harris wrote:
In a message dated Fri, 29 Sep 2006, Aaron Sherman writes:
That said, this is a different point, above and I think it's an easy
one to take on.
role A { method x() {...} }
class B { does A; }
does generate an error per If a role merely declares methods without
defining
