This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/52251] Nonadvancing I/O and the t edit descriptor
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 15 Feb 2012 07:18:42 +0000
- Subject: [Bug fortran/52251] Nonadvancing I/O and the t edit descriptor
- Auto-submitted: auto-generated
- References: <bug-52251-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52251
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-02-15 07:18:42 UTC ---
Answer: It's a bug in gfortran and sunf95
Bob Corbett wrote:
> I filed an interpretation request on this issue in 1998. [...]
> I suspect that Oracle Solaris Studio Fortran is one of the implementations
> that you saw write "Hello" in column 1. A defect report was filed against
> Sun Fortran years ago. I had hoped to fix the problem in the 12.3 release,
> but I ran out of time because I had to work on more important bugs.
The approved interpretation request has the following, cf.
000027 "Sequential formatted I/O: position of the left tab"
at http://j3-fortran.org/doc/year/02/02-006c2.txt :
> QUESTION:
> When a file is positioned within a record at the start of sequential
> formatted I/O, where is the left tab limit (see Section 10.6.1.1)? Is it at
> the start of the record or at the point where the file was positioned at
> the start of execution of the statement?
>
> ANSWER:
> The left tab limit is the point where the file was positioned at the start
> of execution of the statement.
>
> DISCUSSION:
> This follows from the second sentence of 10.6.1.1, which states "Immediately
> prior to data transfer, the left tab limit becomes defined as the character
> position of the current record."
>
> EDITS: None.