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

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: backwards headers vs. C++0x

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
Cc: libstdc++ at gcc dot gnu dot org
Date: Fri, 11 May 2007 12:21:44 +0200
Subject: Re: backwards headers vs. C++0x
References: <9f71cef00703030853n59da180aq4d93f1dde55da180@mail.gmail.com> <45E9B5C3.1080602@suse.de> <1172945289.4743.2.camel@localhost.localdomain> <45E9BD3E.9080706@suse.de> <1172946528.4743.5.camel@localhost.localdomain> <45EB0A67.9010409@codesourcery.com> <20070305170320.GB7387@synopsys.com> <45ED6BA0.5010305@redhat.com> <m3slchft1x.fsf@localhost.localdomain> <4348dea50705091808y7f8e366ch1c947245f856396e@mail.gmail.com>

It's hard to know if -Wno-deprecated was used to silence warnings from
<strstream> (deprecated, but still in the standard) or one of the
non-standard headers such as <iostream.h>, since they all give the
same warning.

Yes. You are right.

There are a couple of things that could be done.

1) Remove all that are not explicitly deprecated, along the lines proposed before. This would only leave strstream, I think.

2) Error instead of warn when using the backward (ie, present but not deprecated headers) when using C++0x.

-benjamin

References:
- Re: backwards headers vs. C++0x
  - From: Jonathan Wakely

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