October 2007 - Boost - lists.preview.boost.org

[Test] Way to tell if a test has failed?
by John Maddock 01 Nov '07

01 Nov '07

If I'm using #include <boost/test/included/test_exec_monitor.hpp> Is there a way to check if the last BOOST_CHECK_CLOSE passed or failed? I need to print out some additional information if it failed so I can track down which test case it was (the checks are in a loop that iterates over a table of data). Thanks, John.

4 9

Re: [boost] [pimpl] Proposal. Determining interest.
by batov 01 Nov '07

01 Nov '07

An overwhelming :-) interest in the proposed Pimpl has certainly been overwhelming. LOL. The Pimpl idiom has certainly been beaten up and its complexity/importance is far from, say, a threading library. Havings said that I feel that the simple Pimpl deployment technique and the suggested Pimpl interface is simple, elegant and pleasant to use with no drawbacks that I can see so far. I've updated and uploaded (as Pimpl-02.zip) the pimpl interface that implements both value- and pointer-semantics. Any comments are most welcome. Best, Vladimir.

4 3

Logging library
by Jurko Gospodnetić 01 Nov '07

01 Nov '07

[This is a post separated from the 'Re: [rfc] Gui library' thread.] Hi John. >> > And if I had to cast my vote for 'the most needed C++ library' it >> > would be a good logging library and not the GUI one... :-) That is the >> > one area where we have not been able to find a 'good enough' solution >> > > He he ;) Please take a look at : > http://torjo.com/log2/doc/html/ > > I'm really interested in your feedback ! Actually we have looked at your library. It looks very promising and we event closely followed its original boost review. It does seem to have what we need (according to the docs and related posts on this list) but for now we chose not to use it only because you seemed to have stopped developing it for a while and no one took over as an active developer. If we were to start using it in our projects, we'd gladly contribute to it but we just did not have the resources to completely take over the development which seemed to be dead. In production code for now we just stick with our own hacked up logging support. Has very few features, does not do most of the things we would like it to, but does the job 'just good enough', holds no surprises and is easy to maintain. Not counting yours, currently the log4cxx library looks the most promising to us. Seems to be most evolved and have a relatively active development. On the other hand, some parts of it are way too filled with bugs (e.g. async logging support) and we were trying to get a handle on those before using it in production code. I really hope you get your library to boost. And we will try to test it out to see we can use it as it is now but I am unsure of the time frame for that as real-life is not leaving us much free time at the moment. :-) Best regards, Jurko Gospodnetić

4 10

[interprocess] inteprocess_exception is not defined
by Boris Gubenko 01 Nov '07

01 Nov '07

The header interprocess/sync/posix/interprocess_recursive_mutex.hpp uses inteprocess_exception which is not defined: bash-2.03$ find boost -name "*.hpp" -exec grep inteprocess_exception {} \; throw inteprocess_exception(system_error_code()); bash-2.03$ Because of this, some interprocess library tests fail to compile on HP-UX. Whether the fact that the offending code in the header is "visible" on HP-UX indicates some configuration problem on this platform, is a different question. Thanks, Boris

2 6

[statechart] Documentation update suggestion.
by Jurko Gospodnetić 01 Nov '07

01 Nov '07

Hi. Just an idea: update the documentation to explicitly note that statechart using code should synchronize both processEvent() and terminate() calls when using a single statechart from multiple threads. We just solved a bug in one of our projects using the statechart library where we forgot to synchronize the terminate() call. Was causing non-reproducible assertion failures in the termination code. :-) Hope this helps. Best regards, Jurko Gospodnetić

2 1

Not yet approved library documentation mark
by David Rodríguez Ibeas 01 Nov '07

01 Nov '07

Hi, I am new to Boost libraries, and each so often I look for some functionality that might be implemented in a Boost library --logging, exception, ...-- some of the libraries that I want are still in work (logging) or pending approval (exception), but it does not seem easy to detect this from the docs. I believe that requiring all proposals' documentation to have a reference to its current review state would be interesting while not time demanding for the developers. What I am proposing is that in any and all not-yet-approved library that is proposed to boost the docs (ideally close to the title) document the status, for example in http://www.revergestudios.com/boost-exception/boost-exception.htm title could read: Boost Exception [pending approval] or something alike. David

4 5

Suddenly unresolved symbols show up on the trunk
by Markus Schöpflin 01 Nov '07

01 Nov '07

