From owner-freebsd-hackers Mon May 5 13:53:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA19255 for hackers-outgoing; Mon, 5 May 1997 13:53:10 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA19249 for ; Mon, 5 May 1997 13:53:06 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA16529; Mon, 5 May 1997 13:49:35 -0700 From: Terry Lambert Message-Id: <199705052049.NAA16529@phaeton.artisoft.com> Subject: Re: /usr/include/ftpio.h is not C++ safe To: bde@zeta.org.au (Bruce Evans) Date: Mon, 5 May 1997 13:49:35 -0700 (MST) Cc: jkh@time.cdrom.com, nadav@barcode.co.il, hackers@FreeBSD.ORG In-Reply-To: <199705052009.GAA09324@godzilla.zeta.org.au> from "Bruce Evans" at May 6, 97 06:09:16 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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. Yes. They are not platform specific. The UCB license was used precisely to allow this sort of code-grabbing and use on non-FreeBSD platforms. In addition, there are cases where old code must be compiled with the -traditional flag (I think this is what Bruce was meaning here) because of existing calling conventions in the code, and the lack of a prototype in scope at the time of inter-object calling in the old code itself. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.