public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38439] I/O PD edit descriptor inconsistency
Date: Thu, 23 Apr 2009 01:52:00 -0000 [thread overview]
Message-ID: <20090423015148.24833.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38439-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-04-23 01:51 -------
Getting back to this. We have a problem of choices here. In format statements
such as:
WRITE (*,'(1PD24.15E4)') 1.0d0
Currently gfortran allows an extension of an optional comma separating format
specifiers. This results in the format string above being seen as:
'(1PD24.15,E4)'
The error message given in the original post is from the missing period after
the E4.
We could choose to allow the optional comma only with -std=legacy and then
these misleading situations would not occur. I am leaning in favour of this
more restrictive approach. Any opinions?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38439
next prev parent reply other threads:[~2009-04-23 1:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 21:35 [Bug fortran/38439] New: " burnus at gcc dot gnu dot org
2008-12-08 0:53 ` [Bug fortran/38439] " jvdelisle at gcc dot gnu dot org
2008-12-25 19:47 ` jvdelisle at gcc dot gnu dot org
2009-01-21 6:51 ` jvdelisle at gcc dot gnu dot org
2009-01-22 3:05 ` jvdelisle at gcc dot gnu dot org
2009-01-22 10:55 ` burnus at gcc dot gnu dot org
2009-01-23 5:46 ` jvdelisle at gcc dot gnu dot org
2009-01-24 18:11 ` jvdelisle at gcc dot gnu dot org
2009-04-23 1:52 ` jvdelisle at gcc dot gnu dot org [this message]
2009-04-23 2:53 ` kargl at gcc dot gnu dot org
2009-10-11 17:38 ` jvdelisle at gcc dot gnu dot org
2009-10-11 17:41 ` jvdelisle at gcc dot gnu dot org
2009-10-11 19:20 ` jvdelisle at gcc dot gnu dot org
2009-10-12 0:53 ` jvdelisle at gcc dot gnu dot org
2009-10-12 0:54 ` jvdelisle at gcc dot gnu dot org
2009-10-12 7:39 ` dominiq at lps dot ens dot fr
2009-10-12 12:42 ` jvdelisle at gcc dot gnu dot org
2009-10-12 13:32 ` dominiq at lps dot ens dot fr
2009-10-12 13:42 ` 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=20090423015148.24833.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).