This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Something's wrong with recent g++ include files
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Subject: Re: Something's wrong with recent g++ include files
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 04 Dec 2000 23:44:16 -0200
- Cc: gcc-bugs at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <200012040059.eB40xhu24078@fillmore.constant.com>
On Dec 3, 2000, Benjamin Kosnik <bkoz@redhat.com> wrote:
> These parts of the library are deprecated: using them should be
> too. To be fair, we're allowing the deprecated parts with the explicit
> use and acknowledgment of -I./backward.
Removing the headers from the standard search path isn't the only way
to deprecate something. IMO, when something is deprecated, it should
trigger a warning, not simply fail to compile.
How about finding the headers by default, but having them emit a
#warning indicating the header is deprecated and shouldn't be relied
upon? Then, we can move them out of the default search path in future
versions without getting blamed for breaking thousands of programs
without warning.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me