From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Josh Triplett <josh@freedesktop.org>
Subject: Re: [PATCH] allow ifdef in macro arguments
Date: Sun, 21 Oct 2007 11:18:33 +0200 [thread overview]
Message-ID: <20071021091833.GB12794@ins.uni-bonn.de> (raw)
In-Reply-To: <70318cbf0710210207t587f8d2enf024a56e1d10a5df@mail.gmail.com>
Hello Christopher,
* Christopher Li wrote on Sun, Oct 21, 2007 at 11:07:15AM CEST:
> I think some one report it long time ago.
FWIW, embedding directives within macro arguments is not portable
(warned by with gcc -pedantic), and causes undefined behavior according
to C99:6.10.3p11.
Cheers,
Ralf
next prev parent reply other threads:[~2007-10-21 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 9:07 [PATCH] allow ifdef in macro arguments Christopher Li
2007-10-21 9:18 ` Ralf Wildenhues [this message]
2007-10-21 15:52 ` Al Viro
2007-10-22 0:03 ` Josh Triplett
2007-10-22 16:13 ` Christopher Li
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=20071021091833.GB12794@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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: 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 NNTP newsgroup(s).