• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • 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: Nick Zitzmann <email@hidden>
  • Date: Mon, 15 May 2006 21:50:18 -0600


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: Eric <email@hidden>
References: 
 >What's so special about NSString literals? (RE: memory management) (From: Eric <email@hidden>)

  • Prev by Date: Re: incompatible pointer type warning, but everything OK?
  • Next by Date: Is NSPopUpButton KVO compliant?
  • Previous by thread: 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