- Boost - lists.boost.org

[concept check] Working on vc7.1?
by David Abrahams 18 Feb '06

18 Feb '06

Both concept_check_fail_expected and concept_check_class_fail_expected are compiling without errors for me. That makes me concerned that the library doesn't work at all on vc7.1. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Boost regression notification (2006-02-18 [HEAD])
by Douglas Gregor 18 Feb '06

18 Feb '06

Boost Regression test failures Report time: 2006-02-18T13:44:58Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 702 failures in 26 libraries random (1) concept_check (23) functional/hash (3) iostreams (2) graph (4) signals (32) program_options (7) rational (3) test (4) parameter (31) math (3) python (2) wave (3) integer (1) serialization (400) optional (10) spirit (36) pool (1) date_time (5) thread (1) config (1) multi_index (24) ptr_container (43) typeof (21) filesystem (34) assign (7) |random| random_test: intel-9.0-linux |concept_check| stl_concept_covering: borland-5_6_4 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.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 qcc-3.3.5-cpp qcc-3.3.5-gpp tru64cxx71-006 vc-7_1 vc-7_1 |functional/hash| hash_friend_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux hash_global_namespace_test: borland-5_6_4 |iostreams| mapped_file_test: qcc-3.3.5-cpp qcc-3.3.5-gpp |graph| bundled_properties: qcc-3.3.5-cpp qcc-3.3.5-gpp graphviz_test: vc-7_1 vc-7_1 |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.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 qcc-3.3.5-cpp qcc-3.3.5-gpp 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.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 qcc-3.3.5-cpp qcc-3.3.5-gpp vc-7_1 vc-7_1 |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 |rational| rational_test: borland-5_6_4 gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |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 |parameter| basics: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux duplicates: borland-5_6_4 earwicker: borland-5_6_4 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: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mpl: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux ntp: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux preprocessor: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux singular: borland-5_6_4 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: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |math| complex_test: borland-5_6_4 hypot_test: borland-5_6_4 log1p_expm1_test: borland-5_6_4 |python| numpy: gcc-4_0-darwin slice: gcc-4_0-darwin |wave| testwave: cw-9_5-darwin testwave_dll: cw-9_4 cw-9_5-darwin |integer| integer_traits_test: qcc-3.3.5-gpp |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_codecvt_null: qcc-3.3.5-gpp 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 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 test_demo_pimpl_dll: cw-9_4 test_demo_polymorphic_dll: cw-9_4 test_demo_portable_archive_dll: cw-9_4 test_demo_xml: intel-win32-8_1 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 intel-win32-8_1 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: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_map_binary_archive_dll: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_map_text_archive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_map_text_archive_dll: borland-5_6_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_map_text_warchive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux test_map_text_warchive_dll: borland-5_6_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux test_map_xml_archive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_map_xml_archive_dll: borland-5_6_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_map_xml_warchive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux test_map_xml_warchive_dll: borland-5_6_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux 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_dll: cw-9_4 test_null_ptr_text_archive_dll: cw-9_4 test_null_ptr_text_warchive_dll: cw-9_4 test_null_ptr_xml_archive_dll: cw-9_4 test_null_ptr_xml_warchive_dll: cw-9_4 test_nvp_binary_archive_dll: cw-9_4 test_nvp_text_archive_dll: cw-9_4 test_nvp_text_warchive_dll: cw-9_4 test_nvp_xml_archive_dll: cw-9_4 test_nvp_xml_warchive_dll: cw-9_4 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_dll: cw-9_4 test_reset_object_address_dll: cw-9_4 test_set_binary_archive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_set_binary_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_set_text_archive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_set_text_archive_dll: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_set_text_warchive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux test_set_text_warchive_dll: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux test_set_xml_archive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_set_xml_archive_dll: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-gpp test_set_xml_warchive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux test_set_xml_warchive_dll: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux 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_utf8_codecvt: qcc-3.3.5-gpp 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 |optional| optional_test_io: cw-9_4 gcc-2.95.3-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.5-linux gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux intel-win32-8_1 tru64cxx71-006 |spirit| scanner_value_type_tests: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 qcc-3.3.5-cpp tru64cxx71-006 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.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 qcc-3.3.5-cpp tru64cxx71-006 vc-7_1 vc-7_1 |pool| test_pool_alloc: qcc-3.3.5-cpp |date_time| testgreg_serialize_dll: cw-9_4 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 |thread| test_mutex_lib: tru64cxx71-006 |config| math_info: borland-5_6_4 |multi_index| test_basic: tru64cxx71-006 test_capacity: tru64cxx71-006 test_comparison: tru64cxx71-006 test_composite_key: tru64cxx71-006 test_conv_iterators: tru64cxx71-006 test_copy_assignment: tru64cxx71-006 test_hash_ops: tru64cxx71-006 test_iterators: tru64cxx71-006 test_list_ops: tru64cxx71-006 test_modifiers: tru64cxx71-006 test_mpl_ops: tru64cxx71-006 test_observers: tru64cxx71-006 test_projection: tru64cxx71-006 test_range: tru64cxx71-006 test_rearrange: tru64cxx71-006 test_safe_mode: cw-9_4 cw-9_5-darwin tru64cxx71-006 test_set_ops: tru64cxx71-006 test_special_list_ops: vc-7_1 test_special_set_ops: tru64cxx71-006 test_update: cw-9_4 cw-9_5-darwin tru64cxx71-006 |ptr_container| incomplete_type_test: cw-9_4 cw-9_5-darwin indirect_fun: cw-9_4 cw-9_5-darwin iterator_test: cw-9_4 cw-9_5-darwin no_exceptions: cw-9_4 cw-9_5-darwin ptr_array: cw-9_4 cw-9_5-darwin ptr_deque: cw-9_4 cw-9_5-darwin ptr_list: cw-9_4 cw-9_5-darwin ptr_map: cw-9_4 cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin qcc-3.3.5-cpp qcc-3.3.5-gpp vc-7_1 vc-7_1 ptr_set: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.5-linux gcc-4.0.2-linux intel-win32-8_1 tru64cxx71-006 ptr_vector: cw-9_4 cw-9_5-darwin serialization: cw-9_4 cw-9_5-darwin gcc-4.0.2-linux tru64cxx71-006 tree_test: cw-9_4 cw-9_5-darwin tut1: cw-9_4 cw-9_5-darwin view_example: cw-9_4 cw-9_5-darwin |typeof| function_ptr_from_tpl_emulation: vc-7_1 vc-7_1 function_ptr_from_tpl_native: vc-7_1 vc-7_1 lvalue_emulation: gcc-4.0.2-linux lvalue_native: gcc-4.0.2-linux type_native: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-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 intel-9.0-linux qcc-3.3.5-cpp qcc-3.3.5-gpp vc-7_1 vc-7_1 |filesystem| convenience_test: borland-5_6_4 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: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux mbpath: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux operations_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux operations_test_dll: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux path_test: borland-5_6_4 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: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux tru64cxx71-006 |assign| multi_index_container: tru64cxx71-006 ptr_list_inserter: cw-9_4 cw-9_5-darwin ptr_list_of: cw-9_4 cw-9_5-darwin ptr_map_inserter: cw-9_4 cw-9_5-darwin

