public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113839] misleading syntax error message
Date: Thu, 08 Feb 2024 20:29:55 +0000	[thread overview]
Message-ID: <bug-113839-4-8armdhyqoV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113839-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113839

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Frank Heckenbach from comment #0)
> While I appreciate gcc trying to by helpful, it seems it goes wrong rather
> often.

That doesn't match my experience. The errors that mention a specific grammar
production tend to be accurate, with the odd exception like this bug (which
will get fixed).

I find the problem is that telling the user that a particular grammar
production (like "unqualified-id" or "primary-expression") is expected isn't
really helpful to the layperson who doesn't memorize the BNF-like grammar in
the standard. Clang tends to do a better job in that regard, balancing accuracy
with comprehensibility.

If you encounter cases where a diagnostic is misleading, wrong, or just
unhelpfully technical in its wording, please do report them so they can be
improved.

      parent reply	other threads:[~2024-02-08 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 19:02 [Bug c++/113839] New: " f.heckenbach@fh-soft.de
2024-02-08 19:05 ` [Bug c++/113839] " pinskia at gcc dot gnu.org
2024-02-08 19:06 ` mpolacek at gcc dot gnu.org
2024-02-08 19:17 ` f.heckenbach@fh-soft.de
2024-02-08 20:22 ` redi at gcc dot gnu.org
2024-02-08 20:29 ` redi at gcc dot gnu.org [this message]

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-113839-4-8armdhyqoV@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).