public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/20040] A new expression must check the access level of delete operator Date: Fri, 08 Sep 2006 20:30:00 -0000 [thread overview] Message-ID: <20060908203015.30036.qmail@sourceware.org> (raw) In-Reply-To: <bug-20040-10087@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from amylaar at gcc dot gnu dot org 2006-09-08 20:30 ------- g++ also fails to check the accessibility of the destructor: class C { private: void operator delete (void *p) throw (); }; void f () { C *p = new C; } class D { private: ~D (); }; void g () { D *p = new D; } -- amylaar at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joern dot rennecke at st dot | |com Known to fail|2.95.3 3.0.4 3.2.3 3.3.3 |2.95.3 3.0.4 3.2.3 3.3.3 |3.4.0 4.0.0 |3.4.0 4.0.0 4.2.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20040
next parent reply other threads:[~2006-09-08 20:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20040-10087@http.gcc.gnu.org/bugzilla/> 2006-09-08 20:30 ` amylaar at gcc dot gnu dot org [this message] [not found] <bug-20040-4@http.gcc.gnu.org/bugzilla/> 2022-01-06 21:19 ` jason at gcc dot gnu.org 2022-01-07 22:12 ` cvs-commit at gcc dot gnu.org 2022-01-21 20:18 ` cvs-commit at gcc dot gnu.org 2022-01-28 4:40 ` jason at gcc dot gnu.org 2005-02-18 4:11 [Bug c++/20040] New: " msadoghi at ca dot ibm dot com 2005-02-18 4:12 ` [Bug c++/20040] " pinskia 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=20060908203015.30036.qmail@sourceware.org \ --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).