Path: utzoo!attcan!uunet!kddlab!titcca!sragwa!wsgw!socslgw!diamond
From: diamond@csl.sony.JUNET (Norman Diamond)
Newsgroups: comp.std.c
Subject: Re: __STDC__ and non-conforming ANSI C compilers
Message-ID: <10093@socslgw.csl.sony.JUNET>
Date: 23 Dec 88 03:17:48 GMT
References: <3236@pegasus.ATT.COM> <9167@smoke.BRL.MIL> <14856@lll-winken.llnl.gov>
Organization: Sony Computer Science Laboratory Inc., Tokyo, Japan
Lines: 30

In article <14856@lll-winken.llnl.gov>, casey@gauss.llnl.gov (Casey Leedom) writes:

> The Apollo SR10 compiler defines __STDC__.  It supports functional
> prototyping.  It does not support any other feature of ANSI C that I
> know of.  In particular, I know that it does not support the new "##"
> preprocessor syntax to generate a null length break between
> preprocessor macros.

> [[It should be noted that Apollo doesn't see any problem with the
> described situation.  They don't feel that they are misusing the
> __STDC__ symbol.]]

Well.

1.  Rhetorical question:  If you buy a history book that contains
deliberate, fraudulent lies, are you legally entitled to a refund?

2.  Sounds like a lot of programmers, who have already put #if __STDC__
in their code, might not mind globally editing __STDC__ to __ANSIC__
after they read this.  Perhaps the committee could be persuaded to make
that change, and trademark it, before things get any worse.  The amount
of future effort that could be saved is substantial.

(Incidentally, __ANSIC__ might be better than __ANSI__ because there
might eventually be __ANSIUNIX__, __ANSIWINDOWS__, etc.)
-- 
Norman Diamond, Sony Computer Science Lab (diamond%csl.sony.jp@relay.cs.net)
  The above opinions are my own.   |  Why are programmers criticized for
  If they're also your opinions,   |  re-inventing the wheel, when car
  you're infringing my copyright.  |  manufacturers are praised for it?