On 16 Feb 2010, at 13:21, Torsten Curdt wrote:
I am really really irritated. Got an iPhone project. Got quite some
categories with additions to the standard APIs. All good.
Just the darn NSData refuses to accept the category ... and I have no
clue why. It's as simple as
@interface NSData
I am really really irritated. Got an iPhone project. Got quite some
categories with additions to the standard APIs. All good.
Just the darn NSData refuses to accept the category ... and I have no
clue why. It's as simple as
@interface NSData (NSDataAdditions)
+ (id)
Why NSConcreteData? Does it create a different object under
the hood
Yes, NSData is a class cluster (see Google). NSString, NSArray
and NSDictionary are too, and no doubt others. But I don't see
why you shouldn't put a category on NSConcreteData, other than
the fact that the sand might
I am really really irritated. Got an iPhone project. Got quite some
categories with additions to the standard APIs. All good.
Just the darn NSData refuses to accept the category ... and I have no
clue why. It's as simple as
@interface NSData (NSDataAdditions)
+ (id)
Bah ... one really just has to write the email to the list to find the
fix himself. So here is what happened: I had added a new file to the
Xcode project and renamed it.
When checking with nm I found that the symbol for the category was
actually missing ...and fair enough - it was just missing
