From owner-freebsd-hackers Sat Aug 7 20:45:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9C1F314C3B for ; Sat, 7 Aug 1999 20:45:17 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id UAA02767; Sat, 7 Aug 1999 20:42:11 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id UAA01179; Sat, 7 Aug 1999 20:42:11 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 7 Aug 1999 20:42:11 -0700 (PDT) Message-Id: <199908080342.UAA01179@vashon.polstra.com> To: billf@jade.chc-chimes.com Subject: Re: prototypes with __P In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Bill Fumerola wrote: > On Fri, 6 Aug 1999, Matthew Hunt wrote: > > > I have no idea how much of the FreeBSD code would actually build on > > a K&R compiler. > > Thanks to Bruce, a lot of it. Note, the use of __P is discouraged in new code. From style(9): Only use the __P macro from the include file if the source file in general is (to be) compilable with a K&R Old testament compiler. Use of the __P macro in new code is discouraged, although modifications to existing files should be consistent with that file's conventions. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message