CODEWITHSUNDEEP
iphonecocoa-touchstringnsstringcreation
mk12
mk12

Reputation: 26364

iPhone Dev - NSString Creation

I'm really confused with NSStrings. Like when should I do

NSString *aString = @"Hello";

of should it be:

NSString *aString = [[NSString alloc] initWithString:@"Hello"];

But then its different when you're assigning a value to an NSString property isn't it? Can someone clear this up for me?

Thanks!!

Upvotes: 0

Views: 1888

Answers (2)

Louis Gerbarg
Louis Gerbarg

Reputation: 43452

In general you should do the first, but they are mostly functionally the same. You can treat constant NSStrings just like normal NSString string objects, for instance:

[@"Hello" length]

will return 5. You can assign them to properties, everything just works. The one thing you might notice is that with the constant NSStrings you don't have to worry about retain/release. That is because they are actually mapped into the applications readonly data section, and don't have allocated memory. Retain and release calls against them still work, they just become noops.

Upvotes: 2

jbrennan
jbrennan

Reputation: 12003

NSString *aString = @"Hello";

Will create an autoreleased string. That is, if you don't explicitly retain it, it will might disappear after your method is over (and sometimes that's totally fine). But if you want to hold on to it past that time, you'll need to retain it.

If you create a property for that string like this

@property (retain) NSString *aString;

And then assign like this:

self.aString = @"Hello";

Then you've properly retained the string and it will stick around.

On the other hand, using alloc, init will create a string for you with a retain count of 1, and if you don't need it past that method, you should release it.

****Edit: @"Hello" is not an autoreleased string, as others have pointed out. My bad. ****

Upvotes: 0

Related Questions