This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: backward -> deprecated
- To: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Subject: Re: backward -> deprecated
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Thu, 5 Apr 2001 22:15:25 -0700 (PDT)
- cc: jason at redhat dot com, libstdc++ at gcc dot gnu dot org
Hey Neil, thanks for getting back to me. Hopefully what I'm trying to do
is clear now.
> > Part one: Put libstdc++-v3/include/backward headers into separate
> > backwards directory when installing.
> > http://gcc.gnu.org/ml/gcc-patches/2001-04/msg00339.html
> > http://gcc.gnu.org/ml/gcc-patches/2001-04/msg00341.html
Ok. Can I go ahead and check these patches in?
> Ah. I bet that #warning in system headers is suppressed because we
> suppress warnings generated in system headers. Ugh. This diagnostic
> suppression business just continues to get uglier.
>
> It shouldn't be too hard to fix, though. Give me a day or two.
Ok. I also realized that _GXX_DEPRECATED should just be __DEPRECATED,
because -Wno-deprecated isn't a C++ flag. Other than that, and the fact
that
backward_warning.h
can just
#ifndef already_seen
#define already_seen 1
do-warning-stuff
#endif
or whatever
and have the warning appear only once per translation unit, is this the
shape that the patch should take? Should I check it in (with those mods)?
thanks,
benjamin