February 2006 - Boost - lists.preview.boost.org

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

03 Feb '06

Boost Regression test failures Report time: 2006-02-03T13:12:24Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 747 failures in 26 libraries random (1) concept_check (24) serialization (364) config (1) utility (1) graph (7) signals (32) program_options (7) foreach (12) rational (5) tr1 (57) parameter (2) math (3) smart_ptr (4) python (2) wave (3) test (44) functional/hash (1) spirit (41) xpressive (24) date_time (7) multi_array (6) bind (1) algorithm/string (6) typeof (38) filesystem (54) |random| random_test: intel-9.0-linux |concept_check| stl_concept_covering: borland-5_6_4 cw-8_3 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 mingw-3_4_2 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 |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_demo_xml_load: intel-win32-8_1 test_demo_xml_save: 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 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: 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 mingw-3_4_2 test_map_binary_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 mingw-3_4_2 test_map_text_archive: 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 mingw-3_4_2 test_map_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 intel-win32-8_1 mingw-3_4_2 test_map_text_warchive: 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: 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: 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 mingw-3_4_2 test_map_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 mingw-3_4_2 test_map_xml_warchive: 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: 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: 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 mingw-3_4_2 test_set_binary_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 mingw-3_4_2 test_set_text_archive: 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 mingw-3_4_2 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 mingw-3_4_2 test_set_text_warchive: 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: 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 mingw-3_4_2 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 mingw-3_4_2 test_set_xml_warchive: 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_shared_ptr_132_binary_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 |config| math_info: borland-5_6_4 |utility| compressed_pair_test: borland-5_6_4 |graph| csr_graph_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux dominator_tree_test: cw-8_3 graphviz_test: vc-7_1 vc-7_1 vc-7_1 matching_test: cw-8_3 |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 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.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 |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 |foreach| array_byref: borland-5_6_4 array_byval: borland-5_6_4 call_once: borland-5_6_4 cstr_byref: borland-5_6_4 cstr_byval: borland-5_6_4 dependent_type: borland-5_6_4 noncopyable: borland-5_6_4 pair_byref: borland-5_6_4 pair_byval: borland-5_6_4 stl_byref: borland-5_6_4 stl_byval: borland-5_6_4 user_defined: borland-5_6_4 |rational| rational_test: borland-5_6_4 cw-8_3 gcc-2.95.3-stlport-4.6.2-linux vc-7_1 vc-7_1 |tr1| test_ios_std_header: gcc-2.95.3-linux test_istream_std_header: gcc-2.95.3-linux test_limits_std_header: gcc-2.95.3-linux test_locale_std_header: gcc-2.95.3-linux test_ostream_std_header: gcc-2.95.3-linux test_streambuf_std_header: gcc-2.95.3-linux test_tuple_tricky: borland-5_6_4 tr1_add_const_test: borland-5_6_4 tr1_add_cv_test: borland-5_6_4 tr1_add_pointer_test: borland-5_6_4 tr1_add_reference_test: borland-5_6_4 tr1_add_volatile_test: borland-5_6_4 tr1_aligned_storage_test: borland-5_6_4 tr1_alignment_of_test: borland-5_6_4 tr1_has_nothrow_assign_test: borland-5_6_4 tr1_has_nothrow_constr_test: borland-5_6_4 tr1_has_nothrow_copy_test: borland-5_6_4 tr1_has_trivial_assign_test: borland-5_6_4 tr1_has_trivial_constr_test: borland-5_6_4 tr1_has_trivial_copy_test: borland-5_6_4 tr1_has_trivial_destructor_test: borland-5_6_4 tr1_has_virtual_destructor_test: borland-5_6_4 tr1_is_arithmetic_test: borland-5_6_4 tr1_is_array_test: borland-5_6_4 tr1_is_class_test: borland-5_6_4 tr1_is_compound_test: borland-5_6_4 tr1_is_const_test: borland-5_6_4 tr1_is_convertible_test: borland-5_6_4 tr1_is_empty_test: borland-5_6_4 tr1_is_enum_test: borland-5_6_4 tr1_is_floating_point_test: borland-5_6_4 tr1_is_function_test: borland-5_6_4 tr1_is_fundamental_test: borland-5_6_4 tr1_is_integral_test: borland-5_6_4 tr1_is_member_func_test: borland-5_6_4 tr1_is_member_obj_test: borland-5_6_4 tr1_is_member_pointer_test: borland-5_6_4 tr1_is_object_test: borland-5_6_4 tr1_is_pod_test: borland-5_6_4 tr1_is_pointer_test: borland-5_6_4 tr1_is_polymorphic_test: borland-5_6_4 tr1_is_reference_test: borland-5_6_4 tr1_is_same_test: borland-5_6_4 tr1_is_scalar_test: borland-5_6_4 tr1_is_signed_test: borland-5_6_4 tr1_is_union_test: borland-5_6_4 tr1_is_unsigned_test: borland-5_6_4 tr1_is_void_test: borland-5_6_4 tr1_is_volatile_test: borland-5_6_4 tr1_remove_const_test: borland-5_6_4 tr1_remove_cv_test: borland-5_6_4 tr1_remove_pointer_test: borland-5_6_4 tr1_remove_reference_test: borland-5_6_4 tr1_remove_volatile_test: borland-5_6_4 tr1_tricky_abstract_type_test: borland-5_6_4 tr1_tricky_add_pointer_test: borland-5_6_4 tr1_tricky_partial_spec_test: borland-5_6_4 |parameter| duplicates: borland-5_6_4 singular: borland-5_6_4 |math| complex_test: borland-5_6_4 hypot_test: borland-5_6_4 log1p_expm1_test: borland-5_6_4 |smart_ptr| auto_ptr_rv_test: borland-5_6_4 cw-8_3 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |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 |test| errors_handling_test: borland-5_6_4 cw-8_3 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 intel-9.0-linux intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 parameterized_test_test: borland-5_6_4 cw-8_3 test_fp_comparisons: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tools_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 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 |functional/hash| container_fwd_test: borland-5_6_4 |spirit| grammar_def_test: cw-8_3 grammar_def_test_debug: cw-8_3 vc-7_1 scanner_value_type_tests: cw-8_3 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 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 scanner_value_type_tests_debug: cw-8_3 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 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 |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-8_3 cw-9_4 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 vc-7_1 |multi_array| access: cw-8_3 assign: cw-8_3 assign_to_array: cw-8_3 index_bases: cw-8_3 iterators: cw-8_3 slice: cw-8_3 |bind| bind_dm3_test: borland-5_6_4 |algorithm/string| find: cw-9_4 cw-9_5-darwin tru64cxx71-006 replace: cw-9_4 cw-9_5-darwin tru64cxx71-006 |typeof| data_member_emulation: cw-8_3 function_emulation: cw-8_3 function_native: cw-8_3 function_ptr_emulation: cw-8_3 function_ptr_from_tpl_emulation: cw-9_4 vc-7_1 function_ptr_from_tpl_native: cw-9_4 mingw-3_4_2 vc-7_1 function_ref_emulation: cw-8_3 lvalue_emulation: gcc-4.0.2-linux lvalue_native: gcc-4.0.2-linux member_function_emulation: cw-8_3 modifiers_emulation: cw-8_3 noncopyable_emulation: cw-8_3 std_emulation: cw-8_3 template_dependent_emulation: cw-8_3 template_enum_emulation: cw-8_3 template_int_emulation: cw-8_3 template_multiword_emulation: cw-8_3 template_tpl_emulation: cw-8_3 template_type_emulation: cw-8_3 type_emulation: cw-8_3 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 mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 |filesystem| convenience_test: borland-5_6_4 cw-8_3 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux fstream_test: borland-5_6_4 cw-8_3 gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux large_file_support_test: borland-5_6_4 cw-8_3 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mbcopy: borland-5_6_4 cw-8_3 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: borland-5_6_4 cw-8_3 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 mingw-3_4_2 operations_test: borland-5_6_4 cw-8_3 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: cw-8_3 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 cw-8_3 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux path_test_dll: cw-8_3 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux simple_ls: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux wide_test: borland-5_6_4 cw-8_3 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