1 0

[graph] test not in Jamfile: bidir_remove_edge.hpp
by David Abrahams 18 Feb '06

18 Feb '06

Is that intentional? -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

LVALUE_TYPEOF to be dropped
by Arkadiy Vertleyb 18 Feb '06

18 Feb '06

Hi. It turned out that we can't provide the portable implementation of LVALUE_TYPEOF that would be both safe and useful. The primary purpose of this feature would be to assist in creation of wrapper functions (possibly through the result_of). The current implementation cannot distinguish between const rvalues and lvalues, and so yields const T& instead of const T (on VC7.1+, for UDT, it's also volatile& instead of volatile, and volatile const& instead of volatile const). If used in a wrapper function, this would lead to a dangling reference. An alternative would be to yield rvalue for anything other than T&, but this would not work with const T& where T is non-copyable (again, on MS for UDT -- also with volatile [const] T&). There are some (non-portable) ways to do better, but those work only for vc and gcc. Returning different results on different compilers would make it useless for generic code which is the primary target of this feature. I am pretty sure nobody depends on LVALUE_TYPEOF in 1.34... So, unless there are some serious objections, we are not including LVALUE_TYPEOF into 1.34. If, at some point in the future, a better way is found to determine lvalueness, this feature can be added again. Regards, Arkadiy

