public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10649: is_pointer<T> reports pointer to member function is not a pointer Date: Thu, 08 May 2003 14:16:00 -0000 [thread overview] Message-ID: <20030508141600.16360.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10649; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: notbob@tessellation.com Cc: giovannibajo@libero.it, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/10649: is_pointer<T> reports pointer to member function is not a pointer Date: 08 May 2003 16:11:57 +0200 Robert Schwartz <robertallanschwartz@yahoo.com> writes: | --- giovannibajo@libero.it wrote: | > Synopsis: is_pointer<T> reports pointer to member function is not a pointer | > | > State-Changed-From-To: open->closed | > State-Changed-By: bajo | > State-Changed-When: Wed May 7 00:40:10 2003 | > State-Changed-Why: | > No, a member function pointer cannot match "T*". What would | > be T, in fact? | | is_pointer<int foo::*>::value (i.e. pointer to member variable) evaluates to true. | If I remove the * from "int foo::*", then I get "int foo::". | I know this isn't a valid C++ type, but a pointer to a member | variable is still a pointer, no? In which sense? A pointer to member is a different kind of beast. It is much more close to a struct than to a usual pointer. -- Gaby
next reply other threads:[~2003-05-08 14:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-08 14:16 Gabriel Dos Reis [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-09 7:06 Gabriel Dos Reis 2003-05-08 22:36 Giovanni Bajo 2003-05-08 22:36 Phil Edwards 2003-05-08 22:26 Robert Schwartz 2003-05-08 0:26 Giovanni Bajo 2003-05-08 0:16 Giovanni Bajo 2003-05-07 23:56 Phil Edwards 2003-05-07 23:36 Giovanni Bajo 2003-05-07 23:16 Robert Schwartz 2003-05-07 0:40 giovannibajo 2003-05-06 22:56 notbob
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=20030508141600.16360.qmail@sources.redhat.com \ --to=gdr@integrable-solutions.net \ --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: 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).