Re: [Boost-cmake] Test feedback
Beman Dawes wrote: > > Before inventing something new, why not ask the Boost.Build folks how > they suppress unwanted pop ups during Boost regression tests. They went > through the exact same sequence you are now repeating; first a lot of > popups occurred, then a few, then a few that closed automatically after > some time, and finally none at all. That's regardless of whether the > test involved is running under Boost.Test or not. Excellent point, but I assumed that Troy had already investigated that code since the suggestion has already been made in this thread. I have the impression that because of the way CMake launches build commands, the BB technique doesn't work all by itself(?) > Also, are you aware Boost.Test already has the equivalent of > "lightweight_test"? See trunk\boost\test\minimal.hpp. Is that really equivalent? IIUC, at the very least, minimal.hpp still defines your main() for you. > If minimal.hpp is > missing something, shouldn't the missing feature be added there rather > inventing a whole new kind of lightweight test? I wasn't proposing an additional kind of test; I was proposing a facility one could #include in a TU that would suppress error dialogs on Windows. -- Dave Abrahams BoostPro Computing http://www.boostpro.com ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] Test feedback
On Sun, Jun 29, 2008 at 9:41 AM, troy d. straszheim <[EMAIL PROTECTED]> wrote: > David Abrahams wrote: > >> troy d. straszheim wrote: >> >> The test that causes this is just a program with a main() routine... It >>> seems like it should use boost.test, and boost.test should be >>> responsible for making these dialog-suppressing calls. (Does that sound >>> like it makes sense?) >>> >> >> 1. I'm reluctant to recommend that any program use Boost.Test until its >> documentation is made to correspond to its actual interface. >> >> 2. You'd better ask Gennadiy what makes sense for Boost.Test; I don't >> understand the rationale by which it gets developed >> >> 3. Maybe we could have an option in boost/detail/lightweight_test, or >> simply a separate header called boost/detail/regression.hpp that >> includes something that does this. Maybe the old >> "dynamically-initialized static member of a template" trick makes sense >> here. >> >> > Roger that, skipping to #3... Before inventing something new, why not ask the Boost.Build folks how they suppress unwanted pop ups during Boost regression tests. They went through the exact same sequence you are now repeating; first a lot of popups occurred, then a few, then a few that closed automatically after some time, and finally none at all. That's regardless of whether the test involved is running under Boost.Test or not. Also, are you aware Boost.Test already has the equivalent of "lightweight_test"? See trunk\boost\test\minimal.hpp. If minimal.hpp is missing something, shouldn't the missing feature be added there rather inventing a whole new kind of lightweight test? --Beman ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] Test feedback
David Abrahams wrote: troy d. straszheim wrote: The test that causes this is just a program with a main() routine... It seems like it should use boost.test, and boost.test should be responsible for making these dialog-suppressing calls. (Does that sound like it makes sense?) 1. I'm reluctant to recommend that any program use Boost.Test until its documentation is made to correspond to its actual interface. 2. You'd better ask Gennadiy what makes sense for Boost.Test; I don't understand the rationale by which it gets developed 3. Maybe we could have an option in boost/detail/lightweight_test, or simply a separate header called boost/detail/regression.hpp that includes something that does this. Maybe the old "dynamically-initialized static member of a template" trick makes sense here. Roger that, skipping to #3... -t ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
