@lists.apple.com
Oggetto: Re: IsReadableFileAtPath
-Kevin
On Mar 1, 2010, at 11:20 AM, gMail.com wrote:
Hi,
I need to check whether a file or a symlink could be really copied.
I have just seen that the Cocoa API isReadableFileAtPath traverses the
symlink, so, in case the target file
@gmail.com
Cc: cocoa-dev@lists.apple.com
Oggetto: Re: IsReadableFileAtPath
-Kevin
On Mar 1, 2010, at 11:20 AM, gMail.com wrote:
Hi,
I need to check whether a file or a symlink could be really copied.
I have just seen that the Cocoa API isReadableFileAtPath traverses the
symlink, so
Hi,
I need to check whether a file or a symlink could be really copied.
I have just seen that the Cocoa API isReadableFileAtPath traverses the
symlink, so, in case the target file is not readable, my app doesn't copy
the symlink, while the Finder can properly do. So my app does wrong
On Mar 1, 2010, at 12:20 PM, gMail.com wrote:
I need to check whether a file or a symlink could be really copied.
I have just seen that the Cocoa API isReadableFileAtPath traverses the
symlink, so, in case the target file is not readable, my app doesn't copy
the symlink, while the Finder can
On Mar 1, 2010, at 11:20 AM, gMail.com wrote:
I have just seen that the Cocoa API isReadableFileAtPath traverses the
symlink, so, in case the target file is not readable, my app doesn't copy
the symlink, while the Finder can properly do. So my app does wrong.
-isReadableFileAtPath is just
?
-Kevin
On Mar 1, 2010, at 11:20 AM, gMail.com wrote:
Hi,
I need to check whether a file or a symlink could be really copied.
I have just seen that the Cocoa API isReadableFileAtPath traverses the
symlink, so, in case the target file is not readable, my app doesn't copy
the symlink, while
On Mar 1, 2010, at 3:24 PM, Jens Alfke wrote:
-isReadableFileAtPath is just a convenience. If you don't want to traverse
symlinks, call -fileAttributesAtPath:traverseLink: and use NO for the second
parameter.
Unfortunately, fileAttributesAtPath:traverseLink: is deprecated. The
replacement