2 ms·
> but it causes silent bugs, where you thought something was happening but it wasn't. In Objective-C, it could be a silent bug or just intended behavior to sen
by protomyth 13y ago
> but it causes silent bugs, where you thought something was happening but it wasn't.
In Objective-C, it could be a silent bug or just intended behavior to send messages to a nil object. It is explained here: http://developer.apple.com/library/ios/#documentation/cocoa/conceptual/ProgrammingWithObjectiveC/WorkingwithObjects/WorkingwithObjects.html http://developer.apple.com/library/ios/#documentation/cocoa/...
- Strilanc 13y agoOf course, the behavior may be intended. I've certainly taken advantage of nil doing nothing. I've also accidentally had a nil where it wasn't expected, and lost time figuring out why particular effects weren't occurring. More time than I would have lost if the mistake had caused an immediate exception. The same type of mistake is still possible (unexpected value), though the consequences are different, so I don't think it makes sense to say nil solves the null problem.