- Boost - lists.boost.org

[filesystem][program options][serialization][test] comp.lang.c++.moderated: problem Boost libraries
by David Abrahams 26 Feb '07

26 Feb '07

I don't know if everyone saw this post and the *long* ensuing thread (I have been away from the NGs for the past month or so) but IMO it's very important for us (I mean the authors and maintainers of the referenced libraries) to address posts like this one, both to show our responsiveness but also to counter the inevitable FUD that ensuses when such posts are not answered. -- Dave Abrahams Boost Consulting www.boost-consulting.com

4 3

BOOST_MPL_HAS_XXX_TRAIT_DEF
by Gennadiy Rozental 26 Feb '07

26 Feb '07

I think example in subject reference page has a typo: BOOST_MPL_HAS_XXX_TRAIT_DEF(has_xxx) should be BOOST_MPL_HAS_XXX_TRAIT_DEF(xxx) Also: Does anyone know any workaround to make it work for Sunpro 5.3 compiler? Specifically I need to detect that particular method is the member of the template argument class. Gennadiy

1 0

[Report] 116 regressions on RC_1_34_0 (2007-02-22)
by Douglas Gregor 26 Feb '07

26 Feb '07

Boost Regression test failures Report time: 2007-02-22T05:41:47Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 116 failures in 12 libraries date_time (2) foreach (1) functional/hash (1) graph (1) iostreams (10) math (1) numeric/interval (1) parameter (1) python (73) regex (3) test (18) wave (4) |date_time| testdate_input_facet: msvc-7.1_stlport4 testdate_input_facet_dll: msvc-7.1_stlport4 |foreach| rvalue_const: intel-linux-9.0 |functional/hash| hash_float_test: intel-linux-9.0 |graph| graphviz_test: msvc-7.1_stlport4 |iostreams| bzip2_test: intel-linux-9.0 msvc-7.1 msvc-8.0 file_descriptor_test: gcc-cygwin-3.4.4 gzip_test: intel-linux-9.0 msvc-7.1 msvc-8.0 zlib_test: intel-linux-9.0 msvc-7.1 msvc-8.0 |math| common_factor_test: msvc-6.5 |numeric/interval| test_float: msvc-7.1_stlport4 |parameter| python_test: gcc-cygwin-3.4.4 |python| andreas_beyer: gcc-cygwin-3.4.4 args: gcc-cygwin-3.4.4 auto_ptr: gcc-cygwin-3.4.4 back_reference: gcc-cygwin-3.4.4 bases: gcc-cygwin-3.4.4 intel-linux-9.0 ben_scott1: gcc-cygwin-3.4.4 bienstman1: gcc-cygwin-3.4.4 bienstman2: gcc-cygwin-3.4.4 bienstman3: gcc-cygwin-3.4.4 borrowed: gcc-cygwin-3.4.4 builtin_converters: gcc-cygwin-3.4.4 callbacks: gcc-cygwin-3.4.4 const_argument: gcc-cygwin-3.4.4 crossmod_exception: gcc-cygwin-3.4.4 crossmod_opaque: gcc-cygwin-3.4.4 data_members: gcc-cygwin-3.4.4 defaults: gcc-cygwin-3.4.4 dict: gcc-cygwin-3.4.4 docstring: gcc-cygwin-3.4.4 enum: gcc-cygwin-3.4.4 exception_translator: gcc-cygwin-3.4.4 exec: gcc-cygwin-3.4.4 intel-linux-9.0 extract: gcc-cygwin-3.4.4 implicit: gcc-cygwin-3.4.4 injected: gcc-cygwin-3.4.4 iterator: gcc-cygwin-3.4.4 keywords: gcc-cygwin-3.4.4 list: gcc-cygwin-3.4.4 long: gcc-cygwin-3.4.4 map_indexing_suite: gcc-cygwin-3.4.4 minimal: gcc-cygwin-3.4.4 multi_arg_constructor: gcc-cygwin-3.4.4 nested: gcc-cygwin-3.4.4 numpy: gcc-cygwin-3.4.4 object: gcc-cygwin-3.4.4 object_manager: gcc-cygwin-3.4.4 opaque: gcc-cygwin-3.4.4 operators: gcc-cygwin-3.4.4 pearu1: gcc-cygwin-3.4.4 pickle1: gcc-cygwin-3.4.4 pickle2: gcc-cygwin-3.4.4 pickle3: gcc-cygwin-3.4.4 pickle4: gcc-cygwin-3.4.4 pointee: gcc-cygwin-3.4.4 intel-linux-9.0 pointer_type_id_test: gcc-cygwin-3.4.4 intel-linux-9.0 pointer_vector: gcc-cygwin-3.4.4 polymorphism: gcc-cygwin-3.4.4 polymorphism2: gcc-cygwin-3.4.4 polymorphism2_auto_ptr: gcc-cygwin-3.4.4 properties: gcc-cygwin-3.4.4 raw_ctor: gcc-cygwin-3.4.4 return_arg: gcc-cygwin-3.4.4 select_arg_to_python_test: gcc-cygwin-3.4.4 select_from_python_test: gcc-cygwin-3.4.4 select_holder: gcc-cygwin-3.4.4 shared_ptr: gcc-cygwin-3.4.4 slice: gcc-cygwin-3.4.4 staticmethod: gcc-cygwin-3.4.4 stl_iterator: gcc-cygwin-3.4.4 str: gcc-cygwin-3.4.4 test_pointer_adoption: gcc-cygwin-3.4.4 try: gcc-cygwin-3.4.4 tuple: gcc-cygwin-3.4.4 upcast: gcc-cygwin-3.4.4 intel-linux-9.0 vector_indexing_suite: gcc-cygwin-3.4.4 virtual_functions: gcc-cygwin-3.4.4 voidptr: gcc-cygwin-3.4.4 wrapper_held_type: gcc-cygwin-3.4.4 |regex| regex_regress_threaded: msvc-7.1_stlport4 msvc-8.0 static_mutex_test: gcc-cygwin-3.4.4 |test| boost_check_equal_str: gcc-mingw-3.4.2 msvc-6.5 msvc-6.5 msvc-6.5_stlport4 errors_handling_test: gcc-mingw-3.4.2 fixed_mapping_test: gcc-mingw-3.4.2 ifstream_line_iterator_test: gcc-mingw-3.4.2 output_test_stream_test: gcc-mingw-3.4.2 parameterized_test_test: gcc-mingw-3.4.2 prg_exec_fail3: cw-9.4 result_report_test: gcc-mingw-3.4.2 test_case_template_test: gcc-mingw-3.4.2 test_fp_comparisons: gcc-mingw-3.4.2 test_tools_test: gcc-mingw-3.4.2 msvc-6.5 msvc-6.5 msvc-6.5_stlport4 token_iterator_test: gcc-mingw-3.4.2 |wave| test_re2c_lexer: msvc-7.1_stlport4 test_slex_lexer: msvc-7.1_stlport4 testwave: msvc-7.1_stlport4 testwave_dll: msvc-7.1_stlport4

3 6

Boost inspection notification (2007-02-26/RC_1_34_0) *X*
by Rene Rivera 26 Feb '07

26 Feb '07

Boost Inspection Report Run Date: 17:02:21 UTC, Monday 26 February 2007 An inspection program <http://www.boost.org/tools/inspect/index.html> checks each file in the current Boost CVS for various problems, generating this as output. Problems detected include tabs in files, missing copyrights, broken URL's, and similar misdemeanors. Totals: 11447 files scanned 908 directories scanned (including root) 195 problems reported Problem counts: 0 files with invalid line endings 0 bookmarks with invalid characters 3 invalid urls 104 broken links 21 unlinked files 22 file/directory names issues 1 files with tabs 9 violations of the Boost min/max guidelines 35 usages of unnamed namespaces in headers (including .ipp files) Summary: archive (3) bind (1) boost-root (3) build (1) date_time (1) doc (2) filesystem (37) graph (2) iostreams (3) lambda (3) math (8) more (1) mpl (1) multi_array (2) ptr_container (1) python (10) regex (1) regression (32) serialization (1) test (81) type_traits (1) Details: *R* invalid (cr only) line-ending *A* invalid bookmarks, invalid urls, broken links, unlinked files *N* file/directory names issues *T* tabs in file *M* uses of min or max that have not been protected from the min/max macros, or unallowed #undef-s *U* unnamed namespace in header |archive| boost/archive/basic_streambuf_locale_saver.hpp: *N* name exceeds 31 characters boost/archive/impl/xml_wiarchive_impl.ipp: *U* unnamed namespace at line 53 boost/archive/iterators/remove_whitespace.hpp: *U* unnamed namespace at line 57 |bind| boost/bind/placeholders.hpp: *U* unnamed namespace at line 25 |boost-root| index.htm: *A* broken link: doc/hmtl/date_time.html *A* broken link: doc/hmtl/date_time/details.html#changes *A* broken link: more/BoostCon07.html |build| tools/build/v2/test/test_system.html: *A* unlinked file |date_time| libs/date_time/xmldoc/date_time_docs_howto.html: *A* unlinked file |doc| doc/html/boost_math/inverse_complex.html: *A* unlinked file doc/html/jam.html: *A* unlinked file |filesystem| libs/filesystem/doc/do-list.htm: *A* invalid URL (hardwired file): file://?/ *A* invalid URL (hardwired file): file://?/UNC/ libs/filesystem/doc/i18n.html: *A* broken link: convenience.htm#basic_recursive_directory_iterator *A* broken link: exception.htm *A* broken link: operations.htm *A* broken link: operations.htm#Do-the-right-thing *A* broken link: operations.htm#is_directory *A* broken link: operations.htm#is_file *A* broken link: operations.htm#status libs/filesystem/doc/index.htm: *A* broken link: ../build/Jamfile *A* broken link: convenience.htm *A* broken link: fstream.htm *A* broken link: operations.htm#create_directory *A* broken link: operations.htm#create_hard_link *A* broken link: operations.htm#current_path *A* broken link: operations.htm#directory_iterator *A* broken link: operations.htm#equivalent *A* broken link: operations.htm#file_size *A* broken link: operations.htm#initial_path *A* broken link: operations.htm#is_file *A* broken link: operations.htm#is_symlink *A* broken link: operations.htm#status *A* broken link: operations.htm#symlink_status *A* broken link: path.htm#Canonical *A* broken link: path.htm#Grammar *A* broken link: path.htm#Normalized *A* broken link: path.htm#default_name_check *A* broken link: path.htm#name_check_mechanism *A* broken link: path.htm#normalize *A* broken link: path.htm#operator_eq *A* broken link: path.htm#synopsis libs/filesystem/doc/portability_guide.htm: *A* broken link: path.htm#name_check_typedef libs/filesystem/doc/tr2_proposal.html: *A* invalid URL (hardwired file): file:///C|/boost/site/libs/filesystem/doc/operations.htm#complete_note |graph| libs/graph/example/file_dependencies.cpp: *M* violation of Boost min/max guidelines on line 139 libs/graph/test/serialize.cpp: *T* |iostreams| libs/iostreams/doc/acknowledgments.html: *A* unlinked file libs/iostreams/doc/concepts/multi-character.html: *A* unlinked file libs/iostreams/doc/installation.html: *A* broken link: ../../../tools/build/v1/build_system.htm |lambda| boost/lambda/core.hpp: *U* unnamed namespace at line 62 boost/lambda/detail/lambda_functors.hpp: *U* unnamed namespace at line 25 boost/lambda/exceptions.hpp: *U* unnamed namespace at line 24 |math| libs/math/test/common_factor_test.cpp: *M* violation of Boost min/max guidelines on line 146 *M* violation of Boost min/max guidelines on line 147 *M* violation of Boost min/max guidelines on line 193 *M* violation of Boost min/max guidelines on line 194 |more| more/separate_compilation.html: *A* broken link: ../libs/config/test/link/test/Jamfile.v2 |mpl| boost/mpl/alias.hpp: *U* unnamed namespace at line 17 |multi_array| boost/multi_array/base.hpp: *U* unnamed namespace at line 69 libs/multi_array/test/generative_tests.hpp: *U* unnamed namespace at line 57 |ptr_container| libs/ptr_container/doc/tutorial_example.html: *A* unlinked file |python| libs/python/doc/building.html: *A* broken link: ../../../tools/build/v1/build_system.htm *A* broken link: ../../../tools/build/v1/build_system.htm#user_globals *A* broken link: ../../../tools/build/v1/build_system.htm#variants libs/python/doc/tutorial/doc/html/python/hello.html: *A* broken link: ../../../../../example/tutorial/Jamrules libs/python/doc/tutorial/index.html: *A* broken link: ../../../LICENSE_1_0.txt libs/python/doc/v2/May2002.html: *A* broken link: ../../../../tools/build/v1/build_system.htm *A* broken link: ../../../../tools/build/v1/gen_aix_import_file.py libs/python/doc/v2/faq.html: *A* broken link: ../../../../tools/build/v1/build_system.htm |regex| libs/regex/performance/input.html: *A* unlinked file |regression| regression/.htaccess: *N* leading character of ".htaccess" is not alphabetic tools/regression/test/test-cases/incremental/bjam.log.1: *N* name contains more than one dot character ('.') tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/compile-fail.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/completed.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/compile-fail.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/completed.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/lib.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/misfire.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/no-run.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/run_pyd.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/test-case.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/test-case.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/test-driver.xsl: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_re_match/expected/test_re_match.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_test_case_status/explicit-failures-markup.xml.test: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ *N* name contains more than one dot character ('.') *N* name exceeds 31 characters tools/regression/xsl_reports/test/test-components/test_test_structure/explicit-failures-markup.xml.test: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ *N* name contains more than one dot character ('.') *N* name exceeds 31 characters tools/regression/xsl_reports/xsl/html/issues_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/library_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/library_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/make_tinyurl.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/summary_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/summary_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/issues_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/library_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/library_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/make_tinyurl.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_user_legend.html: *A* unlinked file |serialization| libs/serialization/src/basic_xml_grammar.ipp: *U* unnamed namespace at line 43 |test| boost/test/floating_point_comparison.hpp: *U* unnamed namespace at line 206 *U* unnamed namespace at line 228 boost/test/impl/cpp_main.ipp: *U* unnamed namespace at line 42 boost/test/impl/exception_safety.ipp: *U* unnamed namespace at line 400 boost/test/impl/framework.ipp: *U* unnamed namespace at line 199 boost/test/impl/plain_report_formatter.ipp: *U* unnamed namespace at line 45 boost/test/impl/progress_monitor.ipp: *U* unnamed namespace at line 38 boost/test/impl/results_collector.ipp: *U* unnamed namespace at line 106 boost/test/impl/results_reporter.ipp: *U* unnamed namespace at line 48 boost/test/impl/unit_test_log.ipp: *U* unnamed namespace at line 79 boost/test/impl/unit_test_monitor.ipp: *U* unnamed namespace at line 35 boost/test/impl/unit_test_parameters.ipp: *U* unnamed namespace at line 50 boost/test/results_collector.hpp: *U* unnamed namespace at line 40 boost/test/test_tools.hpp: *U* unnamed namespace at line 262 boost/test/utils/iterator/token_iterator.hpp: *U* unnamed namespace at line 166 boost/test/utils/named_params.hpp: *U* unnamed namespace at line 216 boost/test/utils/runtime/cla/dual_name_parameter.ipp: *U* unnamed namespace at line 43 boost/test/utils/runtime/cla/modifier.hpp: *U* unnamed namespace at line 34 boost/test/utils/runtime/env/modifier.hpp: *U* unnamed namespace at line 34 boost/test/utils/runtime/file/config_file.hpp: *U* unnamed namespace at line 169 *U* unnamed namespace at line 64 *U* unnamed namespace at line 74 boost/test/utils/runtime/file/config_file_iterator.hpp: *U* unnamed namespace at line 68 boost/test/utils/trivial_singleton.hpp: *U* unnamed namespace at line 52 *U* unnamed namespace at line 61 libs/test/build/msvc71_proj/config_file_iterator_test.vcproj: *N* name exceeds 31 characters libs/test/doc/components/prg_exec_monitor/compilation.html: *A* broken link: ../../../build/Jamfile libs/test/doc/components/prg_exec_monitor/index.html: *A* broken link: ../../../../../boost/test/cpp_main.hpp libs/test/doc/components/test_tools/index.html: *A* broken link: ../../tests/boost_check_equal_str.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_CLOSE.html: *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_MESSAGE.html: *A* broken link: BOOST_MESSAGE.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_SMALL.html: *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/test_tools/reference/tools_list.html: *A* broken link: ../../btl1.gif *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/utf/compilation.html: *A* broken link: ../../../build/Jamfile libs/test/doc/components/utf/components/index.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/components/test_case/abstract_interface.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/auto_register_facility.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/boost_function_tc.html: *A* broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/class_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/function_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_boost_function_tc.html: *A* broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_class_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_function_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/tc_template.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_log/custom_log_formatter.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_log/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_result/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_suite/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/index.html: *A* broken link: getting_started/index.html libs/test/doc/components/utf/parameters/build_info.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/catch_system_errors.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/detect_memory_leaks.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/index.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/log_format.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/log_level.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/no_result_code.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/output_format.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/random.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/report_format.html: *A* broken link: ../../../../../LICENSE_1_0.txt *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/report_level.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/show_progress.html: *A* broken link: ../../btl1.gif libs/test/doc/examples/unit_test_example1.html: *A* broken link: ../../example/unit_test_example1.cpp libs/test/doc/examples/unit_test_example2.html: *A* broken link: ../../example/unit_test_example2.cpp libs/test/doc/examples/unit_test_example3.html: *A* broken link: ../../example/unit_test_example3.cpp libs/test/doc/examples/unit_test_example4.html: *A* broken link: ../../example/unit_test_example4.cpp libs/test/doc/examples/unit_test_example5.html: *A* broken link: ../../example/unit_test_example5.cpp *A* broken link: ../../example/unit_test_example5.input libs/test/doc/tests/auto_unit_test_test.html: *A* broken link: ../../test/auto_unit_test_test.cpp libs/test/doc/tests/auto_unit_test_test_mult.html: *A* broken link: ../../test/auto_unit_test_test_mult1.cpp *A* broken link: ../../test/auto_unit_test_test_mult2.cpp libs/test/doc/tests/unit_test_suite_ex_test.html: *A* broken link: ../../test/unit_test_suite_ex_test.cpp libs/test/doc/tutorials/hello_the_testing_world.html: *A* broken link: ../../../../../LICENSE_1_0.txt *A* broken link: ../execution_monitor/index.html libs/test/doc/tutorials/new_year_resolution.html: *A* broken link: ../../../../../../LICENSE_1_0.txt |type_traits| libs/type_traits/cxx_type_traits.htm: *A* unlinked file

