public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Byron Stanoszek <gandalf@winds.org>
To: Neil Booth <NeilB@earthling.net>
Cc: geoffk@cygnus.com, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
	jakub@redhat.com
Subject: Re: warning: pasting would not give a valid preprocessing token
Date: Fri, 15 Sep 2000 16:53:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0009151952090.28656-100000@winds.org> (raw)
In-Reply-To: <20000914235302.A9969@daikokuya.demon.co.uk>

On Thu, 14 Sep 2000, Neil Booth wrote:

> Byron,
> 
> I hope this fixes it for you.  I'm bootstrapping now, and will then
> run the testsuite.

This works like a charm. Thanks for the speedy bugfix!

 -Byron

> 	* cpplex.c (ON_REST_ARG): Correct the test.
> 	(maybe_paste_with_next): Duplicate a token that fail pasting,
> 	and clear its PASTE_LEFT flag, so that nested pasting attempts
> 	do not occur.
> 	* gcc.dg/cpp/paste10.c: Testcase.

-- 
Byron Stanoszek                         Ph: (330) 644-3059
Systems Programmer                      Fax: (330) 644-8110
Commercial Timesharing Inc.             Email: bstanoszek@comtime.com

  parent reply	other threads:[~2000-09-15 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000914185040.A12722@daikokuya.demon.co.uk>
     [not found] ` <Pine.LNX.4.21.0009141510140.21092-201000@winds.org>
2000-09-14 15:53   ` Neil Booth
2000-09-14 16:02     ` Neil Booth
2000-09-14 16:08     ` Jeffrey A Law
2000-09-15 16:53     ` Byron Stanoszek [this message]
2000-08-11 20:41 Byron Stanoszek
2000-08-11 20:46 ` Geoff Keating
2000-08-11 20:58   ` Byron Stanoszek
2000-08-11 23:31     ` Zack Weinberg
2000-08-12  8:19       ` Byron Stanoszek
2000-09-06 19:18         ` Zack Weinberg
2000-09-07 12:04           ` Byron Stanoszek
2000-09-11 21:44             ` Zack Weinberg

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=Pine.LNX.4.21.0009151952090.28656-100000@winds.org \
    --to=gandalf@winds.org \
    --cc=NeilB@earthling.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@cygnus.com \
    --cc=jakub@redhat.com \
    /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).