Re: import vs include Re: Porting autogsdoc to OSX

[Helge Hess]

Nicola Pero wrote:
> > Exactly. Just as a side note, Lars Sonchocky-Helldorf filed the request 
> > for "safe-guarding" OS X Foundation/Cocoa Headers against multiple 
> > #includes as an Apple Bug with radar ID  #2868753. Today, just one day 
> > later (!), the ticket has been closed.
> >
> > State: Verify
> > Resolution: Behaves Correctly
>
> You can always file the bug again if you disagree with them.
>
> I always thought that a company (Apple) quarrelling with his customers
> (Lars, you etc) - like in this case - is a very silly company.

There are some million more customers Apple needs to care about ... I 
wonder whether Omni's frameworks have safeguarded headers and whether 
they use #import (I'm pretty sure they do).

> I frankly don't understand why they can't protect the headers against
> multiple #includes.  That way, they would just make more users happy (both
> the ones who want to use #import, and the ones who want to use #include),
> and they would loose nothing.

They would make the ten GNUstep developers more happy, their real 
customers do not care at all and go on using #import as the 
documentation suggests.
Further they would need to modify about half of their code files, which 
from a managers point of view very likely breaks something. Not to 
mention existing documentation materials.

There is no point in stating "#import is deprecated" if the major ObjC 
developer base uses (and always used) #import on a day-by-day basis. I 
completly agree with you that it's a non-issue to safe guard header 
files. I completly disagree with you that using #import is an issue.

Personally I safeguard all my header files and I always use #import for 
Foundation and AppKit. This way I'm safe in every direction.
I'm pretty sure that's the only option which makes sense for tools like 
gs-autodoc or gsweb or GNUmail which are supposed to work on MacOSX.

Greetings
  Helge