I think I understand retain/release in objective-C for the most part. However, I have a specific case I am unsure about. Here is an example:
+ (NSString *)getPlayerNameByIndex:(NSInteger)globalIndex:(ABAddressBookRef)addressBook
{
...
Player *player = [PlayerHelper loadPlayer:globalIndex];
NSString *name = [PlayerHelper getPlayerName:player :addressBook];
[player release];
// 'retain' here?
return name;
}
+ (NSString *)getPlayerName:(Player *)player:(ABAddressBookRef)addressBook
{
...
NSString *name = [[[NSString alloc] initWithString:player.nickname] autorelease];
return name;
}
So then I call…
NSString *name = [PlayerHelper getPlayerNameByIndex:index:addressBook];
// name is 'autorelease'?
What I saw on random occasions is that the view sometimes shows the ‘name’ field as empty when it populates the table after coming back from another view. This could be another issue but I want to be sure of my use of ‘autorelease’.
The core of my question is the use of ‘autorelease’ in getPlayerName. Does the ‘autorelease’ state of being get passed through method getPlayerNameByIndex to the caller?
Or, do I have to call ‘retain’ in the intermediary method? I am thinking ‘autorelease’ may be releasing in method getPlayerNameByIndex.
Hopefully my question is clear. Any help is appreciated.
Update: Some more info for clarification…
NSError *error = nil;
Player *player = nil;
NSArray *array = [appDelegate.managedObjectContext executeFetchRequest:request error:&error];
if ([array count] == 1)
{
player = [array objectAtIndex:0];
[player retain];
}
This is essentially the “loadPlayer” method which loads info from core data. From the answers it sounds like I do not need to call [player retain], since it is an autorelated object, and I can simply return “player” and use it? Thanks for the responses!
The answer is yes.
whether you want to call
retaindepends on the semantics of your method.In Obj-C/Cocoa, the following convention applies: a method whose name begins with “alloc” or “new” or contains “copy” will return a
retainedobject; otherwise you can expect to get anautoreleasedobject, then it is the caller responsibility to retain it according to its needs.autoreleased objects are released at the next point in time when the autorelease pool is drained; this is usually associated to going back to the main loop (though, no details are available about this); so you can be pretty sure that auto-releasing does not kick in in
getPlayerNameByIndex…Hope this helps clarifying the issue…