[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: #import vs #include
From: |
Artem Baguinski |
Subject: |
Re: #import vs #include |
Date: |
Tue, 30 Dec 2003 13:26:51 +0100 |
User-agent: |
Mutt/1.5.5.1i |
On Tue, Dec 30, 2003 at 12:34:37PM +0100, Dennis Leeuw wrote:
> Artem Baguinski wrote:
> >quoting http://gnustep.made-it.com/GSPT/xml/Tutorial_en.html :
> >
> > In Cocoa, #import is used instead of #include to prevent duplicated
> > declarations. But GNU GCC doesn't support #import as good as Apple's
> > GCC, and GNUstep use #include.
> >
> >is that statment correct? what's wrong with GNU GCC's #import support?
> >and BTW doesn't G in GCC stand for GNU?
> >
>
> 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.
well, "deprecated" != "not supported as good", i suggest that sentence
in the tutorial will be modified, may be with link to
http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=%23import+deprecated+gcc&btnG=Google+Search
;-)
--
gr{oe|ee}t{en|ings}
artm