At 04:28 PM 10/12/2001 -0400, Gregor N. Purdy wrote:
>Michael --
>
> > I'm of the opinion that you shouldn't just be able to jump into
> > another code-segment.
>
>I agree.
That's fine. I don't. :)
>Since in the future, different chunks of code could be
>compiled with different oplibs, the opfunc and opinfo lookups
>will have to move to be close to the bytecode stream, not part
>of the interpreter proper (although the interpreter may cache
>them to save indirections).
Right, so? All that means is we need an opcode to set the current opfunc
table. We need that *anyway*, since every scope we enter can potentially
change the opfunc table.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
