public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56520] Syntax error causes misleading message: "Invalid character in name"
Date: Tue, 07 Jul 2015 18:30:00 -0000 [thread overview]
Message-ID: <bug-56520-4-A5qm1lq7ZB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56520-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56520
--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Jul 07, 2015 at 05:23:17PM +0000, casey.webster at gmail dot com wrote:
>
> Also, while I'll agree that "Unclassifiable statement" is better
> than "Invalid character in name", it would be nicer to see
> "Unbalanced parenthesis".
>
I'm sorry that gfortran does not meet your needs. But, given
how gfortran's matchers work, I doubt that anyone will produce
a patch to do what you want. I could be wrong. Maybe someone
will take up the challenge.
The patch I developed and committed specifically addresses a
problem where the error message and the locus to which it
pointed are simply wrong. In 'c = exp(+a))', the old error
message pointed to '+', which is a valid token in a valid
expression.
next prev parent reply other threads:[~2015-07-07 18:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 13:44 [Bug fortran/56520] New: " arjen.markus at deltares dot nl
2014-01-07 10:10 ` [Bug fortran/56520] " dominiq at lps dot ens.fr
2015-07-01 9:56 ` dominiq at lps dot ens.fr
2015-07-01 17:54 ` kargl at gcc dot gnu.org
2015-07-01 17:55 ` kargl at gcc dot gnu.org
2015-07-02 17:29 ` kargl at gcc dot gnu.org
2015-07-07 17:23 ` casey.webster at gmail dot com
2015-07-07 18:30 ` sgk at troutmask dot apl.washington.edu [this message]
2015-07-07 19:10 ` casey.webster at gmail dot com
2015-07-07 19:33 ` sgk at troutmask dot apl.washington.edu
2015-07-08 2:21 ` casey.webster at gmail dot com
2015-07-16 18:45 ` kargl at gcc dot gnu.org
2015-07-16 19:05 ` kargl 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-56520-4-A5qm1lq7ZB@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).