- Boost - lists.boost.org

Windows event objects still considered harmful?
by Robin Boerdijk 18 Jan '06

18 Jan '06

Hi, I don't agree with the rationale for excluding a Windows event object-like construct from the Boost thread package. The rationale justifies the exclusion based on the "Concurrent Programming Concepts" paper by Per Brich Hansen in which event variables are dismissed as unsafe. The fundamental problem of event variables according to Hansen's paper is that, "if the sender causes [signals] the event before the receiver waits for it, the receiver will remain delayed until the next event is caused [signalled]". However, Windows event objects don't work like this. From the API specification: "When the state of an auto-reset event object is signaled, it remains signaled until a single waiting thread is released; the system then automatically resets the state to nonsignaled. If no threads are waiting, the event object's state remains signaled." In other words, the receiver will _not_ remain delayed if the sender signals the event before the receiver waits for it. Based on this observation, I think the reference to Hansen's paper should be removed from the rationale. It does not apply to Windows event objects and I had to spend $10 to download the paper from the ACM website and find this out. Furthermore, according to the rationale, "Experienced programmers using the Windows platform today report that event variables are a continuing source of errors". Are there any links to documents that describe these problems? Are these problems perhaps related to the PulseEvent() method, which does cause the behaviour Hansen described but has been deprecated (the API documentation states "This function is unreliable and should not be used. It exists mainly for backward compatibility"). In short, are Windows event objects still considered harmful? Thanks, Robin Boerdijk __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 2

Windows event objects still considered harmful?
by Robin Boerdijk 18 Jan '06

18 Jan '06

Hi, I don't agree with the rationale for excluding a Windows event object-like construct from the Boost thread package. The rationale justifies the exclusion based on the "Concurrent Programming Concepts" paper by Per Brich Hansen in which event variables are dismissed as unsafe. The fundamental problem of event variables according to Hansen's paper is that, "if the sender causes [signals] the event before the receiver waits for it, the receiver will remain delayed until the next event is caused [signalled]". However, Windows event objects don't work like this. From the API specification: "When the state of an auto-reset event object is signaled, it remains signaled until a single waiting thread is released; the system then automatically resets the state to nonsignaled. If no threads are waiting, the event object's state remains signaled." In other words, the receiver will _not_ remain delayed if the sender signals the event before the receiver waits for it. Based on this observation, I think the reference to Hansen's paper should be removed from the rationale. It does not apply to Windows event objects and I had to spend $10 to download the paper from the ACM website and find this out. Furthermore, according to the rationale, "Experienced programmers using the Windows platform today report that event variables are a continuing source of errors". Are there any links to documents that describe these problems? Are these problems perhaps related to the PulseEvent() method, which does cause the behaviour Hansen described but has been deprecated (the API documentation states "This function is unreliable and should not be used. It exists mainly for backward compatibility"). In short, are Windows event objects still considered harmful? Thanks, Robin Boerdijk __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 3

[doc,patch] iterator_facade.html
by LI Daobing 18 Jan '06

18 Jan '06

$ diff -u /usr/share/doc/libboost-doc/HTML/libs/iterator/doc/it erator_facade.html iterator_facade.html --- /usr/share/doc/libboost-doc/HTML/libs/iterator/doc/iterator_facade.html 2006-01-12 00:23:36.000000000 +0800 +++ iterator_facade.html 2006-01-18 14:46:22.000000000 +0800 @@ -1110,7 +1110,7 @@ <pre class="literal-block"> class const_node_iterator : public boost::iterator_facade< - node_iterator + const_node_iterator , node_base <strong>const</strong> , boost::forward_traversal_tag > -- LI Daobing

1 0

Pointer variant
by Pierre THIERRY 18 Jan '06

18 Jan '06

In my code, I use variants with only pointers type as bounded types. Mainly a plain pointer to a type and one or more smart pointers to this same type. Would a derived variant that would be dereferencable if all of it's bounded type also are of interest for Boost.Variant library? Would anyone be willing to implement it? (i.e. should I dive in the code and try to do it myself?) Variantly, Nowhere man -- nowhere.man(a)levallois.eu.org OpenPGP 0xD9D50D8A

1 0

Boost regression notification (2006-01-17 [HEAD])
by Douglas Gregor 17 Jan '06

17 Jan '06

