home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aix
- Path: sparky!uunet!newsgate.watson.ibm.com!yktnews!admin!yktnews!prener
- From: prener@watson.ibm.com (Dan Prener)
- Subject: Re: More IBM "oversights"
- Sender: news@watson.ibm.com (NNTP News Poster)
- Message-ID: <PRENER.92Dec12012820@prener.watson.ibm.com>
- In-Reply-To: wrat@unisql.UUCP's message of 11 Dec 92 22:39:02 GMT
- Date: Sat, 12 Dec 1992 06:28:20 GMT
- Disclaimer: This posting represents the poster's views, not necessarily those of IBM
- References: <4348@unisql.UUCP>
- Nntp-Posting-Host: prener.watson.ibm.com
- Organization: IBM T.J. Watson Research Center, Hawthorne, New York
- Lines: 17
-
- In article <4348@unisql.UUCP> wrat@unisql.UUCP (wharfie) writes:
-
- > The xlc compiler is absolutely recalcitrant about accepting
- > anything like " Window foo = NULL". But the X11 headers
- > are full of stuff like "XtWindowOfObject(object) != NULL"
- > which of course won't compile with the native compiler. We
- > have to sprinkle our code with crap like "#ifdef IBM #undef XtIsRealized"
- > and fix it.
-
- > If IBM has a better compiler (I can't believe they compiled X with
- > xlc) can a customer get it? Or does xlc have an undocumented
- > "Stop behaving like turbo pascal" mode?
-
- If you invoke xlc as "cc" rather than as "xlc" it is somewhat more permissive.
- See the stanza in /etc/xlc.cfg for the exact differences.
- --
- Dan Prener (prener@watson.ibm.com)
-