- Boost - lists.boost.org

Boost regression notification (2005-09-14 [HEAD])
by Douglas Gregor 14 Sep '05

14 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-14T05:00:21Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. typeof Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 263 failures in 17 libraries: algorithm/string (1) concept_check (14) date_time (5) filesystem (8) foreach (7) graph (7) iostreams (1) math (6) mpl (2) parameter (18) python (1) regex (36) serialization (40) spirit (2) thread (24) typeof (87) wave (4) |algorithm/string| regex: gcc-3_3-darwin |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 |date_time| testlocal_time_iterator: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc testlocal_time_period: gcc-2.95.3-linux msvc |filesystem| convenience_test: msvc default_name_check_test: msvc fstream_test: msvc large_file_support_test: msvc operations_test: msvc operations_test_dll: msvc path_test: msvc path_test_dll: msvc |foreach| user_defined: cw-8_3 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-6_5-stlport vc-7_0 |graph| biconnected_components_test: gcc-3.4.4-linux gcc-3_4_3-sunos mingw-3_4_2 graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |iostreams| regex_filter_test: gcc-3_3-darwin |math| octonion_test: gcc-4_0-darwin gcc-4_0-darwin quaternion_test: gcc-4_0-darwin gcc-4_0-darwin special_functions_test: gcc-4_0-darwin gcc-4_0-darwin |mpl| size_t: gcc-4_0-darwin gcc-4_0-darwin |parameter| basics: 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 gcc-4_0-darwin msvc macros: 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 msvc unnamed: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| data_members: msvc |regex| bad_expression_test: gcc-3_3-darwin captures_example: gcc-3_3-darwin captures_test: gcc-3_3-darwin collate_info: gcc-3_3-darwin concept_check: gcc-3_3-darwin credit_card_example: gcc-3_3-darwin grep: gcc-3_3-darwin icu_example: gcc-3_3-darwin mfc_example: gcc-3_3-darwin object_cache_test: gcc-3_3-darwin partial_regex_grep: gcc-3_3-darwin partial_regex_match: gcc-3_3-darwin posix_api_check: gcc-3_3-darwin posix_api_check_cpp: gcc-3_3-darwin recursion_test: gcc-3_3-darwin regex_config_info: gcc-3_3-darwin regex_dll_config_info: gcc-3_3-darwin regex_grep_example_1: gcc-3_3-darwin regex_grep_example_2: gcc-3_3-darwin regex_grep_example_3: gcc-3_3-darwin regex_grep_example_4: gcc-3_3-darwin regex_iterator_example: gcc-3_3-darwin regex_match_example: gcc-3_3-darwin regex_merge_example: gcc-3_3-darwin regex_regress: gcc-3_3-darwin regex_regress_dll: gcc-3_3-darwin regex_replace_example: gcc-3_3-darwin regex_search_example: gcc-3_3-darwin regex_split_example_1: gcc-3_3-darwin regex_split_example_2: gcc-3_3-darwin regex_timer: gcc-3_3-darwin regex_token_iterator_eg_1: gcc-3_3-darwin regex_token_iterator_eg_2: gcc-3_3-darwin static_mutex_test: gcc-3_3-darwin msvc wide_posix_api_check_cpp: gcc-3_3-darwin |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier: msvc test_barrier_lib: intel-9.0-linux msvc test_condition: msvc test_condition_lib: intel-9.0-linux msvc test_mutex: msvc test_mutex_lib: intel-9.0-linux msvc test_once: msvc test_once_lib: intel-9.0-linux msvc test_read_write_mutex: msvc test_read_write_mutex_lib: intel-9.0-linux msvc test_thread: msvc test_thread_lib: intel-9.0-linux msvc test_tss: msvc test_tss_lib: intel-9.0-linux msvc test_xtime: msvc test_xtime_lib: intel-9.0-linux msvc |typeof| data_member_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux data_member_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 function_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux function_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 msvc function_ptr_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux function_ptr_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 function_ref_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux function_ref_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 lvalue_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux lvalue_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 msvc member_function_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux member_function_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux modifiers_native: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 template_int_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux template_int_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 template_tpl_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux template_tpl_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 msvc template_type_emulation: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux template_type_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 intel-win32-9_0 type_emulation: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux type_native: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux intel-9.0-linux

