public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/950: Template lookup problem
Date: Sun, 10 Nov 2002 12:46:00 -0000	[thread overview]
Message-ID: <20021110204602.1739.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/950; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: c++/950: Template lookup problem
Date: Sun, 10 Nov 2002 14:46:04 -0600 (CST)

 A reduced testcase for this one is
 --------------------------------------------
 struct B { void a (int n); };
 struct D: public B {};
 
 template <typename T> struct X {
     template<typename Y>
     static void foo (const Y&, void (T::*)(Y));
 };
 
 int main () {
   int n = 3;
   X<D>::foo(n, &D::a);
 }
 --------------------------------------
 The error I get is this one:
 x.cc: In function `int main()':
 x.cc:11: error: no matching function for call to `X<D>::foo(int&, void
    (B::*)(int))'
 
 Thus, the compiler cannot find a match for X::foo, since &D::a is 
 immediately converted to &B::a, i.e. to a pointer to member function of 
 the _base_ class, although we have taken a p-t-m-f of the derived class. I 
 don't know what the standard says on this one, but at least the failure 
 mode is clear now.
 
 The problem can be worked around using a temporary variable of type 
   void (D::*)(int)
 or an explicit cast.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


             reply	other threads:[~2002-11-10 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-10 12:46 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-20 23:36 Wolfgang Bangerth
2001-08-12  9:38 lerdsuwa

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=20021110204602.1739.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: link
Be 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).