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,1901f265c928a511
X-Google-Attributes: gid103376,public
Path: 
 g2news1.google.com!news2.google.com!proxad.net!news.cs.univ-paris8.fr!newsfeed.vmunix.org!news-mue1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!cs.tu-berlin.de!uni-duisburg.de!not-for-mail
From: Georg Bauhaus <sb463ba@l1-hrz.uni-duisburg.de>
Newsgroups: comp.lang.ada
Subject: Re: new revision ada
Date: Tue, 22 Jun 2004 16:37:16 +0000 (UTC)
Organization: GMUGHDU
Message-ID: <cb9n7s$iig$1@a1-hrz.uni-duisburg.de>
References: <e057956f.0405310532.1a1fa4c8@posting.google.com>
   <Xns94FC4607FBB23pchapinsovernet@207.106.92.237>
 <40BDBBFA.2020203@noplace.com> <gn12d0pk7e6hhmhr6k87hcj4olebou5hel@4ax.com>
 <Xns950AE3710571Cjimmaureenrogers@204.127.36.1>
 <1087475285.166449@master.nyc.kbcfp.com>
 <Xns950BB3B4DBFE6jimmaureenrogers@204.127.36.1>
 <2jlepqF12qbb6U1@uni-berlin.de> <sa4r7s9hkp6.fsf_-_@snoopy.apana.org.au>
 <cb927q$332$1@a1-hrz.uni-duisburg.de>
 <Xns951044442A0Ajimmaureenrogers@204.127.36.1>
NNTP-Posting-Host: l1-hrz.uni-duisburg.de
X-Trace: a1-hrz.uni-duisburg.de 1087922236 19024 134.91.1.34 (22 Jun 2004
 16:37:16 GMT)
X-Complaints-To: usenet@news.uni-duisburg.de
NNTP-Posting-Date: Tue, 22 Jun 2004 16:37:16 +0000 (UTC)
User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (HP-UX/B.11.00
 (9000/800))
Xref: g2news1.google.com comp.lang.ada:1788
Date: 2004-06-22T16:37:16+00:00
List-Id: <comp.lang.ada>

James Rogers <jimmaureenrogers@att.net> wrote:
 
: Your solution detaches the information from the notification.
: This detachment causes problems, which are compounded by
: concurrency. If two exceptions are raised in a program and
: their state information is stored in some buffer such as
: a protected object, how will a handler determine which state
: belongs to which exception occurrence?

The handler might create a unique id from a protecte counting
object, the task ID as Martin has said, and the exception ID
and pass this unique id as exception message.
The message will then become the lookup key in a map.

You could for example store XML in the map.

I'm not thinking of this as a general replacement for exception
handling, because it does incur a number of things that might go
wrong.
That is, I'd keep exception handling a local mechanism 
and write code for more elaborate gotos. :-)


Georg