Daniel Jalkut of Red Sweater Software fame wrote an entry today about warnings and how we dutifully ignore them. I share his concerns wholeheartedly. There is nothing more frustrating than compiling a project (of seemingly good quality on the web) only to be bombarded with all manners of warnings to the point the important stuff just slips by unnoticed. Objective-C makes this all the more easier due to its dynamic nature.
Although I don’t believe in forcing warnings into errors (some warnings can legitimately be ignored), I do make it a point to kill as many warnings (if not all of them) in code I ship (milestones, releases). Obviously, warnings will be abundant during development, but it should be just as important to get them solved as it is to debug and sample before pushing a program to the public.