Date: Tue, 29 Apr 1997 12:59:56 -0400 (EDT) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!lakes.water.net!rivers, ponds!opus.cts.cwu.edu!skynyrd Cc: ponds!freefall.cdrom.com!freebsd-hackers Subject: Re: netdb.h and -traditional. Message-ID: <199704291659.MAA01192@lakes.water.net>
next in thread | raw e-mail | index | archive | help
Chris Timmons writes: > > Could you say something like 'gcc -traditional -Dconst=""' to make them > disappear before the compiler sees them? Sure - which is exactly what I did for this particular instance. My "meta-question" is - should I have to do that, or are we going to support compiling older non-ANSI sources? > Aside from a user-hack of this > class I can't say I would be for mangling our include files any more than > they are already. > > You could probably lock yourself in a room with the O'Reilley perl and > regex books for a while and come up with some patterns to transform your > sources to be more reasonable wrt ISO c (which would be a better > investment in time spent :) Protoize, cproto and some other tools are available for this - so it's not a big problem... I just prefer that things keep compiling with newer releases, unchanged. Although, I recognize that change is going to be needed sooner or later or nothing moves forward... my philosphy is "break as little as possible." Also, if you look back in the mail archives; you'll see I run into this problem about once every 14 months or so... > > -Chris > > > On Mon, 28 Apr 1997, Thomas David Rivers wrote: > > > > > I was attempting to compile some older non-ANSI programs, that > > require the -traditional option on GCC. > > > > Unfortunately, netdb.h (and possibly other headers) use ANSI > > keywords (notably - 'const') which breaks this. > > > > Should our header files be compilable by non-ANSI compilers? > > > > - Dave Rivers - > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704291659.MAA01192>