public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9183: [3.2 regression] Typenames in foreign namespaces inhibit  member function template argument deduction
Date: Tue, 14 Jan 2003 23:46:00 -0000	[thread overview]
Message-ID: <20030114234602.13001.qmail@sources.redhat.com> (raw)

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

From: Janis Johnson <janis187@us.ibm.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, klfd21@yahoo.de,
   gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/9183: [3.2 regression] Typenames in foreign namespaces inhibit 
 member function template argument deduction
Date: Tue, 14 Jan 2003 15:46:21 -0800

 This bug was fixed on the mainline by the following patch.
 That information is probably not very useful, given the size
 of the patch, but at least now we know.
 
 --- gcc/gcc/cp/ChangeLog ---
 2002-07-31  Mark Mitchell  <mark@codesourcery.com>
 
         * call.c
         * cp-tree.def
         * cp-tree.h
         * cvt.c
         * decl2.c
         * init.c
         * method.c
         * parse.y
         * pt.c
         * search.c
         * semantics.c
         * typeck.c
         * typeck2.c
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9183
 
 
 


             reply	other threads:[~2003-01-14 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14 23:46 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-28 15:36 ehrhardt
2003-01-06 14:56 paolo

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=20030114234602.13001.qmail@sources.redhat.com \
    --to=janis187@us.ibm.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).