> Speaking as a battle-hardened QA manager, the one simple step of
> turning on all warnings and removing them
Absolutely. Which is why pointless warnings really annoy me!
FYI, I'm not talking about Xcode/gcc here. I'm thinking of an old version of
Watcom, in which a warning was generated for eve
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-harde