1 0

[Report] 46 regressions on RC_1_34_0 (2007-02-26)
by Douglas Gregor 26 Feb '07

26 Feb '07

Boost Regression test failures Report time: 2007-02-26T06:29:24Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 46 failures in 12 libraries algorithm/string (1) foreach (1) functional/hash (1) graph (1) iostreams (10) math (3) multi_index (4) numeric/interval (1) parameter (1) python (5) regex (4) test (14) |algorithm/string| regex: gcc-3.2.3_linux |foreach| rvalue_const: intel-linux-9.0 |functional/hash| hash_float_test: intel-linux-9.0 |graph| graphviz_test: msvc-7.1_stlport4 |iostreams| bzip2_test: intel-linux-9.0 msvc-7.1 msvc-8.0 file_descriptor_test: gcc-cygwin-3.4.4 gzip_test: intel-linux-9.0 msvc-7.1 msvc-8.0 zlib_test: intel-linux-9.0 msvc-7.1 msvc-8.0 |math| common_factor_test: msvc-6.5 msvc-6.5_stlport4 msvc-7.1_stlport4 |multi_index| test_safe_mode: intel-linux-9.0 test_set_ops: gcc-3.3.6_linux test_special_set_ops: gcc-3.3.6_linux test_update: gcc-3.3.6_linux |numeric/interval| test_float: msvc-7.1_stlport4 |parameter| python_test: gcc-cygwin-3.4.4 |python| bases: intel-linux-9.0 exec: intel-linux-9.0 pointee: intel-linux-9.0 pointer_type_id_test: intel-linux-9.0 upcast: intel-linux-9.0 |regex| regex_regress_threaded: gcc-cygwin-3.4.4 msvc-6.5_stlport4 msvc-7.1_stlport4 msvc-8.0 |test| boost_check_equal_str: gcc-mingw-3.4.2 msvc-6.5 errors_handling_test: gcc-mingw-3.4.2 fixed_mapping_test: gcc-mingw-3.4.2 ifstream_line_iterator_test: gcc-mingw-3.4.2 output_test_stream_test: gcc-mingw-3.4.2 parameterized_test_test: gcc-mingw-3.4.2 prg_exec_fail3: cw-9.4 result_report_test: gcc-mingw-3.4.2 test_case_template_test: gcc-mingw-3.4.2 test_fp_comparisons: gcc-mingw-3.4.2 test_tools_test: gcc-mingw-3.4.2 msvc-6.5 token_iterator_test: gcc-mingw-3.4.2

