Re: Method call optimization.

[Chaim Frenkel]

>>>>> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes:

NI> So having the object carry around a (pointer to a) table to methods  
NI> has merit. But how to index that table? Computing the union of all possible
NI> method names for all possible classes and assiging each a slot in the table
NI> will yield a very large table which for any particular class will be sparse.
NI> Hence perl5's use of class's "stash" hash has where to store it.


For the "my Dog $spot" case, that's not an issue, compile time resolution.

But for the generic object. The package itself can contain an indirection
table. This would be that sparse table with the offset in the object vtbl.

We might be able to also use this table to hold debugging information.

<chaim>
-- 
Chaim Frenkel                                        Nonlinear Knowledge, Inc.
[EMAIL PROTECTED]                                               +1-718-236-0183