http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59727
--- Comment #6 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- (In reply to Marian Szebenyi from comment #5) > (In reply to Jerry DeLisle from comment #4) > > Seems to me that once the 4 items requested in the read statement have been > satisfied, i.e. 4 properly-delimited items have been found, what is in the > rest of the string should be irrelevant. With this interpretation, the > original code is perfectly valid. > This is why we need to check the standard. Normally when reading from a line, you move to the end of the line after the last valid value to prepare for the next read. This is a requirement for file I/O. In your case, the end of the record is not at at the end of the 20 bytes of substring that you give to the read statement. READ (LINE(1:20),*) I1,R1,R2,I2 is more correct in that it does not pass undefined content to the READ. I am not saying you are wrong, I am just saying that the string expression LINE in its entirety as specified would be classified by the Fortran standards as undefined since it has not been fully initialized. Therefore, by the Standard, it is invalid code. However, this does not mean we would not want to accept it as an extension and do something differently. Usually in cases like this, we dialog a bit about it in bugzilla here or on the gfortran list and we will also see what other compilers do with this case and then we will decide what to do.
