Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!munnari.oz.au!spool.mu.edu!uunet!kithrup!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.unix.aix
Subject: Re: RS6000 questions/comments
Keywords: compiler problems rs6000
Message-ID: <1991Jun29.073405.24859@kithrup.COM>
Date: 29 Jun 91 07:34:05 GMT
Article-I.D.: kithrup.1991Jun29.073405.24859
References: <141@ssi.UUCP> <678126129.18432@mindcraft.com>
Distribution: usa
Organization: Kithrup Enterprises, Ltd.
Lines: 18

In article <678126129.18432@mindcraft.com> karish@mindcraft.com (Chuck Karish) writes:
>>	I almost tried a -D__STDC__=0 on the compile line, but chickened
>>	out, maybe I'll try that some other time.
>If the code you're porting assigns a special meaning to the
>case where __STDC__ == 0, it's broken and should be fixed.  Not
>an AIX problem.  The #define would probably have worked.  Any
>problems caused by doing this should be reported to IBM as
>bugs; their tests for __STDC__ in headers should be correct.

Chuck, I'm disappointed.  __* is reserved for the implementation; if you
define it at all, anything is allowed to happen.  (See one of Henry
Spencer's or Chris Torek's descriptions of what "anything" could mean.)

-- 
Sean Eric Fagan  | "What *does* that 33 do?  I have no idea."
sef@kithrup.COM  |           -- Chris Torek
-----------------+              (torek@ee.lbl.gov)
Any opinions expressed are my own, and generally unpopular with others.