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, nobody@gcc.gnu.org,
	rpm31@student.canterbury.ac.nz
Subject: Re: preprocessor/9764: Varargs macro extension incorrectly expands if the varargs argument is the macro itself
Date: Wed, 19 Feb 2003 23:48:00 -0000	[thread overview]
Message-ID: <20030219234850.5116.qmail@sources.redhat.com> (raw)

Synopsis: Varargs macro extension incorrectly expands if the varargs argument is the macro itself

State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Wed Feb 19 23:48:50 2003
State-Changed-Why:
    3.1 and later give the following, which is correct.  I've not checked 3.0, but I expect it's similar.
    
    $ cat /tmp/bar.c
    #define func(a, varargs...) _func(a, ##b)
    
    func(a, func(a, b));
    $ gcc -E /tmp/bar.c
    # 1 "/tmp/bar.c"
    # 1 "<built-in>"
    # 1 "<command line>"
    # 1 "/tmp/bar.c"
    
    
    /tmp/bar.c:3:19: pasting "," and "b" does not give a valid preprocessing token
    _func(a,b);

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


             reply	other threads:[~2003-02-19 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 23:48 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-20  6:56 Neil Booth
2003-02-20  0:06 Ryan Mallon
2003-02-19 22:16 rpm31

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=20030219234850.5116.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=nobody@gcc.gnu.org \
    --cc=rpm31@student.canterbury.ac.nz \
    /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).