Dan Sugalski <[EMAIL PROTECTED]> wrote:
> This needs some docs, but I figured I'd throw out the short
> description to the list since they've come up, and we ought to finish
> them.
$ cat does.pasm
new P0, .Array
does I0, P0, "array"
print I0
does I0, P0, "scalar"
print I0
At 10:55 AM -0400 8/17/04, Gay, Jerry wrote:
> since presumably interfaces are a bit more uniquely named than
methods, and an object may be able to do something some class does
while not actually being in that class.
should interface names be registered somewhere?
Nope.
how are collisions handle
> since presumably interfaces are a bit more uniquely named than
> methods, and an object may be able to do something some class does
> while not actually being in that class.
>
should interface names be registered somewhere?
how are collisions handled?
i can imagine a scenario where multiple
This needs some docs, but I figured I'd throw out the short
description to the list since they've come up, and we ought to finish
them.
For parrot, interfaces are *very* simple things. An interface is a
string tag which can be attached to a class. Each class can have
multiple interface tags at
