Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 513837
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T07:27:47+00:00 2026-05-13T07:27:47+00:00

In the iPhone objective-c world, I’ve seen this pattern everywhere and I use it

  • 0

In the iPhone objective-c world, I’ve seen this pattern everywhere and I use it myself all the time without really understanding what is going on:

In Test.h

@interface Test: UIViewController
{
   NSMutableArray *testArray;
}
@property (retain, nonatomic) NSMutableArray *testArray;

And in Test.m

@implementation Test
@synthesize testArray

- (void) viewDidLoad
{

  // why do we do this?
  NSMutableArray *init = [[NSMutableArray alloc] init]; 
  self.testArray = init;
  [init release];

  [self.testArray addObject: @"A"]; // why can't I do this directly?
  ...
}

- (void) dealloc
{
  [testArray release];
  [super dealloc];
}

My question is: if testArray has a retain on it when it’s declared in the property, why do we need to create a new NSMutableArray init object, assign that to testArray and release? Why can’t I just start using testArray in viewDidLoad without doing anything else?

I know there’s some debate over the best way of doing this (creating a new object, or using an autorelease object), but in both cases, we end up with testArray with a retain count of 1. Which I believe the ‘retain’ property already gives it. So why the need to create this init object?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T07:27:47+00:00Added an answer on May 13, 2026 at 7:27 am

    The ‘retain’ property doesn’t automatically create an NSMutableArray for you. Rather, it simply indicates that whenever you do assign something to that property, it will be retained.

    If your code were this:

    - (void) viewDidLoad
    {
      [self.testArray addObject: @"A"];
    }
    

    Then self.testArray would be nil, and thus it would be essentially a no-op. Until you assign something to self.testArray, it’s empty.

    Here’s what’s going on.

    - (void) viewDidLoad
    {
      // we need to assign an NSMutableArray to self.testArray.
    
      NSMutableArray *init = [[NSMutableArray alloc] init];
      // The array has been retained once (by the call to |alloc|)
    
      self.testArray = init;
      // The array is assigned to a property with the 'retain' attribute
      // Thus, the array has now been retained twice
    
      [init release];
      // We release the array, so it now is retained once.
    
      // We now have an array in self.testArray, so we can add something to it.
      [self.testArray addObject: @"A"];
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.