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.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,699cc914522aa7c4
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news3.google.com!news.glorb.com!proxad.net!proxad.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Structured exception information
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: <eog0g5$2bn$1@cernne03.cern.ch> <u7ivnp09z.fsf@stephe-leake.org>
 <eoinoh$855$1@cernne03.cern.ch> <ud55drgzz.fsf@stephe-leake.org>
 <eolaen$b4h$1@cernne03.cern.ch> <ur6trwdov.fsf@stephe-leake.org>
 <wccd55alqzu.fsf@shell01.TheWorld.com> <u1wlpy8q7.fsf@stephe-leake.org>
 <wcc64b1jqsp.fsf@shell01.TheWorld.com>
 <fqw8vg9tbju.142raphcqkjrq.dlg@40tude.net>
 <wccmz4cszut.fsf@shell01.TheWorld.com>
Date: Mon, 22 Jan 2007 15:39:53 +0100
Message-ID: <19m5bhhcnh423$.dlvfewj3onxc.dlg@40tude.net>
NNTP-Posting-Date: 22 Jan 2007 15:39:52 CET
NNTP-Posting-Host: d52e8a15.newsspool2.arcor-online.net
X-Trace: 
 DXC=9PfTW3009J:kUFX=Y?aLP;A9EHlD;3Yc24Fo<]lROoR1Fl8W>\BH3Y2hk23ATak289DNcfSJ;bb[5FCTGGVUmh?4LK[5LiR>kg28>YjUb80EO<
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:8401
Date: 2007-01-22T15:39:52+01:00
List-Id: <comp.lang.ada>

On Sun, 21 Jan 2007 18:51:22 -0500, Robert A Duff wrote:

> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
> 
>> On Sat, 20 Jan 2007 17:07:18 -0500, Robert A Duff wrote:
>>
>>> The truth is, the interactions between exceptions and finalization are
>>> nasty, and hard to get right.
>>
>> Yes. I wondering, isn't it the *same* problem as with Storage_Error?
> 
> Please remind me which Storage_Error problem we're talking about.
>
> There are language problems with Storage_Error (you can't know what data
> was half-baked at the point of running out of memory).  But perhaps
> you're referring to something else?

It was about handling S_E. If I remember correctly it was a thread a year
or so ago, in which you started to talk about some alternative, about how
it could/should be done, but then stopped yourself with usual mantra "that
would not be Ada." (:-))

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de