Re: What are the official limits of Cocoa when it comes to the length of path names?
Re: What are the official limits of Cocoa when it comes to the length of path names?
- Subject: Re: What are the official limits of Cocoa when it comes to the length of path names?
- From: Eric Schlegel <email@hidden>
- Date: Fri, 13 Jul 2007 07:10:32 -0700
On Jul 13, 2007, at 5:06 AM, Alastair Houghton wrote:
This isn't especially surprising, because (if I remember rightly)
FSRefs internally store a path (on Mac OS X, anyway; earlier
versions presumably hold a CNID instead).
No, FSRefs do not store a path; they store a directory ID/file ID
pair, and therefore on filesystems with native support for file IDs
are immune to path limitations.
It's easy to get the impression that FSRef is a workaround for this
problem, particularly because FSRefs constructed using legacy Carbon
APIs may point to something in the fake /.vol folder (on HFS+
anyway), which I believe is used to provide direct access to files
by CNID (and which can, on HFS+, be used to access files whose
pathnames are too long). This trick won't work at all on other
filesystems, I shouldn't think.
That's correct, FSRefs have the same path length limitations on
filesystems that don't have native file ID support.
-eric
_______________________________________________
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