Re: Why is NSString->FSRef so hard?
Re: Why is NSString->FSRef so hard?
- Subject: Re: Why is NSString->FSRef so hard?
- From: Uli Kusterer <email@hidden>
- Date: Fri, 1 May 2009 14:22:03 +0200
On 30.04.2009, at 13:12, Alastair Houghton wrote:
3. AFAIK the Carbon layer maps them back again. Carbon's filesystem
functions are implemented on top of the BSD layer, not alongside it
as some people assume (OK, OK, there is the ".vol" special folder
and there are a couple of additional entry-points that Carbon uses
that are really SPI rather than API, but they're still BSD-level
things).
In defense of those "some people", it should be mentioned that this
has changed over time. AFAIK, in 10.0 Carbon and POSIX (I'm lumping
together anything that uses POSIX paths here) took two parallel, but
mostly separate paths, leading to fun bugs like permissions being
ignored in some cases.
At some later MacOS revision, this was changed to have one common
pipeline. Since not every description gets updated with every system
revision, it's easy to see how people could get confused.
Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
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