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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,1a4156f047b063f X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!postnews.google.com!o21g2000prh.googlegroups.com!not-for-mail From: Shark8 Newsgroups: comp.lang.ada Subject: Re: Forcing Exception Handling Date: Tue, 1 Mar 2011 07:23:56 -0800 (PST) Organization: http://groups.google.com Message-ID: References: <02901b13-da72-48ae-9cb3-bf1a10144c44@u3g2000vbe.googlegroups.com> <4d6c07c1$0$6885$9b4e6d93@newsspool2.arcor-online.net> <195bsgigtzacu$.13u18z09ptrtw$.dlg@40tude.net> NNTP-Posting-Host: 174.28.181.54 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1298993036 21597 127.0.0.1 (1 Mar 2011 15:23:56 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 1 Mar 2011 15:23:56 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: o21g2000prh.googlegroups.com; posting-host=174.28.181.54; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729; .NET4.0E),gzip(gfe) Xref: g2news2.google.com comp.lang.ada:18656 Date: 2011-03-01T07:23:56-08:00 List-Id: On Mar 1, 1:56=A0am, "Dmitry A. Kazakov" wrote: > > Also consider this: > > =A0 =A0declare > =A0 =A0 =A0 Foo : exception: > =A0 =A0begin > =A0 =A0 =A0 ... > =A0 =A0 =A0 raise Foo; > =A0 =A0end; =A0-- Foo propagates out its scope!! > What's wrong with handling it with OTHERS? > A possibility to handle this is exception promotion, e.g. Foo to > Program_Error, when Foo gets finalized. A third is to convert Exceptions to a hierarchy as stated in my last post. I'm not sure that's a Good Thing, but I think it's actually better than type extension; which I thought would be nice earlier... but the more I think on the problem the more it seems it would be utterly burdensome for implementors as well as possibly impossible-to-get-right.