Re:The Brilliance of “nil” in Objective-C
by happytoexplain on Friday April 29, 2022 @02:56PM
(#31209266)
>Don’t make it an exception to compare against nil. But don’t ascribe any other meaning to the value
If comparing against nil does not fail, you are ascribing the value of "false" to it. If it works in every use case, you are ascribing an arbitrary value to it in every use case.
If comparing against nil does not fail, you are ascribing the value of "false" to it. If it works in every use case, you are ascribing an arbitrary value to it in every use case.