23 Nov
2009
23 Nov
'09
6:04 p.m.
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.)