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,88076dc693273166
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2004-01-03 14:03:38 PST
Path: 
 archiver1.google.com!news2.google.com!news.maxwell.syr.edu!elnk-pas-nf1!elnk-nf2-pas!newsfeed.earthlink.net!attbi_feed3!attbi.com!attbi_s04.POSTED!not-for-mail
From: tmoran@acm.org
Newsgroups: comp.lang.ada
Subject: Re: To raise an exception in task and handle/catch it in outer-block.
References: <D3GJb.279$Mb5.5088@news2.e.nsc.no>
X-Newsreader: Tom's custom newsreader
Message-ID: <Z_GJb.739626$Fm2.662614@attbi_s04>
NNTP-Posting-Host: 67.161.24.134
X-Complaints-To: abuse@comcast.net
X-Trace: attbi_s04 1073167417 67.161.24.134 (Sat, 03 Jan 2004 22:03:37 GMT)
NNTP-Posting-Date: Sat, 03 Jan 2004 22:03:37 GMT
Organization: Comcast Online
Date: Sat, 03 Jan 2004 22:03:38 GMT
Xref: archiver1.google.com comp.lang.ada:4084
Date: 2004-01-03T22:03:38+00:00
List-Id: <comp.lang.ada>

Personally, I would find it somewhat clearer to enclose the stuff that
may have/handle exceptions in a block of its own, rather than the task's
begin-end block.  That makes it clearer that exception handling has
nothing to do with whether the task finishes up with an "accept Stop" etc.

   task body A_Task is
   begin
     begin
       do stuff
     exception
       when others => do stuff
     end;
     accept Stop...
   end A_Task;