1 0

Boost regression notification (2005-09-13 [RC_1_33_0])
by Douglas Gregor 14 Sep '05

14 Sep '05

<html> <head> <meta http-equiv="refresh" content="1; url=issues-email.txt"> </head> <body> <p>Update in progress (building archive index, done in approximately 6 seconds), please wait...</p> </body> </html>

3 2

Re: [boost] Scons users?
by David Gruener 14 Sep '05

14 Sep '05

David Abrahams wrote: > ... chosen Scons over Boost.Build. > It would be useful for us to understand some of the > reasons why, if some of you wouldn't mind letting us know. At the point of the decision against bbs times ago the poor documentation and the unclear state of usability of bbsv2 were reasons against bbs. Using an existing powerfull language as base for a build system is unbeatable concerning expressiveness and extensibility: You can hack and extend SCons in any way with ease to get what you want. A litle bad aftertaste was and is that SCons still performs poorly in real-word projects. 0.02 $

1 0

[program_options] undefined references
by Richard Hadsell 14 Sep '05

14 Sep '05

We are using Boost 1.33.0 with g++ 3.4.4 on an Opteron machine. I compiled .a archive libraries for our users to link to. The compile options we normally build our software with are '-march=opteron -m64 -ansi -mieee-fp -fPIC' along with '-O2' or '-g'. One of our users ran into this problem trying to link his program (I shortened some of our names): ...: In function `bssProgramOptions::parse_config_file(char const*)': x.cc:252: undefined reference to `boost::program_options::basic_parsed_options<char> boost::program_options::parse_config_file<char>(std::basic_istream<char, std::char_traits<char> >&, boost::program_options::options_description const&)' ...(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcEC1ERKSt6vectorISsSaISsEE+0x27): In function `boost::program_options::basic_command_line_parser<char>::basic_command_line_parser(std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)': .../boost/program_options/detail/parsers.hpp:32: undefined reference to `boost::program_options::detail::cmdline::cmdline(std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)' ...(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcE7optionsERKNS0_19options_descriptionE+0x19): In function `boost::program_options::basic_command_line_parser<char>::options(boost::program_options::options_description const&)': .../boost/program_options/detail/parsers.hpp:49: undefined reference to `boost::program_options::detail::cmdline::set_options_description(boost::program_options::options_description const&)' ...(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcE10positionalERKNS0_30positional_options_descriptionE+0x19): In function `boost::program_options::basic_command_line_parser<char>::positional(boost::program_options::positional_options_description const&)': .../boost/program_options/detail/parsers.hpp:59: undefined reference to `boost::program_options::detail::cmdline::set_positional_options(boost::program_options::positional_options_description const&)' ...(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcE5styleEi+0x17): In function `boost::program_options::basic_command_line_parser<char>::style(int)': .../boost/program_options/detail/parsers.hpp:67: undefined reference to `boost::program_options::detail::cmdline::style(int)' ...(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcE3runEv+0x2b): In function `boost::program_options::basic_command_line_parser<char>::run()': .../boost/program_options/detail/parsers.hpp:84: undefined reference to `boost::program_options::detail::cmdline::run()' ...(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcEC1EiPPc+0x4e): In function `boost::program_options::basic_command_line_parser<char>::basic_command_line_parser(int, char**)': .../boost/program_options/detail/parsers.hpp:42: undefined reference to `boost::program_options::detail::cmdline::cmdline(std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)' collect2: ld returned 1 exit status Does anyone recognize these symptoms? -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

1 1

[singleton] call_once
by Jason Hise 14 Sep '05

14 Sep '05

How does call_once work? Does it maintain a separate mutex for each unique function pointer passed in, or is there only one global mutex shared by all calls to call_once? In other words, can call_once(foo, flag) block call_once(bar, flag2)? -Jason