1 0

[RC_1_34_0] failures + analysis
by David Abrahams 26 Feb '07

26 Feb '07

I've been running release-mode tests of the release branch using the native AMD64 version of VC++ 8.0, and things have settled down now to the point where I think the failure report is useful. You can see the results in the BoostConsulting column of the release branch regression report (http://tinyurl.com/lawq3) but I've enclosed a list of the failures along with my analysis. I pruned the error messages down to a representative sample for each failure so this should be easy to review. The libraries with failures are: bind concept_check date_time graph iterator numeric program_options python range spirit test thread tr1 typeof Although this platform/compiler is not part of our official release requirements, I hope that the consolidation, pruning, and analysis will make it easier to use than the webpage, to the point that the library maintainers will prefer using what I've enclosed, or at least will be willing to give it a few moments' attention. Thanks, Dave ------- compile-c-c++ concept_check/stl_concept_covering.obj known bogus test. compile-c-c++ graph/csr_graph_test.obj call "C:\Program Files (x86)\Microsoft Visual Studio 8\VC\vcvarsall.bat" amd64 >nul cl /Zm800 -nologo @"Z:\results\boost\bin.v2\libs\graph\test\csr_graph_test.test\msvc-8.0.m\rls\adrs-mdl-64\instr-set-optrn\thrd-mlt\csr_graph_test.obj.rsp" csr_graph_test.cpp ..\libs\graph\test\csr_graph_test.cpp(353) : error C2752: 'boost::property_map<Graph,Property>' : more than one partial specialization matches the template argument list with [ Graph=boost::compressed_sparse_row_graph<boost::directedS,Vertex,Edge>, Property=double Vertex::* ] ..\boost/graph/compressed_sparse_row_graph.hpp(737): could be 'boost::property_map<boost::compressed_sparse_row_graph<Directed,VertexProperty,EdgeProperty,GraphProperty,Vertex,EdgeIndex>,TBundle::* >' ..\boost/graph/properties.hpp(352): or 'boost::property_map<Graph,TBundle::* >' ..\boost/pending/property.hpp(46) : error C2825: 'PropertyTag': must be a class or namespace when followed by '::' ..\boost/graph/properties.hpp(199) : see reference to class template instantiation 'boost::property_kind<PropertyTag>' being compiled with [ PropertyTag=double Vertex::* ] ..\libs\graph\test\csr_graph_test.cpp(353) : see reference to class template instantiation 'boost::property_map<Graph,Property>' being compiled with [ Graph=boost::compressed_sparse_row_graph<boost::directedS,Vertex,Edge>, Property=double Vertex::* ] compile-c-c++ iterator/lvalue_concept_fail.obj The optimizer seems to be defeating the concept check. Newer concept checks in HEAD don't have this problem. compile-c-c++ numeric/det.obj compile-c-c++ numeric/integer.obj compile-c-c++ numeric/mul.obj compile-c-c++ numeric/overflow.obj compile-c-c++ numeric/pi.obj compile-c-c++ numeric/pow.obj compile-c-c++ numeric/test_float.obj All of the above: ..\boost/numeric/interval/hw_rounding.hpp(38) : fatal error C1189: #error : Boost.Numeric.Interval: Please specify rounding control mechanism. compile-c-c++ program_options/test_convert.obj Appears to be a missing #include file, but it also looks like this should be using boost/detail/lightweight_test.hpp ..\libs\program_options\test\test_convert.cpp(22) : error C3861: 'assert': identifier not found ..\libs\program_options\test\test_convert.cpp(77) : error C2143: syntax error : missing ';' before '<' compile-c-c++ tr1/std_test_bind_tricky.obj Looks like a Boost bug. Missing #include? ..\libs\tr1\test\test_bind_tricky.cpp(21) : error C2039: 'is_placeholder' : is not a member of 'std::tr1' ..\libs\tr1\test\test_bind_tricky.cpp(54) : see reference to function template instantiation 'void check_placeholder<boost::arg<I>>(const T &)' being compiled with [ I=1, T=boost::arg<1> ] compile-c-c++ tr1/std_test_function_tricky.obj It's unknown what the problem is here; I suggest using boost/mpl/assert.hpp for a more descriptive message. ..\libs\tr1\test\test_function_tricky.cpp(77) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] ..\libs\tr1\test\test_function_tricky.cpp(78) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] compile-c-c++ tr1/std_test_mem_fn_tricky.obj This one looks like a Boost bug. ..\libs\tr1\test\test_mem_fn_tricky.cpp(37) : error C2664: 'boost::_mfi::dm<R,T> boost::mem_fn<expected_result(void),test>(R (__cdecl test::* ))' : cannot convert parameter 1 from 'expected_result (__cdecl test::* )(void) volatile' to 'expected_result (__cdecl test::* )(void)' with [ R=expected_result (void), T=test ] Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast ... compile-c-c++ tr1/std_test_ref_wrapper_tricky.obj It's unknown what the problem is here; I suggest using boost/mpl/assert.hpp for a more descriptive message. ..\libs\tr1\test\test_ref_wrapper_tricky.cpp(38) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] ..\libs\tr1\test\test_ref_wrapper_tricky.cpp(39) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] compile-c-c++ tr1/test_bind_tricky.obj Looks like a Boost bug. Missing #include? ..\libs\tr1\test\test_bind_tricky.cpp(21) : error C2039: 'is_placeholder' : is not a member of 'std::tr1' ..\libs\tr1\test\test_bind_tricky.cpp(54) : see reference to function template instantiation 'void check_placeholder<boost::arg<I>>(const T &)' being compiled with [ I=1, T=boost::arg<1> ] compile-c-c++ tr1/test_function_tricky.obj It's unknown what the problem is here; I suggest using boost/mpl/assert.hpp for a more descriptive message. ..\libs\tr1\test\test_function_tricky.cpp(77) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] ..\libs\tr1\test\test_function_tricky.cpp(78) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] compile-c-c++ tr1/test_mem_fn_tricky.obj This one looks like a Boost bug. ..\libs\tr1\test\test_mem_fn_tricky.cpp(37) : error C2664: 'boost::_mfi::dm<R,T> boost::mem_fn<expected_result(void),test>(R (__cdecl test::* ))' : cannot convert parameter 1 from 'expected_result (__cdecl test::* )(void) volatile' to 'expected_result (__cdecl test::* )(void)' with [ R=expected_result (void), T=test ] Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast ... compile-c-c++ tr1/test_ref_wrapper_tricky.obj It's unknown what the problem is here; I suggest using boost/mpl/assert.hpp for a more descriptive message. ..\libs\tr1\test\test_ref_wrapper_tricky.cpp(38) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] compile-c-c++ typeof/data_member_native.obj compile-c-c++ typeof/function_binding_native.obj compile-c-c++ typeof/function_native.obj compile-c-c++ typeof/function_ptr_from_tpl_native.obj compile-c-c++ typeof/function_ptr_native.obj compile-c-c++ typeof/function_ref_native.obj compile-c-c++ typeof/member_function_native.obj compile-c-c++ typeof/modifiers_native.obj compile-c-c++ typeof/nested_typedef_native.obj compile-c-c++ typeof/noncopyable_native.obj compile-c-c++ typeof/odr1.obj compile-c-c++ typeof/odr2.obj compile-c-c++ typeof/std_native.obj compile-c-c++ typeof/template_dependent_native.obj compile-c-c++ typeof/template_enum_native.obj compile-c-c++ typeof/template_int_native.obj compile-c-c++ typeof/template_multiword_native.obj compile-c-c++ typeof/template_tpl_native.obj compile-c-c++ typeof/template_type_native.obj compile-c-c++ typeof/type_native.obj I think these are all expected failures, and we fix them in 1.35 (CVS HEAD) with a newly-discovered VC8 bugfeature. ..\boost/typeof/typeof.hpp(104) : fatal error C1189: #error : native typeof is not supported testing.capture-output bind/mem_fn_eq_test.run looks like a Boost bug. ..\libs\bind\test\mem_fn_eq_test.cpp(175): test 'boost::mem_fn(&X::mf0_1) != boost::mem_fn(&X::mf0_2)' failed in function 'int __cdecl main(void)' ..\libs\bind\test\mem_fn_eq_test.cpp(178): test 'boost::mem_fn(&X::cmf0_1) != boost::mem_fn(&X::cmf0_2)' failed in function 'int __cdecl main(void)' ... 36 errors detected. testing.capture-output date_time/testmicrosec_time_clock.run looks like a Boost bug. 2007-Feb-25 10:27:54 2007-Feb-25 10:27:54.730125000 Pass :: hours match Pass :: minutes match Pass :: seconds match Pass :: hours date Pass :: last is less 2007-Feb-25 10:27:54 2007-Feb-25 10:27:54.730125000 Pass :: hours match Pass :: minutes match Pass :: seconds match Pass :: hours date FAIL :: last is less ... testing.capture-output python/exec.run This failure is a combination of broken Windows Python support in BBv2 (working on it) and local configuration issues on the test machine. EXIT STATUS: 128 testing.capture-output spirit/symbols_add_null.run testing.capture-output spirit/symbols_add_null_debug.run ..\libs\spirit\test\symbols_add_null.cpp(52): test '0' failed in function 'int __cdecl main(void)' ..\libs\spirit\test\symbols_add_null.cpp(62): test '0' failed in function 'int __cdecl main(void)' testing.capture-output test/prg_exec_fail3.run This one is very suspicious, because there's no ====== BEGIN OUTPUT ====== ... EXIT STATUS: 1 ====== END OUTPUT ====== sequence in the log, and yet bjam marks it as failing. testing.capture-output thread/test_tss_lib.run Not sure what this one means. ====== BEGIN OUTPUT ====== Running 1 test case... tss_instances = 0; tss_total = 5 tss_instances = 5; tss_total = 5 ../libs/thread/test/test_tss.cpp(151): error in "test_tss": Support of automatic tss cleanup for native threading API not available *** 1 failure detected in test suite "Master Test Suite" EXIT STATUS: 201 ====== END OUTPUT ====== -- Dave Abrahams Boost Consulting www.boost-consulting.com

