public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thfanning at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64506] New: FORMAT Parse Error with Continuation Line
Date: Tue, 06 Jan 2015 05:59:00 -0000 [thread overview]
Message-ID: <bug-64506-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64506
Bug ID: 64506
Summary: FORMAT Parse Error with Continuation Line
Product: gcc
Version: 4.9.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: thfanning at gmail dot com
Created attachment 34385
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34385&action=edit
Sample program to illustrate parse error.
In a FORMAT statement, a character literal immediately followed by a
continuation character (&) and then a comment character (!) results in a parse
error. A simple program is attached that implements the following statements:
100 format('This format is OK.'&
)
200 format('This format fails.'&!comment
)
300 format('This format fails.'& !comment
)
400 format('This format is OK.' &!comment
)
500 format('This format is OK.' & !comment
)
Compiling this results in the following:
200 format('This format fails.'&!comment
1
Error: Unexpected element '&' in format string at (1)
gfortran_parse_error.f90:13.32:
300 format('This format fails.'& !comment
1
Error: Unexpected element '&' in format string at (1)
next reply other threads:[~2015-01-06 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 5:59 thfanning at gmail dot com [this message]
2015-01-09 10:30 ` [Bug fortran/64506] " dominiq at lps dot ens.fr
2015-02-01 20:42 ` burnus at gcc dot gnu.org
2015-02-13 16:58 ` jvdelisle at gcc dot gnu.org
2015-02-13 17:09 ` jvdelisle at gcc dot gnu.org
2015-02-17 20:13 ` jvdelisle at gcc dot gnu.org
2015-03-01 2:29 ` jvdelisle at gcc dot gnu.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=bug-64506-4@http.gcc.gnu.org/bugzilla/ \
--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).