Article View: comp.std.c
Article #5586Re: __STDC__ and non-conforming ANSI C compilers
From: Johan Vromans
Date: Sun, 15 Jan 1989 14:26
Date: Sun, 15 Jan 1989 14:26
11 lines
844 bytes
844 bytes
From article <9369@smoke.BRL.MIL>, by gwyn@smoke.BRL.MIL (Doug Gwyn ): > Apart from screaming at MicroSoft about this brain damage, I guess we > all have now been forced to use "#if __STDC__" to survive that stupid > decision. ... which will yield a nice warning "__STDC__ not defined, treated as zero" in at least one C implementation I know. -- Johan Vromans jv@mh.nl via european backbone (mcvax) Multihouse [A-Za-z ]* [NB]V uucp: ..!mcvax!mh.nl!jv Gouda - The Netherlands phone: +31 1820 62944
Technical Details
Message-ID:
<2788@mhres.mh.nl>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!mcvax!hp4nl!mhres!jvReferences:
<9369@smoke.BRL.MIL>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!mcvax!hp4nl!mhres!jv From: jv@mhres.mh.nl (Johan Vromans) Newsgroups: comp.std.c Subject: Re: __STDC__ and non-conforming ANSI C compilers Message-ID: <2788@mhres.mh.nl> Date: 15 Jan 89 14:26:14 GMT References: <9369@smoke.BRL.MIL> Organization: Multihouse NV, the Netherlands Lines: 11