Leopold Toetsch wrote:

Below inline attached is a proposal for vtable changes, mainly WRT method lookup.

First, a general question: under what circumstances is it OK and/or expected for the opcode C<getclass> and the VTABLE entry VTABLE_get_class to return different results?


At the moment, these return quite different results for all of the standard PMCs.

The more general observation behind this question: if Parrot is going to provide a mechanism by which a class can override get_class, then the runtime should depend on such interfaces instead of bypassing them and attempting to standardize on mechanisms.

- Sam Ruby

Reply via email to