From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,699cc914522aa7c4 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit From: Brian May Newsgroups: comp.lang.ada Subject: Re: Structured exception information References: Date: Mon, 29 Jan 2007 12:30:48 +1100 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.19 (linux) Cancel-Lock: sha1:YhXJm9eXXLkXfeRA2mrj3TKtupA= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: snoopy.microcomaustralia.com.au X-Trace: quokka.wn.com.au 1170034227 202.173.153.89 (29 Jan 2007 10:30:27 +0800) X-Complaints-To: abuse@westnet.com.au Path: g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newscon02.news.prodigy.net!prodigy.net!news.glorb.com!quokka.wn.com.au!not-for-mail Xref: g2news2.google.com comp.lang.ada:8671 Date: 2007-01-29T12:30:48+11:00 List-Id: >>>>> "Stephen" == Stephen Leake writes: Stephen> Why do you want to? Generally, all you can do is report Stephen> the error to the user. Sorry, found this thread late. It depends on the situation. Reporting the error is just one possible action. There are others: * log the error. * display error on console. * retry the operation. * do something else instead. * ignore the error. * panic. The more structured information the exception handler gets, it more help it gets in deciding the proper course of action. If it was a procedure that caused an exception, it might be able to store some of this information for later retrieval, but if it was a function that caused the exception, this may be harder. Unfortunately, I cannot think of an example that isn't seriously brain dead right now. -- Brian May