[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 14:32:01 +0000 (GMT) |
> Well, that's something I don't understand. In my understanding #import
> statements should be better by far, because they take the burden of
> "safeguarding" your headers from you and they're also faster, as they
> prevent headers from being opened more than once - something which the
> #include thing cannot do. So why is it you consider #include superior
> over #import statements (asking out of curiosity)?
Please check the past mailing list archives for more information.
- Porting autogsdoc to OSX, Marcus Müller, 2002/02/26
- Re: Porting autogsdoc to OSX, Nicola Pero, 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, 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
- Re: import vs include Re: Porting autogsdoc to OSX, Nicola Pero, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Helge Hess, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Nicola Pero, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Richard Frith-Macdonald, 2002/02/27