From owner-freebsd-hackers  Mon May  5 18:06:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA03303
          for hackers-outgoing; Mon, 5 May 1997 18:06:25 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA03296
          for <hackers@FreeBSD.ORG>; Mon, 5 May 1997 18:06:22 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id LAA20852; Tue, 6 May 1997 11:04:48 +1000
Date: Tue, 6 May 1997 11:04:48 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199705060104.LAA20852@godzilla.zeta.org.au>
To: bde@zeta.org.au, jkh@time.cdrom.com
Subject: Re: /usr/include/ftpio.h is not C++ safe
Cc: hackers@FreeBSD.ORG, nadav@barcode.co.il
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Now you might respond "ah, but I was speaking in generalities - I
>didn't mean libftpio specifically so much as I meant any library with
>headers in /usr/include", In which case I could only put my head in my
>hands at the thought of going through all those libraries and adding
>ANSI-variant prototypes, much less making them all C++ safe.

They all already support K&R except <dialog.h>, <ftpio.h>, <libdisk.h>,
<md2.h>, <md4.h>, <md5.h>, <ncurses.h>, <pcap.h>, <pcap-namedb.h>,
<strhash.h>, <unctrl.h>.  I.e., all except 0 CSRG-derived headers, 2
LBL-derived ones (pcap*), 3 Linux-derived ones (dialog, ncurses, unctrl)
and 6 jkh/phk headers (the rest) support K&R.

>I think it's a slippery slope you're trying to negotiate there, Bruce;
>watch your footing. ;-)

You're on the slope :-).

Bruce