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: Alastair Houghton <email@hidden>
- Date: Fri, 13 Jul 2007 15:32:05 +0100
On 13 Jul 2007, at 15:10, Eric Schlegel wrote:
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.
I know I was poking about in one of the carbon FS reference types and
found a path; perhaps it was FSSpec instead. I don't use Carbon APIs
that much in most of my code, as the BSD layer covers most of the
functionality in a way that I'm more familiar with :-)
Anyway, my point was still valid; using FSRef isn't a fully general
workaround for path length limits. It'll work sometimes, but sadly
not always.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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