Boost Regression test failures Report time: 2006-01-17T14:06:47Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 442 failures in 21 libraries xpressive (24) date_time (6) multi_array (2) python (13) graph (5) random (1) numeric/interval (3) signals (30) tr1 (3) concept_check (21) smart_ptr (2) rational (4) filesystem (31) test (5) program_options (7) serialization (206) wave (3) parameter (12) spirit (34) iostreams (22) typeof (8) |xpressive| c_traits: cw-9_5-darwin misc1: cw-9_5-darwin regress: cw-9_5-darwin test1: cw-9_5-darwin test10: cw-9_5-darwin test10u: cw-9_5-darwin test1u: cw-9_5-darwin test2: cw-9_5-darwin test2u: cw-9_5-darwin test3: cw-9_5-darwin test3u: cw-9_5-darwin test4: cw-9_5-darwin test4u: cw-9_5-darwin test5: cw-9_5-darwin test5u: cw-9_5-darwin test6: cw-9_5-darwin test6u: cw-9_5-darwin test7: cw-9_5-darwin test7u: cw-9_5-darwin test8: cw-9_5-darwin test8u: cw-9_5-darwin test9: cw-9_5-darwin test9u: cw-9_5-darwin test_non_char: cw-9_5-darwin |date_time| testgreg_serialize_dll: cw-9_4 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 vc-7_1 |multi_array| access: gcc-3.3.6-linux gcc-3.4.4-linux |python| defaults: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-4.0.2-linux docstring: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-4.0.2-linux numpy: gcc-4_0-darwin slice: gcc-4_0-darwin |graph| csr_graph_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux graphviz_test: vc-7_1 vc-7_1 vc-7_1 |random| random_test: intel-9.0-linux |numeric/interval| det: tru64cxx71-006 mul: tru64cxx71-006 overflow: tru64cxx71-006 |signals| dead_slot_test: gcc-2.95.3-linux 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.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin mingw-3_4_2 mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 trackable_test: gcc-2.95.3-linux 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.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin mingw-3_4_2 mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 |tr1| test_exception: gcc-2.95.3-stlport-4.6.2-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_stdexcept: gcc-2.95.3-stlport-4.6.2-linux |concept_check| stl_concept_covering: cw-9_4 cw-9_5-darwin gcc-2.95.3-linux 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.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 mingw-3_4_2 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 |smart_ptr| auto_ptr_rv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |rational| rational_test: gcc-2.95.3-stlport-4.6.2-linux vc-7_1 vc-7_1 vc-7_1 |filesystem| convenience_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux fstream_test: gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux large_file_support_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mbcopy: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux mingw-3_4_2 mingw-3_4_2 mbpath: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 mingw-3_4_2 operations_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux operations_test_dll: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux path_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux path_test_dll: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux simple_ls: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux wide_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux mingw-3_4_2 mingw-3_4_2 tru64cxx71-006 |test| test_fp_comparisons: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tools_test: gcc-4_0-darwin mingw-3_4_2 mingw-3_4_2 |program_options| cmdline_test_dll: cw-9_4 options_description_test_dll: cw-9_4 parsers_test_dll: cw-9_4 positional_options_test_dll: cw-9_4 unicode_test_dll: cw-9_4 variable_map_test_dll: cw-9_4 winmain_dll: cw-9_4 |serialization| test_array_binary_archive_dll: cw-9_4 test_array_text_archive_dll: cw-9_4 test_array_text_warchive_dll: cw-9_4 test_array_xml_archive_dll: cw-9_4 test_array_xml_warchive_dll: cw-9_4 test_binary_binary_archive_dll: cw-9_4 test_binary_text_archive_dll: cw-9_4 test_binary_text_warchive_dll: cw-9_4 test_binary_xml_archive_dll: cw-9_4 test_binary_xml_warchive_dll: cw-9_4 test_class_info_load_binary_archive_dll: cw-9_4 test_class_info_load_text_archive_dll: cw-9_4 test_class_info_load_text_warchive_dll: cw-9_4 test_class_info_load_xml_archive_dll: cw-9_4 test_class_info_load_xml_warchive_dll: cw-9_4 test_class_info_save_binary_archive_dll: cw-9_4 test_class_info_save_text_archive_dll: cw-9_4 test_class_info_save_text_warchive_dll: cw-9_4 test_class_info_save_xml_archive_dll: cw-9_4 test_class_info_save_xml_warchive_dll: cw-9_4 test_contained_class_binary_archive_dll: cw-9_4 test_contained_class_text_archive_dll: cw-9_4 test_contained_class_text_warchive_dll: cw-9_4 test_contained_class_xml_archive_dll: cw-9_4 test_contained_class_xml_warchive_dll: cw-9_4 test_cyclic_ptrs_binary_archive_dll: cw-9_4 test_cyclic_ptrs_text_archive_dll: cw-9_4 test_cyclic_ptrs_text_warchive_dll: cw-9_4 test_cyclic_ptrs_xml_archive_dll: cw-9_4 test_cyclic_ptrs_xml_warchive_dll: cw-9_4 test_delete_pointer_binary_archive_dll: cw-9_4 test_delete_pointer_text_archive_dll: cw-9_4 test_delete_pointer_text_warchive_dll: cw-9_4 test_delete_pointer_xml_archive_dll: cw-9_4 test_delete_pointer_xml_warchive_dll: cw-9_4 test_demo_auto_ptr_dll: cw-9_4 test_demo_fast_archive_dll: cw-9_4 test_demo_pimpl_dll: cw-9_4 test_demo_polymorphic_dll: cw-9_4 test_demo_portable_archive_dll: cw-9_4 test_deque_binary_archive_dll: cw-9_4 test_deque_text_archive_dll: cw-9_4 test_deque_text_warchive_dll: cw-9_4 test_deque_xml_archive_dll: cw-9_4 test_deque_xml_warchive_dll: cw-9_4 test_derived_binary_archive_dll: cw-9_4 test_derived_class_binary_archive_dll: cw-9_4 test_derived_class_ptr_binary_archive_dll: cw-9_4 test_derived_class_ptr_text_archive_dll: cw-9_4 test_derived_class_ptr_text_warchive_dll: cw-9_4 test_derived_class_ptr_xml_archive_dll: cw-9_4 test_derived_class_ptr_xml_warchive_dll: cw-9_4 test_derived_class_text_archive_dll: cw-9_4 test_derived_class_text_warchive_dll: cw-9_4 test_derived_class_xml_archive_dll: cw-9_4 test_derived_class_xml_warchive_dll: cw-9_4 test_derived_text_archive_dll: cw-9_4 test_derived_text_warchive_dll: cw-9_4 test_derived_xml_archive_dll: cw-9_4 test_derived_xml_warchive_dll: cw-9_4 test_diamond_binary_archive_dll: cw-9_4 test_diamond_text_archive_dll: cw-9_4 test_diamond_text_warchive_dll: cw-9_4 test_diamond_xml_archive_dll: cw-9_4 test_diamond_xml_warchive_dll: cw-9_4 test_list_binary_archive_dll: cw-9_4 test_list_ptrs_binary_archive_dll: cw-9_4 test_list_ptrs_text_archive_dll: cw-9_4 test_list_ptrs_text_warchive_dll: cw-9_4 test_list_ptrs_xml_archive_dll: cw-9_4 test_list_ptrs_xml_warchive_dll: cw-9_4 test_list_text_archive_dll: cw-9_4 test_list_text_warchive_dll: cw-9_4 test_list_xml_archive_dll: cw-9_4 test_list_xml_warchive_dll: cw-9_4 test_map_binary_archive_dll: cw-9_4 test_map_text_archive_dll: cw-9_4 intel-win32-8_1 test_map_text_warchive: intel-win32-8_1 test_map_text_warchive_dll: cw-9_4 test_map_xml_archive_dll: cw-9_4 test_map_xml_warchive_dll: cw-9_4 test_multiple_ptrs_binary_archive_dll: cw-9_4 test_multiple_ptrs_text_archive_dll: cw-9_4 test_multiple_ptrs_text_warchive_dll: cw-9_4 test_multiple_ptrs_xml_archive_dll: cw-9_4 test_multiple_ptrs_xml_warchive_dll: cw-9_4 test_non_default_ctor_binary_archive_dll: cw-9_4 test_non_default_ctor_text_archive_dll: cw-9_4 test_non_default_ctor_text_warchive_dll: cw-9_4 test_non_default_ctor_xml_archive_dll: cw-9_4 test_non_default_ctor_xml_warchive_dll: cw-9_4 test_non_intrusive_binary_archive_dll: cw-9_4 test_non_intrusive_text_archive_dll: cw-9_4 test_non_intrusive_text_warchive_dll: cw-9_4 test_non_intrusive_xml_archive_dll: cw-9_4 test_non_intrusive_xml_warchive_dll: cw-9_4 test_null_ptr_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_null_ptr_binary_archive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_null_ptr_text_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_null_ptr_text_archive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_null_ptr_text_warchive: gcc-3.3.6-linux gcc-3.4.4-linux test_null_ptr_text_warchive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_null_ptr_xml_archive_dll: cw-9_4 test_null_ptr_xml_warchive_dll: cw-9_4 test_nvp_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_binary_archive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_text_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_text_archive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_text_warchive: gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_text_warchive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_xml_archive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_xml_warchive: gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_xml_warchive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_object_binary_archive_dll: cw-9_4 test_object_text_archive_dll: cw-9_4 test_object_text_warchive_dll: cw-9_4 test_object_xml_archive_dll: cw-9_4 test_object_xml_warchive_dll: cw-9_4 test_optional_binary_archive_dll: cw-9_4 test_optional_text_archive_dll: cw-9_4 test_optional_text_warchive_dll: cw-9_4 test_optional_xml_archive_dll: cw-9_4 test_optional_xml_warchive_dll: cw-9_4 test_polymorphic_binary_archive_dll: cw-9_4 test_polymorphic_text_archive_dll: cw-9_4 test_polymorphic_text_warchive_dll: cw-9_4 test_polymorphic_xml_archive_dll: cw-9_4 test_polymorphic_xml_warchive_dll: cw-9_4 test_primitive_binary_archive_dll: cw-9_4 test_primitive_text_archive_dll: cw-9_4 test_primitive_text_warchive_dll: cw-9_4 test_primitive_xml_archive_dll: cw-9_4 test_primitive_xml_warchive_dll: cw-9_4 test_private_ctor_dll: cw-9_4 test_recursion_binary_archive_dll: cw-9_4 test_recursion_text_archive_dll: cw-9_4 test_recursion_text_warchive_dll: cw-9_4 test_recursion_xml_archive_dll: cw-9_4 test_recursion_xml_warchive: gcc-3.4.4-linux test_recursion_xml_warchive_dll: cw-9_4 gcc-3.3.6-linux test_reset_object_address_dll: cw-9_4 test_set_binary_archive_dll: cw-9_4 test_set_text_archive_dll: cw-9_4 test_set_text_warchive_dll: cw-9_4 test_set_xml_archive_dll: cw-9_4 test_set_xml_warchive_dll: cw-9_4 test_shared_ptr_132_text_archive: intel-win32-8_1 test_shared_ptr_132_text_archive_dll: intel-win32-8_1 test_simple_class_binary_archive_dll: cw-9_4 test_simple_class_ptr_binary_archive_dll: cw-9_4 test_simple_class_ptr_text_archive_dll: cw-9_4 test_simple_class_ptr_text_warchive_dll: cw-9_4 test_simple_class_ptr_xml_archive_dll: cw-9_4 test_simple_class_ptr_xml_warchive_dll: cw-9_4 test_simple_class_text_archive_dll: cw-9_4 test_simple_class_text_warchive_dll: cw-9_4 test_simple_class_xml_archive_dll: cw-9_4 test_simple_class_xml_warchive_dll: cw-9_4 test_split_binary_archive_dll: cw-9_4 test_split_text_archive_dll: cw-9_4 test_split_text_warchive_dll: cw-9_4 test_split_xml_archive_dll: cw-9_4 test_split_xml_warchive_dll: cw-9_4 test_tracking_binary_archive_dll: cw-9_4 test_tracking_text_archive_dll: cw-9_4 test_tracking_text_warchive_dll: cw-9_4 test_tracking_xml_archive_dll: cw-9_4 test_tracking_xml_warchive_dll: cw-9_4 test_variant_binary_archive_dll: cw-9_4 test_variant_text_archive_dll: cw-9_4 test_variant_text_warchive_dll: cw-9_4 test_variant_xml_archive_dll: cw-9_4 test_variant_xml_warchive_dll: cw-9_4 test_vector_binary_archive_dll: cw-9_4 test_vector_text_archive_dll: cw-9_4 test_vector_text_warchive_dll: cw-9_4 test_vector_xml_archive_dll: cw-9_4 test_vector_xml_warchive_dll: cw-9_4 test_void_cast_dll: cw-9_4 |wave| testwave: cw-9_5-darwin testwave_dll: cw-9_4 cw-9_5-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 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 tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |spirit| scanner_value_type_tests: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 scanner_value_type_tests_debug: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 |iostreams| auto_close_test: tru64cxx71-006 code_converter_test: tru64cxx71-006 component_access_test: tru64cxx71-006 compose_test: tru64cxx71-006 copy_test: tru64cxx71-006 counter_test: tru64cxx71-006 example_test: tru64cxx71-006 filtering_stream_test: tru64cxx71-006 finite_state_filter_test: tru64cxx71-006 flush_test: tru64cxx71-006 invert_test: tru64cxx71-006 line_filter_test: tru64cxx71-006 newline_test: tru64cxx71-006 pipeline_test: tru64cxx71-006 regex_filter_test: tru64cxx71-006 restrict_test: tru64cxx71-006 seekable_file_test: tru64cxx71-006 seekable_filter_test: tru64cxx71-006 stdio_filter_test: tru64cxx71-006 symmetric_filter_test: tru64cxx71-006 tee_test: tru64cxx71-006 wide_stream_test: tru64cxx71-006 |typeof| function_ptr_from_tpl_emulation: vc-7_1 vc-7_1 vc-7_1 function_ptr_from_tpl_native: vc-7_1 vc-7_1 vc-7_1 lvalue_emulation: gcc-4.0.2-linux lvalue_native: gcc-4.0.2-linux

