Re: !foo vs foo == nil

On Aug 21, 2008, at 7:57 AM, Sam Mo wrote: On Aug 21, 2008, at 4:47 AM, Thomas Engelmeier wrote: Am 21.08.2008 um 05:03 schrieb Michael Ash: There was a common perception that NULL is not really the same as nil. But seems like in the end it really is (void*)0. They differ in type, not

Re: !foo vs foo == nil

On Aug 21, 2008, at 4:47 AM, Thomas Engelmeier wrote: Am 21.08.2008 um 05:03 schrieb Michael Ash: There was a common perception that NULL is not really the same as nil. But seems like in the end it really is (void*)0. They differ in type, not in value. "NULL" is (void *) 0. "nil" is (id)

Re: Localize App Title?

On Aug 5, 2008, at 7:25 AM, Chunk 1978 wrote: i've localized the info.plist file, and added these keys to the english subfile: LSHasLocalizedDisplayName according to this web page,

Re: plist parsing in c

On Jul 6, 2008, at 3:12 PM, Keith Duncan wrote: The only reliable* way to access system preferences is through the CFPreferences API which NSUserDefaults is built on. CFURLCreateDataAndPropertiesFromResource() and CFPropertyListCreateXMLData() for read. CFPropertyListCreateXMLData() and

Re: Style Question

On Jun 28, 2008, at 4:54 AM, Robert Claeson wrote: On 28 Jun 2008, at 06:30, Alex Wait wrote: I have noticed, coming from C++ and Visual Studio (at school), a couple style differences if (value) { //do something } insteasd of if (value) { //do something } Also since I am using this

Re: NSString uppercaseString

On Jun 27, 2008, at 10:12 AM, Tito Ciuro wrote: As Matt also points out, the documentation is not always crystal- clear, so I was simply trying to answer Sam's specific question. Since not all APIs behave the same way I added the link to the "Memory Management Programming Guide for Cocoa" pa

NSString uppercaseString

Newbie here: I am looking at the documentation in Xcode for the method uppercaseString in NSString class but it does not mention how the return NSString is being released. Will the return NSString be released when the originator be released? Or I have to release the return NSString separately? O