>
>As a last sort of alternative. I had invisioned PMC's has having separate
>vtables for each of the many different types of operations. Meaning, that
a
>scalar-int would be separate from a scalar-string-num, etc. Since it seems
>that we're not currently doing this, it would require 8 times as many
>vtable's, but it would prevent hardly any if-statements.
>
>>
>> I can't. :(
>>
>> /* It's more efficient to use our own caching than the PMC's cache
>> Why? Because we also need to store state on what type of thing is
>> in the cache, and this can be one of three things. (four, if you
>> include "nothing") Four things is two bits, which means two flag
>> tests instead of one. Hence, we just use the old-style IOK/NOK/POK */
>>
>> > *) Swap out vtables as the pmc internals change, rather than vectoring
>> > off flags.
>
>Ops, yeah, that's what I was trying to say above.
>
>
That's the way to go I thing, you'd just changed vtable to the appropriate
variant instead of switching on the PS_INTEGER flag.
Benoit
