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++/107178] Diagnosis for colon vs semi-colon in a member function declaration Date: Fri, 07 Oct 2022 08:12:23 +0000 [thread overview] Message-ID: <bug-107178-4-uwh2WuJjum@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 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2022-10-07 Status|UNCONFIRMED |NEW --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #1) > GCC diagonstic seems reasonable. Only from the most mechanical perspective. > because GCC assumes you started to define a bitfield which is reasonable > assumention really. Not really, because the chances of somebody typing ':' instead of ';' is quite high (they're on the same key on many keyboard layouts) and the chances of somebody trying to define a bit-field with a function type is practically zero. Although the parser just sees "bit-field with function type" we can apply some intelligence and say that's probably not what the user was trying to do. A simple typo is more likely. > At least GCC points out the colon and even suggest you started a bitfield > which is what a colon normally does here .... But not with a function type.
next prev parent reply other threads:[~2022-10-07 8:12 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 ` [Bug c++/107178] " pinskia at gcc dot gnu.org 2022-10-07 3:59 ` llvm at rifkin dot dev 2022-10-07 8:12 ` redi at gcc dot gnu.org [this message] 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-uwh2WuJjum@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).