From owner-freebsd-hackers Mon May 5 14:13:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20658 for hackers-outgoing; Mon, 5 May 1997 14:13:38 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20653 for ; Mon, 5 May 1997 14:13:36 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id OAA07634; Mon, 5 May 1997 14:13:49 -0700 (PDT) To: Bruce Evans cc: nadav@barcode.co.il, hackers@FreeBSD.ORG Subject: Re: /usr/include/ftpio.h is not C++ safe In-reply-to: Your message of "Tue, 06 May 1997 06:09:16 +1000." <199705052009.GAA09324@godzilla.zeta.org.au> Date: Mon, 05 May 1997 14:13:48 -0700 Message-ID: <7632.862866828@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Don't pollute new code with the __P() gunge. It just makes it harder > >to read and there are no compilers we need to use which do not accept > >full ANSI prototypes. > > Headers in /usr/include should support K&R since they may be used with > old code. "May be" just isn't strong enough for this man, and I thought we already went over all of this just a few weeks ago in core! I certainly do not intend on adding __P() garbage to any header file I'm responsible for, that's for sure. Jordan