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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,820de86ed0dafb8a X-Google-Attributes: gid103376,public From: "Jean-Pierre Rosen" Subject: Re: Help Me Please :) Date: 2000/03/31 Message-ID: <8c20ps$995$1@wanadoo.fr>#1/1 X-Deja-AN: 604741910 References: <89rlvr$gn9$1@nntp3.atl.mindspring.net> <38D8A607.F61F0FFF@mail.com> <8brm79$jm3$1@slb6.atl.mindspring.net> <8brs96$ikp$1@nnrp1.deja.com> <8c139a$onc$1@nntp9.atl.mindspring.net> X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Complaints-To: abuse@wanadoo.fr X-Trace: wanadoo.fr 954500732 9509 193.250.43.158 (31 Mar 2000 11:05:32 GMT) Organization: Adalog X-MSMail-Priority: Normal NNTP-Posting-Date: 31 Mar 2000 11:05:32 GMT Newsgroups: comp.lang.ada Date: 2000-03-31T11:05:32+00:00 List-Id: [long discussions about the value of parameterized exceptions snipped] My 2 Euro-cents: Exceptions are a programming tool, not a high level error-handling mechanism. In any project, you must define a policy for handling errors. Exceptions are a powerful tool for unwinding the call stack, and without them, there are many error handling policies that you could not define. They do NOT free you from defining the policy for a project! If you need to store more information when an error occurs, call some Error procedure, and define it the way you like; there you can store the context in a global variable, or if you need to make it tasking safe, in a task attribute. For those who can read french, there is a chapter in my book detailing these issues (shameless plug: http://pro.wanadoo.fr/adalog/livrejpr.htm). -- --------------------------------------------------------- J-P. Rosen (Rosen.Adalog@wanadoo.fr) Visit Adalog's web site at http://pro.wanadoo.fr/adalog