From: Zack Weinberg <zack@wolery.cumb.org>
To: Byron Stanoszek <gandalf@winds.org>
Cc: Geoff Keating <geoffk@cygnus.com>, gcc@gcc.gnu.org
Subject: Re: warning: pasting would not give a valid preprocessing token
Date: Wed, 06 Sep 2000 19:18:00 -0000 [thread overview]
Message-ID: <20000906191826.H31801@wolery.cumb.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0008121115410.7340-100000@winds.org>
On Sat, Aug 12, 2000 at 11:18:56AM -0400, Byron Stanoszek wrote:
> On Fri, 11 Aug 2000, Zack Weinberg wrote:
>
> > Very recent versions of gcc should not give that warning for the
> > specific case of , ## <rest argument>.
>
> Well, I just tried it on the August 11 snapshot. So unless you put in a patch
> over the night, it still issues those warnings.
A month later (apologies)... I believe this has now been fixed.
Please update and let me know if you still have problems. You want
this change:
2000-09-04 Jakub Jelinek <jakub@redhat.com>
* cpplex.c (ON_REST_ARG): Check VAR_ARGS flag of current context,
use posn - 1 to index into tokens array.
(maybe_paste_with_next): Adjust caller.
It may or may not be in the 2000-09-04 snapshot, but will be in the
-11 snapshot when that comes out.
zw
next prev parent reply other threads:[~2000-09-06 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2000-09-07 12:04 ` Byron Stanoszek
2000-09-11 21:44 ` Zack Weinberg
[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
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=20000906191826.H31801@wolery.cumb.org \
--to=zack@wolery.cumb.org \
--cc=gandalf@winds.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@cygnus.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).