Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!mailrus!uflorida!ufqtp!bernhold
From: bernhold@qtp.ufl.edu (David E. Bernholdt)
Newsgroups: comp.lang.fortran
Subject: Re: Using END= and ERR= in READs
Message-ID: <448@orange19.qtp.ufl.edu>
Date: 1 Mar 89 18:39:47 GMT
References: <436@orange19.qtp.ufl.edu> <14166@admin.mips.COM>
Reply-To: bernhold@orange19 (David E. Bernholdt)
Organization: University of Florida Quantum Theory Project
Lines: 24

In article <14166@admin.mips.COM> rogerk@mips.COM (Roger B.A. Klorese) writes:
>In article <436@orange19.qtp.ufl.edu> bernhold@qtp.ufl.edu (David E. Bernholdt) writes:
>>Logic tells me that an
>>end-of-file condition should be handled by an ERR= iff no END= is
>>present.
>
>No, your experience with VMS FORTRAN tells you this.  End-of-file is not
>considered an error in FORTRAN 77, but an expectable condition; it is not
>necessarily subject to handling via ERR=.

Actually, VMS FORTRAN has nothing to do with it.  Can you show me a
FORTRAN compiler that does NOT produce and ERROR message on an
end-of-file if it is not trapped?  I haven't yet seen one.

I understand what the standard says about EOF and error conditions.  I
also understand how to use IOSTAT.  The point I was trying to make
when I asked the question is why does and EOF have to be trapped
separately in all cases, when as far as the computer is concerned one
is just as much an error as the other?
-- 
David Bernholdt			bernhold@qtp.ufl.edu
Quantum Theory Project		bernhold@ufpine.bitnet
University of Florida
Gainesville, FL  32611		904/392 6365