Re: import vs include Re: Porting autogsdoc to OSX

[Pete French]

> what (if anything) we should do about that.  Presumably if someone wants 
> to write code for MacOS-X they would use import in their code.

I think they have to as #include breaks on OSX (which is where this
thread started isnt it ?)

Regardless of the theorietical "correctness" the fact remains
that if you want portable code which run on GNUstep, OSX, OpenStep
and YellowBOX/NT you use #import for the external headers. You should
make sure your own headers are properly protecetd against #include though,
as should any GNUstep headers. If #import goes away in future then you
just need to do a global substitute to port the code.

-bat.