In Boost testing, wouldn't it be a good idea to have a script that scans the output generated from each successful test for the word "warning" and indicate its presence in the test matrix? Perhaps leave the box green but instead of "pass" have it say "pass/w" or something. Without this, platform-specific warnings can only be addressed after they're reported by the end users. Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
Emil Dotchevski wrote:
In Boost testing, wouldn't it be a good idea to have a script that scans the output generated from each successful test for the word "warning" and indicate its presence in the test matrix? Perhaps leave the box green but instead of "pass" have it say "pass/w" or something. Without this, platform-specific warnings can only be addressed after they're reported by the end users.
Perhaps. Though some warnings would never show, because the affecting switches are never used in boost testing. In practice, anyway, you need the compiler for most changes, be them warning suppressions or workarounds. And what you don't have you can't support. -- Genny
On Sat, Sep 13, 2008 at 2:21 PM, Gennaro Prota <gennaro.prota@yahoo.com> wrote:
Emil Dotchevski wrote:
In Boost testing, wouldn't it be a good idea to have a script that scans the output generated from each successful test for the word "warning" and indicate its presence in the test matrix? Perhaps leave the box green but instead of "pass" have it say "pass/w" or something. Without this, platform-specific warnings can only be addressed after they're reported by the end users.
Perhaps. Though some warnings would never show, because the affecting switches are never used in boost testing.
In practice, anyway, you need the compiler for most changes, be them warning suppressions or workarounds. And what you don't have you can't support.
I'm with you 100%, I personally don't pay much attention to warnings. I was mostly saying that since users of Boost complain about them, I (as a Boost developer) don't mind addressing the issue before my code is included in user builds, but I can't do it without the testing framework at least preserving the successful logs. Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
participants (2)
-
Emil Dotchevski -
Gennaro Prota