public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	loewis@informatik.hu-berlin.de, nobody@gcc.gnu.org
Subject: Re: c++/4283: Implicit typename extension should be optional
Date: Sat, 15 Dec 2001 10:20:00 -0000	[thread overview]
Message-ID: <20011215182005.31564.qmail@sources.redhat.com> (raw)

Synopsis: Implicit typename extension should be optional

State-Changed-From-To: open->feedback
State-Changed-By: nathan
State-Changed-When: Sat Dec 15 10:20:05 2001
State-Changed-Why:
    it is now deprecated on the mainline (and so will be
    in 3.1), it is hoped it will be removed in 3.2
    
    Is this sufficient? You get an unconditional warning
    on its use now.

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


             reply	other threads:[~2001-12-15 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15 10:20 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-27 17:13 rodrigc
2001-12-16  4:26 Martin von Loewis
2001-09-10  6:26 loewis

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=20011215182005.31564.qmail@sources.redhat.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=loewis@informatik.hu-berlin.de \
    --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).