On Apr 26, 2009, at 8:22 AM, Iceberg-Dev wrote:

Is it possible to copy a symbolic link (the symbolic link file and not the item it references) using the FSPathCopyObjectSync API?

No valuable info was found in the documentation, the list archive, google results.

The File Manager Reference
http://developer.apple.com/documentation/Carbon/Reference/ File_Manager/Reference/reference.html#//apple_ref/c/func/ FSCopyObjectSync
saying
A pointer to the source object to copy. The object can be a file or a directory.


would suggest to me that a symlink file would be OK.

Not sure if your searching came across "FSCopyObject - /Sources/ FSCopyObject.c"
http://developer.apple.com/SampleCode/FSCopyObject/listing3.html

but it might be informative to your question.

I was into these or similar links for a problem of my own yesterday but "the documentation, the list archive and google results" did lead to a resolution which they often do. I wasn't aware symlinks might be a problem until I started getting -1407 File Manager errors that seemed related to these files. Since you are aware in advance they might be a concern a little testing might give you a more definite answer and save some searching. (Fwiw, I eliminated the use in one place of an FSSpec since these seem to be getting more and more deprecated these days and I used FSPathMakeRefWithOptions (10.4+) in another place which looked like it would default resolve symlinks and these changes seemed to correct my own problem. No -1407 errors).

Mike Hall        hallmike at att dot net
http://www.geocities.com/mik3hall
http://sourceforge.net/projects/macnative



Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

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 arch...@mail-archive.com

Reply via email to