On Tue, Sep 8, 2009 at 1:11 PM, Stewart, Robert<Robert.Stewart@sig.com> wrote:
Emil Dotchevski wrote:
Warnings may indicate a problem with your own code but in anyone else's code they should be ignored.
Unfortunately, compilers don't distinguish yours from theirs, so that doesn't work. It also doesn't solve the problem for those that prefer to treat warnings as errors.
It also doesn't solve the problem of those who prefer to shoot themselves in the foot. :)
Insisting to fix warnings is somewhat insulting to the author of the library, too. It presumes that they did something unreasonable, when in fact the warning itself may be unreasonable.
The warning may, in fact, be unreasonable, but the library author should do all possible to quiet the warning.
Why? Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode