Re: Porting autogsdoc to OSX

[Nicola Pero]

> >> The last thing, which is somewhat odd, is that every #imports in
> >> GNUstep* are written as #includes. I think that this was done merely
> >> because nobody wants an #import statement (which is compiler specific)
> >> when the same can be achieved with an #include and additional checks in
> >> the included file preventing duplicate includes, right? While this 
> >> might be feasible from a theoretical standpoint (personally, I don't know
> >> whether this is the case) it's pretty contra-productive in real life. 
> >> OS X's headers don't have such constructs and hence don't prevent 
> >> duplicate includes - which caused the compiles to fail several times.
> >
> > GNUstep uses #include because usage of #import is strongly deprecated by
> > the same authors of GCC (Apple engineers included)
> 
> Thanks for clarifying that point. However, it leaves us in an awkward 
> position: What's the best idea to cope with this discrepancy (theory vs. 
> reality) now and in the future?
> 
> Just to make my point straight: at present, the headers shipped with 
> Apple's Foundation do not reflect the point of view of their gcc 
> engineers.

I sure see your problem with porting, and hope you can find a good
solution.

But my point is that the solution is *not* to downgrade gnustep-base to
use #import.

If the Apple Foundation headers are not protected against multiple
inclusions, that is a bug in their headers.  Fill in a bug report and tell
them.

NB - GNUstep headers work if you #import them.  You can #import them if
you like.  We use #include because it's better, but nothing prevents you
from using #import.