public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, yujie.wu@hec.utah.edu Subject: Re: c++/9665: error with member and member template of same name Date: Fri, 14 Feb 2003 21:09:00 -0000 [thread overview] Message-ID: <20030214210936.10427.qmail@sources.redhat.com> (raw) Old Synopsis: g++ (GCC) 3.2.1 rejects obvious legal code New Synopsis: error with member and member template of same name State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Fri Feb 14 21:09:36 2003 State-Changed-Why: Confirmed. A simpler testcase is --------------------- template <typename T> struct A { void foo(); template <typename> void foo(); }; template <typename T> void A<T>::foo() {} ------------------------ tmp/g> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc x.cc:7: error: expected 2 levels of template parms for `void A<T>::foo()', got 1 The problem goes away of course, if the member template is removed. It also goes away if we change the order of declaration (!) of the two versions of foo, which already suggests the right patch: presently we walk the list of member functions and stop at the first one with name foo. We then note that the number of template levels is incorrect and error out. Rather, we should continue walking and only issue an error if we don't find a match. I have seen this error before, so I think this report is a duplicate of something, but can't find the other one right now. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9665
next reply other threads:[~2003-02-14 21:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-14 21:09 bangerth [this message] 2003-04-07 10:46 Giovanni Bajo 2003-04-07 13:58 bangerth
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=20030214210936.10427.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=yujie.wu@hec.utah.edu \ /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).