Changes between Version 1 and Version 2 of WarningFixes

Timestamp:

Nov 8, 2009, 5:25:41 PM (13 years ago)

Author:

John Maddock

Comment:

--

WarningFixes

@@ -5 +5 @@
  * Boost headers: warnings emitted with a long template instantiation back trace are particularly troublesome.
  * Boost source code: Users building Boost on their platform should ideally see a clean build with no warnings.
+ * Core libraries, that are reused by other Boost libraries.
 
 The main test compilers and flags are:
@@ -12 +13 @@
 
 In addition if library test cases can be made warning free, then we can begin to enforce a no-warnings policy by testing with warnings-as-errors with the above compilers.
+
+||'''Library'''||'''Owner'''||'''Status'''||'''Notes'''||
+||Config||johnmaddock||Clean||Only headers are clean, I haven't looked at the tests.||
+||Type Traits||johnmaddock||Clean||One test has (unfixable?) warnings with gcc.||
+||Regex||johnmaddock||Clean|| ||
+||Test||johnmaddock||[https://svn.boost.org/trac/boost/ticket/3598 Patches]||A couple of tests still produce warnings: Jamfile issues?||
+||Thread|| ||Warnings|| ||
+||Date Time|| ||Warnings|| ||
+||Program Options|| ||Warnings|| ||
+
+Please set the Status field above to one of:
+
+ * unknown - library hasn't been tested for warnings yet.
+ * warnings - we know that the library has warnings, but no one has done anything about it yet.
+ * bug - if a bug report has been filed on the trac (with link)
+ * patch - if a Trac patch has been filed (with link).
+ * clean - fixes are in Trunk.
+ * release - fixes are in release branch.
+
+Please set the owner field to the Trac user ID of the person currently investigating so that we don't duplicate effort.
+
+Libraries can be tested by cd'ing into boost-root/libname/test and invoking:
+
+{{{
+bjam msvc warnings=all
+}}}
+or
+{{{
+bjam gcc warnings=all cxxflags=-Wextra
+}}}
+