On Feb 26, 2016, at 6:12 PM, Jens Alfke wrote:
> On Feb 26, 2016, at 4:48 PM, Quincey Morris
> wrote:
>>
>> According to NSError documentation:
>
> Thanks, but I did read the documentation before asking.
I think Quincey Morris' summary is accurate - at least, it matches my
understanding - a
On Feb 26, 2016, at 18:12 , Jens Alfke wrote:
>
> Thanks, but I did read the documentation before asking.
Then your question makes no sense. One of the URL keys is specific to
NSURLErrorDomain, and that isn’t your error domain to use. That means your only
standard choice is the other URL key.
> On Feb 26, 2016, at 4:48 PM, Quincey Morris
> wrote:
>
> According to NSError documentation:
Thanks, but I did read the documentation before asking.
> On Feb 26, 2016, at 4:53 PM, dangerwillrobinsondan...@gmail.com wrote:
>
> It seems like the shorter one would be for a "click here to se
It seems like the shorter one would be for a "click here to see more
information or open this file URL" and the longer one is for "this URL failed
to load".
But it definitely deserves a docs bug.
It might be one of those obscure things noted in some programming guide doc,
but even if it is tha
On Feb 26, 2016, at 16:33 , Jens Alfke wrote:
>
> What’s the difference between these? If I’m creating an NSError and adding a
> URL to it, which one is preferred?
According to NSError documentation:
> • NSURLErrorKey
> The corresponding value is an NSURL object.
>
> • NSURLErrorFailingURLErr
So, NSError.h declares NSURLErrorKey, as a userInfo key for the URL associated
with the error.
And NSURLError.h declares NSURLErrorFailingURLErrorKey, which appears to have
the same purpose.
Neither of these is deprecated, although there’s yet another constant
(NSErrorFailingURLStringKey) that i
