public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jmarshall@acm.org,
	neil@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: preprocessor/5153: #include path not affected by #line in cpplib
Date: Sat, 23 Feb 2002 09:56:00 -0000	[thread overview]
Message-ID: <20020223163015.19178.qmail@sources.redhat.com> (raw)

Synopsis: #include path not affected by #line in cpplib

Responsible-Changed-From-To: unassigned->neil
Responsible-Changed-By: neil
Responsible-Changed-When: Sat Feb 23 08:30:14 2002
Responsible-Changed-Why:
    Mine.  Thanks for your bug report.
State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Sat Feb 23 08:30:14 2002
State-Changed-Why:
    After some discussion of a patch that I originally submitted to revert this behaviour here:
    
    http://gcc.gnu.org/ml/gcc-patches/2002-02/msg01470.html
    
    we decided to retain the current behaviour.  The above link starts a thread that also references other mails where the old behaviour was considered to be a bug.  Since the old behaviour had the potential for much confusion (see referenced mails), and which can often, if not always, be obtained with an extra -I switch, we have decided the current semantics are the lesser evil.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5153


             reply	other threads:[~2002-02-23 16:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  9:56 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-24 12:22 John Marshall
2001-12-18 16:16 Zack Weinberg
2001-12-18 15:16 Neil Booth
2001-12-18  6:46 John Marshall

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=20020223163015.19178.qmail@sources.redhat.com \
    --to=neil@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jmarshall@acm.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).