------- Comment #3 from burnus at gcc dot gnu dot org 2006-11-28 22:58 -------
(In reply to comment #2)
> > The read should read "1" of the first record and then "2" and "3" of the
> > second record.
> I don't think so.
You are of cause right. I should have really read
> F 2003, 9.5.3.4.1 (Unformatted data transfer):
more carefully (I did twice and missed that part). The bug is really that if
one reads too much data END= and not ERR= is triggered.
A quick test with ifort shows that it outputs the message "input statement
requires too much data" if one removes ERR=.
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail|4.2.0 4.3.0 |4.1.0 4.2.0 4.3.0
Summary|Unformatted reads exceeding |Unformatted reads exceeding
|one record should use the |storage units gives EOF
|next record not give EOF |instead of ERR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30009
