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-05-30 04:39:02 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!nycmny1-snh1.gtei.net!chcgil2-snf1.gtei.net!news.gtei.net!news.binc.net!kilgallen
From: Kilgallen@SpamCop.net (Larry Kilgallen)
Newsgroups: comp.lang.ada
Subject: Re: I/O - exception handling
Date: 30 May 2003 06:39:00 -0500
Organization: LJK Software
Message-ID: <HRIVuniNObpl@eisner.encompasserve.org>
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>
NNTP-Posting-Host: eisner.encompasserve.org
X-Trace: grandcanyon.binc.net 1054294657 1932 192.135.80.34 (30 May 2003
 11:37:37 GMT)
X-Complaints-To: abuse@binc.net
NNTP-Posting-Date: Fri, 30 May 2003 11:37:37 +0000 (UTC)
Xref: archiver1.google.com comp.lang.ada:38078
Date: 2003-05-30T06:39:00-05:00
List-Id: <comp.lang.ada>

In article <slrnbdef7h.79e.randhol+abuse@kiuk0152.chembio.ntnu.no>, Preben Randhol <randhol+abuse@pvv.org> writes:
> Larry Kilgallen wrote:
>> In article <slrnbde04e.ps.randhol+abuse@kiuk0152.chembio.ntnu.no>, Preben Randhol <randhol+abuse@pvv.org> writes:
>> 
>>> I see, but why would it? I mean why would Is_Open start poking in the
>>> I/O. On Linux/Unix you don't lock files as in Windows, so you cannot
>>> tell if the file is opened or not as 10 programs may open it at the same
>>> time. Therefore I thought the implementation would be a test if the Open
>>> procedure succeded or not?
>> 
>> Certainly.
>> 
>>     1. function Is_Open(File : in File_Type) return Boolean;
>> 
>>          1. Returns True if the file is open (that is, if it is associated
>> 	    with an external file), otherwise returns False. 
>> 
>> That does not seem to have anything to do with whether other programs
>> have associated with the same external file.
> 
> No, so then why would an exception in Is_Open be expected at all? Are
> there some perculiar hardware where you need to poke into the I/O to see
> if a file was opened?

???

By "Certainly" I meant agreement.

I was not one who said an exception in Is_Open would be expected.