Re: c++/7755: Please make -Wno-deprecated do just that

Re: c++/7755: Please make -Wno-deprecated do just that

[bangerth]

Synopsis: Please make -Wno-deprecated do just that

State-Changed-From-To: feedback->open
State-Changed-By: bangerth
State-Changed-When: Wed Jan  8 11:53:38 2003
State-Changed-Why:
    The documentation says that -Wno-deprecated is C++ only.
    Starting with 3.3, the C front end does indeed reject this
    flag, so I guess it erroneously just accepted it, but did
    nothing.
    
    Compiling the code with the C++ front end yields errors
    with 3.2.2 and 3.3, and is accepted with 3.4. I think it
    should yield an error with 3.4 as well, since the C++
    front end treated __FUNCTION__ differently from the 
    beginning. I don't know why it does now.
    
    Since -Wno-deprecated is a C++ option, I change the category
    of this report. Given the strange behavior above, shall I
    also change the synopsis to something like "Incorrect
    behavior of __FUNCTION__"?
    
    W.

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

Re: c++/7755: Please make -Wno-deprecated do just that

[H. Peter Anvin]

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
 

Re: c++/7755: Please make -Wno-deprecated do just that

[Joseph S. Myers]

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

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
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, 8 Jan 2003 22:59:56 +0000 (GMT)

 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).
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 

Re: c++/7755: Please make -Wno-deprecated do just that

[H. Peter Anvin]

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
 
 

Re: c++/7755: Please make -Wno-deprecated do just that

[Wolfgang Bangerth]

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/7755: Please make -Wno-deprecated do just that
Date: Wed, 8 Jan 2003 14:48:05 -0600 (CST)

 > 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.
 
 Regards
   W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 

Re: c++/7755: Please make -Wno-deprecated do just that

[H. Peter Anvin]

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

From: "H. Peter Anvin" <hpa@zytor.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        hpa@zytor.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/7755: Please make -Wno-deprecated do just that
Date: Wed, 08 Jan 2003 12:38:41 -0800

 bangerth@dealii.org wrote:
 > Synopsis: Please make -Wno-deprecated do just that
 > 
 > State-Changed-From-To: feedback->open
 > State-Changed-By: bangerth
 > State-Changed-When: Wed Jan  8 11:53:38 2003
 > State-Changed-Why:
 >     The documentation says that -Wno-deprecated is C++ only.
 >     Starting with 3.3, the C front end does indeed reject this
 >     flag, so I guess it erroneously just accepted it, but did
 >     nothing.
 >     
 >     Compiling the code with the C++ front end yields errors
 >     with 3.2.2 and 3.3, and is accepted with 3.4. I think it
 >     should yield an error with 3.4 as well, since the C++
 >     front end treated __FUNCTION__ differently from the 
 >     beginning. I don't know why it does now.
 >     
 >     Since -Wno-deprecated is a C++ option, I change the category
 >     of this report. Given the strange behavior above, shall I
 >     also change the synopsis to something like "Incorrect
 >     behavior of __FUNCTION__"?
 >     
 
 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.
 
 Thanks,
 
 	-hpa