Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: What's so special about NSString literals? (RE: memory management)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What's so special about NSString literals? (RE: memory management)

Subject: Re: What's so special about NSString literals? (RE: memory management)
From: Eric <email@hidden>
Date: Wed, 17 May 2006 09:48:20 -0700

So they are never deallocated throughout the program's lifetime?

On 5/15/06, Nick Zitzmann <email@hidden> wrote:

On May 15, 2006, at 9:15 PM, Eric wrote:

> I'm just curious as to why when NSStrings are created using literal
> (as in
> @"a string"), I never have to worry about retaining it or releasing
> it.
> What's so special about it?

They're stored as constant strings in the binary. They'll exist in
memory as long as the program is running.

Nick Zitzmann
<http://www.chronosnet.com/>

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: What's so special about NSString literals? (RE: memory	management)
From: Nick Zitzmann <email@hidden>


References:  
  >What's so special about NSString literals? (RE: memory management) (From: Eric <email@hidden>)
  >Re: What's so special about NSString literals? (RE: memory	management) (From: Nick Zitzmann <email@hidden>)




Prev by Date:
Re: Should I retain/release IBOutlet?

Next by Date:
resetCursorRects being called too often?

Previous by thread:
Re: What's so special about NSString literals? (RE: memory	management)

Next by thread:
Re: What's so special about NSString literals? (RE: memory	management)

Index(es):

Date
Thread