Warning Messages
- Warning Message: '<className>' may not respond to '<methodName>'
Interpretation: A message receiver is a class that does not have the named method defined for it. The method name in your message may be spelled or capitalized incorrectly. Alternatively, the receiver may belong to a different class than you think it is in.
- Warning Message: Cannot find interface declaration for '<className>'
Interpretation: The implementation file does not include an
#importdirective for the header file.- Warning Message: Control reaches end of non-void function
Interpretation: Your method is declared to return a value, but the method does not contain a
returnstatement. This commonly occurs when you insert an empty method as a placeholder in the implementation and the method is defined to return a non-void value.- Warning Message: Incompatible Objective-C types initializing ’struct NSArray *', expected ’struct NSString *'
Interpretation: A method declaration in the header states that the returned value is an
NSString, but the implementation says the returned value is anNSArray. They need to be the same type.- Warning Message: Incompatible Objective-C types returning ’struct NSString *', expected ’struct NSArray *'
Interpretation: A method is defined to return an
NSArray, but the returned value is defined as anNSStringtype.- Warning Message: Incomplete implementation of class '<className>'
Interpretation: The compiler can’t match all declarations in the header with corresponding implementations. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access