4 7

BoostCon'07 Registration Now Open
by info＠boostcon.com 26 Feb '07

26 Feb '07

The following message is a courtesy copy of an article that has been posted to comp.lang.c++.moderated,comp.std.c++,comp.lang.c++ as well. I'm pleased to announce that the official website for the inaugural Boost conference is up and registration is open: http://www.boostcon.com Due to the very high quality of the submissions we've received, our program committee has been able to assemble a lineup of speakers and topics the likes of which I haven't seen anywhere (http://www.boostcon.com/program) Combine that with the relaxed atmosphere of the conference venue (http://www.boostcon.com/location) and I think we can all look forward to a truly unique and memorable week of working and learning together. I invite you to visit http://www.boostcon.com/registration to register. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

[RC_1_34_0].[hp-ux].[acc.jam] Threading set multi ?
by Prashant Thakre 26 Feb '07

26 Feb '07

Hi, The build flags for HP-UX are set to "<threading>multi" and "64-bit" in RC_1_34_0/tools/build/v2/tools/acc.jam i.e. "-mt" and "+DD64". 1.actions acc.link bind NEEDLIBS 2.actions acc.link.dll bind NEEDLIBS 3.actions acc.compile.c 4.actions acc.compile.c++ Has this been done on purpose ? Regards, Prashant Thakre

