I know this suggestion has been made but I want to expand a little on it. a "library" - warning policy test. This would be just like any other library as far as the testing system goes. It would have maybe 10? small compile only tests which would emit warnings or not. The source would describe which warning is in fact being tested. Presumably, the test matrix would permit one to look at the warning messages. (I'm not sure that the current one does this). In anycase, it would permit the test matrix be used to check the warning status for each warning on each compiler at a specified warning level. I see this as the only way to get a real grip on how these things vary among the array of compiler's we might use. I realize that it would be some work, but I would think it wouldn't be all that much more - if any - than that which has already been expended on the wiki. It would have the great advantage of being relatively free of "maintainence by hand". It would automate the whole process of determining the status of different compilers in this area. Robert Ramey Paul A. Bristow wrote:

https://svn.boost.org/trac/boost/wiki/Guidelines/MaintenanceGuidelines (bottom of the page)

has a collection of suggestions for 'quieting' warnings on MSVC and GCC, but no information on other compilers yet.

Can users of these compilers please

1 Assert that they never have a problem with unhelpful compiler warnings from Boost stuff, or

2 Send common warnings and suggestions for dealing with them by suppressing or by 'fixing' the code (so that I can add to the guidelines.

Thanks

Paul

--- Paul A. Bristow Prizet Farmhouse Kendal, UK LA8 8AB +44 1539 561830, mobile +44 7714330204 pbristow@hetp.u-net.com