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,d676a4bf883e6826
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!newsread.com!news-xfer.newsread.com!news-feed01.roc.ny.frontiernet.net!nntp.frontiernet.net!nntp.giganews.com.MISMATCH!border1.nntp.dca.giganews.com!nntp.giganews.com!local1.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 21 Feb 2005 17:59:43 -0600
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <5f59677c.0502190711.1d6d2492@posting.google.com>
 <id7cvc.igh.ln@hunter.axlog.fr> <wcchdk54lxu.fsf@shell01.TheWorld.com>
Subject: Re: task synchronization and activation
Date: Mon, 21 Feb 2005 18:01:29 -0600
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID: <g6KdnfB9ludy6IffRVn-uw@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-nudPgA4tyiMmNQ8BGW/3g6Gp53KUwkkxWytfp2rCZxtqoD+FPz16MIGGv4MBEVWC8DYYvLteyvskwM1!awZ0yR1ooU4K6zcGMUk1aLnT+T6EVQ9MG3D3HznsrPWpnZLQBXzOWLxD9xeU3lZ5I0OP/5zdbjNF
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.31
Xref: g2news1.google.com comp.lang.ada:8454
Date: 2005-02-21T18:01:29-06:00
List-Id: <comp.lang.ada>

"Robert A Duff" <bobduff@shell01.TheWorld.com> wrote in message
news:wcchdk54lxu.fsf@shell01.TheWorld.com...
...
> For another thing, what about exceptions in the exception handler part
> of a task?  Those can't be handled by the task either, so they get
> dropped on the floor -- nobody gets notified.  And in this case,
> there is no 100% reliable workaround -- you can wrap that handler
> in another block statement with another handler, but then what about
> the 'nother handler?  There's an infinite regress.  You could carefully
> inspect the outermost handler of a task, and make sure it doesn't have
> any bugs (good idea!) -- but it could still get Storage_Error.

In Ada 2005, you can use a task termination handler to detect this. But that
too isn't perfect, because it can't guarantee to work in the face of a
Storage_Error (nothing can, really, and that is the most common problem in
my experience).

                   Randy.