|
Compiler warnings are one of the most helpful tools for developers. The compiler can not only warn you about obvious mistakes (such as a method you forgot to implement); it also identifies many code patterns that, though syntactically correct, are potentially dangerous (like signed/unsigned conversion) or just plain wrong (such as mismatched format specifiers in a format string). Both the Clang compiler frontend and Apple’s default Xcode project templates have a default set of warnings enabled, designed to warn you about many probable errors in your code but not annoy you with tons of false positives.... They are not the best choice for new projects, though. Instead, you should strive to switch on as many warnings as possible. Which warnings should you enable? All of them, most of the time.
|
|
|
|
|
It gives me a nice warm fuzzy feeling to know that if I ever accidentally slip into using Objective-C I will be warned, comprehensively, repeatedly and necessarily.
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|