From owner-freebsd-arch Wed Jan 30 23:56:18 2002 Delivered-To: freebsd-arch@freebsd.org Received: from badboy.mail.pas.earthlink.net (badboy.mail.pas.earthlink.net [207.217.120.20]) by hub.freebsd.org (Postfix) with ESMTP id 97D3637B400 for ; Wed, 30 Jan 2002 23:56:15 -0800 (PST) Received: from harrier.mail.pas.earthlink.net ([207.217.120.12] helo=harrier.prod.itd.earthlink.net) by badboy.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16WC0m-0007fB-00 for arch@freebsd.org; Wed, 30 Jan 2002 23:52:00 -0800 Received: from pool0237.cvx21-bradley.dialup.earthlink.net ([209.179.192.237] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WC0d-0004oF-00; Wed, 30 Jan 2002 23:51:51 -0800 Message-ID: <3C58F78E.3F66EA8E@mindspring.com> Date: Wed, 30 Jan 2002 23:51:42 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok/asmodai Cc: Kirk McKusick , arch@FreeBSD.ORG, Peter Wemm , Poul-Henning Kamp , Dallas De Atley , Jordan Hubbard , "Perry E. Metzger" , "Todd C. Miller" , Theo de Raadt Subject: Re: __P macro question References: <68578.1012450924@winston.freebsd.org> <200201310701.g0V71Ci75803@beastie.mckusick.com> <20020131072933.GQ22384@daemon.ninth-circle.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jeroen Ruigrok/asmodai wrote: > Which items can we identify to tackle in this effort? > > - Get rid of __P() macros in source files > - Use proper ANSI prototypes, this flows from the point above > > what else? Other candidates are other macros in cdefs.h; because of the __attribute stuff, I would be loathe to get rid of it entirely, since it encapsulates some GCC dependence/independence, but the const/void/volatile definitions are a possibility. There are also the varradic function declarations, which are not all ANSI-C style, yet, use of __STRING and __CONCAT, etc.. My recommendation would be to do __P() first, now that there is a cross-BSD consensus, and leave other changes for other discussions. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message