Question

Let’s say I’ve got an array with strings.

NSArray *names = [NSArray arrayWithObjects: @"One", @"Two", @"Three", nil];

What I want is to initiate objects of some custom class and them add them to a mutable array. I’m using a custom init method that takes a string argument.

To be more specific, I want to [SomeClass alloc] initWithName: aName] and add the resulting object to a NSMutableArray.

I’m thinking of using Objective-C fast enumeration. So what I get is:

NSMutableArray *objects = [NSMutableArray arrayWithCapacity: [names count];

for (NSString *name in names) {
    [objects addObject: [[[SomeClass alloc] initWithName: name] autorelease]];
}

The problem is that I can’t add nil to the array and I don’t like exception handling. However, my initiation method may return nil. So I decide to check first before adding (prevention). My new for-in-loop is:

SomeClass *someObject;

for (NSString *name in names) {
    someObject = [[[SomeClass alloc] initWithName: name] autorelease];
    if (someObject) {
        [objects addObject: someObject];
    }
}

Now, instead of immediately passing the new object to the array, I’m setting up a pointer someObject first and then passing the pointer to the array instead.

This example raises a question to me. When I someObject = [[[SomeClass alloc] initWithName: name] autorelease] in the loop, do the existing objects (which are added using the same pointer) in the array change too?

To put it in other words: does the addObject: (id)someObject method make a new internal copy of the pointer I pass or do I have to create a copy of the pointer — I don’t know how — and pass the copy myself?

Thanks a lot! 🙂

Answer 1

Three20 provides the answer!