Date: Wed, 7 May 1997 06:41:18 -0400 (EDT) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!zeta.org.au!bde, bde@zeta.org.au, ponds!time.cdrom.com!jkh Cc: ponds!FreeBSD.ORG!hackers, ponds!barcode.co.il!nadav Subject: Re: /usr/include/ftpio.h is not C++ safe Message-ID: <199705071041.GAA03145@lakes.water.net>
next in thread | raw e-mail | index | archive | help
> > >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. Oops - what about netdb.h and uses of 'const', etc... (which should work, but apparently don't.) > > >I think it's a slippery slope you're trying to negotiate there, Bruce; > >watch your footing. ;-) > > You're on the slope :-). I think we're all there :-) > > Bruce >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705071041.GAA03145>