public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "terry at chem dot gu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43265] [4.3/4.4/4.5 Regression] No EOF condition if reading with '(x)' from an empty file
Date: Sat, 06 Mar 2010 03:37:00 -0000 [thread overview]
Message-ID: <20100306033652.20973.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43265-14178@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from terry at chem dot gu dot se 2010-03-06 03:36 -------
Subject: Re: [4.3/4.4/4.5 Regression] No EOF condition
if reading with '(x)' from an empty file
> Also the F95 standard says in 10.6.1:
>
> "The position specified by an X edit descriptor is forward from the
> current
> position. On input, a position beyond the last character of the record may
> be
> specified if no characters are transmitted from such positions."
>
> This to me means there is no END condition if there is no transfer after
> the X.
> I am wondering of this should be an extension, give the END condition with
> -std=gnu and not with -std=f95? Also, perhaps we should discuss on c.l.f.
Should I interpret that as being that the code I presented currently
behaves in a way consistent with the F95 standard? (Any differences here
with the F90 or F77 standards?)
It seems that's a critical question, irrespective of any principle of
least surprise.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43265
next prev parent reply other threads:[~2010-03-06 3:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 6:05 [Bug fortran/43265] New: Read no longer jumps on end terry at chem dot gu dot se
2010-03-05 9:08 ` [Bug fortran/43265] [4.3/4.4/4.5 Regression] No EOF condition if reading with '(x)' from an empty file burnus at gcc dot gnu dot org
2010-03-05 17:02 ` hjl dot tools at gmail dot com
2010-03-05 18:08 ` burnus at gcc dot gnu dot org
2010-03-05 23:07 ` jvdelisle at gcc dot gnu dot org
2010-03-06 1:08 ` jvdelisle at gcc dot gnu dot org
2010-03-06 3:32 ` jvdelisle at gcc dot gnu dot org
2010-03-06 3:37 ` terry at chem dot gu dot se [this message]
2010-03-06 3:54 ` jvdelisle at gcc dot gnu dot org
2010-03-06 5:30 ` jvdelisle at gcc dot gnu dot org
2010-03-06 9:49 ` burnus at gcc dot gnu dot org
2010-03-08 20:20 ` jvdelisle at gcc dot gnu dot org
2010-03-09 14:41 ` jvdelisle at gcc dot gnu dot org
2010-03-09 15:36 ` burnus at gcc dot gnu dot org
2010-03-09 20:14 ` jvdelisle at gcc dot gnu dot org
2010-03-10 12:42 ` burnus at gcc dot gnu dot org
2010-03-10 16:27 ` rguenth at gcc dot gnu dot org
2010-03-11 2:27 ` jvdelisle at gcc dot gnu dot org
2010-03-12 14:33 ` jvdelisle at gcc dot gnu dot org
2010-03-12 14:36 ` jvdelisle at gcc dot gnu dot org
2010-03-18 2:38 ` jvdelisle at gcc dot gnu dot org
2010-03-18 2:43 ` jvdelisle at gcc dot gnu dot org
2010-03-18 2:52 ` jvdelisle at gcc dot gnu dot org
2010-03-18 2:54 ` jvdelisle at gcc dot gnu dot org
2010-03-18 3:52 ` jvdelisle at gcc dot gnu dot org
2010-03-18 3:56 ` jvdelisle at gcc dot gnu dot org
2010-03-18 3:58 ` jvdelisle at gcc dot gnu dot org
2010-03-29 2:50 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:22 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:25 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:54 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:56 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:57 ` jvdelisle at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100306033652.20973.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).