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,d8a4797a79f9c90f
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-06-02 21:16:22 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!wn12feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc02.POSTED!not-for-mail
Message-ID: <3EDC20F1.9030108@attbi.com>
From: "Robert I. Eachus" <rieachus@attbi.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: I/O - exception handling
References: <bat3ee$2ec$1@ns.felk.cvut.cz> <bauf7t$tei$1@ns.omskelecom.ru>
 <3ED4114A.5060204@spam.com> <bb1oo9$1l6q$1@ns.felk.cvut.cz>
 <slrnbd8v3n.5sv.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <vd9ukj95b439f0@corp.supernews.com>
 <slrnbde04e.ps.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <cmuo5I51JdmL@eisner.encompasserve.org>
 <slrnbdef7h.79e.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <vdfdfnmacnf8b2@corp.supernews.com> <3EDA24D2.6060003@attbi.com>
 <vdnq907pgc2rda@corp.supernews.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 24.62.164.137
X-Complaints-To: abuse@attbi.com
X-Trace: sccrnsc02 1054613776 24.62.164.137 (Tue, 03 Jun 2003 04:16:16 GMT)
NNTP-Posting-Date: Tue, 03 Jun 2003 04:16:16 GMT
Organization: AT&T Broadband
Date: Tue, 03 Jun 2003 04:16:16 GMT
Xref: archiver1.google.com comp.lang.ada:38432
Date: 2003-06-03T04:16:16+00:00
List-Id: <comp.lang.ada>

Randy Brukardt wrote:

> Of course, but the question I was answering was about Is_Open, not
> Close. I would give different advice about Close, for the reasons you
> give. But a compiler raising Use_Error on Is_Open would be pretty weird
> (and unhelpful).

If I seemed to be disagreeing with you, the fault is mine.  I certainly 
don't want to imagine a file type where Use_Error on Is_Open makes 
sense, let alone actually use such a file!  Hmmm.  That file state is 
being maintained on Triton, but this is a real time system, and I 
guarantee a response within 100 microseconds--okay Use_Error it is...