[snip inlining PMC vtable]
On Wed, Nov 07, 2001 at 09:49:04AM -0500, Dan Sugalski wrote: > We can't do that. PMCs, even statically typed ones, can change their > vtables as they see fit. That is true, but it does not negate the option of inlining, it simply increases the overhead required for inlining. It means you have to track where you've inlined code, and modify those places in the event of a change to the vtable, a simple relink. It is like flushing your cache after a change to the database, only the database is a vtable and the cache is the executable. Basically, one could argue that 99 out of 100 scripts will never see a vtable change during runtime. Outside of special cases, like creation of tied variables, vtable entries should be basically static. The question is should not be one of possibility, but whether inlining would give enough of a performance boost with real code to offset the overhead of having to relink/assemble a program's code when a vtable is changed.
