The subject of this thread, and discussion of it both here and elsewhere, has
suggested a closely related question:
When a static library is linked in, what classes within the static library are
loaded, only the referenced classes, or all of them? One quick note --
regarding the -all_load link
On Sat, Apr 23, 2011 at 3:22 PM, Stephen J. Butler
wrote:
> Now the tools, on the other hand, were less smart in Xcode3 and below.
> Autocomplete, IB message browser, etc only knew about the
> messages/properties visible to the immediate code block (via import,
> include, etc). That Apple has fixe
Thanks for the response, Stephen. I was under the impression that category
modification was limited to the types within which they are imported. Thanks
for expanding my knowledge of categories!
Cheers,
Brad
On Apr 23, 2011, at 3:22 PM, Stephen J. Butler wrote:
> On Sat, Apr 23, 2011 at 3:36
On Sat, Apr 23, 2011 at 3:36 PM, Bradley S. O'Hearne
wrote:
> Since transitioning to Xcode 4, I have discovered a very curious shift in the
> way Objective C categories are handled in static libraries. In general, if
> you create an Objective C category, you have to import that category into an
Since transitioning to Xcode 4, I have discovered a very curious shift in the
way Objective C categories are handled in static libraries. In general, if you
create an Objective C category, you have to import that category into an
implementation (.m) class in order for that category's additions t
