2008/2/17, Han-Wen Nienhuys <[EMAIL PROTECTED]>: > Isn't it be possible to catch SIGSEGV, and check whether it was > caused by overflow?
Couldn't that leave the interpreter in a strange state so that one would need to quit and restart? The current scheme allows the interpreter to continue to run after error.
