>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? We could tell people: you can use "do", but be prepared
that your handler will decrease in overall performance and use more memory,
so try to avoid "do" at all cost. You won't get around keeping a list
linking variable names to their numbers as that'll be used in debugging.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
