Re: #import vs #include

[Adam Fedor]

On Tuesday, December 30, 2003, at 11:35 AM, Alex Perez wrote:

> *SIGH*
> > Yep the G stands for GNU and the problem with #import is that it 
> > is/was depricated (from gcc). But I don't know what the 
> > current/future state of gcc will be. If the #import will be valid or 
> > that we still need to use #include and ifdefs.
> In GCC 3.4 #import *IS UNDEPRECATED* We really need to pull together 
> and clarify that in our documentation, IMO. Personally, I'd vouch for 
> --enable-import being on in GNUstep-make by default in light of this 
> FACT, and also that all documentation which contains this kind of FUD 
> be changed to reflect this new reality.

--enable-import just suppresses the warning, if there is one.
Many people still use old compilers, so for them, the warning is 
appropriate. When they switch to gcc 3.4, gcc will of course no longer 
give the warning, so the --enable-import option doesn't matter. I'll 
change the documentation though.