This is the mail archive of the gcc-bugs@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]
Other format:	[Raw text]

Re: c++/9923: Include file behaves differently

From: Nathan Sidwell <nathan at codesourcery dot com>
To: Steve Letter <letter at austin dot apc dot slb dot com>
Cc: nathan at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, sletter at slb dot com, gcc-gnats at gcc dot gnu dot org
Date: Mon, 03 Mar 2003 20:44:25 +0000
Subject: Re: c++/9923: Include file behaves differently
Organization: Codesourcery LLC
References: <20030303181625.2107.qmail@sources.redhat.com> <1046717537.15978.278.camel@twain.austin.apc.slb.com>

Steve Letter wrote:

Could you please explain why it isn't a bug?  It IS breaking a bunch of
our code.  We have to "wrap" the system header, so we have our own (that
includes the "real" header).

To help me work around this (not a bug) feature, could you explain (a
little ) what happens to cause this (not a bug) behavior?

read the manual about fixincludes and #include_next

nathan

--
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
         The voices in my head said this was stupid too
nathan at codesourcery dot com : http://www.cs.bris.ac.uk/~nathan/ : nathan at acm dot org

References:
- Re: c++/9923: Include file behaves differently
  - From: nathan
- Re: c++/9923: Include file behaves differently
  - From: Steve Letter

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