Dan Sugalski <[EMAIL PROTECTED]> wrote:
> The full explanation is:
> can - checks to see if an object can perform a specific, single
> method. (A parent class may provide them)
> isa - checks to see if the named class is in the inheritance
> hierarchy for the object
> does - checks to see if the object implements the named collection of
> methods. (Often, but not always, called an interface)
Thanks for the thorough description.
So the question arises, if and how we implement these vtables for all
classes/*.pmc. Do we want to have the methods too? Or should C<can> check
a bitfield, if the PMC can do that corresponding vtable.
WRT Cdoes>: This could be one more flag in the pmc definition:
pmclass PerlArray extends Array need_ext does array {
Any proposals for interface names:
array
hash
scalar
sub (invocable)
struct
...
leo
