Comments on Cocoa with Love: 8 Confusing Objective-C Warnings and Errors

With regards to Rule #2 and forwarding declaring v...

2011-08-15T09:56:38.695-07:00

With regards to Rule #2 and forwarding declaring vs. importing a peer class in the .h/.m files respectively: If we're using a custom view controller, and we want it to conform to a protocol that is defined by a peer class rather than a superclass, it isn't possible to use a forward declaration and still still declare ourselves a conforming delegate. What's the best practice in this case? Do we make exception and import the .h of our protocol-defining-class within our view controller's .h?

Having methods in a class with the same name but d...

2011-07-19T22:11:29.491-07:00

Having methods in a class with the same name but different signatures is something I did in Java, is this the problem and should I not be doing this in Objective-C.

AARUUSH-2011

Also for the error: "duplicate interface decl...

2011-06-14T08:11:20.988-07:00

Also for the error: "duplicate interface declaration for class", you can get this if your import statements are below your @implementation line in your .m file.

If you want subclasses to inherit methods but not ...

2010-04-16T05:25:40.000-07:00

If you want subclasses to inherit methods but not to have those methods in the public interface (effectively being "protected" scope methods), you should declare an @protocol for the class with these pseudo-protected methods, put it in a "-priv.h" header file and only #include it in the subclasses.

No way of fixing. The declaration of a method in m...

2010-04-16T04:59:25.000-07:00

No way of fixing. The declaration of a method in m file cannot be seen in the child class as you #import only the header file.