1 0

Why use Boost?
by Paul Giaccone 03 Feb '06

03 Feb '06

There is a thread on the Boost-users mailing list at the moment asking what users needed to know when they got started with Boost. One of the points raised is that, while pretty much all users of Boost think it is great, they didn't know when they started using it why it was so great and why it would be to their advantage to use it. One of the reasons for this is that the front page of the website does not really sell the product. I agreed with this point. Here's a summary of my posting: "What the site needs, in my view, on the front page is some sort of material selling Boost. Why was Boost set up in the first place? Because, in some areas, C++ is deficient, is difficult to use or expects too much of the programmer. Boost helps by providing what is useful but missing and takes a lot of the work out of C++ programming. "Essentially, Boost needs to sell itself as something that no C++ programmer would want to be without. Think how the adman would write it: "C++ getting you down? Spending hours tracking down that memory leak? Then try Boost! It will change your life!" Well, maybe not, but something along these lines would certainly go a long way to showing why anyone should be using Boost. At the moment, the front page tells me is that the libraries are free, portable, peer-reviewed and work well with the C++ standard library, but that doesn't tell me why it is to anyone's advantage to use them." David Abrahams of Boost Consulting, who started the thread, suggested that I write a paragraph for a selection of Boost libraries that did just this. Below is what I came up with, from my experience as a Boost user who has used the libraries mentioned. I think it would be helpful to both users and developers if this text or something similar could be included on the front page of boost.org or some other prominent place on the website. For myself, if I had seen something like this content on the front page, I would have rushed to download the libraries. What do you, as the developers, think of this proposal? Keep up the excellent work. Paul Giaccone "Memory allocation on the heap in C++ requires the programmer to manage the memory, make sure that there is always at least one pointer to the memory and deallocating it at the right time. It is easy to forget to do this or to do it in the wrong place in the code, which causes memory leaks, or, worse, program crashes. Boost makes life easier for the programmer by providing various 'smart pointers' that automatically maintain memory allocated on the heap, deallocating it at the right time and requiring minimal intervention from the user." "A programmer wanting to read and write structured data (such as the member variables of a class) to file can run into a number of problems. How should the data be formatted when written to file? Do the read and write functions correspond exactly? If the structure of the data changes in future releases of the program, will it still possible to read files that were written using the old format? Are files written on one platform readable on another? How should pointers be handled? Boost provides a serialization library that manages all of these problems and more simply and elegantly." "In standard C++, handling multiple command-line arguments usually requires the user to write a bespoke parser to read in and interpret these arguments and handle syntax errors, missing arguments, duplicated flags and the like. Boost's program_options library handles command-line arguments without fuss." "Writing user-defined input and output streams can be tricky. The Boost iostreams library gives the user easy access a range of useful functionality, including data encryption, compression in various standard formats, line-ending conversion and output in XML format." "C++ allows for casting between similar types, such as int and double. The Boost conversion library extends what is possible with casting, enabling the user to cast integers to strings and vice versa, and to cast safely between polymorphic types."

