public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haynberg at sig dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/62143] New: unlimited number of class name qualifiers allowed Date: Thu, 14 Aug 2014 18:28:00 -0000 [thread overview] Message-ID: <bug-62143-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62143 Bug ID: 62143 Summary: unlimited number of class name qualifiers allowed Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: trivial Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: haynberg at sig dot com I'm not sure if this is a bug or allowed by the standard. Either way, it's strange this is allowed. $ cat t.cpp #include <iostream> using namespace std; struct X { void foo(); }; // an unlimited number of "X::"s are allowed !! void X::X::X::X::X::foo() { cout << "ctor" << endl; } // if you uncomment this, you'll get a redefinition error // void X::foo() // { // cout << "ctor" << endl; // } int main() { X x; x.foo(); } $ g++ t.cpp $ a.out ctor $ g++ -v ... gcc version 4.8.2 (GCC) ... $ uname -isr Linux 3.0.38-0.5-default x86_64
next reply other threads:[~2014-08-14 18:28 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-14 18:28 haynberg at sig dot com [this message] 2014-08-15 0:38 ` [Bug c++/62143] " redi 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-62143-4@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).