1 0

[Boost-bugs] [ boost-Bugs-1668728 ] bjam bug in windows?
by SourceForge.net 26 Feb '07

26 Feb '07

Bugs item #1668728, was opened at 2007-02-26 04:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1668728&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: bjam Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: locksmith (locksmith) Assigned to: Rene Rivera (grafik) Summary: bjam bug in windows? Initial Comment: Compiling zlib and bzip2 libraries for use by iostream using the latest bjam build gives the following error: unknown dependent target <@boost!libs!iostreams!build>libboost_bzip2.lib After replacing the following in bzip2.jam 30c30 < if !$(NO_BZIP2) --- > if ! $(NO_BZIP2) and zlib.jam 30c30 < if !$(NO_ZLIB) --- > if ! $(NO_ZLIB) it manages to compile after that. Is it a bug in bjam? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1668728&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Bimap Review
by John Maddock 26 Feb '07

26 Feb '07

Bimap Review ~~~~~~~~~~~~ First off, I'm pleased to see the first of our Google Summer of Code student projects come up for review, and I think Matias should be congratulated for persevering though to this stage. The headline for this review, is that I think the library should be accepted into Boost, it's a very convenient specialisation of Multi-Index that will no doubt find many uses. Documentation and design ~~~~~~~~~~~~~~~~~~~~~~~~ First off I like the docs: they are, as others have noted more colourful than most Boost docs, but I rather like them. In fact I think I prefer the code-boxouts used to the usual Boost style for these :-) The one minute tutorial is pretty straightforward, but I would like to see a slightly longer description of what a Bimap is, off the top of my head: "A bimap is an associative container, that contains two types, with objects of either type usable as a key to find a matching object of the other type. Therefore a bimap has three views: a set of pairs of elements that are related to each other, and two map views that allow either type to be used as a lookup key." Still not perfect by any means, but perhaps something along these lines before your existing code example? Or else cut and paste something from the longer tutorial where I see you do have a nice description. Looking at this again, I think I see the issue about left/right now that other reviewers have raised. The relation type is not a generalisation of std::pair (or even a std::tr1::tuple). Wait a minute, I'm confused actually, the docs say: "The relation class is a generalization of std::pair. The two values are named left and right to express the symmetry of this type." But then the examples that follow access the two members of the relation by "first" and "second", so which is it? Ah, double checking, the relation class uses left and right, but if you dereference a left or right view iterator you get a pair-compatible type with first and second? Is that right? If so folks are going to get really confused, it's got to be either left/right or first/second everywhere I think. So I think I'm beginning to lean towards the first/second names as suggested by others. Other than that the one minute tutorial is very useful I think. Extended tutorial ~~~~~~~~~~~~~~~~~ Everything is very good as far as the section on tagging. When I scanned this section at the end of the SOC period, I didn't really "get" it, and reading in depth now, it's still taken me a while. It's taken me time to try and put my finger on the problem though, I think it's this: tagging isn't what the user wants to do, tagging is just the means to and end. What the user wants to do is access the bimap through meaningful names rather than the generic left/right names. So the title and introduction of the section needs to reflect that, and then everything else will make more sense I think (I hope anyway!). Maybe calling the section "Assigning user defined names to views and types" or something would do it, it's sort of like "named parameters", except they're not parameters, so I'm struggling for good terminology. Anyone have any better suggestions? I have to confess as well, I'm not completely convinced that the tagging mechanism is worth the effort: I can well imagine just writing my own accessor functions so I can write: get_people(my_bimap); rather than: get<people>(my_bimap); But I don't feel strongly enough to argue against providing it. I liked the "Bimap and Boost" section, an excellent idea IMO. The dependencies section has "Clearly Boost.MultiIndex has been abused by this library." I don't think you meant to use the word "abused" here! :-) The reference section I've mostly just skimmed though I'm afraid, but one thing I did notice is that your complexity notation - things like O(M(n)) - really needs to be linked to the explanation of the terms. If you define some quickbook templates for the links and then search and replace for "M" etc it shouldn't take too long to link up. Test Programs ~~~~~~~~~~~~~ I'm happy that Matias has fixed these now, however I did notice some commented out tests: # Enable this to force the mutant_relation test # Warning: it may fail in some standard compliant compilers, because the # mutant idiom uses need that struct { TA f; TB s; }; be layout compatible # with struc { TA s; TB f; }; and this is not in the standard. # However, most modern compiler support it. # #[ run ] #[ run ] # Enable this to force the standard_relation test # It is not always enabled because if the mutant idiom is supported, then it # is not needed and if not, it is tested in test_relation.cpp. # #[ run ] [ run ] ; Should we be concerned about this? I also tried to compile the programs in the examples folder, but got quite a few errors (logfiles attached). Other than that I like the library's design, it's well documented, and it fulfils a genuine need, so providing the compiler-issues can be sorted out, then it should be accepted into Boost. Incidentally, I also noticed that Intel/Win32 compiles took a very long time to complete indeed: many times longer than msvc or gcc. Not sure there's anything can be done about that though unfortunately :-( John Maddock.

2 1