From: Rasmus Andersen <rasmus@jaquet.dk>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: __func__ in 2.5.33?
Date: Wed, 4 Sep 2002 08:34:37 +0200 [thread overview]
Message-ID: <20020904083436.A26538@jaquet.dk> (raw)
In-Reply-To: <3D752E38.EF352F48@zip.com.au>; from akpm@zip.com.au on Tue, Sep 03, 2002 at 02:48:40PM -0700
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
On Tue, Sep 03, 2002 at 02:48:40PM -0700, Andrew Morton wrote:
> The parenthesised (__func__) is there to force you to not try to
> perform this string pasting. Support for __FUNCTION__ pasting is
> being phased out of gcc.
>
> You need:
>
> #define func_enter() sx_dprintk (SX_DEBUG_FLOW, "sx: enter %s\n", __FUNCTION__)
Ah, OK. I apparently missed the part about the pasting part
being phased out, alongside missing Paul Larson's patch.
Thanks to both of you,
Rasmus
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-09-04 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 20:52 __func__ in 2.5.33? Rasmus Andersen
2002-09-03 21:48 ` Andrew Morton
2002-09-04 6:34 ` Rasmus Andersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-03 22:03 Paul Larson
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=20020904083436.A26538@jaquet.dk \
--to=rasmus@jaquet.dk \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.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