From: Harvey Harrison <harvey.harrison@gmail.com>
To: Yoann Padioleau <padator@wanadoo.fr>
Cc: Johannes Berg <johannes@sipsolutions.net>,
mosfet <forumer@smartmobili.com>,
linux-sparse@vger.kernel.org, Julia Lawall <julia@diku.dk>
Subject: Re: source code transform
Date: Thu, 08 Jan 2009 16:38:56 -0800 [thread overview]
Message-ID: <1231461536.5715.31.camel@brick> (raw)
In-Reply-To: <87skntqs5e.fsf@aryx.cs.uiuc.edu>
On Thu, 2009-01-08 at 17:45 -0600, Yoann Padioleau wrote:
> Johannes Berg <johannes@sipsolutions.net> writes:
> @@
> identifier f;
> @@
>
> f(...)
> {
> + fprintf(stderr, "%s: %s()\n", __FILE__, __FUNCTION__);
> ...
> }
>
Personal pet-peeve, use __func__, not __FUNCTION__.
__func__ is C, __FUNCTION__ is a gcc-extension.
Cheers,
Harvey
next prev parent reply other threads:[~2009-01-09 0:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 18:48 source code transform mosfet
2009-01-07 19:03 ` Johannes Berg
2009-01-08 7:52 ` Nicholas Mc Guire
2009-01-08 23:45 ` Yoann Padioleau
2009-01-09 0:38 ` Harvey Harrison [this message]
2009-01-09 17:06 ` Yoann Padioleau
2009-01-31 23:37 ` H. Peter Anvin
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=1231461536.5715.31.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=forumer@smartmobili.com \
--cc=johannes@sipsolutions.net \
--cc=julia@diku.dk \
--cc=linux-sparse@vger.kernel.org \
--cc=padator@wanadoo.fr \
/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).