[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-12-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-12-05 06:36 --- No comments for a while, closing as won't fix. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-04-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-04-29 03:38 --- Notice what gfortran does with this modified from the original test case: read(str,'(i1)') a ./a.out 0 Here we properly pad as expected. Now, the subtlety here is: should we provide positioning

[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-04-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-04-29 04:06 --- Also, we need to consider taking F2003 9.10 at face value. Notice the use of the word attempt: An end-of-file condition occurs in the following cases: (1) When an endfile record is encountered during the

[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-04-27 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2009-04-27 11:58 --- Regarding the reading of '(x5,i1)' from a too short string: I asked at c.l.f, see http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/bbe85b69b188f999 (My ceterum censeo:) Regarding the vendor

[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-04-27 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2009-04-27 17:33 --- Dick Hendrickson answered (see link above): 'It's scattered around, but the PAD= is the thing you want. In internal I/O it says it acts as if there were an OPEN without a PAD= specifier. In the OPEN section it

[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-04-14 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2009-04-14 08:09 --- I think gfortran has this right. This is an attempt to read from an internal unit of length zero. Try the same operation from a zero length file. I'm not sure whether gfortran is right, but my program from

[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-04-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-04-15 02:16 --- Without trying it. Your example is not a zero length file. You have written at least a LF or CR-LF. I am not convinced yet. I just want to know the basis. Is this standard conforming or is it an extension?

[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-04-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-04-11 15:46 --- I think gfortran has this right. This is an attempt to read from an internal unit of length zero. Try the same operation from a zero length file. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39587

[Bug fortran/39587] Reading integer from gives end-of-file instead of reading a 0

2009-03-30 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2009-03-30 20:31 --- Steve Lionel thinks that compilers accepting for .false. are standard conforming as they are not required to diagnose this. Thus, I would like to see this extension in gfortran as well ;-) --