Re: Framework won't link (was: WHy is Xcode such a PITA?)
Re: Framework won't link (was: WHy is Xcode such a PITA?)
- Subject: Re: Framework won't link (was: WHy is Xcode such a PITA?)
- From: Scott Tooker <email@hidden>
- Date: Sun, 16 Dec 2007 11:19:39 -0800
On Dec 16, 2007, at 9:24 AM, Fritz Anderson <email@hidden>
wrote:
The umbrella #include does not have to be only in the precompiled
prefix. (Though I am reluctant to disagree with Scott Tooker.) You
can (and should) #include the umbrella header in each of your
headers that need symbols from that framework. The umbrella headers
are guarded against reinclusion, it's good documentation, and if the
umbrella isn't precompiled for some reason, your header will still
work.
I'll fully admit that having the import or includes only in the prefix
header when possible is mostly driven by style and simplicity in the
code, so you are totally correct (especially when using #import) that
duplicating the include in the individual headers shouldn't cause
problems.
However, in my experience the simpler the include/import tree and
build setting for a project, the easier it is to deal with build
problems later on (though I do like your suggestion about adding the
import to document the code). This becomes especially important when
dealing with #includes of a header file (since it is up to the
individual header files to guard themselves from multiple inclusion,
unlike #import).
Scott
— F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden