This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/26509] incorrect behaviour of error-handler for internal read
- From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Mar 2006 06:39:39 -0000
- Subject: [Bug fortran/26509] incorrect behaviour of error-handler for internal read
- References: <bug-26509-11277@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-03-09 06:39 -------
OK, after some discussion on comp.lang.fortran it is clear tha END and EOR are
not error conditions. They are there to allow for example, reading in a loop
until the end of a file is reached and branching out. A true error condition
would be something like a disk failure and the like.
So, if an application is anticipating hitting the End-of-File deliberately then
use the END parameter. Likewise for EOR.
The most portable method to handle things is to use IOSTAT and test for the
conditions of interest.
I think the right thing to do is close this as not-a-bug.
--
jvdelisle at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26509