|
From: | Helge Hess |
Subject: | import vs include Re: Porting autogsdoc to OSX |
Date: | Tue, 26 Feb 2002 23:43:12 +0100 |
Hi,I absolutly don't understand the discussion of #include vs #import. #import is always available since it's part of Objective-C. #import has it's problems which is solved by safe-guarding the header file. So any #include capable header file is a perfect #import header file. Conclusion: Safe-guard any header file but use #import in code nevertheless. That way no code will break.
To the specific problem: gstep-base may or may not use #import internally, but gs-autodoc should use #import because otherwise it's not OpenStep conform and therefore not portable. OpenStep requires #import and doesn't require safe-guarded headers.
I'm also amazed that MIME and XML functionality is put into gstep-base. Why does a *Foundation* library require XML and MIME functionality ??? Hm. Gstep-base is IMHO radically violating the one major feature of OpenStep, portability between Foundations. That way you will never reach MacOSX developers ...
Greetings Helge
[Prev in Thread] | Current Thread | [Next in Thread] |