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++/96120] Ambiguity diagnostic message of "invalid use of type 'void' in parameter declaration" Date: Wed, 08 Jul 2020 16:15:08 +0000 [thread overview] Message-ID: <bug-96120-4-DvJiUBjJgf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96120-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96120 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- GCC's diagnostic seems fine to me. Using 'void' as the type of a parameter is invalid. There's a special case for (void) but that isn't relevant to your declaration, which has two parameters.
next prev parent reply other threads:[~2020-07-08 16:15 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-08 15:44 [Bug c++/96120] New: " haoxintu at gmail dot com 2020-07-08 16:13 ` [Bug c++/96120] " redi at gcc dot gnu.org 2020-07-08 16:15 ` redi at gcc dot gnu.org [this message] 2020-07-08 16:21 ` haoxintu at gmail dot com 2020-07-08 19:33 ` 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-96120-4-DvJiUBjJgf@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).