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 21:16:00 -0000 [thread overview] Message-ID: <20030108211605.23370.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: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/7755: Please make -Wno-deprecated do just that Date: Wed, 08 Jan 2003 13:10:21 -0800 Wolfgang Bangerth wrote: >>If -Wno-deprecated is not the right way to disable this warning, then >>please do provide another flag to do so. Not being able to selectively >>squelsh this warning is a total showstopper for being able to use newer >>gcc's for several projects. > > > But if the deprecated feature is removed in the next version of gcc, > you're not much better off, either: your code simply needs to be fixed, > and given the example you showed this is actually not so difficult. > > That does not mean that I'm not in favor of implementing such a warning, > but I guess few people feel incited to invent a switch for old branches > where newer versions will not allow the feature warned for anyway. > Well, given that gcc still supports -traditional, some amount of backwards compatibility probably needs to be accounted for... -hpa
next reply other threads:[~2003-01-08 21:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-08 21:16 H. Peter Anvin [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-08 23:46 H. Peter Anvin 2003-01-08 23:06 Joseph S. Myers 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=20030108211605.23370.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: linkBe 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).