Re: [boost] Are warnings acceptable artifacts from builds?

Subject: Re: [boost] Are warnings acceptable artifacts from builds?
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-09-11 14:31:48

Emil Dotchevski wrote:
>
> If the "we want no warnings dammit" crowd main argument is "at my
> company we have zero-warnings policy, we can't do anything about it"
> then arguing whether or not any particular warning should be addressed
> is pointless (OTOH, I'd bet that no company has zero-warnings policy
> because some warnings can't be dealt with any other way but by
> disabling them.)

Disabling a warning, provided the scope is controlled, is fine.  A company may craft a warnings policy, used whenever building code, that always disables select warnings, too, but that doesn't violate the zero warnings policy.

Given a certain warnings configuration, however, developers at a zero warnings company expect builds to produce no warnings, which leads to expecting library cooperation.

So long as the library author/maintainer is willing to try to eliminate warnings identified by users, there should be no problem.  This is appropriate even for users that don't have a zero-warnings policy.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.