• 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: Status of @"" strings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Status of @"" strings


  • Subject: Re: Status of @"" strings
  • From: Markus Hitter <email@hidden>
  • Date: Thu, 12 Jul 2001 14:38:44 +0200

Am Donnerstag, 12. Juli 2001 um 13:55 schrieb Bill Cheeseman:

So, if you want to have a temporary empty string that you CAN release so
that it won't hang around in the code for the life of the app, is this
preferred? --

NSString *emptyString = [[NSString alloc] init];

I'm quite sure the instructions to do so eat a lot more bytes than the empty constant. Further, this needs some processor cycles while the constant does not.

Even for non-empty constants there isn't much to win unless you store the contents in a (load-on-demand) resource file.


Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/


  • Follow-Ups:
    • Re: Status of @"" strings
      • From: Michael Grant <email@hidden>
References: 
 >Re: Status of @"" strings (From: Bill Cheeseman <email@hidden>)

  • Prev by Date: Re: Bug in Security Framework?
  • Next by Date: NSBezierPath, Accessing elements of a NSBezierPath path
  • Previous by thread: Re: Status of @"" strings
  • Next by thread: Re: Status of @"" strings
  • Index(es):
    • Date
    • Thread