public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51424] New: [C++11] G++ should diagnose self-delegating constructors Date: Mon, 05 Dec 2011 16:10:00 -0000 [thread overview] Message-ID: <bug-51424-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51424 Bug #: 51424 Summary: [C++11] G++ should diagnose self-delegating constructors Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: jason@gcc.gnu.org CC: pedro.lamarao@gmail.com, ville.voutilainen@gmail.com This modification of g++.dg/template/meminit1.C should get a diagnostic in C++11 mode as well: template <class T > struct S { S() : S() {} // { dg-message "delegating constructors" "" { target c++98 } } // { dg-error "delegates to itself" "" { target c++11 } } }; S<int> s; because 12.6.2 says, "If a constructor delegates to itself directly or indirectly, the program is ill-formed; no diagnostic is required." The diagnostic is not required, but it is easy to give, so we should do so.
next reply other threads:[~2011-12-05 16:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-05 16:10 jason at gcc dot gnu.org [this message] 2013-08-29 12:54 ` [Bug c++/51424] " paolo.carlini at oracle dot com 2013-08-30 15:39 ` paolo at gcc dot gnu.org 2014-04-22 11:38 ` jakub at gcc dot gnu.org 2014-04-22 12:03 ` ville.voutilainen at gmail dot com 2014-04-22 12:53 ` jakub at gcc dot gnu.org 2014-04-28 9:54 ` paolo.carlini at oracle dot com 2014-04-28 10:33 ` ville.voutilainen at gmail 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-51424-4@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).