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 16:08:02 -0800
- Subject: Re: #import and PCH
- References: <EEAA5436-2FF2-11D7-9BDA-0030657EA24A@apple.com>
Geoffrey Keating wrote:
On Friday, January 24, 2003, at 03:19 PM, Neil Booth wrote:
Stan Shebs wrote:-
We do get it right 99% of the time, because of the simplified
pathnames we use. So anything that works now will work with that,
which is why I suggested it as the solution.
It's a good solution for FSF GCC. Mac development still has a problem,
but no reason to trouble everybody here about that.
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 believe GNUstep decided to switch over to #include, but I'd like
to check on that. Assuming they have, then #import could be documented
in 3.4 that it will be gone in 3.5. Unlike some other features being
proposed for removal, this one is still in active use today.
Stan