public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: asbrown@ati.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: preprocessor/3852: cpp: parantheses wrong in variable argument macros Date: Sat, 28 Jul 2001 03:58:00 -0000 [thread overview] Message-ID: <20010728105822.10529.qmail@sourceware.cygnus.com> (raw) Synopsis: cpp: parantheses wrong in variable argument macros State-Changed-From-To: open->closed State-Changed-By: neil State-Changed-When: Sat Jul 28 03:58:21 2001 State-Changed-Why: 3.0 gives the much prettier:- $ cpp /tmp/test.c # 9 "/tmp/test.c" void main() { (0); (0, (0)); (0, 0); (0); } which is what I imagine you wanted. It's good to know this is fixed; I didn't realise there were bugs in 2.95.2 macro varargs. 3.0 is completely rewritten from scratch. Yours is an interesting testcase. Do you mind if I butcher it into test suite form? Neil. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3852&database=gcc
next reply other threads:[~2001-07-28 3:58 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-28 3:58 neil [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-27 19:16 asbrown
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=20010728105822.10529.qmail@sourceware.cygnus.com \ --to=neil@gcc.gnu.org \ --cc=asbrown@ati.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.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: 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).