Re: I/O - exception handling

[Preben Randhol <randhol+abuse@pvv.org>]

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?

-- 
Preben Randhol                    http://www.pvv.org/~randhol/