-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Nicola Musatti Sent: Wednesday, May 02, 2007 1:53 PM To: boost@lists.boost.org Subject: Re: [boost] [1.34.0beta] many, many warnings... :(
I'm convinced that library authors already make an effort to clear warnings on the platforms they have available. The real problem is dealing with platforms not available to developers. For those you do need to rely on regression reports and feedback after a tentative patch can take as long as a whole week. Furthermore I'm sure that library authors already devote to Boost all the time they can afford.
Exactly, which is why I suggested a fix-all-warnings bug. [snip]
If we do this, and then at some point accept this catch-all set of patches, then we can turn on warnings as errors once the patches have been merged. I've had to do this before, and this works as far as setting you up for the future.
For how many platforms at the same time? I don't see this working unless you're able to ensure nightly regression testing turnaround for all the supported platforms.
It sounds like gcc/msvc are the ones people would be most happy with. By turnaround, do you mean them actually running? I don't see why it wouldn't be possible for a subset of configurations. Sohail