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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1e4bb63e08046e1a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-10-24 14:22:42 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!news-out.cwix.com!newsfeed.cwix.com!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: is exception when others => null; smart? Date: 24 Oct 2002 16:22:40 -0500 Organization: LJK Software Message-ID: References: <3DB8204B.2080804@attbi.com> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1035494487 16608 192.135.80.34 (24 Oct 2002 21:21:27 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Thu, 24 Oct 2002 21:21:27 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:30114 Date: 2002-10-24T16:22:40-05:00 List-Id: In article , Simon Wright writes: > Mark Biggar writes: > >> Probably not. If you want the opposite policy change it to: >> >> when others => raise; >> >> BTW, make it an optional feature which way you want it. > > If you do make it optional, the options should be > > * have "when others => raise;". > > * have no handler at all. The important difference between these options, I presume, would be whether or not you are being paid by the line of code written :-)