🚀 go-pugleaf

In article <gnusenet674@bibsyst.UUCP> tore@bibsyst.no (Tore Morkemo) writes:
>It seems that SCO's cc and gcc can't agree on preprocesing. We're running
>SCO 3.2.4 and devsys for 3.2.4. I'm not sure but I think the bug/feature
>showed up in 3.2.4

What you are seeing is the difference between manifest defines on SCO cc and
gcc.  Gcc has correctly defined __STDC__ to be 1, and SCO cc has defined
__STDC__ to be 0.  If having __STDC__ defined as 1 is causing you grief
in /usr/include header files when compiling with gcc, then I would recommend
either overriding the value of __STDC__ at compile time with -D__STDC__=0
(which will produce warnings on gcc 1.40), or altering the manifest define
in your gcc source tree.  I certainly wouldn't recommend that you attempt
to modify your /usr/include header files.

>Here's the testprogram.....
>;cat prep.c
>#ifdef __STDC__
>STDC it is...
>#endif

The equivalent "not #if" preprocessor check to the above is;

#if ! defined(__STDC__)

In the case;

>#if !__STDC__

you are checking the value of __STDC__, and not necessarily whether
it is defined.  If it is not defined at all then the symbol will have
a "value" of 0.

[I've removed comp.std.c since this isn't relevant to a general standards
discussion, and comp.lang.c since this is an implementation specific thing
that doesn't seem to be welcome there (plus talking about defining __STDC__
as 0 always seems to attract flames over there for some reason :-).]
-- 
     Stacey Campbell - staceyc@sco.com - {uunet,ucscc,att}!sco!staceyc