Xref: utzoo comp.os.os2:344 comp.lang.c:24334 comp.std.c:2245
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!murtoa.cs.mu.oz.au!ditmela!yarra!bohra!ejp
From: ejp@bohra.cpg.oz (Esmond Pitt)
Newsgroups: comp.os.os2,comp.lang.c,comp.std.c
Subject: Re: MSC __STDC__ strange value
Message-ID: <230@bohra.cpg.oz>
Date: 6 Dec 89 23:46:31 GMT
References: <223@bohra.cpg.oz> <1989Dec5.164318.26510@utzoo.uucp>
Reply-To: ejp@bohra.cpg.oz (Esmond Pitt)
Organization: Computer Power Group, Melb, Australia
Lines: 25

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

Some apparently illiterate posters have concluded that I don't know the
difference between #if and #ifdef. I do, and my posting demonstrated
so.

This is truly annoying, folks. Please read.

-- 
Esmond Pitt, Computer Power Group
ejp@bohra.cpg.oz