On 21 Aug 2008, at 04:03, Michael Ash wrote:
This hazard goes away if you turn on the appropriate warnings. I
compile all of my code with "-W -Wall -Wno-unused-parameter", and it
has caught much more than just this error over the years.
[getting slightly off topic]
Speaking as a battle-hardened QA manager, the one simple step of
turning on all warnings and removing them is one of the cheapest ways
possible to improve the quality of the output of a dev team[1]. I'm
astounded that pretty much every commercial dev team I've worked with
have been content to check in code with warnings until I harangue them
about it. Also amazing is that they all KNEW what -Wall and -Werror do
but were content not to bother with them.
Neil.
[1] Of course firing the chaff is cheaper in the short term, but is
not always seen as a pragmatic option when projects are underway.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
