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: "kloedej at knmi dot nl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Mar 2006 08:27:04 -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 #15 from kloedej at knmi dot nl 2006-03-10 08:27 -------
(In reply to comment #14)
> All I'm saying is that in this situation there seems to be no way to jump
> to some label if something goes wrong (because there is no EOR parameter
> for WRITE).
> But I agree that this is not gfortran's problem, but rather
> an inconsistency in the standard.
Dear people,
thanks a lot for the discussion following my bug-report. The situation is clear
to me now, and I agree this is not a real gfortran bug, but a problem in the
standard.
By the way, is there a way to warn/advise users to rather use the iostat
keyword in stead of the err/end keywords in these problematic situations? In
other words, is it possible for gfortran to detect potential problems like
this, and then issue a warning, in addition to stopping with a runtime error?
best regards,
Jos de Kloe.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26509