public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: John Marshall <jmarshall@acm.org> To: neil@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/5153: #include path not affected by #line in cpplib Date: Sun, 24 Feb 2002 12:22:00 -0000 [thread overview] Message-ID: <20020224201602.696.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/5153; it has been noted by GNATS. From: John Marshall <jmarshall@acm.org> To: neil@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: preprocessor/5153: #include path not affected by #line in cpplib Date: Sun, 24 Feb 2002 21:08:24 +0100 On Sat, Feb 23, 2002 at 04:30:15PM -0000, neil@gcc.gnu.org wrote: > 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. I still agree with Andreas [1] that the old behaviour is more self-consistent > Since the old behaviour [...] can > often, if not always, be obtained with an extra -I switch (like I mentioned in the original bug report :-)), but all I really wanted to do was get the change in behaviour mentioned in GNATS and/or the documentation, so the next person who runs into this has more to go on. Thanks for looking into this. John [1] http://gcc.gnu.org/ml/gcc-bugs/1999-06n/msg00098.html
next reply other threads:[~2002-02-24 20:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-24 12:22 John Marshall [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-23 9:56 neil 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=20020224201602.696.qmail@sources.redhat.com \ --to=jmarshall@acm.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=neil@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).