From: Martin Dalecki <dalecki@evision-ventures.com>
To: Greg KH <greg@kroah.com>
Cc: jtv <jtv@xs4all.nl>,
Vladimir Kondratiev <vladimir.kondratiev@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: __FUNCTION__
Date: Wed, 09 Jan 2002 10:05:21 +0100 [thread overview]
Message-ID: <3C3C07D1.4090209@evision-ventures.com> (raw)
In-Reply-To: <3C3B664B.3060103@intel.com> <20020108220149.GA15816@kroah.com> <20020108235649.A26154@xs4all.nl> <20020108231147.GA16313@kroah.com>
Greg KH wrote:
>On Tue, Jan 08, 2002 at 11:56:49PM +0100, jtv wrote:
>
>>Don't have a C99 spec, but here's what info gcc has to say about it:
>>
>>[...description of "function names" extension as currently found in gcc...]
>>
>> Note that these semantics are deprecated, and that GCC 3.2 will
>>handle `__FUNCTION__' and `__PRETTY_FUNCTION__' the same way as
>>`__func__'. `__func__' is defined by the ISO standard C99:
>>
>
>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?
>
String constant coalescing chances. It is a good thing. Anobody who used
__FUNCTION__ which was
neither a proper preprocessor constant nor a proper variable
semantically was in problem.
prev parent reply other threads:[~2002-01-09 9:17 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 ` __FUNCTION__ jtv
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 ` Martin Dalecki [this message]
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=3C3C07D1.4090209@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=greg@kroah.com \
--cc=jtv@xs4all.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.