Xref: utzoo comp.lang.c:33002 comp.std.c:3801 Newsgroups: comp.lang.c,comp.std.c Path: utzoo!telly!druid!darcy From: darcy@druid.uucp (D'Arcy J.M. Cain) Subject: Re: Just a minor new twist on free() Organization: D'Arcy Cain Consulting, West Hill, Ontario Date: Fri, 19 Oct 90 16:15:18 GMT Message-ID: <1990Oct19.161518.23638@druid.uucp> References: <2612@van-bc.wimsey.bc.ca> In article pds@lemming.webo.dg.com (Paul D. Smith) writes: Seems an attribution was left off but looks like ?@van-bc.wimsey.bc.ca said: >[] In article pds@lemming.webo.dg.com (Paul D. Smith) writes: >[] >Oh no! Not that! *Never* *ever* *change* the standard libraries which > >[] At UniFax, we ANSIfy the development environment on all of our > >I'd say all this falls under the "unless they don't work" category! :-) >Even so, as has already been mentioned, there are probably better ways >of doing it than changing the standard includes. > When I installed gcc on my system I modified it to look in /usr/newinclude for headers and then in /usr/include if not found. I then copied header files into the new directory and modified them. This leaves the original header files untouched and in fact cc will still work if necessary using the old header files. What's the point of having an ANSI compiler if you don't have the ANSI standard prototypes? -- D'Arcy J.M. Cain (darcy@druid) | D'Arcy Cain Consulting | I support gun control. West Hill, Ontario, Canada | Let's start with the government! + 416 281 6094 |