October 2005 - Boost - lists.boost.org

multiton discussion
by Jason Hise 07 Oct '05

07 Oct '05

I am trying to decide on the best interface for the multiton to provide. Some background: The singleton interface consists of three smart pointer types: singleton_ptr, const_singleton_ptr, and singleton_ref. Instances of these always automagically refer to the singleton instance. With regard to multi threading, when an operation is performed through a singleton_ptr, an exclusive lock is obtained for the duration of the operation. A const_singleton_ptr behaves similarly, but it acquired a shared lock instead, and only const members of the singleton instance can be accessed. A singleton_ref is considered to be a dereferenced singleton_ptr, so it owns an exclusive lock on the instance for its entire lifetime. It is implicitly convertible to a raw reference to Type, and as such is ideal to use as a proxy to the instance which locks it for the duration of a function call. Ex: void foo ( Type & ); void bar ( ) { // pass the singleton to foo and simultaneously lock the operation foo ( singleton_ref < Type > ( ) ); } Ideally, I would like the multiton to provide a similar interface. I would picture doing this by providing a multiton_ptr, const_multiton_ptr, and multiton_ref, which all take a key to the instance as a constructor param. Question 1) Should multiton_ptrs be copy constructible or assignable? What about multiton_refs? Keep in mind that a multiton_ref owns a lock directly, and thus would need to switch locks if redirected to a different instance. Question 2) Should the multiton_ptr and const_multiton_ptr also function as iterators? If so, should dereferencing them result in a pointer to a pair < const Key &, Type & >, or just a regular pointer to Type? Also, since the container itself is not exposed, how should I provide access to 'begin' and 'end'? Is it sufficient to provide a multiton_ptr constructor which takes an enum, and have that enum define the values begin and end? Question 3) Although each singleton instance in a multiton has its own mutex (assuming a multi threaded policy), operations which can change the state of the multiton container itself also need to be locked with a separate mutex. Thus far, the only operation of this nature that I can see is when a pointer to an instance with a previously unused key is created. However, if client code is using a multiton_ptr as an iterator in a loop, that whole loop needs to be locked with the same mutex as well, lest another thread incidentally create a new instance while the loop is in progress. Should multiton_ptr provide public nested read and write lock types to give client code this access, or should it provide some sort of for_each algorithm instead, which does the locking automatically? Question 4) Should the container used by the multiton become an additional optional policy? A regular map just won't cut it if the multiton needs its instances to exist in shared memory. A few more notes: * The singleton and multiton no longer have any inheritance requirements. Hence, even singleton_ptr < int > is valid, along with any other type one can think of. * An uncreatable base is provided which does use CRTP. If used, uncreatable must also be provided with the factory to use internally. Use of this is completely optional, and makes it completely and absolutely impossible for client code to create singleton instances, no matter how hard it tries to hack around it. (If there is interest in the semantics of this, I will post a more complete description). If anyone feels my design is partially or completely off and has better ideas please let me know. -Jason

2 1

[ptr_container] Serialization?
by Jared McIntyre 07 Oct '05

07 Oct '05

Is there pre-existing code for using the boost::serialization library with the ptr_containers? Jared McIntyre

3 2

[iostreams][iterator] is_incrementable broken on gcc 4.0.2 (was: Re: gcc 4.0.2)
by Jonathan Turkanis 07 Oct '05

07 Oct '05

[I meant to post this on testing and devel] Martin Wille wrote: > Hi, > > > I've added gcc 4.0.2 to my set of toolsets. > > Unfortunately, there are a lot (25) of additional regressions for > 4.0.2. Mainly affected are: Iostreams, Iterator and Spirit. It looks like is_incrementable may be broken on gcc 4.0.2. See, e.g., http://tinyurl.com/7qlow http://tinyurl.com/9mlsu -- Jonathan Turkanis www.kangaroologic.com

1 0

Boost regression notification (2005-10-07 [RC_1_33_0])
by Douglas Gregor 07 Oct '05

07 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-07T14:49:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 246 failures in 6 libraries: graph (1) iostreams (33) multi_index (1) range (3) serialization (202) wave (6) |graph| graphviz_test: cw-9_4 |iostreams| auto_close_test: borland-5_6_4 code_converter_test: borland-5_6_4 component_access_test: borland-5_6_4 compose_test: borland-5_6_4 copy_test: borland-5_6_4 counter_test: borland-5_6_4 example_test: borland-5_6_4 filtering_stream_test: borland-5_6_4 flush_test: borland-5_6_4 gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 invert_test: borland-5_6_4 line_filter_test: borland-5_6_4 newline_test: borland-5_6_4 pipeline_test: borland-5_6_4 regex_filter_test: borland-5_6_4 restrict_test: borland-5_6_4 seekable_filter_test: borland-5_6_4 stdio_filter_test: borland-5_6_4 symmetric_filter_test: borland-5_6_4 tee_test: borland-5_6_4 wide_stream_test: borland-5_6_4 |multi_index| test_serialization: cw-9_5-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_delete_pointer_binary_archive: cw-9_5-darwin test_delete_pointer_binary_archive_dll: cw-9_5-darwin test_delete_pointer_text_archive: cw-9_5-darwin test_delete_pointer_text_warchive: cw-9_5-darwin test_delete_pointer_xml_archive: cw-9_5-darwin test_delete_pointer_xml_warchive: cw-9_5-darwin test_demo_polymorphic: cw-9_5-darwin test_demo_xml_load: gcc-3_3-darwin gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-4_0-darwin test_deque_binary_archive: cw-9_5-darwin test_deque_binary_archive_dll: cw-9_5-darwin test_deque_text_archive: cw-9_5-darwin test_deque_text_warchive: cw-9_5-darwin test_deque_xml_archive: cw-9_5-darwin test_deque_xml_warchive: cw-9_5-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_list_binary_archive: cw-9_5-darwin test_list_binary_archive_dll: cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_5-darwin test_list_ptrs_text_archive: cw-9_5-darwin test_list_ptrs_text_warchive: cw-9_5-darwin test_list_ptrs_xml_archive: cw-9_5-darwin test_list_ptrs_xml_warchive: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: gcc-3_4_3-sunos test_list_text_archive: cw-9_5-darwin test_list_text_warchive: cw-9_5-darwin test_list_xml_archive: cw-9_5-darwin test_list_xml_warchive: cw-9_5-darwin test_map_binary_archive: cw-9_5-darwin test_map_binary_archive_dll: cw-9_5-darwin test_map_text_archive: cw-9_5-darwin gcc-3_4_3-sunos test_map_text_warchive: cw-9_5-darwin test_map_xml_archive: cw-9_5-darwin test_map_xml_warchive: cw-9_5-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: cw-9_5-darwin test_polymorphic_binary_archive_dll: cw-9_5-darwin test_polymorphic_text_archive: cw-9_5-darwin test_polymorphic_text_warchive: cw-9_5-darwin test_polymorphic_xml_archive: cw-9_5-darwin test_polymorphic_xml_warchive: cw-9_5-darwin test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_private_ctor: cw-9_5-darwin test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_reset_object_address: cw-9_5-darwin test_set_binary_archive: cw-9_5-darwin test_set_binary_archive_dll: cw-9_5-darwin test_set_text_archive: cw-9_5-darwin test_set_text_warchive: cw-9_5-darwin test_set_xml_archive: cw-9_5-darwin test_set_xml_warchive: cw-9_5-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_split_text_warchive: gcc-3_4_3-sunos test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux test_variant_binary_archive: cw-9_5-darwin test_variant_binary_archive_dll: cw-9_5-darwin test_variant_text_archive: cw-9_5-darwin test_variant_text_warchive: cw-9_5-darwin test_variant_xml_archive: cw-9_5-darwin test_variant_xml_warchive: cw-9_5-darwin test_vector_binary_archive: cw-9_5-darwin test_vector_binary_archive_dll: cw-9_5-darwin test_vector_text_archive: cw-9_5-darwin test_vector_text_warchive: cw-9_5-darwin test_vector_xml_archive: cw-9_5-darwin test_vector_xml_warchive: cw-9_5-darwin test_void_cast: gcc-3_4_3-sunos test_void_cast_dll: gcc-3_4_3-sunos |wave| test_re2c_lexer: cw-9_4 test_slex_lexer: cw-9_4 testwave: cw-9_4 gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux

1 0

Boost regression notification (2005-10-07 [HEAD])
by Douglas Gregor 07 Oct '05

07 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-07T05:00:16Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 105 failures in 11 libraries: concept_check (13) foreach (1) functional/hash (1) graph (2) mpl (1) parameter (13) serialization (40) spirit (8) thread (4) tuple (1) typeof (21) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |foreach| user_defined: msvc |functional/hash| container_fwd_test: msvc |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_demo_auto_ptr: vc-7_1 test_demo_exception: vc-7_1 test_demo_fast_archive: vc-7_1 test_demo_fast_archive_dll: vc-7_1 test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4

1 0

Who's Using Boost?
by Andreas Pokorny 07 Oct '05

07 Oct '05

Hi, Just found another boost open source user, I could not yet find any statement about which libraries they use. The berlios svn-view service seems to be out of order Yake - http://www.yake.org/ The Yake Engine is a component-based, object-oriented engine written in C++ and primarily designed for VR applications and games. It abstracts typical low-level and middleware APIs and provides various low, mid and application level functionality as well as tools to create and import content. Who is updateing the "Who's Using Boost" page? "Last revised: August 05, 2005 at 12:40:04 GMT" I think it deserves a update. Regards Andreas Pokorny

3 4

About timedlock....
by Boost 07 Oct '05

07 Oct '05

Hi, I want to port program from vc.net to evc4, but the method timedlock has some problem on evc4.....error message as below: boost/thread/detail/lock.hpp(44) : error C2143: syntax error : missing ',' before '&' it seems that wince doesn't support the method timedlock.. I have no idea how to deal with it? Any suggestion? Best Regards.

4 3

About timedlock....
by Tony 07 Oct '05

07 Oct '05

Hi, I want to port program from vc.net to evc4, but the method timedlock has some problem on evc4.....error message as below: boost/thread/detail/lock.hpp(44) : error C2143: syntax error : missing ',' before '&' it seems that wince doesn't support the method timedlock.. I have no idea how to deal with it? Any suggestion? Best Regards.

1 0

Feature request: exception filter for Boost.Bind
by Alex Besogonov 07 Oct '05

07 Oct '05

Hello, world! Today I was browsing RSDN (Russian Software Developer Network) forums and found a great trick for exception handling (http://rsdn.ru/Forum/Message.aspx?mid=1420259&only=1) ============== void TheFunction() { try { ... } catch(...) { ExceptionFilter(); } } void ExceptionFilter() { try { throw; } catch(Exception1 const& e) { //Blah-blah 1 } catch(Exception2 const& e) { //Blah-blah 2 } catch(Exception3 const& e) { //Blah-blah 3 } catch(Exception4 const& e) { //Blah-blah 4 } catch(Exception5 const& e) { throw; //Just rethrow } catch(...) { //Something other } } ============== It turns out that this trick is explicitly permitted by the Standard (as it was pointed in this post: http://rsdn.ru/Forum/Message.aspx?mid=1420469&only=1) I think this trick can be really helpful in conjunction with Boost.Bind. It would be great to write something like this: ==================== boost::function<void()> func= boost::bind_with_filter(&SomeObj::func1,obj,logging_filter()); ==================== If SomeObj::func1 throws an exception then logging_filter will write it into the application's log and suppress its further propagation. Or another use-case: ==================== boost::function<void()> func=boost::bind_with_filter(&ComObject1::func,obj,com_error_translator()); ==================== com_error_translator will translate exceptions from Microsoft's _com_error to something like std::runtime_error. -- With respect, Alex Besogonov(cyberax(a)elewise.com)

2 1

About timedlock....
by Boost 07 Oct '05

07 Oct '05

Hi, I want to port program from vc.net to evc4, but the method timedlock has some problem on evc4..... error message as below: boost/thread/detail/lock.hpp(44) : error C2143: syntax error : missing ',' before '&' it seems that wince doesn't support the method timedlock.. I have no idea how to deal with it? Any suggestion? Best Regards.

1 0