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.
> >
> Are you talking changing the sense of the configure option (to 
> --enable-import)? That's probably a good idea, although if there are 
> going to be strong arguments about this anywhere, it will be on the 
> gnustep-discuss list :-( So perhaps we should document it well and 
> announce the change also. At least developers will be able to decide 
> what they want, just newbie's will be confused by the warnings.

I'm not sure, I don't want another flamewar on this topic, and all is very
unclear at the moment.  Let's just leave it as it is :-)

Btw, check

http://gcc.gnu.org/ml/gcc/2003-01/msg01224.html

and

http://gcc.gnu.org/ml/gcc-patches/2003-01/msg01828.html

for extremely interesting threads about #import.