There is a means to do that: http://ddeville.me/2013/06/ruby-like-nil-messaging-in-objective-c/ http://ddeville.me/2013/06/ruby-like-nil-messaging-in-object...

There is a means to do that: http://ddeville.me/2013/06/ruby-like-nil-messaging-in-objective-c/ http://ddeville.me/2013/06/ruby-like-nil-messaging-in-object... I have a feeling it wouldn't work well in practice if you made the handler raise an exception. As the author notes, you're not the only one sending messages, and Cocoa will probably crash your program with a nil message send sooner or later. But you might be able to use it to find out where it's happening, at least.