Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!seaman.cc.purdue.edu!ags
From: ags@seaman.cc.purdue.edu (Dave Seaman)
Newsgroups: comp.lang.fortran
Subject: Re: bug in IRIS f77 list-directed i/o
Message-ID: <10547@mentor.cc.purdue.edu>
Date: 16 Apr 91 18:14:29 GMT
References: <1600002@acf3.NYU.EDU> <4918@dftsrv.gsfc.nasa.gov>
Sender: news@mentor.cc.purdue.edu
Reply-To: ags@seaman.cc.purdue.edu (Dave Seaman)
Organization: Purdue University
Lines: 28

In article <4918@dftsrv.gsfc.nasa.gov> jim@jagubox.gsfc.nasa.gov (Jim Jagielski) writes:

>Yes, it makes more sense. However, the standard says nothing about "errors"
>in list directed input. So whatever the compiler does basically is fine.

When discussing I/O errors, the standard makes no distinction between list
directed I/O and any other kind.  The statement is simply:

--------------------------------------------------------------------------

12.6 _Error_and_End-of-File_Conditions_

	The set of input/output error conditions is processor dependent.

	[Discussion of end-of-file conditions deleted.]

	[Discussion of processor response to error or end-of-file conditions
	deleted.]

--------------------------------------------------------------------------

Therefore, a standard-conforming processor need not recognize any I/O error
conditions at all.  If any such conditions are defined, they must be handled in
a standard way.

--
Dave Seaman
ags@seaman.cc.purdue.edu