This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: backward -> deprecated
- To: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>
- Subject: Re: backward -> deprecated
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Date: Sun, 1 Apr 2001 15:09:09 +0100
- Cc: Benjamin Kosnik <bkoz at redhat dot com>, libstdc++ at gcc dot gnu dot org
- References: <200104010057.f310vBJ07927@waller.constant.com> <flhf08hiol.fsf@sel.cmla.ens-cachan.fr>
Gabriel Dos Reis wrote:-
> | Phil, Alexandre, and Jason have all indicated some kind of warning for
> | using the backward headers, unless a specific (already existing)
> | warning flag is used. To me, this means some kind of macro definition
> | triggered via this flag (done in cpp a la _EXCEPTIONS)
> |
> | Then, we could add a third directory to the g++ include search patch
> | (a la the target include work) for backward headers, search it, and
> | install the contents of the backward directory into it.
> |
> | Sound reasonable? Other approaches that I've missed that would be easier?
>
> Your proposal sounds reasonable to me. I'm not a cpplib guru so I
> guess we'll need Neil's input as to how to proceed.
Sorry, I've missed this thread apart from what's quoted here. What
advice exactly are you looking for? I don't quite understand all this
about a warning flag and a macro definition. Could you give a trivial
example?
Neil.