8 20

Re: [boost] Help with documentation
by David Maisonave 03 Feb '06

03 Feb '06

"John Phillips" <phillips(a)delos.mps.ohio-state.edu> wrote in message news:<drvqjs$3ls$1(a)sea.gmane.org>... > If you have a great idea for a library, but you don't feel the > documentation is keeping to the same high standards, there is now a > place to look. > If you are frustrated by the documentation of a library and would > love a chance to help make it better, there is now a place to offer your > services. > > On the Wiki, you will now find a link to Documentation Helpers. > This > is a list of people who are volunteering to work with developers to > improve the documentation of libraries and proposed libraries. > If you want to help, go add your name to the list. If you want help, > go look at the list and contact someone. > > Since this is the result of a conversation buried deep in a thread > that some people may not be following, I'm also putting it in its own > thread. Could you please provide a link for those of us who don't know what is Wiki? Thanks

1 0

Re: [boost] Why use Boost?
by David Maisonave 03 Feb '06

03 Feb '06

"David Abrahams" <dave(a)boost-consulting.com> wrote in message news:<ud5i4hat0.fsf(a)boost-consulting.com>... > "David Maisonave" <dmaisonave(a)commvault.com> writes: > >> > Actually, I would rather invest the time in creating an automated > >> > documentation wizard. > >> > >> Great! Any contribution that you can make will have a huge impact. > >> What do you have in mind, if I may ask? > > > > I was thinking of a web based form. > > I wasn't asking what the specific medium would be; I was wondering > what it would actually *do*. At first I was think of a step by step wizard, in which it would ask you for specifics of the target code, and required documentation for the code. Example Form: ------------------------------------------------------------------------ -------------------- Object name: Introduction: Two-minute tutorial: (optional) Parameters: Required Headers: Example Usage: See Also: (optional) Motivation (Rationale): (optional) Notes: (optional) FAQ: (optional) Members: Introduction, Parameters, (Requirements)Required-Preconditions, Postconditions, Effects, Returns, Throws, Notes, Synopsis: ------------------------------------------------------------------------ --------------------

