Nathan Torkington <[EMAIL PROTECTED]> writes:
>Dan Sugalski writes:
>> If the vtable stuff goes into the core perl engine (and it probably will,
>> barring performance issues), then what could happen in the
>
>I have a lot of questions. Please point me to the appropriate place
>if they are answered elsewhere.
>
>vtables are tables of C functions?
I am using them as tables of machine-code functions (compiled from C
being the obvious but not the only way to create those).
>Perl functions?
Not directly. But given a "C" API it is normally easy enough to
wrap the perl function (e.g. the FETCH/GET tie methods layered under
"magic" in perl5).
>Either? How
>would you use them to handle overloading of operators? One function
>in the vtable for every operation?
If the table is with the data yes, else if table is with the code
one function for every type.
>How does that extend to
>user-defined operators?
Badly. But it makes user-defined implementations of existing operators easy.
>
>Nat
--
Nick Ing-Simmons
