From owner-freebsd-hackers  Mon May  5 21:50:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA14751
          for hackers-outgoing; Mon, 5 May 1997 21:50:52 -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 VAA14735
          for <hackers@FreeBSD.ORG>; Mon, 5 May 1997 21:50:46 -0700 (PDT)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA25288; Tue, 6 May 1997 00:50:15 -0400
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue,  6 May 1997 00:50 EDT
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id UAA16913; Mon, 5 May 1997 20:57:57 -0400 (EDT)
Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id VAA29952; Mon, 5 May 1997 21:04:56 -0400 (EDT)
Date: Mon, 5 May 1997 21:04:56 -0400 (EDT)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199705060104.VAA29952@lakes.water.net>
To: ponds!time.cdrom.com!jkh, ponds!lambert.org!terry
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
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > > How can libftpio be used by code which must be compiled -traditional,
> > > without __P()?
> > 
> > And why would you want to compile libftpio with -traditional?
> > I read the paragraph where you say:
> > 
> > 	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.
> > 
> > And I still don't see where this is applicable in this case at all.
> 
> You're still missing my (and I think Bruce's) meaning here.
> 
> I *don't* want to compile libftpio -traditional.  I want to add
> "#include ftpio.h" and link libftpio to an older application which
> must be compiled -traditional.  To do that, the header must be
> compilable with -traditional (ie: it needs __P()).
> 

 Didn't I just post about that *exact* situation two weeks ago :-)

 We already have the problem in our /usr/include files.

 Personally, I still have older code which has yet to be protoized,
which may/may not want to enjoy the fruits of ftpio (or some other
newer library).  It would be nice not to have to rework things too much
just to enhance older stuff...

 This, of course, is countered with being dragged kinking-and-screaming
into the 1980s... :-) :-)  maybe it's time to rework that code...

	- Dave Rivers -