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: "Clark Cox" <email@hidden>
- Date: Fri, 13 Jul 2007 07:40:29 -0700
On 7/13/07, Alastair Houghton <email@hidden> wrote:
On 13 Jul 2007, at 11:36, Stéphane Sudre wrote:
>> Of course, that all depends on your individual case.
>
> Actually, I'm tracking an issue with Alias resolution and I'm
> testing different cases to see where the problem might come from.
> My biggest surprise so far is that the same limit affects
> CFURLGetFSRef.
This isn't especially surprising, because (if I remember rightly)
FSRefs internally store a path
Just a minor nit to pick: that is simply not possible. An FSRef is
only 80 bytes, that is not large enough for a path. And, if it
contained some reference to a path (i.e. a pointer into a table of
some sort), then FSRefs wouldn't be freely copyable (as they are), and
would require some sort of allocate/deallocate or retain/release API.
--
Clark S. Cox III
email@hidden
_______________________________________________
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