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: "Adam R. Maxwell" <email@hidden>
- Date: Fri, 13 Jul 2007 07:17:32 -0700
On Jul 13, 2007, at 05:06, Alastair Houghton wrote:
On 13 Jul 2007, at 11:36, Stéphane Sudre wrote:
Plain path names are always problematic. You should try and use
higher level abstractions like NSURL/CFURL or FSRef where
possible. For drag and dropping of files, a Text Field is not the
best choice, and if only for the reason that the HIG recommends to
avoid showing file paths to the user.
I agree with you. The problem here is that I didn't write any line
of code (this project is code free) to make this happen. The
limitation is in the Cocoa framework.
Well it may actually be in the kernel. If it's in the framework
then it should be fixed, since there's no reason for the framework
to limit the length of a path.
If you download the CoreFoundation source and poke around, it appears
to use a max length of 1024 in quite a few places, so CFURL is likely
broken in this regard as well.
find . -type file -name "*.[ch]" |xargs grep CFMaxPathSize
--
Adam_______________________________________________
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