1. crash function
I have one thing that sometimes irritate me with Euphoria, and that is that
it "crashes" no matter what error occurs. It is fine that the errors are
trapped, but I would at least like it if there was somthing like a "crash
function" that could contain statements that had to be done before the
program crashes with the error message. This would help all of us that lose
data if there is a crash, instead now the data would be stored and THEN
there would be a crash. I guess that there will be mixed feelings about
this, but most of you should at least understand my point. Is it possible,
Robert Craig? The way I see it, it would be an extension of the
crash_message routine.
Einar Mogen
2. Re: crash function
Einar Mogen writes:
> It is fine that the errors are
> trapped, but I would at least like it if there was somthing like a "crash
> function" that could contain statements that had to be done before the
> program crashes with the error message. This would help all of us that lose
> data if there is a crash, instead now the data would be stored and THEN
> there would be a crash.
This idea has come up before. Exception handling of this sort might be nice,
but it is technically a rather tricky thing to add to the current
implementation.
However I'll add your request to my (infamous!) suggestion folder. 
Regards,
Rob Craig
Rapid Deployment Software
