Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ames!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.std.c
Subject: Re: __STDC__ and non-conforming ANSI C compilers
Message-ID: <9369@smoke.BRL.MIL>
Date: 14 Jan 89 12:43:16 GMT
References: <898@ubu.warwick.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <898@ubu.warwick.UUCP> geoff@emerald.UUCP (Geoff Rimmer) writes:
>I think I read in the Microsoft 5.1 C compiler manual that __STDC__ is
>defined to be 0 in that compiler, since it doesn't fully comply to the ANSI
>standard.  If this is so, it makes lines like the following, useless.

Sigh.  I was afraid that somebody would have a cosmic ray fire in their
brain and decide to "#define __STDC__ 0" to be "helpful", and lo! it did.
Of course the REAL way to be helpful would have been to not define
__STDC__ at all in a nonconforming implementation!  One wonders what they
were thinking of.

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.