Re: exception handler
- Posted by Terry Constant <EUforum at terryconstant.com> Aug 24, 2004
- 446 views
Craig wrote: "your routine(s) will be called after the normal ex.err dump occurs, so I guess your routine(s) could look at ex.err in deciding what to do. If a second ex.err is necessary while running your routines, I'll use a different file name, like ex2.err or something. If your routine(s) themselves crash, there won't be any more calls to crash routines. That's the end." Parnell wrote: "Usable. But a formal EU-defined error data passed to the routine would be more useful - detailing reason for crash, file name, line number, calling stack trace(?)." Rob, I am glad to see that you are implementing improved exception handling. I will be happy to get most anything you provide (even while I have my personal preferences.) So, let me make just two comments. 1. As to filename "ex2.err", use something more mnemonic such as: except.err cleanup.err exclean.err exuser.err or whatever mnemonic you choose. 2. I agree with Parnell about the utility of detailed error data being passed to the routine. In addition to Parnell's suggestions, I would like to receive the routine name also, using something like "global", "local" or "top" or whatever is best for statements not inside defined routines. Terry Constant