1 0

Re: [boost] Why use Boost?
by David Maisonave 03 Feb '06

03 Feb '06

"Paul Giaccone" <paulg(a)cinesite.co.uk> wrote in message news:<43E329D5.1050800(a)cinesite.co.uk>... > I intend no disrespect to any of the developers, but > isn't there an unwritten principle in program development that the > developer shouldn't write the documentation because they are too close > to the code to understand what the user requires from the docs? I think this actually makes a good case for having a person critiquing the document who really doesn't know that much about that particular part of the library.

1 0

Re: [boost] Why use Boost?
by David Maisonave 03 Feb '06

03 Feb '06

"Paul Giaccone" <paulg(a)cinesite.co.uk> wrote in message news:<43E1D46C.7000500(a)cinesite.co.uk>... > There is a thread on the Boost-users mailing list at the moment asking > what users needed to know when they got started with Boost. > > One of the points raised is that, while pretty much all users of Boost > think it is great, they didn't know when they started using it why it > was so great and why it would be to their advantage to use it. One of > the reasons for this is that the front page of the website does not > really sell the product. > > I agreed with this point. Here's a summary of my posting: > > "What the site needs, in my view, on the front page is some sort of > material selling Boost. Why was Boost set up in the first place? I totally agree 100%. IMHO, for the most part, the site is setup as if users already know about boost. Most of the help documents seem to be targeted for more advanced C++ programmer. They make no real attempt to sell the library. Although I knew about boost for a long time, I didn't start using it until recently, because I was under the impression, that I would need to add additional *.cpp or lib files to my project in order to use boost. I also thought my binary would increase substantially if I linked to boost just to use a specific object like boost::shared_ptr. IMHO, the help documents waist too much space in giving details that really don't help the average user to figure out how to use an interface. Take intrusive_pr document for an example: http://www.boost.org/libs/smart_ptr/intrusive_ptr.html There's no example usage at all. It waist a lot of space giving details Synopsis and Members, but very little space for an introduction, or a good explanation on how to use it. As a user, why would I care about the Synopsis or Members, if I can't figure out how to use the interface. There should be more focus on introduction and example usage, and less focus on Synopsis and Members section. Moreover, IMHO, in Members section, each member should have an example usage. Take a look at weak_ptr http://www.boost.org/libs/smart_ptr/weak_ptr.htm Look at the members section for lock and rest. There's no usage example and no explanation of their purpose. Why would I care that it throws nothing, if I don't know what it's for. I think there would be 10 times more boost users, if the boost developers put the same quality into the documents, as they do into the code. It would also help developers, if boost had a really GOOD template to do this, and it would serve as a check list for required/recommended documentation. What's the point of creating a great class, if only a handfull of developers ues it, because the majority have no idea how to use it?

7 13

1.34 Release Plan
by Thomas Witt 03 Feb '06

03 Feb '06

