This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: #include <new.h> now causes a warning


Joe Buck <jbuck@synopsys.COM> writes:

| > gcc version 3.1 20010808 (experimental)
| > 
| > The problem is solved, but elsewhere, I am getting
| > the following warning:
| 
| > ###########################################################################
| > g++ -W -Wall -Wpointer-arith -pipe -O3 -g -Wno-uninitialized -fno-implicit-templates   -D_POSIX_THREADS -D_POSIX_THREAD_SAFE_FUNCTIONS -D_REENTRANT -DACE_HAS_AIO_CALLS  -I/opt2/home/craigr/ACE_wrappers -DACE_HAS_RAPI -I/usr/include/rsvp -DACE_HAS_EXCEPTIONS  -c -fPIC -o .shobj/OS.o OS.cpp
| > 
| > In file included from /usr/local/include/g++-v3/backward/new.h:33,
| >                  from /opt2/home/craigr/ACE_wrappers/ace/OS.h:2950,
| >                  from OS.cpp:3:
| > /usr/local/include/g++-v3/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please use the <X> header instead of <X.h> header for 'C++' includes and use the <cX> header instead of <X.h> header for 'C' includes. To disable this warning use -Wno-deprecated.
| > 
| > ###########################################################################
| 
| I think that -Wdeprecated should not be implied by -Wall, but should be
| asked for explicitly.

Joe,

  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.

|  Otherwise there is way too much perfectly valid,
| standards-conformant code out there that will now issue a sea of warnings,

There can't be any standard-conformant way to trigger those warnings.

[...]

| 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.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]