$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: [boost] [new Warnings policy] what to do about msvc "deprecation" and "unsafe" warnings
From: Robert Ramey (ramey_at_[hidden])
Date: 2009-11-16 00:56:29
I've implemented the suggestions in "new warnings policy". It probably DID
catch a few bugs which have probably been in there for years. It wasn't as
bad as I thought - mostly tedium and a few hours of testing. But now I have
a couple of questions:
a) I added
<toolset>gcc:<warnings>all # ?
<toolset>msvc:<warnings>all # == /W4
To my jamfile.
With MSVC 9.0 I now get a blizzard of "deprecation" and "unsafe" warnings.
If the policy is updated to address this, I will implement the
recommendations.
Robert Ramey
PS
I'm wondering if I should replace the above with something which maximizes
the warning level for all compiles. Perhaps just
<warnings>all #?