public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chtz at informatik dot uni-bremen.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66472] -Wshadow gets confused by using statements in template classes Date: Tue, 09 Jun 2015 12:39:00 -0000 [thread overview] Message-ID: <bug-66472-4-1PiM57MorV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66472-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66472 Christoph Hertzberg <chtz at informatik dot uni-bremen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chtz at informatik dot uni-bremen. | |de --- Comment #1 from Christoph Hertzberg <chtz at informatik dot uni-bremen.de> --- Wouldn't this actually be a valid warning if BaseClass had a constructor taking a function pointer/member function pointer? struct BaseClass { BaseClass(int) { std::cout << "int\n"; } BaseClass(int () ) { std::cout << "int()\n"; } BaseClass(int (BaseClass::*)()) {std::cout << "int (BaseClass::*)()\n"; } static int size() { return 0;} int size2() { return 0; } }; struct Foo : public BaseClass { using BaseClass::size; using BaseClass::size2; // size shadows BaseClass::size! Foo(int size) : BaseClass(size) {} Foo() : BaseClass(size) {} // uses BaseClass::size Foo(char) : BaseClass(size2) {} // uses BaseClass::size2 };
next prev parent reply other threads:[~2015-06-09 12:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-09 11:25 [Bug c++/66472] New: " gael.guennebaud at gmail dot com 2015-06-09 12:39 ` chtz at informatik dot uni-bremen.de [this message] 2015-06-09 12:54 ` [Bug c++/66472] " gael.guennebaud at gmail dot com 2015-06-09 13:07 ` glisse at gcc dot gnu.org 2015-06-09 13:11 ` manu at gcc dot gnu.org 2021-12-25 1:43 ` pinskia 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-66472-4-1PiM57MorV@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).