- Boost - lists.preview.boost.org

Volunteering to fix tab and min/max issues
by Jeremiah Willcock 21 May '09

21 May '09

Since tabs in source files and min/max guideline violations are so easy to correct, is it OK if I just fix them in all libraries (except for the inspection tool's examples)? I will not do any that appear to be intentional or that would change the meaning of the code. Do I have permission to do that and just commit the changes? -- Jeremiah Willcock

4 10

how to build boost with bzip2 in non-standard location?
by Oliver Kullmann 20 May '09

20 May '09

Hello, I want to build the full boost library, while I don't have bzip2 installed system-wide (but I just downloaded and installed it locally). It seems to me that http://www.boost.org/boost-build2/doc/html/bbv2/tasks/libraries.html should be relevant here for that task, but I find the descriptions too general to understand. I wonder whether somebody could simply tell me the lines to be entered into the bjam-configuration file? Perhaps bz2 : : <file> Path_to_libbz2.a ; But how to specify where to find bzlib.h ? Isn't it possible to specify the base directory, where then, as, usual include, lib and bin are found? Thanks in any case! Oliver

2 4

bootstrap.sh bug in 1.39.0
by Chris Saunders 20 May '09

20 May '09

There is a typo in the lib install directories in bootstrap.sh: $ diff bootstrap.sh bootstrap.sh.fixed 252c252 < LIBDIR="$EXPREFIX/lib" --- > LIBDIR="$EPREFIX/lib" 390c390 < EOF \ No newline at end of file --- > EOF ps. I wouldn't have minded checking what's on the head of svn first and reporting this throught the regular bug channels, but my browser won't let me past these certificate errors: """ Secure Connection Failed svn.boost.org uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. (Error code: sec_error_unknown_issuer) . . . etc """

3 2

Question for C++ experts about exception allocation failure
by Emil Dotchevski 20 May '09

20 May '09

How is failure to allocate an exception object handled in various compilers? 15.1.4 says that "the memory for the temporary copy of the exception being thrown is allocated in an unspecified way" but I don't think it specifies behavior for the case when the allocation fails. I know that some compilers allocate exceptions from the heap, so does this mean that an attempt to throw any exception could, in theory, result in a std::bad_alloc being thrown instead? As far as I can tell such behavior wouldn't violate the C++ standard, but I'm not sure my interpretation is correct. Anyone? Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

9 17

[MPL] Is there an "include all" header?
by Adam Badura 20 May '09

20 May '09

I am looking for a "include all" header for Boost.MPL. Is there such? For the Boost.Preprocessor (having similar structure) there is <boost/preprocessor.hpp> however <boost/mpl.hpp> does not exist. Is it by purpose or just a forgotten feature? Actually I think having such "include all" headers is very convenient especially for larger libraries. (Yes, I know I can write such header by myself and then just use it every time I want to use Boost.MPL however having a "standard one" would be easier I think.) Adam Badura

1 0

Volunteering to be a Review Manager
by Stewart, Robert 20 May '09

20 May '09

One thing that http://www.boost.org/community/reviews.html#Review_Manager doesn't mention is how a prospective review manager should volunteer. Presumably, one just sends a message to the developer's list to that effect, but I'd think a prescribed subject line would increase the likelihood that the review wizard sees it. _____ Rob Stewart robert.stewart(a)sig.com Software Engineer, Core Software using std::disclaimer; Susquehanna International Group, LLP http://www.sig.com IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

2 1

Re: [boost] Interest check: container with preallocated buffer
by Brian Wood 19 May '09

19 May '09

Thorsten Ottosen writes: >>Dmitry Vinogradov skrev: >> Boost.Array offers constant size container with preallocated buffer, >> Boost.Optional provides from zero to one element. There are no STL >> container with preallocated buffer and it seems custom allocator does >> not help to do this with existing containers. >> >> Does any container exist to offer functionality like Boost.Array but >> allowing to store from 0 to N elements? Is there any interest in such >> container? >> >> PS. It's similar to fixed_string but as a generic container. >Please see >http://www.cs.aau.dk/~nesotto/boost/auto_buffer.zip >http://www.cs.aau.dk/~nesotto/boost/trunk/libs/auto_buffer/doc/html/ > I was looking at the documentation and the Serialization and "Differences from std::vector<T>" pages were both empty. It would be nice to indicate there's nothing there yet for those pages. On the Semantics page is says: auto_buffer( const auto_buffer& r ); - *Effect:* Copy constructor. - *Postconditions:* capacity() == max(r.size(),N) && size() == r.size() . - *Throws:* Nothing if size() <= N and the copy constructor of T cannot throw. Otherwise this might throw exceptions from the allocator of from T's copy constructor. I think there's a typo in the last sentence there. -- Brian Wood Ebenezer Enterprises www.webEbenezer.net "Then Samuel took a rock and set it up between Mizpah and Shen. He named it Ebenezer [Rock of Help] and said, 'Until now the LORD has helped us.'"

2 1

[array] assignement operator
by vicente.botet 19 May '09

19 May '09

Boost.Array defines an assignement operator with the following prototype template<typename T, std::size_t N> class array { public: /... template<typename U> array& operator=(const array<U, N>& rhs); // Effects:std::copy(rhs.begin(),rhs.end(), begin()) }; I was wondering if this can be extended to manage with arrays of different sizes, having as effect the copying of the minimum of N and M elements from the source to the target. template<typename T, std::size_t N> class array { public: /... template<typename U, std::size_t M> array& operator=(const array<U, M>& rhs); // Effects:std::copy(rhs.begin(),rhs.begin()+min(N,M), begin()) }; Is there anything wrong with this interface? Best, _____________________ Vicente Juan Botet Escribá

5 11

Boost up for SourceForge Community Choice Award
by David Abrahams 19 May '09

19 May '09

Cast your vote here: http://tinyurl.com/boost-cca09 Cheers, -- Dave Abrahams BoostPro Computing http://www.boostpro.com

2 1

[thread] Exception propagation for thread::join
by Emil Dotchevski 18 May '09

18 May '09

When joining a thread, in case the thread has exited, I find it convenient to have any exception the thread function throws propagated to the caller of join(). Just as an illustration of what I'm talking about, below is my Win32 implementation of a similar interface. An interesting design decision is what to do if a detached thread throws an exception. Note the line marked with (1) -- I've decided to assert in this case (instead of ignoring the exception, which would be the alternative behavior.) Would something similar be a good addition to Boost Thread? struct windows_thread_info { DWORD id; boost::shared_ptr<HANDLE const> h; boost::function<void()> f; mutable boost::exception_ptr e; boost::shared_ptr<windows_thread_info> self; ~windows_thread_info() { assert(!e); } }; namespace { DWORD WINAPI thread_proc_fwd( void * p ) { assert(p!=0); boost::weak_ptr<windows_thread_info> w; boost::function<void()> f; { boost::shared_ptr<windows_thread_info> wti; static_cast<windows_thread_info *>(p)->self.swap(wti); assert(wti); f=wti->f; assert(f); w=wti; } try { f(); } catch( ... ) { boost::shared_ptr<windows_thread_info> wti=w.lock(); assert(wti); //(1) wti->e=boost::current_exception(); } return 0; } } boost::shared_ptr<windows_thread_info const> win_CreateThread( LPSECURITY_ATTRIBUTES lpThreadAttributes, SIZE_T dwStackSize, boost::function<void()> const & f, DWORD dwCreationFlags ) { assert(f); boost::shared_ptr<windows_thread_info> wti(new windows_thread_info); wti->f=f; wti->self=wti; if( HANDLE h=CreateThread(lpThreadAttributes,dwStackSize,thread_proc_fwd,wti.get(),dwCreationFlags,&wti->id) ) { make_handle(h,CloseHandle).swap(wti->h); return wti; } else { wti->self.reset(); BOOST_THROW_EXCEPTION(x_system() << xi_win_last_error(GetLastError()) << xi_function("CreateThread")); } } void join( windows_thread_info const & wti ) { (void) win_WaitForSingleObject(*wti.h,INFINITE); boost::exception_ptr e; { using std::swap; swap(e,wti.e); } if( e ) boost::rethrow_exception(e); } -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

4 3

git clone up
by troy d. straszheim 18 May '09

18 May '09

In case this reaches any other git enthusiasts, I've rigged up a git clone that is automatically tracking boost svn, here: http://sodium.resophonic.com/git/boost/ Click around on it... it's smoking fast, despite the fact that it is running on hardware I found in the trash on the end of a mediocre uplink. There is a little howto here: http://sodium.resophonic.com/git/boost/about/ The repository (minus checkout) is about 150M, it contains branches and tags going all the way back. It will take a while to do the initial clone but fetches after that are very fast. -t

4 8

release notes for 1.39.0?
by Neal Becker 18 May '09

18 May '09

Where can I find some more detailed release notes? I looked here: http://comments.gmane.org/gmane.comp.lib.boost.announce/233

2 1

[serialization] Enum loading may lead to uninitialized value [Ask for change]
by Andrey Upadyshev 18 May '09

18 May '09

Hi! I found that template boost::archive::detail::load_enum_type (boost\archive\detail\iserializer.hpp) may overvrite loading enum's value with uninitialized ones. See comments: template<class Archive, class T> struct load_enum_type { static void invoke(Archive &ar, T &t){ int i; // Initialize 'i' with trash ar >> boost::serialization::make_nvp(NULL, i); // Imagine: some code in archive skips loading t = static_cast<T>(i); // Ooops, get the trash into 't' } }; I think it is more secure to initialize 'i' from 't'. So, if archive's code skips loading, we just get 't' unchanged instead of corrupted. Probably, someone can fix this in svn? Andrey Upadyshev P.S. Sorry for my English.

2 2

[regex] patch for Sun CC
by Steven Watanabe 18 May '09

18 May '09

AMDG To get regex to work with Sun 5.9, I had to add std:: in one place. Most of the tests pass, but a few still fail for mysterious reasons. Okay to commit? In Christ, Steven Watanabe

2 1

[boost1.38][serialization][Patch Request] Request a patch for fixing crashes on SunOS 64bit platform
by Joanne chiang 18 May '09

18 May '09

Hi, Please consider : 1. fixing the regression issues (iostream error/exception, segmentation faults , illegal instruction etc.) happened when running the testsuite bundled with boost.serilation (v1.38, though I believe it applies to other revisions) on SunOS 5.8 sparc v9 (5.9, 5.10 64-bit also get the same crashes). 2. adding SunOS 64bit platform to the boost regression test trunk : http://www.boost.org/development/tests/trunk/developer/serialization.html ,if possible. Thanks very much, Mave

2 4

Re: [boost] [filesystem] copy_file() not atomic proposed fix
by Beman Dawes 17 May '09

17 May '09

On Fri, May 15, 2009 at 5:10 AM, Andre Merzky <andre@...> wrote: > Quoting [Beman Dawes] (May 12 2009): >> >> Ticket #2925 complains that "boost::filesystem cannot atomically copy >> file if target exists" ... >> >> ... >> >> The proposed solution is to add an option to copy_file(): >> >> enum class copy_option { fail_if_exists, overwrite_if_exists }; >> >> void copy_file( const Path & from_path, const Path & to_path, >> copy_option option=copy_option::fail_if_exists ); >> >> The implementation would be atomic on both POSIX and Windows. >> >> Comments? > > Makes sense. OK, fix committed to trunk. It will go in branches/release once sufficient regression tests have cycled. > I would suggest to check the complete lib for similar > problems. I think most operational and convenience > functions are prone to similar problems. Hum... "most" is too strong; many of the operational functions are implemented as a single operating system API call. I really don't want to spend time analyzing and fixing the V2 codebase. Instead, I've added an item to the V3 do-list to do an atomicity review. I'm planning to spend a lot of time on Filesystem.V3 this summer, and release a V3 beta as the code firms up. Thanks, --Beman

1 0

PropertyTree's XML parsers survey
by Sebastian Redl 17 May '09

17 May '09

Hi, PropertyTree currently has 5 (five!) different xml readers using 4 different parsers. I don't want to maintain them all. Looking at the open tickets for PT shows that most bugs occur in the various xml readers, and there's no point in having more than one. I just wonder which one to keep. To those who use PropertyTree's XML format, which parser do you use? Do you have any experience with the pros and cons of the various parsers? All feedback is highly appreciated. Sebastian

3 2

[test] Boost.Test with Sun CC
by Steven Watanabe 17 May '09

17 May '09

AMDG The attached patch allows the library to build with Sun 5.9. In Christ, Steven Watanabe

2 2

aligned storage problems with borland
by Robert Ramey 17 May '09

17 May '09

Serialization tests indicated that a recent change to aligned storage has broken serialization tests for borland. Could someone please look into this? Error E2031 ..\boost/aligned_storage.hpp 126: Cannot cast from 'aligned_storage<4,8> * const' to 'detail::aligned_storage::aligned_storage_imp<4,8> *' in function aligned_storage<4,8>::address() *** 1 errors in Compile *** Robert Ramey

2 1

[test] Using the Boost Unit Test Framework with shared libs
by Peter 17 May '09

17 May '09

Hi I am using Boost.Test from the current boost 1.38 , on cygwin ( gcc ) and I want to use it with multiple test files and with shared libs ( in order to speed up the compilation time which is too long for me when using the header include variant ). What is the recommended way ? ( I read the doc, several times and I read the _long_ threads on the mailing list concerning the static/shared library issue, but I am not sure that I understood all the details). I did the following: *in mainTest.cpp:* #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MAIN #include "../inc/globalFixture.hpp" #include "../inc/testfile1.hpp" #include "../inc/testfile2.hpp" *testfile1.hpp:* #include "globalFixture.hpp" BOOST_FIXTURE_TEST_SUITE(ATlib1, Fixture) BOOST_AUTO_TEST_CASE(Resource_Manager) { ... ....BOOST_CHECK .... } BOOST_AUTO_TEST_SUITE_END() *testfile2.hpp:* #include "globalFixture.hpp" BOOST_FIXTURE_TEST_SUITE(ATlib2, Fixture) BOOST_AUTO_TEST_CASE(FileManager { ... BOOST_CHECK .... } BOOST_AUTO_TEST_SUITE_END() *globalfixture.hpp: *#ifndef _GLOBALFIXTURE_HPP #define _GLOBALFIXTURE_HPP #define BOOST_TEST_MODULE ATlib #include <iostream> #include <boost/test/unit_test.hpp> #include <boost/test/detail/unit_test_parameters.hpp> #include <boost/bind.hpp> #include <boost/test/output_test_stream.hpp> using namespace boost::unit_test; struct GlobalConfig { GlobalConfig() { std::cout << "GlobalConfig setup\n"; using namespace boost::unit_test; if (runtime_config::log_level() < log_warnings) unit_test_log.set_threshold_level(log_successful_tests); }; ~GlobalConfig() { std::cout << "GlobalConfig teardown\n"; } }; BOOST_GLOBAL_FIXTURE(GlobalConfig); struct Fixture { Fixture() { BOOST_TEST_MESSAGE("setup Fixture"); using namespace boost::unit_test; unit_test_log.set_threshold_level(log_successful_tests); } ~Fixture() { BOOST_TEST_MESSAGE("teardown Fixture"); } }; #endif /* _GLOBALFIXTURE_HPP */* *I then link to boost_unit_test_framework-gcc34-mt-1_38.so The link passes , but I get a warning from gcc++ 3.4.4 that auto-linking has been enabled ( I will provide the exact details if useful ). I can execute the resulting mainTest.exe without problems, but the compiler warnings tells that something is not quite right. Is the above example the right way to use multiple test files ? Are the flags for shared libs correctly set ? Thanks for your help. PS: I think that Boost.Test is not easy to grasp ( at least for me ). I think this is partially due to a lack of complete examples ( involving for examples a test suite with more than one test file ). Also the static/shared library topic and the related macros ( BOOST_TEST_DYN_LINK etc ) could do with a concrete example. Maybe the mentioned case above could serve as an example after clarification. Peter

3 3

[New Feature Suggestion] Dynamic exception handlers registration
by Alex Tkachenko 17 May '09

17 May '09

Hello there. A while back I wrote usefull tool for organizing exception handling. The general idea is borrowed from boost::execution_monitor (http://www.boost.org/doc/libs/1_38_0/libs/test/doc/html/execution-monitor.h…) . Similarly, I call this unit "Exception Monitor". It allows to dynamically register exception converters and convert exception objects from any source types to arbitrary target type. For instance, if you write some integration code which uses several external modules, and each of these modules could generate their own tree of exceptions, you would face serious issue trying to implement error diagnostic. One approach is to handle only base exception for each module and to catch them in function main(). Let's assume that all exceptions are inherited from std::exception, so we need to catch single base (std::exception). This approach is convenient but not precise. Even if we want just to output error message using std::exception::what() we have only some general low level error description, moreover this description could be completely wrong. It doesn't reflect actual cause of the error because at the place where the exception is originally generated it couldn't know about context of execution. On the contrary, we can catch low-level exceptions in the place where execution context is more obvious and convert it to some "application" exception which contains more information about current situation. This is the solution for detailed error diagnostic, but it is too tedious. Also such code is unscalable, error prone and hard to support. Look at the following example: /////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////// class app_error: public virtual std::exception { ... }; void foo() { try { ...local state... unit1::foo(...); unit2::foo(...); } catch(const unit1::exception1& ex) { //...convert caught exception to app_error using local state throw app_error(...); } catch(const unit1::exception2& ex) { //...convert caught exception to app_error using local state throw app_error(...); } catch(const unit2::exception& ex) { //...convert caught exception to app_error using local state throw app_error(...); } } int main() { try { foo(); } catch(const app_error& ex) { cout << "Error: " << ex.what() << endl; } catch(const std::exception& ex) { cout << "Unknown error: " << ex.what() << endl; } catch(...) { cout << "Unknown error" << endl; } } The main drawback of this source code is that exception handling is mixed with 'main' code. It would be better if we could write something like this: /////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////// class app_error: public virtual std::exception { ... }; typedef exc::catcher<app_error> app_catcher; //...exception catcher type typedef std::list<app_catcher> app_catchers; //...container for catchers struct convert_unit1_ex1 { const app_error operator()(const unit1::exception1&); }; struct convert_unit1_ex2 { const app_error operator()(const unit1::exception2&); }; struct convert_unit2_ex { const app_error operator()(const unit2::exception&); }; app_catchers excon; void foo() { ...local state... //...register catchers for possible exceptions excon.push_front( app_catcher::create<unit1::exception1>( convert_unit1_ex1(...local state...))); excon.push_front( app_catcher::create<unit1::exception2>( convert_unit1_ex2(...local state...))); excon.push_front( app_catcher::create<unit2::exception>( convert_unit2_ex(...local state...))); //... unit1::foo(); unit2::foo(); //...good idea is to use RAII to register catchers to avoid this //...manual deregistration: excon.pop_front(); excon.pop_front(); excon.pop_front(); } int main() { try { guard(excon, foo()); } catch(const app_error& ex) { cout << "Error: " << ex.what() << endl; } catch(const std::exception& ex) { cout << "Unknown error: " << ex.what() << endl; } catch(...) { cout << "Unknown error" << endl; } } Pluses of this technique: 1) it encourages developer to implement exception handlers code separatly from 'main' code; 2) it provides framework for detailed exception handling; 3) it offers flexible means for structural arrangement of exception handlers' source code. Very interesting feature of Exception Monitor is ability to sort catchers in "proper" order regarding their inheritance. So catcher for std::runtime_error should be earlier then std::exception. This is what functions exc::insert and exc::replace do. Library source code (it's tested it on gcc 4.3.1): #ifndef EXCEPTION_MONITOR_HEADER_GUARD #define EXCEPTION_MONITOR_HEADER_GUARD /* * Exception Monitor: * allowes dynamic exception handlers registration * Author: Alex Tkachenko * 2009.02.10 */ #include <cassert> #include <boost/function.hpp> #include <boost/static_assert.hpp> #include <boost/type_traits/is_base_of.hpp> #include <boost/shared_ptr.hpp> #include <typeinfo> namespace exc { namespace details { class failed_to_catch_exception {}; //... class try_catcher_base { public: virtual ~try_catcher_base() {} virtual void convert() const = 0; virtual void try_throw_self_exception() const = 0; virtual bool try_catch_self_exception( const try_catcher_base& other) const = 0; virtual const std::type_info& type() const = 0; }; template<typename Texception_to, typename Texception_from> class try_catcher: public try_catcher_base { typedef boost::function<const Texception_to (const Texception_from&)> converter_f; public: try_catcher(const converter_f& iconverter): converter(iconverter) { assert(!converter.empty() && "Null converter"); } private: void convert() const { try { throw; } catch(const Texception_from& ex) { throw converter(ex); } catch(...) { throw failed_to_catch_exception(); } } void try_throw_self_exception() const { throw (Texception_from*)0; } bool try_catch_self_exception(const try_catcher_base& other) const { try { other.try_throw_self_exception(); } catch(Texception_from*) { return true; } catch(...) { return false; } } const std::type_info& type() const { return typeid(Texception_from); } //... converter_f converter; }; }//...namespace details template<typename Texception_to> class catcher { typedef boost::shared_ptr<details::try_catcher_base> impl_t; catcher(const impl_t& iimpl): impl(iimpl) { assert(impl && "NULL catcher implementation"); } void convert() const { impl->convert(); } void try_throw_self_exception() const { impl->try_throw_self_exception(); } bool try_catch_self_exception(const catcher& other) const { return impl->try_catch_self_exception(*other.impl); } public: typedef Texception_to Texception_to_type; template<typename Texception_from> static const catcher create( const boost::function<const Texception_to (const Texception_from&)> converter) { //...it's senseless to convert from derived to base exception, //...or convert exception to its own type BOOST_STATIC_ASSERT( (!boost::is_base_of<Texception_to, Texception_from>::value)); return catcher( impl_t( new details::try_catcher<Texception_to, Texception_from>( converter))); } //... const std::type_info& type() const { return impl->type(); } void swap(catcher& rhs) { impl.swap(rhs.impl); } private: template<typename Treturn, typename Tcatchers> friend Treturn guard( const Tcatchers& catchers, const boost::function<Treturn ()>& func); template<typename TcatchersIterator> friend TcatchersIterator find( TcatchersIterator begin, TcatchersIterator end, const typename std::iterator_traits<TcatchersIterator>::value_type& catcher); //... impl_t impl; }; template<typename Treturn, typename Tcatchers> Treturn guard( const Tcatchers& catchers, const boost::function<Treturn ()>& func) { assert(!func.empty() && "Empty function"); typedef typename Tcatchers::value_type::Texception_to_type Texception_to_type; try { return func(); } catch(...) { const typename Tcatchers::const_iterator end(catchers.end()); for(typename Tcatchers::const_iterator iter(catchers.begin()); end != iter; ++iter) { try { iter->convert(); } catch(const Texception_to_type&) { throw; } catch(details::failed_to_catch_exception) { //...try next handler } } throw; } } template<typename Tcatchers> inline void guard( const Tcatchers& catchers, const boost::function<void ()>& func) { guard<void, Tcatchers>(catchers, func); } template<typename Texception_to> inline bool operator==( const catcher<Texception_to>& lhs, const catcher<Texception_to>& rhs) { return lhs.type() == rhs.type(); } template<typename Texception_to> inline bool operator!=( const catcher<Texception_to>& lhs, const catcher<Texception_to>& rhs) { return !(lhs == rhs); } template<typename Texception_to> inline void swap(catcher<Texception_to>& lhs, catcher<Texception_to>& rhs) { lhs.swap(rhs); } template<typename TcatchersIterator> TcatchersIterator find( TcatchersIterator begin, TcatchersIterator end, const typename std::iterator_traits<TcatchersIterator>::value_type& catcher) { for(;end != begin; ++begin) if(begin->try_catch_self_exception(catcher)) return begin; return end; } template<typename Tcatchers> void insert(Tcatchers& catchers, const typename Tcatchers::value_type& catcher) { typename Tcatchers::iterator iter( exc::find(catchers.begin(), catchers.end(), catcher)); catchers.insert(iter, catcher); } template<typename Tcatchers> void replace(Tcatchers& catchers, const typename Tcatchers::value_type& catcher) { typename Tcatchers::iterator iter( exc::find(catchers.begin(), catchers.end(), catcher)); if(catchers.end() == iter) catchers.push_back(catcher); else if(catcher == *iter) *iter = catcher; else catchers.insert(iter, catcher); } } //...namespace exc #endif /*EXCEPTION_MONITOR_HEADER_GUARD*/

2 1

[test]
by Jochen Heckl 17 May '09

17 May '09

Hi, I think I stumbled over a problem in the boost unit test library. I'm running MSVC 2008 SP1. Maybe also worth mentioning is, that I use _HAS_TR1=0 with any msvc build. Also I compile boost using bjam define=_HAS_TR1=0 ... Well straight to the problem: this code (boost\test\utils\basic_cstring\basic_cstring.hpp, around line 170) template<typename CharT> inline basic_cstring<CharT>::basic_cstring( std_string const& s ) : m_begin( s.c_str() ) , m_end( m_begin + s.size() ) { } will result in a corrupted basic_cstring, if the source string s goes out of scope, which is the case here ( \boost\test\impl\unit_test_main.ipp, around line 179 ) ... int BOOST_TEST_DECL unit_test_main( init_unit_test_func init_func, int argc, char* argv[] ) { try { framework::init( init_func, argc, argv ); if( !runtime_config::test_to_run().is_empty() ) { test_case_filter filter( runtime_config::test_to_run() ); // <--- parameter will become corrupted traverse_test_tree( framework::master_test_suite().p_id, filter ); } ... because of the temporal std::string return from retrieve_parameter (boost\test\impl\unit_test_parameters.ipp, around line 353 ) const_string test_to_run() { return retrieve_parameter( TESTS_TO_RUN, s_cla_parser, s_empty ); } as quick and very very dirty fix I currently use: test_to_run() { static std::string TTR = retrieve_parameter( TESTS_TO_RUN, s_cla_parser, s_empty ); return TTR; } However, I would welcome, if somebody could supply a more suitable solutions. Best Jochen

2 1

Re: [boost] [test] Automatic registration of tests created with BOOST_PARAM_TEST_CASE
by Jan Stolarek 17 May '09

17 May '09

> Here an example that works fine: Awsome, thanks. By the way, I just run into another serious problem, his time with BOOST_CHECK_EQUAL_COLLECTIONS macro that compares values in two collections. When using STL it is very common that elements in the collection are not objects, but pointers to objects. This leads to a serious problem, since people would rather want to compare values of objects that are pointed to, rather than pointer values (i.e. memory adresses). These will practically always be different, except the situation when two collections actually point to same addresses in memory. Now I'm trying to solve this problem. In test_tools.cpp I found : for( ; left_begin != left_end && right_begin != right_end; ++left_begin, ++right_begin, ++pos ) { if( *left_begin != *right_begin ) { res = false; res.message() << "\nMismatch in a position " << pos << ": " << *left_begin << " != " << *right_begin; } } I don't have the time at the moment, but I assume that replacing ( *left_begin != *right_begin ) with (**left_begin != **right_begin) would solve the problem? Jan

2 1

[tuple] swap (also includes question about [sorting])
by Jeremiah Willcock 17 May '09

17 May '09

Thanks to Marcin Zalewski, the problem in my last email has been tracked down to the inability to swap boost::tuples that contain references. There have been a couple of proposals to add that: http://lists.boost.org/Archives/boost/2006/03/102603.php http://lists.boost.org/Archives/boost/2003/05/48488.php but it appears that none of them has made it into Boost. This feature is important because of sorting data structures using zip_iterators as in my previous message: http://www.nabble.com/-iterator--std::sort-on-zip_iterator-td23348384.html and the older posts: http://lists.boost.org/Archives/boost/2004/07/68758.php http://lists.boost.org/boost-users/2009/03/46623.php In particular, std::swap (from GCC 4.0.1) does not work correctly on the result of dereferencing a zip_iterator, which is a Boost tuple of references. The std::swap function does not work at all (fails at compile time) because the result of operator* is not a non-const reference, and std::iter_swap tries to use assignment between the tuples, producing incorrect answers at run time. Is it true that there is no standards-compliant way to solve this problem? If so, would that be a good justification for Boost.Sorting to include an algorithm similar to std::sort but that handles more generalized swappable types? -- Jeremiah Willcock

2 1

[Boost.datetime] Serialization
by Sean Farrow 17 May '09

17 May '09

Hi: Would it be possible to add the funtion Given at the url: http://www.boost.org/doc/libs/1_39_0/doc/html/date_time/serialization.ht ml To the boost.datetime or boost.serialization library for 1.40. Cheers Sean. __________ Information from ESET NOD32 Antivirus, version of virus signature database 4080 (20090515) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

2 1