public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51786] [c++0x] Invalid declaration with decltype accepted Date: Tue, 31 Jan 2012 22:09:00 -0000 [thread overview] Message-ID: <bug-51786-4-1CtdeuLqwx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51786-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51786 --- Comment #3 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2012-01-31 21:26:41 UTC --- It seems to me that all these examples should be rejected (Thanks to Jens Maurer for helping me here): At first it seems, that we can follow the grammar chain starting from /declaration/ in 7 [dcl.dcl] via simple-declaration => decl-specifier-seq_opt init-declarator-list_opt; without the optional init-declarator-list reaching decl-specifier => type-specifier => trailing-type-specifier => simple-type-specifier => decltype(expression). But the show-stopper for this is 7 [dcl.dcl] p3: "In a simple-declaration, the optional init-declarator-list can be omitted only when declaring a class (Clause 9) or enumeration (7.2), that is, when the decl-specifier-seq contains either a class-specifier, an elaborated-type- specifier with a class-key (9.1), or an enum-specifier. [..]" Neither of these three situations applies, so this is no valid /simple-declaration/.
next prev parent reply other threads:[~2012-01-31 21:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-07 16:16 [Bug c++/51786] New: " reichelt at gcc dot gnu.org 2012-01-16 18:14 ` [Bug c++/51786] " paolo.carlini at oracle dot com 2012-01-31 16:25 ` paolo.carlini at oracle dot com 2012-01-31 22:09 ` daniel.kruegler at googlemail dot com [this message] 2012-01-31 22:24 ` paolo.carlini at oracle dot com 2012-10-16 10:49 ` paolo.carlini at oracle dot com 2013-07-06 22:49 ` paolo.carlini at oracle dot com 2013-07-07 13:59 ` 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-51786-4-1CtdeuLqwx@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).