public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Carlo Wood <carlo@alinoe.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/3211: Incorrect, substitution related mangling.
Date: Sun, 17 Jun 2001 17:36:00 -0000	[thread overview]
Message-ID: <20010618003601.5205.qmail@sourceware.cygnus.com> (raw)

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

From: Carlo Wood <carlo@alinoe.com>
To: gcc-bugs@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/3211: Incorrect, substitution related mangling.
Date: Mon, 18 Jun 2001 02:31:05 +0200

 On Sun, Jun 17, 2001 at 06:59:39PM +0200, Carlo Wood wrote:
 > Please note that even:
 > 
 > --------------------
 > #include <iostream>
 > #include <typeinfo>
 >  
 > struct A {
 >   int member(void) { }
 > };
 >  
 > template<typename T>
 >   struct const_test {
 >     typedef int (member_type)(void);
 >     member_type (T::*member_pointer);
 >   };
 >  
 > int main(void)
 > {
 >   std::cout << typeid(const_test<A const>::member_pointer).name() << '\n';
 >   return 0;
 > }
 > --------------------
 > 
 > Returns "MK1AFivE", where "1A" is <type1> and "FivE" is <type2>.  There is no
 > 'const' qualifier for "1A".
 
 Hmmpf.  Ok, that was nonsense... There *is* a 'K' there...
 But it doesn't change the fact that there can only be a 'K' when <type2>
 is a (member) function.  I don't think this changes the relevance of my
 argument that "K1A" shouldn't be a candidate for substitution, nor should
 a substitution be used at that place for "K1A" is one such substitution
 already exists.
 
 -- 
 Carlo Wood <carlo@alinoe.com>


             reply	other threads:[~2001-06-17 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17 17:36 Carlo Wood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13 15:16 loewis
2001-11-13 15:16 loewis
2001-06-18 16:56 Carlo Wood
2001-06-17 10:06 Carlo Wood
2001-06-17  9:56 carlo

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=20010618003601.5205.qmail@sourceware.cygnus.com \
    --to=carlo@alinoe.com \
    --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).