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, martin@xemacs.org,
	nobody@gcc.gnu.org
Subject: Re: c++/9437: template function parameter `T*' shouldn't match pointers to members
Date: Fri, 24 Jan 2003 20:12:00 -0000	[thread overview]
Message-ID: <20030124201259.22766.qmail@sources.redhat.com> (raw)

Synopsis: template function parameter `T*' shouldn't match pointers to members

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Jan 24 20:12:59 2003
State-Changed-Why:
    Something's indeed wrong here. To see what the template
    parameter matches, execute the following variation:
    -------------------------
    extern "C" void printf (const char *, ...);
    
    struct S {
        template <typename T>
        operator T* () const {
          printf ("%s\n", __PRETTY_FUNCTION__);
          return static_cast<T*> (0);
        }
    } null;
    
    struct A { int i; };
    
    static void f (int A::* pmi) { }
    
    int main () { f (null); }
    -----------------------------
    It displays
    g/a> /home/bangerth/bin/gcc-3.4-pre/bin/c++ x.cc
    g/a> ./a.out
    S::operator T*() const [with T = int A::*]
    
    But then the return type would be _pointer_ to member 
    pointer, not member pointer.
    
    Confirmed with 2.95, 3.2.2, 3.3, 3.4
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9437


             reply	other threads:[~2003-01-24 20:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 20:12 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-29 11:38 nathan
2003-01-28 17:53 nathan
2003-01-24 19:46 martin

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=20030124201259.22766.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=martin@xemacs.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).