From owner-freebsd-current Sun Apr 23 17:43:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (dyna225-140.nada.kth.se [130.237.225.140]) by hub.freebsd.org (Postfix) with ESMTP id 2D6D137BA29 for ; Sun, 23 Apr 2000 17:43:29 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id CAA06333; Mon, 24 Apr 2000 02:43:29 +0200 (CEST) (envelope-from assar) To: Matthew Dillon Cc: Bruce Evans , attila , freebsd-current@FreeBSD.ORG Subject: Re: __func__ not declared for kernel build (5.0-CURRENT) References: <200004231730.KAA62311@apollo.backplane.com> From: Assar Westerlund Date: 24 Apr 2000 02:43:28 +0200 In-Reply-To: Matthew Dillon's message of "Sun, 23 Apr 2000 10:30:20 -0700 (PDT)" Message-ID: <5lsnwcqqfj.fsf@assaris.sics.se> Lines: 14 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > 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. You mean outside a function? What's the proper way of dealing with that? > I wish these stupid standards committees would just choose > something that people are already using rather then make up new names! The problem is that __func__ and __FUNCTION__ are not the same thing. And thus it makes sense for them not the use same name. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message