public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9923: Include file behaves differently Date: Mon, 03 Mar 2003 20:46:00 -0000 [thread overview] Message-ID: <20030303204601.31016.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9923; it has been noted by GNATS. From: Nathan Sidwell <nathan@codesourcery.com> To: Steve Letter <letter@austin.apc.slb.com> Cc: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sletter@slb.com, gcc-gnats@gcc.gnu.org Subject: Re: c++/9923: Include file behaves differently Date: Mon, 03 Mar 2003 20:44:25 +0000 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@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next reply other threads:[~2003-03-03 20:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-03 20:46 Nathan Sidwell [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-03 19:36 Andreas Schwab 2003-03-03 19:06 Steve Letter 2003-03-03 18:16 nathan 2003-03-03 17:56 sletter
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030303204601.31016.qmail@sources.redhat.com \ --to=nathan@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).