public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/39109] New: [4.4 Regression] Accessible constructor required for new Date: Thu, 05 Feb 2009 15:10:00 -0000 [thread overview] Message-ID: <bug-39109-87@http.gcc.gnu.org/bugzilla/> (raw) struct N { private: virtual ~N (); }; N * foo () { return new N (); } used to compile until http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138355 Does it really need to have an accessible destructor if it is never deleted? Dodji cited [basic.life]/4 which could mean this is valid. Distilled from thunderbird. -- Summary: [4.4 Regression] Accessible constructor required for new Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jakub at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39109
next reply other threads:[~2009-02-05 15:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-05 15:10 jakub at gcc dot gnu dot org [this message] 2009-02-05 15:11 ` [Bug c++/39109] " jakub at gcc dot gnu dot org 2009-02-05 22:09 ` rguenth at gcc dot gnu dot org 2009-02-07 4:23 ` jason at gcc dot gnu dot org 2009-02-09 21:46 ` jason at gcc dot gnu dot org 2009-02-09 22:10 ` jakub at gcc dot gnu dot 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-39109-87@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).