On Mon, 24 Sep 2001, Uri Guttman wrote:
> >> then what about a win/win? we could make the event checking style a
> >> compile time option.
>
> DS> Odds are you'll get per-op event checking if you enable debugging,
> DS> since the debugging oploop will really be a generic "check event
> DS> every op" loop that happens to have the "pending debugging event"
> DS> bit permanently set. Dunno whether we want to force this at
> DS> compile time or consider some way to set it at runtime. I'd really
> DS> like to be able to switch oploops dynamically, but I can't think
> DS> of a good way to do that efficiently.
>
> hmmm. what about a special op that implements another form of op loop?
> the overhead is almost nil (one op call). the called op loop can run
> forever or decide to return and then the parent op loop takes over
> again.
This type of approach could be implemented in an extension module, could
it not? Because of the current flexible design of Parrot, we don't have
to implement this type of opcode into the core any more than, say fork. Do
we?
- D
<[EMAIL PROTECTED]>
