Xref: utzoo comp.os.os2:321 comp.lang.c:24276 comp.std.c:2232
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!usenet.ins.cwru.edu!mephisto!prism!gitpyr!is813cs
From: is813cs@pyr.gatech.EDU (Cris Simpson)
Newsgroups: comp.os.os2,comp.lang.c,comp.std.c
Subject: Re: MSC __STDC__ strange value
Message-ID: <9692@pyr.gatech.EDU>
Date: 5 Dec 89 15:20:51 GMT
References: <223@bohra.cpg.oz>
Reply-To: is813cs@pyr.gatech.edu (Cris Simpson)
Organization: VA Rehab R&D | Ga Inst of Technology
Lines: 23

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?
>Esmond Pitt, Computer Power Group
>ejp@bohra.cpg.oz

   According to K&R2, (pg 233), __STDC__ must be defined, as well as
(insert your own __ 's)  LINE, FILE, DATE, TIME.   However, since
5.1 is not ANSI, __STDC__ can't be 1.

  To me, it appears to be a ANSI compatible way to say that you're not
ANSI conforming.  Maybe (?) in MSC 6.0,  __STDC__ will == 1.  If not,
I don't know what they're waiting for.

Flames just enlighten me.

cris

-- 
Cris Simpson                            |   
Computer Engineer                       |  No, No!  Not THOSE chains! 
VA Rehab R&D Center                     |    -K. Marx
Atlanta,GA      is813cs@pyr.gatech.edu  |