Re: import vs include Re: Porting autogsdoc to OSX

[Richard Frith-Macdonald]

On Wednesday, February 27, 2002, at 12:16 PM, Helge Hess wrote:

> Nicola Pero wrote:
> > Particularly if we are writing *new* code.  I can understand legacy 
> > code
> > from the past - but why writing new code using GCC C extensions which 
> > are
> > deprecated without hope and which nobody else in the world is using ?
>
> Hm, so you consider the reference implementation, MacOSX, deprecated or 
> even "legacy" code ? Do you really expect MacOSX to change in this 
> point ??
> I don't.
>
> Also what do you mean with "nobody else in the world is using" ??? At 
> least 50 times more developers are using #import than GNUstep. Are you 
> going to discuss with them the whole issue over and over again ?

I think this is a fair point ... while it's not a reason for GNUstep to 
use import,
it does mean we should assume that many people *will* use it - though 
I'm not sure
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.