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++/52018] GCC refuses to accept a disambiguation statement Date: Mon, 30 Jan 2012 09:24:00 -0000 [thread overview] Message-ID: <bug-52018-4-HKKlEg9a5r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52018-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52018 Daniel Krügler <daniel.kruegler at googlemail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.kruegler at | |googlemail dot com --- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2012-01-30 08:56:28 UTC --- The compiler behaves conforming: An elaborated type specifier is not allowed in this context (see [expr.type.conv] p1 which says "A simple-type-specifier (7.1.6.2) or typename-specifier (14.6) [..]", they are only allowed in restricted context like a new expression for example. Note that similar expressions apply more general type-specifiers like "unsigned int" which cannot be used in such an expression. In other words: This does not look like a bug to me. A reduced example would be the following snippet: struct string { string(int); }; enum { string }; void h(struct string); int main() { h(class string(42)); } A simple workaround is to introduce a local typename-specifier: typedef class string c_t; h(c_t(42));
next prev parent reply other threads:[~2012-01-30 8:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-27 12:53 [Bug c++/52018] New: " piotr.wyderski at gmail dot com 2012-01-30 9:24 ` daniel.kruegler at googlemail dot com [this message] 2012-01-31 8:24 ` [Bug c++/52018] " daniel.kruegler at googlemail dot com 2012-01-31 16:11 ` 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-52018-4-HKKlEg9a5r@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).