1 0

[algorithm] About the documentation of boost::algorithm::string.
by Matthew Henderson 17 Jan '06

17 Jan '06

There are two minor problems with the documentation which I have noticed. 1. Undocumented headers. boost/algorithm/string/config.hpp boost/algorithm/string/iter_find.hpp 2. The statement "Each part is copied and added as a new element to the output container." which appears both in the documentation of boost/algorithm/string /split.hpp and in comments of that header file is not an accurate description of what actually happens. Some testing by myself suggests that, in fact, the contents of the original container are overwritten. Matthew Henderson

2 1

min/max addition functionality.
by Vladislav Lazarenko 17 Jan '06

17 Jan '06

Is there any library to do thing like this more easily? [code] int x = -10; int rating = std::max(std::min(x, 5), 0); [/code] As a result, we will have rating in range 0-5. I looked at the minmax library, but looks like there is not such function :-? Maybe I am looking in a wrong way? Thanks in advance, Vladislav Lazarenko.

3 2

[filesystem] Paths as Ranges.
by Matthew Henderson 17 Jan '06

17 Jan '06

I am involved with the development of a generic C++ library for SAT. As part of this project I have been trying to create some tools for refactoring C++ source code and have been using the boost::filesystem library. It seems to us that boost::filesystem::path should be a model of a standard container and/or of boost forward range. This is a natural requirement, and should be easy to fulfil. As things stand we have to provide the following fix ourselves: namespace boost { template <> struct range_const_iterator<boost::filesystem::path> { typedef boost::filesystem::path::iterator type; }; template <> struct range_const_iterator<boost::filesystem::path> { typedef boost::filesystem::path::iterator type; }; template <> struct range_size<boost::filesystem::path> { typedef boost::filesystem::path::iterator::difference_type type; }; namespace filesystem { inline boost::range_size<boost::filesystem::path>::type boost_range _size(const boost::filesystem::path& p) { return std::distance(p.begin(),p.end()); } } It seems that boost::filesystem::path should offer some complete functionality in order to become a model either of a standard container or of a boost range. Incidentally, are there any tools for refactoring C++ code within the boost library or any plans in the future to include such tools? Matthew Henderson

1 0

[Boost-bugs] [ boost-Support Requests-1407844 ] Don't know how to get multiIndex container index shared ptrs
by SourceForge.net 17 Jan '06

17 Jan '06

Support Requests item #1407844, was opened at 2006-01-16 18:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1407844&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Don't know how to get multiIndex container index shared ptrs Initial Comment: Hello! My email address is sean(a)mssengineering.com. I would like to use const_mem_fun of multiIndex to index sharedPtrs. Maybe there is an easy way to do this, but there doesn't seem to be any way obvious to me that is really easy. It would be nice if this was a feature of the multiindex container. Any suggestions and/or work arounds that would make this possible would be great. Thank you, Sean Zlatnik ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1407844&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Outdated workaround?
by AlisdairM 16 Jan '06

16 Jan '06

The following lines are found at the end of boost/iterator/detail/config_def.h : #if BOOST_WORKAROUND(__GNUC__, == 2 && __GNUC_MINOR__ == 95) \ || BOOST_WORKAROUND(__MWERKS__, <= 0x2407) \ || BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x551)) # define BOOST_ITERATOR_NO_MPL_AUX_HAS_XXX // "MPL's has_xxx facility doesn't work" #endif However, I can't find any code using this define - BOOST_ITERATOR_NO_MPL_AUX_HAS_XXX Would it make sense to remove the workaround? -- AlisdairM

2 1