From owner-freebsd-current Sun Apr 23 10:30:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B46C437B688 for ; Sun, 23 Apr 2000 10:30:26 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA62311; Sun, 23 Apr 2000 10:30:20 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 10:30:20 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231730.KAA62311@apollo.backplane.com> To: Bruce Evans Cc: attila , freebsd-current@FreeBSD.ORG Subject: Re: __func__ not declared for kernel build (5.0-CURRENT) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message