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

Subject: Re: [boost] [new Warningspolicy] MSC4180 ontheMaintenance Guidelines
From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2009-11-23 18:25:56

On Mon, Nov 23, 2009 at 10:28 AM, Stewart, Robert
<Robert.Stewart_at_[hidden]> wrote:
> 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.

I'd call this common sense. Assuming you're not proposing that we
introduce some kind of bureaucracy or a committee to help manage
warnings, and assuming everyone agrees that we don't want warnings in
the build logs, then simply reporting a warning will get it removed.

Or are you envisioning a different process?

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode