From owner-freebsd-current Sun Apr 23 20:35:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhop1.nyroc.rr.com (mailhop1-1.nyroc.rr.com [24.92.226.166]) by hub.freebsd.org (Postfix) with ESMTP id 7248437BAC3 for ; Sun, 23 Apr 2000 20:35:27 -0700 (PDT) (envelope-from leisner@rochester.rr.com) Received: from mailout1.nyroc.rr.com ([24.92.226.81]) by mailhop1.nyroc.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with ESMTP id com; Sun, 23 Apr 2000 23:32:09 -0400 Received: from mail2.nyroc.rr.com ([24.92.226.75]) by mailout1.nyroc.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with ESMTP id com; Sun, 23 Apr 2000 23:35:13 -0400 Received: from rochester.rr.com ([24.93.17.24]) by mail2.nyroc.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Sun, 23 Apr 2000 23:35:13 -0400 Received: from soyata.home (IDENT:leisner@localhost [127.0.0.1]) by rochester.rr.com (8.9.3/8.8.5) with ESMTP id XAA06306; Sun, 23 Apr 2000 23:35:20 -0400 Message-Id: <200004240335.XAA06306@rochester.rr.com> X-Mailer: exmh version 2.1.0 09/18/1999 Reply-To: leisner@rochester.rr.com To: Assar Westerlund Cc: Matthew Dillon , Bruce Evans , attila , freebsd-current@FreeBSD.ORG, leisner@rochester.rr.com Subject: Re: __func__ not declared for kernel build (5.0-CURRENT) In-reply-to: Your message of "24 Apr 2000 02:43:28 +0200." <5lsnwcqqfj.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Apr 2000 23:35:20 -0400 From: "Marty Leisner" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Assar Westerlund writes on 24 Apr 2000 02:43:28 +0200 > 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. > What's different about them? __func__ was defined in aztec C nearly two decades ago...I really looked the appearance of a __func__ pseudomacro -- it made lots of stuff much easier to understand (as opposed to __FILE__/__LINE__) -- but __func__ had to be handled by the translater, not the preprocessor... > /assar > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message