Question

I come from a Java background and I am learning Objective C. I am trying to create a class that has a string array and a member function to modify the Array. My code looked like this:

@implementation TAWChapter

@synthesize mSubject;

@synthesize mItems;

- (id) init{
    self.mItems = [[NSMutableArray alloc] init];
    return self; 
}

- (void) setSubject:(NSString *)subject{
    self.mSubject = subject; 
}

- (void) addItem:(NSString *)item{
    [self.mItems addObject:@"asdf"]; 
}

@end

Which didn’t work. I got a "[__NSArrayI addObject:]: unrecognized selector sent to instance " and a "NSInvalidArgumentException". After searching on internet, I changed the single line in the constructor to:

self.mItems = [self.mItems init];

It worked, but why? From a Java developer’s point of view the first one makes more sense than the second one. And I have another line it’s the same as the first one but it’s working(not in a constructor). Can someone explain this to me please?

Answer 1

1. First of all, you should adhere to Objective-C coding conventions. In Objective-C, classes don’t have constructors, they have initialisers. In Objective-C, initialisers invoke the initialiser of the superclass, so it should look like this:

   - init
   {
       self = [super init];
       if (!self) return nil;
   
       // set up other stuff here 
   
       return self;
   }
   

2. Second, unless you are using ARC, you might have a memory leak. The first line of your initialiser assigns an object that you own to a property that also likely takes ownership. You should use either:

   // property takes care of ownership
   self.mItems = [NSMutableArray array];
   

   or:

   // assign to instance variable directly with owned object
   mItems = [[NSMutableArray alloc] init];
   

   Apple sometimes discourage the use of accessor methods in initialisers because it can fiddle with things like KVO, but consistent use of accessor methods ensures proper object ownership and memory management.

3. By changing your line in your initialiser to:

   self.mItems = [self.mItems init];
   

   does nothing. When your initialiser method is called (which is typically just after it has been allocated), all instance variables are automatically set to nil. So what you are doing is just:

   self.mItems = [nil init];
   

   which is just:

   self.mItems = nil;
   

   and, don’t use init without first allocating an instance, and never use init more than once.

4. If you do not let the superclass initialise itself, then it may manifest as problems in other areas. Do a Build & Analyze and ensure you have fixed up any issues pointed out by the analyser.