public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tmmikolajczyk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52126] [4.7 Regression] compilation error Date: Sun, 05 Feb 2012 20:57:00 -0000 [thread overview] Message-ID: <bug-52126-4-ndbe4rzzyz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52126-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52126 --- Comment #2 from tmmikolajczyk at gmail dot com 2012-02-05 20:57:29 UTC --- Further investigation shows that the issue appears only when inheritance from the template class (class B : private A<T>) is provided explicitly. According to the standard a nested class defined inside a class template is implicitly template as well. The modified code reflecting that rule compiles fine: template<typename T> class A { public: void foo() {}; class B : private A { public: typedef A inherited; using inherited::foo; }; }; Anyway, the first version of the code seems to be valid C++ code.
next prev parent reply other threads:[~2012-02-05 20:57 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-05 19:47 [Bug c++/52126] New: " tmmikolajczyk at gmail dot com 2012-02-05 20:29 ` [Bug c++/52126] [4.7 Regression] " jakub at gcc dot gnu.org 2012-02-05 20:57 ` tmmikolajczyk at gmail dot com [this message] 2012-02-06 21:32 ` fabien at gcc dot gnu.org 2012-02-07 15:47 ` rguenth at gcc dot gnu.org 2012-02-07 17:23 ` redi at gcc dot gnu.org 2012-02-12 20:03 ` fabien at gcc dot gnu.org 2012-02-16 10:22 ` fabien at gcc dot gnu.org 2012-02-17 7:52 ` fabien at gcc dot gnu.org 2012-02-17 7:53 ` fabien at gcc dot gnu.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-52126-4-ndbe4rzzyz@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).