public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sutambe at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/33934] New: access control bug in member function templates Date: Sun, 28 Oct 2007 21:05:00 -0000 [thread overview] Message-ID: <bug-33934-15278@http.gcc.gnu.org/bugzilla/> (raw) In the program snippet given below, line number 14 and 20 should have identical access privileges with respect to A::func(). But gcc 4.1.2 compiles line #14 just fine, whereas on line #20, it catches the error correctly. This bug is similar to bug #24118. 1 class A 2 { 3 protected: 4 void func () 5 { } 6 }; 7 8 class B: private A 9 { 10 public: 11 template <class T> 12 void foo () 13 { 14 void (A::*ptr)() = & A::func; 15 // Should not compile but compiles on gcc 4.1.2 16 } 17 18 void bar () 19 { 20 void (A::*ptr)() = & A::func; 21 // Should not compile and gcc throws error. 22 } 23 }; 24 int main (void) 25 { 26 B b; 27 b.foo<int>(); 28 b.bar(); 29 } -- Summary: access control bug in member function templates Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: sutambe at yahoo dot com GCC host triplet: SMP i686 i386 GNU/Linux Fedora Core Release 6 GCC target triplet: SMP i686 i386 GNU/Linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33934
next reply other threads:[~2007-10-28 21:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-28 21:05 sutambe at yahoo dot com [this message] 2007-11-05 0:05 ` [Bug c++/33934] " sutambe at yahoo dot com 2009-04-29 7:05 ` 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=bug-33934-15278@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).