Hi, with 1.33.0 now five months old it is time to get the 1.34.0 release going. Well to be honest it's probably more than time. In order to improve our release process we are planning to adopt a staged release process that is modelled partly after the gcc release process. By and large it can be seen as a formalization of things already done in past releases. A description of the different stages will be given at the end of this mail. But lets get the important issues out of the way first: schedule. I think that we have enough features in CVS already to make 1.34 worthwhile. For that reason the main focus for 1.34 will be a release within reasonable time. For that reason I am going to aim for a feature freeze (Stage 3) in two weeks from now. I ask anybody who can not make that deadline for one reason or another to contact me directly and we try to figure something out. Furthermore for this release feature freeze will also be the cut off date for addition of new libraries. I am planning to flesh out the further schedule in a few days once I got an idea how we are doing with the feature freeze. Thanks Thomas Boost Release Procedure (by Doug Gregor) ==================== Boost development for each release will be divided into four stages, influenced by the GCC development model. The stages move from a very loose, open development model where major changes can be made toward a much more tightly-controlled model as the release date nears. Release managers are appointed for the duration of the release process for a particular version of Boost, and several Boost versions may be in progress at any point in time. However, actual release dates will be staggered to allow testing resources to be allocated to the most imminent release. Stage 1 - Open Development -------------------------- Major changes to libraries or infrastructure may be performed, including large updates or additions to core libraries (e.g., type traits) and tools (e.g., Boost.Build). New libraries and new features can be added freely. Stage 2 - Intracomponent Open Development ----------------------------------------- This stage restricts Stage 1 slightly by banning far-reaching changes to Boost. Major changes to libraries or infrastructure, or the addition of new features and libraries, can be made in the stage. However, the changes must be limited in scope and may not have far-reaching affects. For instance, the build or regression testing systems in Boost cannot be changed at this point, and Boost libraries on which other major components of Boost depend (such as MPL, Type Traits, and Config) may not have large interface changes or be fundamentally rewritten. The Release Manager has final say regarding the classification of changes as "far-reaching" or not; if you are unsure, please ask. Stage 3 - Feature freeze ------------------------ This stage is a bug-fixing stage. Bug fixes may be freely applied to Boost, even if they require substantial changes. Interfaces may not be changed (unless required to fix bugs) and new features should be added only sparingly and with Release Manager approval. New libraries may be introduced at this stage with Release Manager approval, but the introduction of new libraries is tentative: if the new library fails a significant number of its regression tests, it will be removed from the release. Stage 4 - Release preparation ----------------------------- Only bug-fixes and documentation changes may be applied, and the changes should be as minimal and as safe as possible. If a change is large, or has the potential to cause additional failures, consult the Release Manager before applying the change to the repository. Changes that cause failures will be reverted after 48 hours if the failures are not addressed to the Release Manager's satisfaction. The beginning of stage 4 will be marked by the creation of a new CVS branch for the release. At this point, the old CVS branch falls back to stage 1 (for major releases, e.g., 1.XX.0) or stage 3 (for minor releases, e.g., 1.XX.Y). Final Freeze ------------ 7 days prior to a release, the Release Manager will call for a final freeze on the CVS branch corresponding to the release. At this point, no changes may be made to the branch with explicit Release Manager approval. Post-Release ------------ After a release is made, the changes made on the release branch should be merged back into its parent branch. The release branch reverts to stage 4; should another minor release be scheduled on that branch, the Release Manager for that minor version may revert to stage 3 or remain in stage 4 until the point release is imminent. Thomas Witt witt(a)acm.org

22 77

Fwd: pd darwin Symbol not found
by Locatelli Jérôme 03 Feb '06

03 Feb '06

I'am writing a application on MacOS 10.4.4 using darwin 8 with gcc 4, I compile and link my application without problem but when I run my application , I've got the error bellow. Has anybody got an idear?? Thanks. dyld: lazy symbol binding failed: Symbol not found: __ZN5boost6detail3tss4initEPNS_9function1IvPvSaINS_13function_baseEEEE Referenced from: /Users/locatelli/Projets/ics/IcsServer/obj.ics/../lib/ libIcsServerCommandSystem.0 Expected in: flat namespace dyld: Symbol not found: __ZN5boost6detail3tss4initEPNS_9function1IvPvSaINS_13function_baseEEEE Referenced from: /Users/locatelli/Projets/ics/IcsServer/obj.ics/../lib/ libIcsServerCommandSystem.0 Expected in: flat namespace Trace/BPT trap --------------------------------------------------- Locatelli Jérôme Institut Laue-Langevin Service Contrôle des instruments 6 rue Jules Horowitz, BP 156 38042 Grenoble cedex 9 http://www.ill.fr/ Tel: 33 (0)4 76 20 76 27 Fax: 33 (0)4 76 20 77 00 ---------------------------------------------------

1 0

Bind comparisons
by David Abrahams 03 Feb '06

03 Feb '06

Is it really true that I can write bind(f, _1) > _2 but can't write _1 > _2 ?? I can't imagine a good reason for that restriction, but I don't see any indication that the latter is supported in the docs. -- Dave Abrahams Boost Consulting www.boost-consulting.com

5 25

Re: [boost] Why use Boost?
by David Maisonave 03 Feb '06

03 Feb '06

"David Abrahams" <dave(a)boost-consulting.com> wrote in message news:<umzh9idhm.fsf(a)boost-consulting.com>... > "David Maisonave" <dmaisonave(a)commvault.com> writes: > > > "David Abrahams" <dave(a)boost-consulting.com> wrote in message > >> Unfortunately, I think Rob Stewart just became too busy to make the > >> contribution he wanted to. Perhaps you'd like to step up? > > > > > > Actually, I would rather invest the time in creating an automated > > documentation wizard. > > Great! Any contribution that you can make will have a huge impact. > What do you have in mind, if I may ask? I was thinking of a web based form. But I'm flexable

2 1