|
From: | Dennis Leeuw |
Subject: | Re: #import vs #include |
Date: | Tue, 30 Dec 2003 12:34:37 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 |
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.
Dennis
[Prev in Thread] | Current Thread | [Next in Thread] |