Date: Sun, 23 Apr 2000 10:30:20 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Bruce Evans <bde@zeta.org.au> Cc: attila <attila@hun.org>, freebsd-current@FreeBSD.ORG Subject: Re: __func__ not declared for kernel build (5.0-CURRENT) Message-ID: <200004231730.KAA62311@apollo.backplane.com> References: <Pine.BSF.4.21.0004232323020.2928-100000@alphplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:On Sat, 22 Apr 2000, attila! wrote:
:
:> '__func__ is not found for either the 'GENERIC' or 'hun' target.
:
:__func__ is a new feature in C99. It is an alias for the gcc feature
:__FUNCTION_NAME. Both give the name of the current function as a string.
:
:This feature should not be used until C99 becomes Normal, if ever.
:Using it breaks portability. It apparently even breaks compiling
:current kernels with the version of gcc in FreeBSD-3.4. I think
:__func__ was added in egcs (the Changelog entry for adding it in gcc
:is dated Dec 1 1998).
:
:Bruce
You mean __FUNCTION__ ?
__FILE__ and __LINE__ have been standard for a long time. The
obviously missing __FUNCTION__ was added by GCC many years ago, but it was
a while before it's use in defines in header (.h) files was dealt with
properly. I wish these stupid standards committees would just choose
something that people are already using rather then make up new names!
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004231730.KAA62311>