Xref: utzoo comp.lang.c:32914 comp.std.c:3770 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!orcenl!bengsig From: bengsig@oracle.nl (Bjorn Engsig) Newsgroups: comp.lang.c,comp.std.c Subject: How to ANSIfy (Was: Re: Just a minor new twist on free()) Message-ID: <1020@nlsun1.oracle.nl> Date: 16 Oct 90 18:34:04 GMT References: <4d5780ad.20b6d@apollo.HP.COM> <2612@van-bc.wimsey.bc.ca> Reply-To: bengsig@oracle.nl (Bjorn Engsig) Followup-To: comp.lang.c Organization: Oracle Europe, The Netherlands Lines: 18 In article pds@lemming.webo.dg.com (Paul D. Smith) writes: |Oh no! Not that! *Never* *ever* *change* the standard libraries which |ship with your compiler! Article <2612@van-bc.wimsey.bc.ca> by jtc@van-bc.wimsey.bc.ca (J.T. Conklin) says: |At UniFax, we ANSIfy the development environment on all of our |development machines. Header files get protoized and missing |functions get added to the C library. One way to do this, if the vendors headers just miss a few things, is to create your own standard header, make the corrections necessary and #include "/usr/include/whatever.h" in this one, and use -I to get your copy included in stead of the standard one. This, of course is not at all allowed by ANSI (the headers need not even be files), but it will do the trick on most Unix systems. -- Bjorn Engsig, E-mail: bengsig@oracle.com, bengsig@oracle.nl ORACLE Corporation From IBM: auschs!ibmaus!cs.utexas.edu!uunet!oracle!bengsig "Stepping in others footsteps, doesn't bring you ahead"