..)
which returns the offset of the attribute location relative to the
object. This offset can be cached in the PIC, which gives instant access
to the attribute from the opcode run loop.
Comments?
leo
Proposed vtable changes WRT method lookup
1) rename vtable->data to vtable->class
All current
Matt Fowles <[EMAIL PROTECTED]> wrote:
> Leo~
> On Tue, 18 Jan 2005 16:52:52 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>> That was Cdispatch> in the proposal. C is just
>> called to query one object or class, if it can do the method. Finding
>> the final (MMD) function is done separately
Leo~
On Tue, 18 Jan 2005 16:52:52 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Matt Fowles <[EMAIL PROTECTED]> wrote:
>
> > ... If we add to it support. MMD, however, is where things begin
> > to differ. Instead of havng the find_method with the extra mmd_nr, we
> > could have a MMD_Re
Matt Fowles <[EMAIL PROTECTED]> wrote:
> ... If we add to it support. MMD, however, is where things begin
> to differ. Instead of havng the find_method with the extra mmd_nr, we
> could have a MMD_Resolution PMC which would then get the mro from each
> class, and figure out which method to call
All~
On Tue, 18 Jan 2005 10:18:52 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Sam Ruby <[EMAIL PROTECTED]> wrote:
> > Leopold Toetsch wrote:
>
> >> Below inline attached is a proposal for vtable changes, mainly WRT
> >> method lookup.
>
> > First, a general question: under what circumsta
Sam Ruby <[EMAIL PROTECTED]> wrote:
> 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 and the VTABLE entry
> VTABLE_get_class to return
Dave Whipp <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch wrote:
>> 1) rename vtable->data to vtable->class
>>
>> All current usage of the 'void *data' vtable element is as the object's
>> class. So it should read "PMC *class".
> Its a minor thing, but I would try to avoid using identifiers that ar
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 and the VTABLE entry
VTABLE_get_class to return different results?
At the moment, these return q
Leopold Toetsch wrote:
1) rename vtable->data to vtable->class
All current usage of the 'void *data' vtable element is as the object's
class. So it should read "PMC *class".
Its a minor thing, but I would try to avoid using identifiers that are
keywords in C++: especially in header files. The fact
Below inline attached is a proposal for vtable changes, mainly WRT
method lookup.
Comments welcome,
leo
Proposed vtable changes WRT method lookup
1) rename vtable->data to vtable->class
All current usage of the 'void *data' vtable element is as the object's
class. So it sh
10 matches
Mail list logo
