Stefan Werner wrote:
Actually, it's probably not, because HFS can't store a file with a
":" in
it, but can store a file with a "/" in it. But the UNIX stuff means
much of
the OS can't handle a file with a "/" in it, so it gets mapped to
":" for
the OS. But some Mac APIs can't handle the ":" so that gets mapped
back to
"/".
Ideally, code should not even be aware of what the path separator is.
Always use the system provided methods to concatenate and split paths
(NSURL, CFURL, NSString, FSRefs), then your code couldn't care less if
10.7 should introduce HFS++Extreme with 'e' as path separator.
Ideally, that's true. And a key element of that is to make sure
you're consistent about which API you're using. But you also may need
to do some scrubbing if, for example, there's any chance of the user
entering filename information directly.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
