Re: Why is NSString->FSRef so hard?
Re: Why is NSString->FSRef so hard?
- Subject: Re: Why is NSString->FSRef so hard?
- From: Erg Consultant <email@hidden>
- Date: Tue, 28 Apr 2009 13:56:55 -0700 (PDT)
I was reading it wrong. Page 12 Strings Programming Guide For Cocoa:
Important: NSString provides a number of methods to use Cstrings directly (such as
stringWithCString:,initWithCString:, initWithCString:length:, and
initWithCStringNoCopy:length:freeWhenDone:). These methods use the default C string encoding
and may lose information in the conversion from that encoding. You are strongly discouraged from using
these methods as are deprecated in Mac OS X v10.4.
________________________________
From: Clark Cox <email@hidden>
To: Erg Consultant <email@hidden>
Cc: cocoa-dev <email@hidden>
Sent: Tuesday, April 28, 2009 9:07:00 AM
Subject: Re: Why is NSString->FSRef so hard?
On Mon, Apr 27, 2009 at 10:13 PM, Erg Consultant
<email@hidden> wrote:
> Apple's doc's specifically say to stay away from using the "CString" routines which require encodings.
Where do they say that?
--
Clark S. Cox III
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden