Question

in this code, if collection is released in the class that called init..., what will happen to self.title or self.managedObjectContext? Don’t we have to call .itemName on currentCollection rather than on collection itself?

- (id)initWithCollection:(AACollection *)collection {
    if( (self = [super initWithNibName:@"AACollectionViewController" 
                                bundle:nil]) ) {
        currentCollection = [collection retain];
        self.title = collection.itemName;
        self.managedObjectContext = collection.managedObjectContext;
    }

Thanks

Answer 1

what will happen to self.title or self.managedObjectContext?

You’re retaining collection, so nothing bad will happen. That said, it’s generally a good idea to give your string properties copy semantics. For example, assuming title is a string property, if collection.itemName happens to give you a mutable string, you really want to make an immutable copy of it so that it won’t be changed right under your nose (which could happen if you just reference the mutable string). Using copy will do that for you.

Don’t we have to call .itemName on currentCollection rather than on collection itself?

No. currentCollection and collection will point to the same object. It’s the object that’s retained, not the pointer. Some might consider it better style to use currentCollection, but it’s effectively the same thing either way.