public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Martin Sebor <sebor@roguewave.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10690: bogus ambiguity on templates overloaded on return type
Date: Thu, 08 May 2003 20:56:00 -0000	[thread overview]
Message-ID: <20030508205601.15458.qmail@sources.redhat.com> (raw)

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

From: Martin Sebor <sebor@roguewave.com>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/10690: bogus ambiguity on templates overloaded on return
 type
Date: Thu, 08 May 2003 14:51:19 -0600

 No, typeid (foo<T>) is what I wanted. There is exactly one foo<T>
 for each of the three arguments of T in the program, and they are:
 foo<bool>, foo<short>, and foo<int>. typeid(foo<T>).name() should
 return the name of each specialization. Note that while Intel C++
 gives an ICE, the latest EDG front end, eccp 3.2, that's coming
 out in a few days, is supposed to compile the code correctly. The
 oly other compiler that I know of that compiles the code is IBM
 VAC++ 6.0 (although it fails to link, not sure why).
 
 Martin
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10690
 


             reply	other threads:[~2003-05-08 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 20:56 Martin Sebor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 19:56 giovannibajo
2003-05-08 18:46 sebor

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=20030508205601.15458.qmail@sources.redhat.com \
    --to=sebor@roguewave.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).