public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107178] Diagnosis for colon vs semi-colon in a member function declaration Date: Fri, 07 Oct 2022 03:22:13 +0000 [thread overview] Message-ID: <bug-107178-4-1PAbaKUlcg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107178-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107178 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Severity|normal |enhancement --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- clang diagnostic is way worse in my mind. It does not even point to the : . GCC is assuming if you don't have a constructor you have a type and that type here would be T (S::)() Take: ``` struct S { int (*foo)() : int t; }; ``` Trying to define a pointer to function field foo but used : instead of ;. GCC diagonstic seems reasonable. because GCC assumes you started to define a bitfield which is reasonable assumention really. clang diagnostic here is never even close to helpful. At least GCC points out the colon and even suggest you started a bitfield which is what a colon normally does here ....
next prev parent reply other threads:[~2022-10-07 3:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-07 3:08 [Bug c++/107178] New: " llvm at rifkin dot dev 2022-10-07 3:22 ` pinskia at gcc dot gnu.org [this message] 2022-10-07 3:59 ` [Bug c++/107178] " llvm at rifkin dot dev 2022-10-07 8:12 ` redi at gcc dot gnu.org 2022-10-07 8:27 ` redi at gcc dot gnu.org 2022-10-07 8:28 ` redi 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-107178-4-1PAbaKUlcg@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).