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: Sat, 25 Apr 2009 18:03:44 -0700 (PDT)
When I do that, the conversion from NSString to const UInt8 * path mangles the special characters in the path.
________________________________
From: Stephen J. Butler <email@hidden>
To: Cocoa-Dev List <email@hidden>
Sent: Saturday, April 25, 2009 5:48:09 PM
Subject: Re: Why is NSString->FSRef so hard?
On Sat, Apr 25, 2009 at 7:28 PM, Erg Consultant
<email@hidden> wrote:
> I was using CFURLGetFSRef passing in the NSString which works fine as long as the path contains no special chars. If it does, CFURLGetFSRef returns nil.
CFURLGetFSRef is great if what you have originally is a CF/NSURL. But
if you just have an NSString, you might as well use FSPathMakeRef with
[aString fileSystemRepresentation]. No reason to create an
intermediary NSURL.
_______________________________________________
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
_______________________________________________
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