From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23388 invoked by alias); 8 Jan 2003 21:16:06 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 23371 invoked by uid 71); 8 Jan 2003 21:16:05 -0000 Date: Wed, 08 Jan 2003 21:16:00 -0000 Message-ID: <20030108211605.23370.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "H. Peter Anvin" Subject: Re: c++/7755: Please make -Wno-deprecated do just that Reply-To: "H. Peter Anvin" X-SW-Source: 2003-01/txt/msg00569.txt.bz2 List-Id: The following reply was made to PR c++/7755; it has been noted by GNATS. From: "H. Peter Anvin" To: Wolfgang Bangerth 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