1 1

[statechart] Request for help with Code Warrior failures
by Andreas Huber 18 Feb '06

18 Feb '06

Hi there On both CW versions that statechart is currently tested against, I get some strange failures: 1. Overload resolution behaves unexpectedly: http://tinyurl.com/aonbr 2. In the four tests that build libs or dlls, there seems to be a problem with finding header files: http://tinyurl.com/b6orr Any help in fixing these is highly appreciated. Thanks & Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.

1 0

Preprocessor: Nested loops
by Oliver Kullmann 18 Feb '06

18 Feb '06

Hello, yesterday I spent the day with my first application of the Boost Preprocessor library: Given two sequences A and B (according to the Boost Preprocessor datastructure definition), I want to create a nested switch statement, the outer switch running through the constants in A, the inner loops running through B. Piece of cake: Just apply BOOST_PP_SEQ_FOR_EACH two times. Didn't work, because the preprocessor when evaluating a macro M will suspend the definition of M during the evaluation (thus "no recursion"). Unfortunately, I didn't know this, so I had to find it out the hard way. First of all I think here the documentation of the library doesn't reach its full potential yet: I tried first to read through "Topics", but found all examples contrived and complicated (couldn't find a single plain example), and thus I skipped that and went to Reference, where I found BOOST_PP_SEQ_FOR_EACH, making some still mysterious remarks about "The next available BOOST_PP_FOR repetition." etc. But at various places it somehow says that "reentry problems" whatever this means are solved now. Only when looking it up in the rationale of C99 I found a clear statement about the issue (while the C++ standard somehow supposes you know already the issue). So a clear statement about the limitations of the looping constructions *at each place* would help I would guess quite a few people trying to use this library. (I believe documentation must be written so that it can be entered in many ways, and not assuming you are reading it from the start to the end --- redundancy is needed.) Second of all it seems the current facilities in the library should be enhanced (though I don't understand how FOR and FOR_r is supposed to be used): BOOST_PP_SEQ_FOR_EACH is such a natural and easy thing, the use of it should be promoted, while FOR and its derivates look ugly. But it seems that the library favours FOR, and seems to envisage a main loop using FOR, and only at the second level using FOR_EACH. My solution was to convert the second sequence B into a list, and use BOOST_PP_LIST_FOR_EACH for the inner loop. But it seems to me that this works is pure chance, and with any change in the implementation of BOOST_PP_SEQ_FOR_EACH or BOOST_PP_LIST_FOR_EACH (introducing a common macro) this solution will break. According to what I understand from the documentation, the natural solution, offering for example BOOST_PP_SEQ_FOR_EACH_2, which uses macros guaranteed not to occur in BOOST_PP_SEQ_FOR_EACH, has been deprecated in favour of a more complicated solution. But it seems this more complicated solution works only for one kind of loop, and not for others, and the documentation seems so arcane that I don't have a clue how it could work (the typical phenomenon, that the documentation wants to show off by presenting only complicated examples, which show all sorts of templates, etc., and this without saying what actually should by achieved --- good code solves one problem at a time, and good documentation discusses one problem at a time). So if the library offers a natural way of nesting BOOST_PP_SEQ_FOR_EACH, then documenting this (directly, without solving other problems) would be good, or otherwise adding BOOST_PP_SEQ_FOR_EACH_2 would help some users (actually, just the presence of this second form would announce the underlying problem). Sometimes less general but simpler solutions are preferable over more general but complicated solutions. Oliver P.S. The situation with the preprocessor is complicated by the general silence on this issue in the books. And quite amazing, how the library achieves to squeeze out nearly a general purpose machine (but not with an infinite tape :-)) from the preprocessor machinery, which seems to have been castrated by the designers on purpose.

6 24

Re: [boost] [serialization] exception-safety of container-serialization
by JOAQUIN LOPEZ MU?Z 18 Feb '06

18 Feb '06

