public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arjen.markus at deltares dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/56520] New: Syntax error causes misleading message: "Invalid character in name" Date: Mon, 04 Mar 2013 13:44:00 -0000 [thread overview] Message-ID: <bug-56520-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56520 Bug #: 56520 Summary: Syntax error causes misleading message: "Invalid character in name" Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: arjen.markus@deltares.nl An extra parenthesis at the end of a statement leads to the error message: Invalid character in name at (1) The message has nothing to do with the actual error. Here is a small program to reproduce it: ! misleading.f90 -- ! Syntax error is reported with a misleading message ! program misleading implicit none real :: a, b, c a = 1.0 b = 1.0 c = exp(-a*b) ) end program misleading
next reply other threads:[~2013-03-04 13:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-04 13:44 arjen.markus at deltares dot nl [this message] 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 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@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: linkBe 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).