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

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

Emil Dotchevski wrote:
> On Tue, Sep 8, 2009 at 1:59 PM, Stewart,
> Robert<Robert.Stewart_at_[hidden]> wrote:
> > Emil Dotchevski wrote:
> >> On Tue, Sep 8, 2009 at 1:27 PM, Stewart,
> >> Robert<Robert.Stewart_at_[hidden]> wrote:
> >> > Emil Dotchevski wrote:
> >> >> On Tue, Sep 8, 2009 at 1:11 PM, Stewart,
> >> >> Robert<Robert.Stewart_at_[hidden]> wrote:
> >> >> >
> >> >> > The warning may, in fact, be unreasonable, but the library
> >> >> > author should do all possible to quiet the warning.
> >> >>
> >> >> Why?
> >> >
> >> > For the reasons I already gave.
> >>
> >> To address someone's preference?
> >
> > Come now.  I gave more reasons than that one.
>
> I think that you assume that the warning is reasonable and easy to
> fix, as with most warnings that could be silenced with casts. A lot of
> times, fixing such warnings is common sense. In that case, just a note
> to the library developer would be enough to have it fixed.
>
> But you can't generalize from this, to "all warnings should
> be silenced."

I never did that, though you seem intent upon imposing that view upon me.  Go back and reread my earlier posts.  You'll see that I said to remove all warnings possible.  I know that not all can be removed.  I also know that most can be.  Your arguments have been adversarial from the start, claiming that those with my view are being rude to you, the library developer, whose code shouldn't be questioned.  (Review your own posts to see why I would say so.)

The goal should be to eliminate every warning possible because a library's warnings should not obscure a library user's warnings and errors, because the warnings connote inferior library code quality to the user (I'd think library developers would wish to avoid such connotations), and because there are many that treat warnings as errors.  If warnings cannot be avoided, then they should be documented and the library user must deal with such warnings as best they can.  That doesn't change the goal.

_____
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.