public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7755: Please make -Wno-deprecated do just that
Date: Wed, 08 Jan 2003 23:46:00 -0000	[thread overview]
Message-ID: <20030108234606.29517.qmail@sources.redhat.com> (raw)

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

From: "H. Peter Anvin" <hpa@zytor.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Wolfgang Bangerth <bangerth@ticam.utexas.edu>, gcc-gnats@gcc.gnu.org
Subject: Re: c++/7755: Please make -Wno-deprecated do just that
Date: Wed, 08 Jan 2003 15:42:57 -0800

 Joseph S. Myers wrote:
 > On Wed, 8 Jan 2003, H. Peter Anvin wrote:
 > 
 > 
 >>Well, given that gcc still supports -traditional, some amount of
 >>backwards compatibility probably needs to be accounted for...
 > 
 > 
 > GCC (mainline and 3.3 branch) does not still support -traditional.  
 > Support was deprecated in 3.1 and removed for 3.3 (though the draft
 > release notes for 3.3 fail to mention this).
 > 
 > But -Wno-deprecated makes sense as a C option, not just a C++ one, and
 > should be implemented as such - if people use the blunt instrument of
 > disabling all deprecation warnings, it's their problem when the features
 > are removed, just as if they use -w to disable all warnings, or fail to
 > use -Wall.  This bug report should stay open as a feature request for a
 > manifestly desirable feature (and straightforward to implement - any
 > beginners looking for PRs to work on could reasonably do this one).
 > 
 
 Well put.
 
 	-hpa
 


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 23:46 H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 23:06 Joseph S. Myers
2003-01-08 21:16 H. Peter Anvin
2003-01-08 20:56 Wolfgang Bangerth
2003-01-08 20:46 H. Peter Anvin
2003-01-08 19:53 bangerth

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=20030108234606.29517.qmail@sources.redhat.com \
    --to=hpa@zytor.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).