This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
- From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 16 Jul 2014 01:45:11 +0000
- Subject: [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
- Auto-submitted: auto-generated
- References: <bug-59513-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #24 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Manfred Schwarb from comment #22)
--- snip ---
> Jerry, concerning your cited standard:
> "If the file contains an endfile record" suggests that there is some
> special marker in the file to be read/written.
> In this example, we are doing some formatted IO to a plain text file,
> there are no special markers.
> Do I miss something?
>
> What does/should ftell() report in such a case? That we are one
> character beyond EOF?
I think Dominique has answered as far as the physical aspect.
FTELL just returns the current physical location.