----- Mensaje original ----- De: Thorsten Ottosen <tottosen(a)dezide.com> Fecha: Sábado, Febrero 18, 2006 1:17 am Asunto: Re: [boost] [serialization] exception-safety of container-serialization > David Abrahams wrote: > > Joaquín Mª López Muñoz <joaquin(a)tid.es> writes: > > >>2. It might be of interest to keep a partially recovered object. > >>For instance, think of the situation in which a container is being > >>marshalled thru a socket and you lose internet conectivity. > > > > > > That brings up an interesting point: you have to make sure, when > > writing deserialization for a class, that partial deserialization > > won't leave its instances with broken invariants. > > Well, can't we think if deserialization as just another way of > constructing an object? > > So if deserialization fails, it's like when construction fails and > you > might throw or abort. No? > No, IMHO. There's a crucial difference with failed construction: if a ctor fails the object does not even come into existence. When loading fails, the object into which the loading process was performed exists and should at least honor its invariants. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[asio] Review Status?
by Caleb Epstein 18 Feb '06

18 Feb '06

I realize that there was a LOT of material to digest from this review, but now asio appears to have been "lapped" by shmem, which has had been reviewed and has now been accepted into Boost. When can we expect to hear the final disposition of the asio review? -- Caleb Epstein caleb dot epstein at gmail dot com

2 1

[review] Shmem
by Dave Moore 18 Feb '06

18 Feb '06

I recommend that Shmem be accepted into Boost. Most of my comments below have already been raised by other posters, so I'll just mention which I agree with. I would use Shmem today if it were available in its final form in Boost. - What is your evaluation of the design? I was impressed with the breadth and depth of the design. It thoroughly covers this domain. My only suggestion for the design would be to separate the concept of mmapped_file from that of the mapped region. The mmapped_file class should just be concerned with managing the "backing store", whether that is an ordinary file, /dev/zero, or the Windows swap file. The mmapped_region is responsible for mapping a portion (or all) of the mmapped_file into the process's memory space, and you could have multiple mmapped_regions per mmapped_file. The current implementation could be covered with a convenience class/factory that creates a mmapped_region that maps an entire mmapped_file. - What is your evaluation of the implementation? Overall, quite impressed. I am in strong agreement with the "RAII crowd" in that I do not want to see two phase initialization. To summarize which of the sub-arguments I agree with, or find to be important: 1. I would like to see constructors that throw when they cannot construct the object. 2. I see no compelling need for fstream() equivalent "empty" constructors 3. I do agree that "reopen()" is a useful concept, and that it could also throw. 4. For embedded environments that cannot use exceptions, I suggest using boost::config to disable the throwing() behavior, and provide an "isValid/isOpen" accessor function which would allow embedded developers to interrogate the state of the object. When exceptions are turned on, this function would always return true. Re: Boost::Threads and synchronization primitives I agree that Shmem provides (yet another) compelling case for factoring Boost::Threads into synchronization primitives and higher level thread management objects (threads, pools, thread specific storage, etc.). The synchronization primitives are too useful as separate objects. - What is your evaluation of the documentation? I actually thought it was adequate, if a little rough around the edges. I'm familiar with the problem domain, though. - What is your evaluation of the potential usefulness of the library? Having a comprehensive, cross-platform library for shared memory is hugely useful. - Did you try to use the library? With what compiler? Did you have any problems? I evaluated this library using VC 7.1 and VC 8.0 without problems. - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I put a moderate amount of effort into this evaluation. I read the documentation and looked in depth at the file mapping and allocator objects. - Are you knowledgeable about the problem domain? Yes, I've used shared memory objects and synchronization extensively in financial and research application development. Regards, Dave Moore

8 16

[filesystem] Thoughts on wide character paths
by Peter Dimov 18 Feb '06

18 Feb '06

Recently, I needed to fix a program to work properly with paths that cannot be represented by narrow strings under Windows. The problematic filenames came from the user via drag and drop. I tried to go the wstring route, the same approach that the filesystem library takes; but it was harder than I thought. Many parts of the code base assumed narrow paths. At the end I reverted the changes and just encoded the wide path into UTF-8 at the very start, passed the UTF-8 string through the existing code, then decoded the UTF-8 into a wstring at the very end, immediately before calling the Windows API. It worked. What this means in the [filesystem] context? Basically, instead of: template<class String, class Traits> class basic_path; I used something similar to: class path { private: string data_; // UTF-8, exposition only public: path( wstring const & s ); path( string const & s, encoding_type encoding = system_default ); wstring to_wstring() const; string to_string( encoding_type encoding = system_default ) const; }; -- Peter Dimov http://www.pdimov.com

3 3