Article View: comp.std.c
Article #5667Re: __STDC__ and non-conforming ANSI C compilers
From: Geoff Rimmer
Date: Mon, 23 Jan 1989 08:32
Date: Mon, 23 Jan 1989 08:32
25 lines
1200 bytes
1200 bytes
How about putting the following lines in /usr/include/local/__STDC__fix.h #ifdef __STDC__ #if __STDC__==0 #undef __STDC__ #endif #endif and then at the top of every source file, put #include <local/__STDC__fix.h> I know it's a bit messy, but it would work wouldn't it? Geoff ------------------------------------------------------------ Geoff Rimmer, Computer Science, Warwick University, England. geoff@uk.ac.warwick.emerald "I assure you Brad's presence here comes as a complete surprise" DIDN'T YOU READ THE SCRIPT? - Rocky Horror Picture Show, 1975 ------------------------------------------------------------
Technical Details
Message-ID:
<944@ubu.warwick.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!mcvax!ukc!warwick!geoffReferences:
<9391@smoke.BRL.MIL> <8731@megaron.arizona.edu> <9405@smoke.BRL.MIL> <860@auspex.UUCP> <9422@smoke.BRL.MIL>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!mcvax!ukc!warwick!geoff From: geoff@warwick.UUCP (Geoff Rimmer) Newsgroups: comp.std.c Subject: Re: __STDC__ and non-conforming ANSI C compilers Summary: solution to __STDC__==0 problem Message-ID: <944@ubu.warwick.UUCP> Date: 23 Jan 89 08:32:47 GMT References: <9391@smoke.BRL.MIL> <8731@megaron.arizona.edu> <9405@smoke.BRL.MIL> <860@auspex.UUCP> <9422@smoke.BRL.MIL> Sender: news@warwick.UUCP Reply-To: geoff@emerald.UUCP (Geoff Rimmer) Organization: Computer Science, Warwick University, UK Lines: 25