Why not a direct pointer to the vtbl?
And not having a defined type table, one avoids the bookkeeping
overhead of having to register each type. No need to play with
assigning type numbers (no IANA needed.)
Any object can alter its behavior to a non-defined type by simply
creating a vtbl and using it. (Garbage collection is left as an
excersize for one of Damian's students)
<chaim>
>>>>> "DLN" == David L Nicol <[EMAIL PROTECTED]> writes:
DLN> THE DEFINED TYPE TABLE:
DLN> this is where the jump tables live, rather than in the objects
DLN> themselves, so we don't have "heaviness" of C++ virtuals.
DLN> Within a perl instance, every object type must register itself on
DLN> loading. At registration, a number is assigned, the jump table
DLN> of common functions that that object type overloads is filled, and also
DLN> a pointer to the association for uncommon methods of the object type
DLN> is filled. So the defined type table is an array of constant-sized
DLN> items.
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
