At 05:02 PM 2/3/2001 +0100, Edwin Steiner wrote:
>Might this be madness? (BRAINSTORMS AHEAD!):
Generally, yes. :)
The vtable stuff won't be exposed outside the core. This means embedding
programs and extensions will *not* be using it. Generally speaking, it'll
be opcode functions only that'll be hitting the vtables.
While I'm not hugely averse to some macro-ization, I don't think this is a
spot worth that much mental effort, at least not for individual vtable
calls, which will probably be looking like:
PMC->vtable[ADD][UTF_32](DEST, PMC1, PMC2);
Also, as a sort of side thing, don't expect the vtables for each type to be
all that different, if at all. Conceptually I'm not sure it's worth trying
to segregate them out to scalar, hash, array, and list vtable types. (Plus
we get a minor benefit in that if they all have an identical set of vtable
slots things won't go bang really badly if an incorrect PMC slps in somewhere)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
