[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Porting autogsdoc to OSX
From: |
Nicola Pero |
Subject: |
Re: Porting autogsdoc to OSX |
Date: |
Tue, 26 Feb 2002 11:07:24 +0000 (GMT) |
> 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).
- Porting autogsdoc to OSX, Marcus Müller, 2002/02/26
- Re: Porting autogsdoc to OSX,
Nicola Pero <=
- Re: Porting autogsdoc to OSX, Marcus Müller, 2002/02/26
- Re: Porting autogsdoc to OSX, Marcus Müller, 2002/02/26
- Re: Porting autogsdoc to OSX, Marcus Müller, 2002/02/26
- Re: Porting autogsdoc to OSX, Nicola Pero, 2002/02/26
- import vs include Re: Porting autogsdoc to OSX, Helge Hess, 2002/02/26
- Re: import vs include Re: Porting autogsdoc to OSX, Marcus Müller, 2002/02/26