Re: fileExistsAtPath: NO means YES? (Doc error)
Re: fileExistsAtPath: NO means YES? (Doc error)
- Subject: Re: fileExistsAtPath: NO means YES? (Doc error)
- From: Dave Hersey <email@hidden>
- Date: Thu, 08 Apr 2004 17:00:57 -0400
Thanks for the replies Fritz, Matt,
Just to be clear, it's not that I couldn't figure out how to use
fileExistsAtPath, it's that I wasn't trusting the results because of the
documentation regarding symbolic links.
This was a doc error, though.
My 10.2 build system says this about fileExistsAtPath:isDirectory:
"The method traverses final symbolic links."
The ADC site saus:
"This method does not traverse final symbolic links."
Neither location included any mention of that for the fileExistsAtPath
method w/o the directory param.
So, I tried it out with a broken link at the end of the path and
FileExistsAtPath does indeed return YES.
So this documentation...
>
- (BOOL)fileExistsAtPath:(NSString *)path
>
Returns YES if the file specified in path exists, or NO if it does not. If
>
path specifies a symbolic link, this method traverses the link and returns YES
>
or NO based on the existence of the file at the link destination. If path
>
begins with a tilde, it must first be expanded with
>
stringByExpandingTildeInPath, or this method will return NO.
...seems to be missing the "This method does not traverse final symbolic
links" disclaimer, but it in fact does not.
- Dave
On 4/8/04 3:29 PM, "Fritz Anderson" <email@hidden> wrote:
>
fileExistsAtPath:isDirectory: "does not traverse final symbolic links."
>
>
-- F
_______________________________________________
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.