--- [EMAIL PROTECTED] wrote: > By the way, I have used the let it crash technique to seal up holes > in > already existing applications so I could trace back how bad data got > into the system via which modules and applications....
Does everyone realize that you can still log an error after you trap it? (Yes, Chris, I'm sure you know.) The basic template is TRAP ; ;do any necessary cleanup here D ^%ZTER ;log the error D UNWIND^%ZTER ;quit back to the calling level Q It's good practice to create an entry in the error log, even if you can "recover". Obviously, expected "errors" like device at EOF are an exception (pun intended). === Gregory Woodhouse <[EMAIL PROTECTED]> "All truth passes through three stages: First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." --Arthur Schopenhauer ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
