Re: #import and PCH (fwd)

[Nicola Pero]

Be careful with #import as it might be removed completely from the FSF GCC
compiler soon.  It's causing too many problems for a portable
implementation of precompiled headers.

Reading the gcc mailing lists make me feel this is getting serious - maybe
I should remove the -Wno-import warning from gnustep-make, so that our
users know they are at risk if they use #import.

---------- Forwarded message ----------
Date: Fri, 24 Jan 2003 16:22:17 -0800
From: Geoffrey Keating <address@hidden>
To: Stan Shebs <address@hidden>
Cc: Neil Booth <address@hidden>, address@hidden
Subject: Re: #import and PCH


On Friday, January 24, 2003, at 04:08  PM, Stan Shebs wrote:
> Geoffrey Keating wrote:
>> On Friday, January 24, 2003, at 03:19  PM, Neil Booth wrote:
>>> Ah.  Death to #import!
>>>
>> Yes.  I'm looking at this, and I think the best thing is to have the 
>> Apple compiler look at inodes, and to remove #import altogether from 
>> the FSF.  Any objections?
>>
> I don't think we can go quite that fast - #import is an officially
> documented feature of Objective-C.  For instance, the ObjC reference
> that O'Reilly published last month recommends #import and doesn't
> say anything about it being deprecated.

I guess someone should contact the author, since it's been deprecated 
for a long time now; the CVS archive of cpp.texi says it's been 
obsolete since August 1997.  The warning that FSF GCC produces dates to 
March 2000.  So, it's been obsolete for five years, and deprecated with 
a warning for three.  I think that's long enough.