At 09:56 AM 9/24/2001 -0400, Uri Guttman wrote:
> >>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
>
> >> do we always emit one in
> >> loops?
>
> DS> At least one per statement, probably more for things like regexes.
>
> >> what about complex conditional code? i don't think there is an
> >> easy way to guarantee events are checked with inserted op codes. doing
> >> it in the op loop is better for this.
>
> DS> I'd agree in some cases, but I don't think it'll be a big problem
> DS> to get things emitted properly. (It's funny we're arguing exactly
> DS> opposite positions than we had not too long ago... :)
>
>true!
Funny old world, huh? :)
>then what about a win/win? we could make the event checking style a
>compile time option.
Odds are you'll get per-op event checking if you enable debugging, since
the debugging oploop will really be a generic "check event every op" loop
that happens to have the "pending debugging event" bit permanently set.
Dunno whether we want to force this at compile time or consider some way to
set it at runtime. I'd really like to be able to switch oploops
dynamically, but I can't think of a good way to do that efficiently.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk