From: jtv <jtv@xs4all.nl>
To: Greg KH <greg@kroah.com>
Cc: Vladimir Kondratiev <vladimir.kondratiev@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: __FUNCTION__
Date: Wed, 9 Jan 2002 00:42:48 +0100 [thread overview]
Message-ID: <20020109004248.C26154@xs4all.nl> (raw)
In-Reply-To: <3C3B664B.3060103@intel.com> <20020108220149.GA15816@kroah.com> <20020108235649.A26154@xs4all.nl> <20020108231147.GA16313@kroah.com>
In-Reply-To: <20020108231147.GA16313@kroah.com>; from greg@kroah.com on Tue, Jan 08, 2002 at 03:11:47PM -0800
On Tue, Jan 08, 2002 at 03:11:47PM -0800, Greg KH wrote:
>
> Any reason _why_ they would want to break tons of existing code in this
> manner? Just the fact that the __func__ symbol is there to use?
At a guess, it probably gives the gcc folks some more leeway as to where
they implement the feature relative to string constant concatenation and
such. If that is indeed the case, it could lead to cleaner code.
> Since the C99 spec does not state anything about __FUNCTION__, changing
> it from the current behavior does not seem like a wise thing to do.
I'm pretty sure it's got to be in there somewhere--it was in the summary I
read at the time. :)
Jeroen
next prev parent reply other threads:[~2002-01-08 23:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 21:36 __FUNCTION__ Vladimir Kondratiev
2002-01-08 21:59 ` __FUNCTION__ Ian S. Nelson
2002-01-08 22:17 ` __FUNCTION__ Greg KH
2002-01-08 23:09 ` __FUNCTION__ Vladimir Kondratiev
2002-01-08 22:01 ` __FUNCTION__ Greg KH
2002-01-08 22:56 ` __FUNCTION__ jtv
2002-01-08 23:11 ` __FUNCTION__ Greg KH
2002-01-08 23:39 ` __FUNCTION__ David Weinehall
2002-01-08 23:51 ` __FUNCTION__ Andrew Morton
2002-01-09 0:04 ` __FUNCTION__ David Weinehall
2002-01-09 0:14 ` __FUNCTION__ Andrew Morton
2002-01-09 0:23 ` __FUNCTION__ Anton Altaparmakov
2002-01-08 23:42 ` jtv [this message]
2002-01-09 2:12 ` __FUNCTION__ Richard Henderson
2002-01-09 7:23 ` __FUNCTION__ Greg KH
2002-01-09 7:32 ` __FUNCTION__ Neil Booth
2002-01-09 22:35 ` __FUNCTION__ Richard Henderson
2002-01-09 9:05 ` __FUNCTION__ Martin Dalecki
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=20020109004248.C26154@xs4all.nl \
--to=jtv@xs4all.nl \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vladimir.kondratiev@intel.com \
/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