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:13:55 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!uio.no!ntnu.no!not-for-mail From: Preben Randhol Newsgroups: comp.lang.ada Subject: Re: I/O - exception handling Date: Fri, 30 May 2003 11:13:54 +0000 (UTC) Organization: Norwegian university of science and technology Message-ID: References: <3ED4114A.5060204@spam.com> NNTP-Posting-Host: kiuk0152.chembio.ntnu.no X-Trace: tyfon.itea.ntnu.no 1054293234 24402 129.241.83.78 (30 May 2003 11:13:54 GMT) X-Complaints-To: usenet@itea.ntnu.no NNTP-Posting-Date: Fri, 30 May 2003 11:13:54 +0000 (UTC) User-Agent: slrn/0.9.7.4 (Linux) Xref: archiver1.google.com comp.lang.ada:38076 Date: 2003-05-30T11:13:54+00:00 List-Id: Larry Kilgallen wrote: > In article , Preben Randhol 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? -- Preben Randhol http://www.pvv.org/~randhol/