There is a bit of confusion around the word "understand" here. It is
sensible to think of an object as "understanding" a message or not, but in
fact the selector that tells you whether an object understand a message is
#respondsTo:, while the equivalent on the class which tells you whether
instance
"nil did not understand #selector" is great.
Similarly, "Instance of " can be replace by "a" as in
"aObject did not understand #selector"
"aReadWriteStream did not understand #selector"
For classes
"PragmaMenuBuilder class did not understand #selector"
Daniel Slomovits wrote:
I think it's beca
I think it's because nil *is* pretty special--this is the equivalent of a
NullPointerException or similar in other languages (even though in fact nil
is an object like any other, it *is* usually a different type of *semantic*
error on the part of the programmer than with any other class).
Undefined
