Re: Why is NSString->FSRef so hard?
Re: Why is NSString->FSRef so hard?
- Subject: Re: Why is NSString->FSRef so hard?
- From: Michael Ash <email@hidden>
- Date: Thu, 30 Apr 2009 01:18:58 -0400
On Thu, Apr 30, 2009 at 12:02 AM, Charles Srstka
<email@hidden> wrote:
> With that said, I don't really see what is harmful about recommending the
> use of NSString's path concatenation methods, which could save quite a few
> headaches in the case that this *does* somehow change for some bizarre
> reason, however unlikely that may be.
Nothing wrong with recommending the NSString methods. Indeed, that's a
good idea. What's harmful is spreading false information about HFS's
path separators. When dealing with UNIX paths, the OS X path separator
is /, end of story. (When dealing with Carbon paths, it's :, no matter
what your filesystem, even on UFS, even on FAT32, but a Cocoa app
rarely has any occasion to use Carbon paths.)
Mike
_______________________________________________
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