From owner-freebsd-hackers  Wed May  7 04:21:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA17342
          for hackers-outgoing; Wed, 7 May 1997 04:21:02 -0700 (PDT)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA17320
          for <hackers@FreeBSD.ORG>; Wed, 7 May 1997 04:20:57 -0700 (PDT)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA09061; Wed, 7 May 1997 07:20:19 -0400
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed,  7 May 1997 07:20 EDT
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id GAA00186; Wed, 7 May 1997 06:56:21 -0400 (EDT)
Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id HAA03187; Wed, 7 May 1997 07:03:25 -0400 (EDT)
Date: Wed, 7 May 1997 07:03:25 -0400 (EDT)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199705071103.HAA03187@lakes.water.net>
To: michaelh@cet.co.jp, ponds!time.cdrom.com!jkh
Subject: Re: /usr/include/ftpio.h is not C++ safe
Cc: ponds!zeta.org.au!bde, ponds!FreeBSD.ORG!hackers,
        ponds!barcode.co.il!nadav, ponds!lambert.org!terry
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> On Mon, 5 May 1997, Jordan K. Hubbard 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.
> 
> Mike
> 
> 

 Well - here's a small uproar.  

 I run some older versions of software that I've had now for many years.
With every release of FreeBSD, I simply recompile it and off I go...

 I compile this code with -traditional, because of assumptions about 
parameter promotions...

 So, every new release I send out mail showing how I tripped over
some ANSIisms in our include file (e.g. "const".)

 Thus, even though we don't have to use a K&R compiler; and likely
never will - we may continue to have a need to compile K&R sources.

	- Dave Rivers -