This is the mail archive of the
mailing list for the GCC project.
Re: #include <new.h> now causes a warning
- To: gdr at codesourcery dot com (Gabriel Dos Reis)
- Subject: Re: #include <new.h> now causes a warning
- From: Joe Buck <jbuck at synopsys dot COM>
- Date: Fri, 10 Aug 2001 13:03:46 -0700 (PDT)
- Cc: jbuck at synopsys dot com (Joe Buck), rodrigc at mediaone dot net (Craig Rodrigues), gcc at gcc dot gnu dot org
> | I think that -Wdeprecated should not be implied by -Wall, but should be
> | asked for explicitly.
Gabrial Dos Reis writes:
> I have no opinion on that. However, there ought to be a way to
> educate users to move to standard headers as soon as possible.
> | For example, it will tell people to turn <math.h> into <cmath>, resulting
> | in a program that won't compile with the current default compiler on any
> | GNU/Linux platform.
> Is that *really* the case?
> C-headers are not backward headers and I don't see how they can
> trigger that warning.
The original report claimed that this was so (that math.h would get a
warning), and I did not verify it myself as I've been testing the 3.0
branch, not the trunk.
So: Which headers issue the warning?
Are there any cases where the user is directed to use a header that
is not present in gcc 2.95.x?