MSC __STDC__ strange value

[Peter Golde]

In article <223 at bohra.cpg.oz> ejp at bohra.cpg.oz (Esmond Pitt) writes:
>For some strange reason, the MSC 5.1 compiler defines __STDC__ as 0, so
>Why?

For a simple reason: there is no ANSI standard C yet (at least, last I
heard.)  It simply wrong to advertise conformance to a standard which 
doesn't even exist yet.  For example, several detail of the draft standard
have changed since MSC 5.1 was shipped.  Thus, I argue that Microsofts 
definition is perfectly correct.

Moral: don't confuse a *draft* standard with a real standard.  They're
quite different things.

--Peter Golde (summer intern, Microsft Languages group)