Re: [boost] [new Warningspolicy] MSC4180 ontheMaintenance Guidelines

Subject: Re: [boost] [new Warningspolicy] MSC4180 ontheMaintenance Guidelines
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-11-23 13:28:08

Peter Dimov wrote:
> Stewart, Robert wrote:
> > Peter Dimov wrote:
>
> >> - ensure that warnings are not introduced into other
> >>   developers's code.
> >
> > I'm not sure quite what you mean or how you would impose this.
>
> Developer A has written code that compiles cleanly with MSVC
> /W4. Developer B fixes an issue in this code and the result
> compiles cleanly with g++ -Wall, but happens to introduce a
> warning under MSVC. (Or Sun C++, for that matter.)
>
> (Incidentally, both developers have built at a reasonably
> high warning level and have seen no warnings.)

It would be reasonable to state that if a developer changes the trunk in such a way as to introduce warnings on an inaccessible platform, that developer is required to seek support from other developers to discover a mutually compatible change.

It would be plausible to require only that a developer monitor trunk tests for warnings on other platforms while trying variations of the code seeking compatible changes.  However, that would mean a longer cycle time and more noise in the diffs while seeking an appropriate variation.

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