ANSI compliance bug in Apple C compiler on OS X

[Drew Reynolds <drew at actel dot com>]

Here is the starting point for submitting bugs against the heart of
Mac OS X (Darwin). You must be a registered user. If you are not, it
is free and easy to become one.

http://www.opensource.apple.com//projects/bugs.html

Michael Hopkins writes:
 > 
 > Hi
 > 
 > I am trying to find the right place to ask the following questions, get
 > an authoritative answer and then try to get something done about it.  
 > These groups seems like they must be pretty close to the heart of OS X 
 > development.  Any advice or suggestions of who to contact will be 
 > greatly appreciated.  Is it worth sending a bug report to Apple & if so
 > where to?  I can't find it.. I've sent one to the Darwin page.
 > 
 > In brief, the pre-processor in the Apple OS X cc compiler that I have
 > for OS X (from the ADC site) appears not to be ANSI compliant and 
 > obviously should be, for it to be of much use to the people who want to 
 > port substantial projects from UNIX & Linux (or elsewhere).  Please 
 > see the email copied below for some detail.
 > 
 > Many have suggested using '-traditional-cpp' flags and they solve some
 > of the problems below, but introduce others - probably because they also 
 > break ANSI compliance.
 > 
 > What have Apple done to GNU cc?  This behaviour is not present on any 
 > other UNIX/Linux platform as far as I can establish.
 > 
 > As I say above (& below) - this will affect all of us who want to take
 > advantage of our new 'industrial strength' OS...
 > 
 > Michael
 > 
 > P.S.  Apologies if some of you have seen this part before... 
 > 
[snip]

-- 
Andrew Reynolds			internet: drew@actel.com
Actel Corporation		phone:    (973) 770-4700 ext. 3124
200 Valley Road, Suite 300	fax:      (973) 770-0800
Mt. Arlington, NJ 07856, USA