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++/33101] [DR 577] Bad C++ error on invalid code: <anonymous> has incomplete type Date: Fri, 16 Mar 2012 20:39:00 -0000 [thread overview] Message-ID: <bug-33101-4-0LqxFG5Xcu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-33101-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33101 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Bad C++ error on invalid |[DR 577] Bad C++ error on |code: <anonymous> has |invalid code: <anonymous> |incomplete type |has incomplete type --- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-03-16 20:17:02 UTC --- (In reply to comment #10) > I believe that the resolution of DR 577: > http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#577 > confirms this. The resolution, as of August, 2011, suggests changing > the wording to refer to the *type* void rather than the keyword. > (That change doesn't appear in the N3270 draft; I don't know whether > it appears in the final ISO C++ 2011 standard.) It doesn't, the DR says [Voted into the WP at the February, 2012 meeting.] i.e. after the 2011 standard. > At the very least, since there is (unfortunately) real-world code that > depends on this, I suggest changing it from a fatal error to a warning, > though I think removing the diagnostic altogether would be better. Since GCC, Clang and EDG all reject it today I'm surprised such real-world code hasn't been changed already.
next prev parent reply other threads:[~2012-03-16 20:18 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-33101-4@http.gcc.gnu.org/bugzilla/> 2012-03-16 19:32 ` [Bug c++/33101] " Keith.S.Thompson at gmail dot com 2012-03-16 19:40 ` Keith.S.Thompson at gmail dot com 2012-03-16 20:39 ` redi at gcc dot gnu.org [this message] 2012-03-16 20:46 ` [Bug c++/33101] [DR 577] allow typedefs for void in empty parameter list redi at gcc dot gnu.org 2012-03-16 21:47 ` Keith.S.Thompson at gmail dot com 2012-03-16 22:54 ` redi at gcc dot gnu.org 2014-06-12 14:09 ` paolo.carlini at oracle dot com 2014-06-14 22:56 ` paolo at gcc dot gnu.org 2014-06-14 23:00 ` paolo.carlini at oracle dot com 2014-06-14 23:06 ` paolo.carlini at oracle dot com 2014-06-23 17:06 ` paolo at gcc dot gnu.org 2014-06-23 17:08 ` paolo.carlini at oracle dot com
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-33101-4-0LqxFG5Xcu@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).