No one should be using path-based API any more, generally.
You should use URL-based equivalents.
Why? Really, why? Certainly there are APIs where we have to use URL's and
we have to convert the path into a URL, but where a non-deprecated
path-based URL exists, what current or future obstacles
On Sep 14, 2014, at 00:57 , Aandi Inston aa...@quite.com wrote:
Why? Really, why? Certainly there are APIs where we have to use URL's and
we have to convert the path into a URL, but where a non-deprecated
path-based URL exists, what current or future obstacles do you foresee? The
URL doesn't
Le 14 sept. 2014 à 10:23, Quincey Morris quinceymor...@rivergatesoftware.com
a écrit :
On Sep 14, 2014, at 00:57 , Aandi Inston aa...@quite.com wrote:
Why? Really, why? Certainly there are APIs where we have to use URL's and
we have to convert the path into a URL, but where a
On Sep 14, 2014, at 2:57 AM, Aandi Inston aa...@quite.com wrote:
No one should be using path-based API any more, generally.
You should use URL-based equivalents.
Why? Really, why? Certainly there are APIs where we have to use URL's and
we have to convert the path into a URL, but where a
Performance is another reason. IIRC, in earlier OS X releases it turned out
that there was significant overhead stemming from converting between different
types of file references as a call went up and down the stack —
NSString/CFString —NSURL/CFURL — FSRef — C strings, etc. (This may sound
