Re: FSCopyObject... replacement?
Re: FSCopyObject... replacement?
- Subject: Re: FSCopyObject... replacement?
- From: Jim Luther <email@hidden>
- Date: Thu, 01 May 2014 15:46:31 -0700
The header comments are incorrect. The man page is much more up to date.
- Jim
On May 1, 2014, at 2:33 PM, Paul Kim <email@hidden> wrote:
> According to the docs for FSCopyObjectSync/Async:
> =================
> (Deprecated in OS X v10.8. At the Foundation layer, use copyItemAtURL:toURL:error: instead. At the POSIX/BSD layer, use copyfile(3) OS X Developer Tools Manual Page instead.)
> =================
>
> Since I need the callbacks, I am using copyfile(). It seems to work fine though glancing at the header, I see this:
>
> * This implementation is incomplete and the interface may change in a
> * future release.
>
> I’m taking the header comments with a grain of salt since it’s inaccurate about other things (like the state argument having to be NULL). Maybe the header is grossly out of date? I’m wondering if I can count on copyfile() in the future or if this is going to become deprecated or significantly changed.
>
> paul
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Filesystem-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden