Re: Seeing nil passed to isEqual:, despite non-null declaration
Re: Seeing nil passed to isEqual:, despite non-null declaration
- Subject: Re: Seeing nil passed to isEqual:, despite non-null declaration
- From: Sandor Szatmari <email@hidden>
- Date: Fri, 13 Jan 2017 13:06:11 -0500
I was thinking, and I'm guessing there were no warnings and errors in Xcode on this line of code, that a clean compile would indicate that the header did not match the documentation. Does this make sense?
Sandor
> On Jan 13, 2017, at 12:53, Jens Alfke <email@hidden> wrote:
>
>
>> On Jan 13, 2017, at 9:46 AM, Sean McBride <email@hidden> wrote:
>>
>> Anyone ever seen nil passed to isEqual:? Is the SDK declaration maybe wrong?
>
> Check the class documentation, not just the header. The parameter is declared as:
> anObject The object to be compared to the receiver. May be nil, in which case this method returns NO.
>
> So yes, the parameter should be declared as `nullable`.
>
> —Jens
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden