MSC __STDC__ strange value

[Doug McDonald]

In article <36001 at cc.utah.edu> ORCUTT at 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