OpenEuphoria

Re: "safer" Euphoria

• Posted by Daniel Berstein <daber at PAIR.COM> Jul 13, 1998
• 502 views

-----Original Message-----
De: Cuny, David <David.Cuny at DSS.CA.GOV>
Para: EUPHORIA at cwisserver1.mcs.muohio.edu
<EUPHORIA at cwisserver1.mcs.muohio.edu>
Fecha: Lunes 13 de Julio de 1998 10:16 PM
Asunto: Re: "safer" Euphoria


>The exception handler could be passed a value by Euphoria, indicating if
>the error could be "recovered from". A "recoverable error" might be an
>uninitialized variable, or an out of range index.

Uninitialized variable? I suppose you'll catch this the first time you
pre-alpha-test you program David.

Out of range index is a very difficult to interpret "bug". Why did you get
an out of range error? How much data was corrupted cause of this algorithmic
error?

>The text of the dialog could be selected by the coder, and the "Ignore"
>button would be optional, (but automatically dimmed if Euphoria deemed
>that the error was "unrecoverable").

I agree that a customizable error (crash) message is very useful, Rob
understood it and added crash_message() some time ago. Better than trying to
"predict" if the error is recoverable I think it's better to have a
crash_dump(). This last resource function would do a file dump of whatever
you want to save. Then you can ask your client to send the dump... you'll
then try to recover any information if it's corrupted. You can even provide
your software for a crash_recovery functionality that read the dump and
analize what can be done with it.

Regards,
    Daniel   Berstein
    daber at pair.com