Question

I read somewhere that with NSString in an object, one has to use copy instead of retain. Can someone explain if this is correct and why?

For example I have the following declaration for my singleton:

#import <foundation/Foundation.h>
@class FaxRecipient;

@interface MyManager : NSObject {
    NSString *subject;
    NSString *reference;
    NSString *coverSheet;
    FaxRecipient *faxRecipient;

}

@property (nonatomic, retain) NSString *test1;
@property (nonatomic, retain) NSString *test2;
@property (nonatomic, retain) NSString *test3;
@property (nonatomic,retain) FaxRecipient *faxRecipient;



+ (id)sharedManager;

@end

Answer 1

I think “has to” in the sense of must is a little strong. You can use either copy or retain, but you should generally use copy for your NSString* properties because:

1. You usually don’t want a string property to change under your nose;
2. NSMutableString is a subclass of NSString, so it’s entirely possible that someone might set your NSString* property to point to a mutable string, thus creating the potential for the string to be changed while you’re using it;
3. For immutable classes like NSString, copy operations end up just retaining the original object anyway.

Considering those three points, it’s hard to think of a good reason to use retain instead of copy for your NSString properties.