Objective-C - When to use 'self'

Question

This is unmodified code from Apple's iPhone 'Utility Aplication' template:

- (void)applicationDidFinishLaunching:(UIApplication *)application {   MainViewController *aController = [[MainViewController alloc] initWithNibName:@"MainView" bundle:nil];  self.mainViewController = aController;  [aController release];   mainViewController.view.frame = [UIScreen mainScreen].applicationFrame;  [window addSubview:[mainViewController view]];  [window makeKeyAndVisible];  } 

When mainViewController is assigned to aController, the self keyword is specified:

 self.mainViewController = aController; 

However, when the mainViewController's frame is set, the self keyword is not required:

 mainViewController.view.frame = [UIScreen mainScreen].applicationFrame; 

If I remove the self keyword from the first example, the program crashes with the message:

objc[1296]: FREED(id): message view sent to freed object=0x3b122d0 

If I add the self keyword to the second example, the program runs fine.

Can anyone explain why self is needed in the first case but not the second? I'm assuming that in both cases mainViewController is referring to the same instance variable.

Answer 1

Using self causes your class' "setter" for this variable to be called, rather than changing the ivar directly.

self.mainViewController = aController; 

is equivalent to:

[self setMainViewController:aController]; 

On the other hand:

mainViewController = aController; 

just changes the mainViewController instance variable directly, skipping over any additional code that might be built into UIApplication's setMainViewController method, such as releasing old objects, retaining new ones, updating internal variables and so on.

In the case where your accessing the frame, you're still calling a setter method:

mainViewController.view.frame = [UIScreen mainScreen].applicationFrame; 

expands to:

[[mainViewController view] setFrame:[[UIScreen mainScreen] applicationFrame]]; 

Ideally, to future proof your code, you should also be using self.mainViewController (or [self mainViewController]) when retrieving this value too. In general, classes are much less likely to have important code in their "getter" methods than their "setters", but it's still possible that accessing directly could break something in a future version of Cocoa Touch.