Question

I have 2 questions about how to make a correct readonly property in Objective-C 2.0+.

Here is my original approach, let’s call it solution 1:

@interface ClassA{
 @private
  NSMutableArray *a_;
}

// NOTE: no retain
@property (nonatomic, readonly) NSMutableArray *a;

@end


///////////////////////////////////////
@implementation ClassA

@synthesize a = a_;

- (NSMutableArray *)a{
  if(nil == a_){
    a_ = [[NSMutableArray alloc] array];
  }
  // Potential leak warning on the following line.
  return a_;
}

- (void)dealloc{
  // I released the object here, I think this should be safe.
  [a_ release];
  [super dealloc];
@end

When I compile and analyze it, the system report a warning like this: “a potential leak at ‘return a_'”.

Then I read the document of Objective-C again and find another approach as below. Let’s call it solution 2.

@interface ClassB{
 @private
  NSMutableArray *a_;
}

// NOTE: make it retain+readonly
@property (nonatomic, readonly, retain) NSMutableArray *a;

@end


///////////////////////////////////////
// Add a private category
@interface ClassB ()

// reset the property to readwrite
@property (nonatomic, readwrite, retain) NSMutableArray *a;

@end

//////
@implementation ClassB

@synthesize a = a_;

- (id)init{
  if(self = [super init]){
    // NOTE: set the value as we use property normally.
    self.a = [NSMutableArray array];
  }
  return self;
}

- (void)dealloc{
  self.a = nil;
  [super dealloc];
@end

Now, here are my questions:

• Is it possible to use solution 1 and get rid of ‘potential leak’?
• Does solution 2 the common solution?

Thank you guys!

— Tonny

Answer 1

As requested, I’m reproducing my comment as an answer:

[[NSMutableArray alloc] array] should give you a compiler warning, and it will definitely crash. You want [[NSMutableArray alloc] init].