4 11

[thread rewite]
by John Maddock 14 Sep '05

14 Sep '05

Matt, Anthony, You are making any changes to the thread library on a cvs branch right? We aim to keep the cvs HEAD in as close to a release-ready state as we can, so new / experimental code shouldn't be in the HEAD right now. I'm asking because we already have some regressions caused by changes to call_once in the cvs HEAD: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/thread… Thanks, John.

2 3

[thread] explicit constructor in thread
by Matt Hurd 14 Sep '05

14 Sep '05

any particular reason why the function sig accepted is function < void ( void ) > instead of function < void ( void * ) > which you might deduce as more complete for at least these four platforms: thread function signatures ( noted in ACE ) posix = function< void * ( void * ) > win32 = function < DWORD ( void * ) > vxworks without pthreads = function < int (...) > // if such a thing were possible?? pSoS = function < void (void *) > any other examples or thoughts ? matt

2 1

Re: [boost] Interest in an arbitrary precision library?
by Martin Bonner 14 Sep '05

14 Sep '05

----Original Message---- From: Daryle Walker [mailto:darylew@hotmail.com] Sent: 14 September 2005 07:12 To: Boost mailing list Subject: Re: [boost] Interest in an arbitrary precision library? > On 9/13/05 7:28 AM, "Andy Little" <andy(a)servocomm.freeserve.co.uk> > wrote: > >> "Daryle Walker" <darylew(a)hotmail.com> wrote >> >>> OK. When you say "arbitrary precision," you mean that a precision >>> limit must be set (at run-time) before an operation. Most people >>> use "arbitrary precision" to mean unlimited precision, not your >>> "run-time cut-off" precision. >> >> Are there really libraries that have unlimited precision? >> What happens when the result of a computation is irrational? > > You can't store it conventionally, since such numbers would need an > infinite amount of memory. You would just give up and have to define > some sort of rounding/cut-off philosophy. As another poster said, > you could store the irrational components of a number with some sort > of formula (but only for algebraically irrational numbers, not > transcendentally irrational numbers). Why only for algebraiclly irrational numbers? There is no reason (in principle) that the representation of an irrational shouldn't include trig / hyperbolic / bessel functions of irrationals, or even definite integrals. Of course, at this point you get close to rewriting a chunk of Matlab or Mathematica. On the other hand, simplifying (sqrt(5)-sqrt(3))*(sqrt(5)+sqrt(3)) to exactly 2 is quite a challenge too (and if you don't then the unlimited precision representation doesn't really buy you anything). -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

New flag to add to Linux DEBUG mode compilation
by Kevin Wheatley 14 Sep '05

14 Sep '05

1 1

[Review] Reminder xpressive formal review
by Thomas Witt 14 Sep '05

14 Sep '05

Hi, This is to remind everyone of the formal review of Eric Niebler's xpressive library. The review period is scheduled to end Sunday, September 18. I want to especially point out the xpressive is not just another 'regex' library. It goes beyond the scope of regular regex (no pun intended) engines. Here is what Eric has to say: "Although xpressive's primitives are regex-ish in nature, xpressive is far more than just a regular expression engine. It is a pattern matching engine with the power of context-free grammars. By allowing you to embed one pattern in another by reference, xpressive lets you find patterns in data that are recursive in nature. Problems that are intractible with "classic" regular expressions, such as matching balanced nested parentheses or matching XML tags, are simple with xpressive. So xpressive is more rightly thought of as a context-free grammar engine with exhaustive backtracking. The goal is to provide one framework and one set of pattern matching primitives that scales from simple strstr-style grepping, through ordinary regexing, all the way to full-blown parsing." For a glimpse of what xpressive can do look at "Grammars and Nested Matches" here: http://tinyurl.com/d7637 This link takes you to the online docs. The full sources and docs (also in PDF) are available here: http://tinyurl.com/8fean Thomas Review Manager xpressive Thomas Witt witt(a)acm.org

1 0