Hello, I number of string tests just started failing with the following error: ld: Unresolved: boost::debug::under_debugger(void) boost::debug::attach_debugger(bool) boost::debug::detect_memory_leaks(bool) boost::debug::break_memory_alloc(long) boost::debug::set_debugger(boost::unit_test::basic_cstring<const char>, boost::unit_test::callback1<const boost::debug::d For example: libs/algorithm/string/test/predicate.test libs/algorithm/string/test/find.test libs/algorithm/string/test/regex.test What happened? Markus

3 4

[Test] Patch to fix problems with VC8-Windows CE
by David Deakins 01 Nov '07

01 Nov '07

Attached is a small patch for execution_monitor.ipp to fix Windows CE-related problems in the new test library code. The changes are mostly just a few #ifdef blocks to account for the following: - The Windows CE CRT does not support _set_se_translator or _set_invalid_parameter_handler. - The Windows CE CRT supplies _vsnprintf instead of vsnprintf. - The Windows CE CRT does not support errno. Thanks, -Dave Index: execution_monitor.ipp =================================================================== --- execution_monitor.ipp (revision 40282) +++ execution_monitor.ipp (working copy) @@ -141,7 +141,9 @@ #endif +#ifndef UNDER_CE #include <errno.h> +#endif #include <boost/test/detail/suppress_warnings.hpp> @@ -158,7 +160,8 @@ #ifdef __BORLANDC__ # define BOOST_TEST_VSNPRINTF( a1, a2, a3, a4 ) std::vsnprintf( (a1), (a2), (a3), (a4) ) #elif BOOST_WORKAROUND(_MSC_VER, <= 1310) || \ - BOOST_WORKAROUND(__MWERKS__, BOOST_TESTED_AT(0x3000)) + BOOST_WORKAROUND(__MWERKS__, BOOST_TESTED_AT(0x3000)) || \ + defined(UNDER_CE) # define BOOST_TEST_VSNPRINTF( a1, a2, a3, a4 ) _vsnprintf( (a1), (a2), (a3), (a4) ) #else # define BOOST_TEST_VSNPRINTF( a1, a2, a3, a4 ) vsnprintf( (a1), (a2), (a3), (a4) ) @@ -905,6 +908,8 @@ //____________________________________________________________________________// +#ifndef UNDER_CE + void BOOST_TEST_CALL_DECL invalid_param_handler( wchar_t const* /* expr */, wchar_t const* /* func */, @@ -916,6 +921,8 @@ "Invalid parameter detected by C runtime library" ); } +#endif + //____________________________________________________________________________// void BOOST_TEST_CALL_DECL @@ -951,11 +958,14 @@ int execution_monitor::catch_signals( unit_test::callback0<int> const& F ) { +#ifndef UNDER_CE _invalid_parameter_handler old_iph; if( !p_catch_system_errors ) _set_se_translator( &detail::system_signal_exception::seh_catch_preventer ); - else { + else +#endif + { if( !!p_detect_fp_exceptions ) detail::switch_fp_exceptions( true ); @@ -963,15 +973,19 @@ _CrtSetReportHook( &detail::assert_reporting_function ); #endif +#ifndef UNDER_CE old_iph = _set_invalid_parameter_handler( reinterpret_cast<_invalid_parameter_handler>( &detail::invalid_param_handler ) ); +#endif } detail::system_signal_exception SSE( this ); + + int ret_val = 0; __try { __try { - return detail::do_invoke( m_custom_translators , F ); + ret_val = detail::do_invoke( m_custom_translators , F ); } __except( SSE( GetExceptionCode(), GetExceptionInformation() ) ) { throw SSE; @@ -982,11 +996,13 @@ if( !!p_detect_fp_exceptions ) detail::switch_fp_exceptions( false ); +#ifndef UNDER_CE _set_invalid_parameter_handler( old_iph ); +#endif } } - return 0; + return ret_val; } //____________________________________________________________________________// @@ -1093,10 +1109,20 @@ // ************** system_error ************** // // ************************************************************************** // +#ifdef UNDER_CE + system_error::system_error() +: p_errno( 0 ) +{} + +#else + +system_error::system_error() : p_errno( errno ) {} +#endif + //____________________________________________________________________________// } // namespace boost

2 6

Re: [boost] [pimpl] Proposal. Determining interest.
by Vladimir.Batov＠wrsa.com.au 01 Nov '07

01 Nov '07

> I've downloaded it, read the documentation, and I think it looks promising. > > To test it out I'm converting a pimpled class in my code base to use > your library. This class is noncopyable and as such it isn't immediately > obvious to me whether the class should be modeled using the pimpl's > value semantics, pointer semantics, or some other semantic that doesn't > yet exist. > > > Thanks, > > Michael Marcin Achieving non-copyability seems as straightforward as struct Foo : public pimpl<Foo>::pointer_semantics, boost::noncopyable { }; Thanks, Vladimir.

2 1

[fusion/range] rev 40506 broke xpressive
by Markus Schöpflin 31 Oct '07

31 Oct '07

Hello, this checkin: ------------------------------------------------------------------------ r40506 | nesotto | 2007-10-27 15:57:20 +0000 (Sat, 27 Oct 2007) | 1 line Changed paths: D /trunk/boost/range/const_reverse_iterator.hpp M /trunk/boost/range/metafunctions.hpp D /trunk/boost/range/result_iterator.hpp D /trunk/boost/range/reverse_result_iterator.hpp cleaned up deprecated headers ------------------------------------------------------------------------ is the cause for this errors seen in xpressive: cxx: Severe: ../../../boost/xpressive/detail/utility/symbols.hpp, line 24: could not open source file "boost/range/result_iterator.hpp" (srcfilnoopen) #include <boost/range/result_iterator.hpp> ------------------------------------------^ Probably xpressive needs an update? Regards, Markus

5 9