public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9923: Include file behaves differently
Date: Mon, 03 Mar 2003 19:36:00 -0000	[thread overview]
Message-ID: <20030303193601.17848.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

The following reply was made to PR c++/9923; it has been noted by GNATS.

From: Andreas Schwab <schwab@suse.de>
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:26:51 +0100

 Steve Letter <letter@austin.apc.slb.com> writes:
 
 |> 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).
 
 Name the wrappers differently.
 
 Andreas.
 
 -- 
 Andreas Schwab, SuSE Labs, schwab@suse.de
 SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
 Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
 "And now for something completely different."


             reply	other threads:[~2003-03-03 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 19:36 Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-03 20:46 Nathan Sidwell
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=20030303193601.17848.qmail@sources.redhat.com \
    --to=schwab@suse.de \
    --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: link
Be 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).