Re: v2.5 suggestions
- Posted by Robert Craig <rds at RapidEuphoria.com> Nov 22, 2004
- 532 views
Andy Serpa wrote: > How about a specific constant we can use with abort() that will trigger the > crash routines? > abort(1/0) will work, I suppose, but abort(FATAL_ERROR) might be more > elegant. Also, > a way to reset or re-order multiple crash routines would probably come in > handy. Thanks for the suggestion. When I get more feedback from several people, I'll see what improvements can be made. I've used crash_routine() myself to e-mail ex.err's and other debug info from remote CGI programs. A translated program that dies, normally just reports a machine-level exeception, with no traceback or variable dump, but with crash_routine() it can output useful debug info before dying. There are probably many other useful things you can do. > And let's get routine_id()'s for the built-in functions for the final v2.5 > already. > This can't possibly be a very big deal at all... I know, it sounds simple, but there are some complications. I'll look at it again. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com