From owner-freebsd-hackers Tue May 6 19:27:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA24423 for hackers-outgoing; Tue, 6 May 1997 19:27:09 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA24417 for ; Tue, 6 May 1997 19:27:06 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id CAA14402; Wed, 7 May 1997 02:26:34 GMT Date: Wed, 7 May 1997 11:26:34 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: jkh@time.cdrom.com, bde@zeta.org.au, nadav@barcode.co.il, hackers@FreeBSD.ORG Subject: Re: /usr/include/ftpio.h is not C++ safe In-Reply-To: <199705061651.JAA18643@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 6 May 1997, Terry Lambert wrote: > > > I hate __P() and will fight a guerilla war against it if I have to. > > > > So do I. I'd do it in straight ANSI first and then if there's an uproar > > of people who can provide details of their K&R applications that require > > __P() then you can begrudgingly add it later. > > Cool. You guys sound like Sun Microsystems statistically adressing > sev 1 bugs. On the contrary, a consistent interface exclusively tailored for new code reduces the spec and this increases the chances of delivering bug free code for the class of new apps that would use the lib. Regards, Mike Hancock