ResolvingAliases was: Re: NSFileManager's enumeratorAtPath can't handle aliases
ResolvingAliases was: Re: NSFileManager's enumeratorAtPath can't handle aliases
- Subject: ResolvingAliases was: Re: NSFileManager's enumeratorAtPath can't handle aliases
- From: publiclook <email@hidden>
- Date: Mon, 11 Aug 2003 12:43:36 -0400
The following link shows some length core foundation code to convert a
path string that may include aliases into a fully resolved path:
http://developer.apple.com/documentation/Cocoa/Conceptual/
LowLevelFileMgmt/Tasks/ResolvingAliases.html
I have not been copying and pasting this code everywhere my
applications deal with paths obtained from open panels, save panels,
preferences, drag and drop etc. Am I in for trouble ?
It seems very un-Cocoa-like for us to have to replicate the ugly
complicated redundant code in many places within our applications. Is
the link above obsolete ? Was it a temporary work around ? Do
NSString's path handling methods now take care of this nonsense
(perhaps within -fileSystemRepresentation) ?
I think failure to handle valid file system paths within Cocoa's path
handling and returning methods is a serious bug, and I will submit it
unless this is no longer an issue. This could become the world's first
ten minute bug report ;)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.