From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>,
jt@hpl.hp.com, Jeff Garzik <jgarzik@mandrakesoft.com>,
thunder@lightweight.ods.org, linux-kernel@vger.kernel.org
Subject: Re: FW: 2.5.34: IR __FUNCTION__ breakage
Date: Fri, 20 Sep 2002 15:11:09 -0700 [thread overview]
Message-ID: <20020920221109.GA9184@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020920214138.GA9638@daikokuya.co.uk>
On Fri, Sep 20, 2002 at 10:41:38PM +0100, Neil Booth wrote:
> Bjoern A. Zeeb wrote:-
>
> > > > Also, specifically relating to varargs macros as described above, you
> > > > can certainly have a varargs macro with zero args, just look at C99
> > > > varargs macros...
> > >
> > > I remember that it didn't work. Ok, I'll try again.
> >
> > if I remember corretly with C99 if you do s.th. like this (simple
> > sample):
> >
> > #define LOG(level, format, ...) \
> > log(level, format, ##__VA_ARGS__);
>
> No, this is only valid C99 if __VA_ARGS__ is the empty list.
>
> I posted the correct way to write this macro about a week ago that
> works with all versions of GCC (and follows their documented
> behaviour; this stuff *is* all documented).
>
> Neil.
Err... Can you point me to your post ?
Jean
next prev parent reply other threads:[~2002-09-20 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MNEMKBGMDIMHCBHPHLGPMEEDDDAA.dag@brattli.net>
2002-09-20 17:13 ` Jean Tourrilhes
2002-09-20 17:17 ` Jeff Garzik
2002-09-20 17:19 ` Jean Tourrilhes
2002-09-20 18:10 ` Bjoern A. Zeeb
2002-09-20 21:41 ` Neil Booth
2002-09-20 22:11 ` Jean Tourrilhes [this message]
2002-09-20 17:25 ` Thunder from the hill
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=20020920221109.GA9184@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=bzeeb-lists@lists.zabbadoz.net \
--cc=jgarzik@mandrakesoft.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@daikokuya.co.uk \
--cc=thunder@lightweight.ods.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
all inboxes | Powered by JetHome®