Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!aries!mcdonald
From: mcdonald@aries.uiuc.edu (Doug McDonald)
Newsgroups: comp.std.c
Subject: Re: MSC __STDC__ strange value
Message-ID: <1989Dec7.151846.1220@ux1.cso.uiuc.edu>
Date: 7 Dec 89 15:18:46 GMT
References: <36001@cc.utah.edu>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Organization: School of Chemical Sciences, Univ. of Illinois at Urbana-Champaign
Lines: 15

In article <36001@cc.utah.edu> ORCUTT@cc.utah.edu writes:
>Turbo C has an option (-A?) that disables extended keywords
>like near, far, huge, pascal, and interrupt.  When this option
>is not used, __STDC__ is not defined.  When this option is
>used, __STDC__ is defined as 1.  Could MSC have a similiar option
>that, when used, defines __STDC__ as 1 and when not used,
>defines __STDC__ as 0?

NO NO NO it can't.

Because MSC (at least up to and including 5.1) is NOT ANSI C .

Neither is Turbo. So if it does that, it is flat out WRONG.

Doug McDonald