public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@ticam.utexas.edu To: gcc-gnats@gcc.gnu.org Subject: c++/8271: Templates and pointers to const member functions Date: Thu, 17 Oct 2002 15:26:00 -0000 [thread overview] Message-ID: <20021017221917.3030.qmail@sources.redhat.com> (raw) >Number: 8271 >Category: c++ >Synopsis: Templates and pointers to const member functions >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Oct 17 15:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Wolfgang Bangerth >Release: unknown-1.0 >Organization: >Environment: all gcc versions since at least 2.95 >Description: The following code compiles with gcc: ------------------------------------------- struct X { void f () const; }; template <class T> void g(void (T::*) ()); void h () { g (&X::f); }; ------------------------------------------- On the other hand, it fails to compile with at least two other compilers, which made me wonder who's right and who is wrong. The point is that the template function g takes a member function pointer, but we pass a pointer to a _const_ member function. gcc does what seems very reasonable,namely identifying the template argument T with "const X". However, other compilers do not do this. They say there is no prototype for an argument 'void (T::*)() const'. I tried to find normative statements in the standard, but could not find anything that would match my case, which is probably only due to an incomplete search through the standard. So, I would be happy about a statement by someone more knowledgeable about this than me :-) Thanks Wolfgang >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-17 22:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-17 15:26 bangerth [this message] 2003-01-07 19:26 René Møller Fonseca 2003-01-07 20:05 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=20021017221917.3030.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-gnats@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).