Question

The following code is on Apple’s website.

1) Inside the setMyArray method, is it necessary to release myArray before setting a new value to it? I thought setting the value of an object to a new object, will release the old object from memory.

2) Why does it say myArray = [newArray mutableCopy];, instead of simply saying myArray = newArray;? Is it necessary to pass a mutable copy to our property?

@interface MyClass : NSObject {
    NSMutableArray *myArray;
}
@property (nonatomic, copy) NSMutableArray *myArray;
@end

@implementation MyClass
@synthesize myArray;

- (void)setMyArray:(NSMutableArray *)newArray {
    if (myArray != newArray) {
        [myArray release];
        myArray = [newArray mutableCopy];
    }
}
@end

EDIT:
Would it be the same if myArray was (nonatomic, retain)

Apple Documentation
copy
    Specifies that a copy of the object should be used for assignment. (The default is assign.)
    **The previous value is sent a release message**.

Answer 1

With respect to #1, yes you must release myArray before setting a new value to it, otherwise you’ll leak. Note the property, it’s labelled as a copy, meaning that myArray will hold an object with a reference count of one once its set.

And with regards to #2, because if you don’t mutableCopy, you’re not getting a copy of the object, you’re simply pointing at the other thing. So, if the other thing goes away, you’ll have a pointer to a dangling object. Bad things ensue from that point forward.