Xref: utzoo comp.os.os2:340 comp.lang.c:24297 comp.std.c:2239
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!brunix!cs169054
From: cs169054@cs.brown.edu (Peter Golde)
Newsgroups: comp.os.os2,comp.lang.c,comp.std.c
Subject: Re: MSC __STDC__ strange value
Message-ID: <22283@brunix.UUCP>
Date: 6 Dec 89 02:41:37 GMT
References: <223@bohra.cpg.oz>
Sender: news@brunix.UUCP
Reply-To: cs169054@cslab2b.UUCP (Peter Golde)
Organization: Brown University Department of Computer Science
Lines: 14

In article <223@bohra.cpg.oz> ejp@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)