Re: OODL: Runtime Code Generation: Almost as evil as the secant

[DeRobertis]

At 11:26 AM +0100 on 12/5/99, M. Uli Kusterer wrote:
>>There are verious other scenarios simular to five that are more intricate,
>>and harder to work around. In five, Interpreter could just be told not to
>>re-use temps for other variables, though this is quite inefficient. And
>>these little messes make optimization -- something I'd eventually like to
>>add in -- a LOT harder.
>
>Anthony,
>
> couldn't we just turn off optimizations if a "do" statement is detected
>inside a handler?...

That'd take care of that one scenario, but there are a bunch more. And it
still does not handle passing the environment to the "do" handler.