Re:Compiler Warnings for Objective-C Developers
by demallien on Saturday April 27, 2013 @07:44PM
(#5619502)
Warnings are output to stderr. Personally I just do this:
make > /dev/null
All that you see after that are warnings and errors.
Re:Compiler Warnings for Objective-C Developers
by gizmo686 on Saturday April 27, 2013 @07:26PM
(#5619443)
When I build a program with make, the warnings are very easy to spot. While you do, without warnings, see a bunch of text fly through the screen, all of that text looks incredibly simmilar. Warnings (and errors) stick out in the wall of text.
Re:Compiler Warnings for Objective-C Developers
by redshirtrob on Saturday April 27, 2013 @07:46PM
(#5619511)
I guess we've just had different experiences. I can say from experience, without a doubt, that I could not possibly pick out a warning among hundreds of compile/link commands.
Now, if dependencies were in order, and I'd just made a small change to a single file, and had previously built the project successfully, I'm sure I could probably catch a single warning. That's a lot of assumptions to work from. I prefer to let the build fail.
Certainly building with a tool like Xcode makes the warnings more conspicuous, and you can just choose to fix all warnings. I don't see anything wrong with that approach, but I still prefer to just treat the warnings as errors. I guess it's just how I'm built.:)