OpenEuphoria

Crash routine

• Posted by Michael Sabal <mikes at notations.com> Mar 19, 2001
• 445 views

I've been on this bandwagon a few times before; but I want to address some =
of the issues Rob brought up.

Reasons why a crash routine recovery system is better than a crash =
message:

1) I can display my message in any format I'd like:  message box, popup =
graphics, help window, *NO CONSOLES*.

2) Say I have a 10 module program, each using different sets of data which =
are opened upon module entry and closed upon module exit.  If there is a =
subscripting but in module 4 that causes a crash, I can still safely use =
the other 9 modules.  But not if the program bombs out completely.  A =
really good modular crash routine will display a pop-up error message, =
write a crash-analysis file to disk, disable the menu option that =
activates the module, close all files and controls associated with the =
module, and return control to the main menu.  Maybe it could even email =
the crash file to an admin user who can fix the error at the same time the =
user is working in another module (since program code is stored in memory =
during execution). =20

Rob, please don't write this feature off too quickly.  Added stability has =
never hurt a bottom line!

Michael J. Sabal