This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: #import and PCH
- From: Stan Shebs <shebs at apple dot com>
- To: Geoffrey Keating <geoffk at apple dot com>
- Cc: Neil Booth <neil at daikokuya dot co dot uk>, gcc-patches at gcc dot gnu dot org
- Date: Fri, 24 Jan 2003 17:25:41 -0800
- Subject: Re: #import and PCH
- References: <0FB1E243-2FFB-11D7-9BDA-0030657EA24A@apple.com>
Geoffrey Keating wrote:
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.
That warning predates the introduction of OS X, and wasn't very well
advertised, if confused messages from ObjC users are anything to go
by. The latest GNUstep argument about using #import was only a few
months ago. I just grepped through latest GNUstep in CVS and it has
16000 #include vs 2000 #import statements so at least the tide is
turning, but it's not there yet.
We could dial up the heat by making the #import warning in GCC the
only one that can't be turned off... 1/2 :-)
(I bet the ORA author Andrew Duncan didn't know about the deprecation
because he was using Apple's compiler to test all the examples.)
Stan