Article View: comp.std.c
Article #5627Re: __STDC__ and non-conforming ANSI C compilers
From: Peter da Silva
Date: Thu, 19 Jan 1989 22:51
Date: Thu, 19 Jan 1989 22:51
16 lines
965 bytes
965 bytes
If you really want to survive __STDC__==0, then here's a workable solution... (1) Use "#if __STDC__" throughout. (2) AT the beginning of your program, put this: #ifndef __STDC__ #define __STDC__ 0 #endif This will mean you will always have __STDC__ defined as 0 or 1. -- Peter da Silva, Xenix Support, Ferranti International Controls Corporation. Work: uunet.uu.net!ficc!peter, peter@ficc.uu.net, +1 713 274 5180. `-_-' Home: bigtex!texbell!sugar!peter, peter@sugar.uu.net. 'U` Opinions may not represent the policies of FICC or the Xenix Support group.
Technical Details
Message-ID:
<2820@ficc.uu.net>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!ficc!peterReferences:
<9391@smoke.BRL.MIL> <8731@megaron.arizona.edu> <9405@smoke.BRL.MIL> <9422@smoke.BRL.MIL>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.std.c Subject: Re: __STDC__ and non-conforming ANSI C compilers Message-ID: <2820@ficc.uu.net> Date: 19 Jan 89 22:51:12 GMT References: <9391@smoke.BRL.MIL> <8731@megaron.arizona.edu> <9405@smoke.BRL.MIL> <9422@smoke.BRL.MIL> Organization: Xenix Support Lines: 16