At 01:30 PM 10/12/2001 -0400, Michael Maraist wrote:
>I'm of the opinion that you shouldn't just be able to jump into
>another code-segment.
[Snip]
>And thus be prevented from changing context; That would be relegated
>to a subroutine invocation (especially since such subroutines can be
>dynamically modified).
Ummm... what do you think we're using to call into subroutines? Or just do
global control-flow changes?
>The benifits of while(code[PC]) are potentially outweighed by the
>overhead of code[PC + arg_offset]. Thus I'm mostly inclined to always
>support the current "safe" method ("while(code>start && code<stop...")
The current 'safe' method's going away reasonably soon, as it's
insufficient for safety in a multi-segment program and incurs a cost for
every opcode when we really only need to have that cost incurred on
branches or jumps. It's a good safety net for development in the current
single-segment setup, but don't take it for more than that.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
