On May 22, 2008, at 1:40 AM, Jens Alfke wrote:
On 21 May '08, at 10:50 PM, Charles Srstka wrote:
What becomes the purpose of the Carbon File Manager, anyway?
Cocoa's already got a file manager. And yet even after seven years,
with all the new APIs, new language features, and new paradigms
that have been added to Cocoa, its file manager still has
absolutely no support for forks or anything non-path based.
It's not Cocoa's goal to provide Objective-C APIs to every single
feature of the system, just to the most common ones that are used in
applications. If you compare <Files.h> with NSFileManager, it's like
night and day — the former is an enormous API (even if you filter
out the old deprecated functions) that provides a lot of
functionality that isn't present in the latter. And vital
functionality too, for the OS as a whole, even if most apps don't
need it.
Is it really vital functionality, though? Resource forks have been
deprecated for some time now, and FSRefs, while useful and well-liked
by many users, don't really seem to be on Apple's radar these days.
FSRefs are also highly filesystem-dependent, and HFS+, the only file
system (as far as I know) that currently fully supports them, is
showing its age and ready to be replaced, possibly by a file system
like ZFS that wasn't invented by Apple.
Charles_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
