- Boost - lists.preview.boost.org

Re: [boost] date_time: local_date_time small fix
by Roman Yakovenko 28 Nov '05

28 Nov '05

> > 2. Base class already has those operators, so why do you hide them? > > Unless I'm missing something the base class provides for > comparison to other > local times not ptimes: > > local_date_time l_time1(...), l_time2(...); > if (ltime_1 == ltime_2) {... 1. template<class utc_time_=posix_time::ptime, class tz_type=date_time::time_zone_base<utc_time_> > class local_date_time_base : public date_time::base_time<utc_time_, boost::posix_time::posix_time_system> { 2. template <class T, class time_system> class base_time : private boost::less_than_comparable<T , boost::equality_comparable<T > > { public: typedef T time_type; //!Equality operator -- others generated by boost::equality_comparable bool operator==(const time_type& rhs) const { return time_system::is_equal(time_,rhs.time_); } As you can see date_time::base_time<utc_time_, boost::posix_time::posix_time_system> do provides comparison operator for ptime. > Jeff Roman Yakovenko

1 0

Re: [boost] date_time: local_date_time small fix
by Roman Yakovenko 28 Nov '05

28 Nov '05

> [mailto:boost-bounces@lists.boost.org]On Behalf Of Jeff Garland > > Actually it's intentional to not do an automatic conversion > there. Call > utc_time() to get the ptime. Could you explains the reasons? I see 2 problems with this approach: 1. creation of ptime object on stack, why? 2. Base class already has those operators, so why do you hide them? > Jeff > _______________________________________________ Thanks Roman Yakovenko

2 1

Re: [boost] date_time: second_clock and microsec_clock errors
by Roman Yakovenko 28 Nov '05

28 Nov '05

> [mailto:boost-bounces@lists.boost.org]On Behalf Of Jeff Garland > > [micro]second_clock< boost::local_time::local_date_time_base<> > > > could not be compiled. The problematic function is: private: static > > time_type create_time(::std::tm* current); > > > > The error is that local_date_time_base<> does not have constructors > > that takes date and time duration. > > It's not really a problem. With local_time you need to > provide a timezone > pointer to get a time value. So you call it like this: > //get time in new york time zone: > boost::shared_ptr<time_zone> ny_tz(new > posix_time_zone("EST-05EDT,M4.1.0,M10.5.0")); > > local_date_time ldt3 = local_microsec_clock::local_time(ny_tz); > > > You'll note that there is another overloading in clock > classes for this case: > > template<class time_zone_type> > static time_type local_time(shared_ptr<time_zone_type> tz_ptr); Yes, I discovered work around few days ago. I posted the error here, because I think that this error indicates, that something wrong with design. I think that date_time library should define local_microsec_clock, not in terms of microsec_clock, but using an other class that is aware of time zone. Why is microsec_clock class not aware of time zones? > Jeff Thanks Roman Yakovenko

2 1

date_time: special_value_from_string link error
by Roman Yakovenko 28 Nov '05

28 Nov '05

Hi. Free function special_value_from_string is missing BOOST_DATE_TIME_DECL. This cause link error on windows, vc 7.1, while working with date time library as dll. ( boost version is 1.33.1 beta ) Thanks Roman Yakovenko

2 1

date_time: second_clock and microsec_clock errors
by Roman Yakovenko 28 Nov '05

28 Nov '05

Good morning. I think I found small bug, but I am not sure. ( boost version is 1.33.1 beta ) Description: [micro]second_clock< boost::local_time::local_date_time_base<> > could not be compiled. The problematic function is: private: static time_type create_time(::std::tm* current); The error is that local_date_time_base<> does not have constructors that takes date and time duration. Thanks Roman Yakovenko

2 1

date_time: local_date_time small fix
by Roman Yakovenko 28 Nov '05

28 Nov '05

Good morning. Consider next use case: struct my_ldt : public boost::local_time::local_date_time_base<>{ my_ldt() : boost::local_time::local_date_time_base<>( boost::posix_time::ptime() , boost::shared_ptr< boost::date_time::time_zone_base<boost::posix_time::ptime> >() ) {} }; int _tmain(int argc, _TCHAR* argv[]) { boost::posix_time::ptime t; my_ldt m; m == t; //^^^^^^^^ //this will not compile ( at least on VC 7.1 ) //the error is error C2678: binary '==' : no operator found which takes a left-hand operand of type 'my_ldt' (or there is no acceptable conversion) } fix: Add next code to the local_date_time_base class typedef date_time::base_time<utc_time_, boost::posix_time::posix_time_system> base_type; using base_type::operator==; using base_type::operator<; using base_type::operator-; Thanks Roman Yakovenko

2 1

Boost::factory in new vault?
by Dave Moore 28 Nov '05

28 Nov '05

Is the boost::factory mentioned in this thread available in the new vault anywhere? Is it possible for anyone to upload it? *http://lists.boost.org/boost-users/2005/05/11828.php*<http://lists.boost.org/boost-users/2005/05/11828.php> Thanks, Dave

1 0

Boost.Iostreams - memory leak in zlib filter
by Martin Slater 28 Nov '05

28 Nov '05

Hi there, Just been tracking a memory leak that ended up coming out of the zlib filter. We're using the boost 1.32.0 with the last non integrated verison of iostreams from Jonathans website, I've integrated what appear to be fixes for this leak in the current cvs head but the leak was still there. It seems that line 383 in boost\iostreams\filter\zlib.hpp (cvs head version) should be void zlib_decompressor_impl<Alloc>::close() { reset(false, false); } instead of void zlib_decompressor_impl<Alloc>::close() { reset(false, true); } This makes the leak go away for me, does this seem right? cheers Martin

2 2

[1.33.1][test] missing include problem
by Graham Bennett 28 Nov '05

28 Nov '05

Hi all, When compiling the 1.33.1 beta I noticed that a missing #include is causing a compilation problem: boost/test/impl/plain_report_formatter.ipp is missing a #include <ostream>. I'm using the Roguewave standard library, which often turns this kind of error up as its standard headers don't include quite the same set of files as gcc. It would be great if this could be fixed for the final release of 1.33.1. cheers, Graham -- Graham Bennett

3 2

Boost regression notification (2005-11-27 [RC_1_33_0])
by Douglas Gregor 27 Nov '05

27 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-27T14:15:14Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-27 [HEAD])
by Douglas Gregor 27 Nov '05

27 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-27T06:00:26Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 304 failures in 17 libraries: concept_check (15) foreach (5) graph (3) io (1) math (1) mpl (1) multi_array (7) parameter (12) program_options (56) regex (5) serialization (30) smart_ptr (1) spirit (3) tr1 (104) typeof (21) wave (9) xpressive (30) |concept_check| stl_concept_covering: cw-9_4 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-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 vc-7_1 |foreach| array_byref: intel-win32-8_1 array_byval: intel-win32-8_1 rvalue_const: intel-win32-9_0 stl_byref: intel-win32-8_1 stl_byval: intel-win32-8_1 |graph| graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |multi_array| access: cw-9_4 assign: cw-9_4 assign_to_array: cw-9_4 idxgen1: cw-9_4 index_bases: cw-9_4 iterators: cw-9_4 slice: cw-9_4 |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |program_options| cmdline_test: cw-9_4 intel-win32-8_1 mingw-3_4_2 vc-7_1 vc-7_1 cmdline_test_dll: cw-9_4 vc-7_1 vc-7_1 options_description_test: cw-9_4 intel-win32-8_1 mingw-3_4_2 vc-7_1 vc-7_1 options_description_test_dll: cw-9_4 vc-7_1 vc-7_1 parsers_test: cw-9_4 intel-win32-8_1 mingw-3_4_2 vc-7_1 vc-7_1 parsers_test_dll: cw-9_4 vc-7_1 vc-7_1 positional_options_test: cw-9_4 intel-win32-8_1 mingw-3_4_2 vc-7_1 vc-7_1 positional_options_test_dll: cw-9_4 vc-7_1 vc-7_1 unicode_test: cw-9_4 intel-win32-8_1 vc-7_1 vc-7_1 unicode_test_dll: cw-9_4 vc-7_1 vc-7_1 variable_map_test: cw-9_4 intel-win32-8_1 mingw-3_4_2 vc-7_1 vc-7_1 variable_map_test_dll: cw-9_4 vc-7_1 vc-7_1 winmain: cw-9_4 intel-win32-8_1 mingw-3_4_2 vc-7_1 vc-7_1 winmain_dll: cw-9_4 mingw-3_4_2 vc-7_1 vc-7_1 |regex| grep: cw-9_4 intel-win32-8_1 mingw-3_4_2 vc-7_1 vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |smart_ptr| shared_ptr_alloc2_test: cw-9_4 |spirit| multi_pass_compile_tests: intel-win32-8_1 traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: cw-9_4 gcc-3_4_3-sunos std_run_complex_overloads: cw-9_4 gcc-3_4_3-sunos std_run_random: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_array: cw-9_4 std_test_bind: cw-9_4 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: cw-9_4 std_test_function: cw-9_4 std_test_hash: cw-9_4 std_test_mem_fn: cw-9_4 std_test_random: cw-9_4 std_test_regex: cw-9_4 std_test_result_of: cw-9_4 std_test_tr1_include: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: cw-9_4 test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_bind: cw-9_4 test_complex: cw-9_4 test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function: cw-9_4 test_hash: cw-9_4 test_iterator: gcc-2.95.3-linux test_mem_fn: cw-9_4 test_new: gcc-2.95.3-stlport-4.6.2-linux test_random: cw-9_4 test_reference_wrapper: cw-9_4 test_result_of: cw-9_4 test_shared_ptr: cw-9_4 test_tr1_include: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_add_const_test: cw-9_4 tr1_add_cv_test: cw-9_4 tr1_add_pointer_test: cw-9_4 tr1_add_reference_test: cw-9_4 tr1_add_volatile_test: cw-9_4 tr1_aligned_storage_test: cw-9_4 tr1_alignment_of_test: cw-9_4 tr1_extent_test: cw-9_4 tr1_has_nothrow_assign_test: cw-9_4 tr1_has_nothrow_constr_test: cw-9_4 tr1_has_nothrow_copy_test: cw-9_4 tr1_has_trivial_assign_test: cw-9_4 tr1_has_trivial_constr_test: cw-9_4 tr1_has_trivial_copy_test: cw-9_4 tr1_has_trivial_destructor_test: cw-9_4 tr1_has_virtual_destructor_test: cw-9_4 tr1_is_arithmetic_test: cw-9_4 tr1_is_array_test: cw-9_4 tr1_is_base_of_test: cw-9_4 tr1_is_class_test: cw-9_4 tr1_is_compound_test: cw-9_4 tr1_is_const_test: cw-9_4 tr1_is_convertible_test: cw-9_4 tr1_is_empty_test: cw-9_4 tr1_is_enum_test: cw-9_4 tr1_is_floating_point_test: cw-9_4 tr1_is_function_test: cw-9_4 tr1_is_fundamental_test: cw-9_4 tr1_is_integral_test: cw-9_4 tr1_is_member_func_test: cw-9_4 tr1_is_member_obj_test: cw-9_4 tr1_is_member_pointer_test: cw-9_4 tr1_is_object_test: cw-9_4 tr1_is_pod_test: cw-9_4 tr1_is_pointer_test: cw-9_4 tr1_is_polymorphic_test: cw-9_4 tr1_is_reference_test: cw-9_4 tr1_is_same_test: cw-9_4 tr1_is_scalar_test: cw-9_4 tr1_is_signed_test: cw-9_4 tr1_is_union_test: cw-9_4 tr1_is_unsigned_test: cw-9_4 tr1_is_void_test: cw-9_4 tr1_is_volatile_test: cw-9_4 tr1_rank_test: cw-9_4 tr1_remove_all_extents_test: cw-9_4 tr1_remove_const_test: cw-9_4 tr1_remove_cv_test: cw-9_4 tr1_remove_extent_test: cw-9_4 tr1_remove_pointer_test: cw-9_4 tr1_remove_reference_test: cw-9_4 tr1_remove_volatile_test: cw-9_4 tr1_tricky_abstract_type_test: cw-9_4 tr1_tricky_add_pointer_test: cw-9_4 tr1_tricky_function_type_test: cw-9_4 tr1_tricky_incomplete_type_test: cw-9_4 tr1_tricky_is_enum_test: cw-9_4 tr1_tricky_partial_spec_test: cw-9_4 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 cw-9_4 modifiers_native: cw-9_4 cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave: cw-9_4 intel-win32-8_1 mingw-3_4_2 vc-7_1 vc-7_1 testwave_dll: cw-9_4 intel-win32-8_1 vc-7_1 vc-7_1 |xpressive| misc1: cw-9_4 test1: cw-9_4 test1u: cw-9_4 test2: cw-9_4 test2u: cw-9_4 test3: cw-9_4 test3u: cw-9_4 test4: cw-9_4 test4u: cw-9_4 test5: cw-9_4 test5u: cw-9_4 test6: cw-9_4 test6u: cw-9_4 test7: cw-9_4 test7u: cw-9_4 test8: cw-9_4 test8u: cw-9_4 test9: cw-9_4 test9u: cw-9_4 test_basic_regex: cw-9_4 test_cycles: cw-9_4 test_dynamic: cw-9_4 test_match_results: cw-9_4 test_non_char: cw-9_4 test_regex_algorithms: cw-9_4 test_regex_compiler: cw-9_4 test_regex_iterator: cw-9_4 test_regex_primitives: cw-9_4 test_regex_token_iterator: cw-9_4 test_static: cw-9_4

1 0

Full MS compiler version info?
by Paul A Bristow 27 Nov '05

27 Nov '05

Installation of the final 8.0 (after beta 1 and 2) has caused me some confusion because the output build logs don't contain the full compiler version. For example using a post build event with the test suite, as recommended (- strongly see PS below) --build_info=yes includes this info: Platform: Win32 Compiler: Microsoft Visual C++ version 8.0 STL : Dinkumware standard library version 405 Boost : 1.33.0 The macro _MSC_FULL_VER is 140050215 looks like version 1400 build 50215 Would it be useful to decode in boost/config/compiler/visual.hpp this into version 8.0 and build 50215? (Or?) A new macro BOOST_COMPILER_BUILD ? So that various releases can be distingushed? Paul PS The post CMD.EXE was started with '\\hetp3\i$\boost_1_33_0\libs\test\build\msvc71_proj' as the current directory path. UNC paths are not supported. Defaulting to Windows directory. Running 5 test cases... Which misses showing the full log report that IS shown with an autorun (which is any case much more convenient and recommended by Gennadiy at /boost_1_33_0/libs/test/doc/usage/msvc_net.html etc I found a MS article http://support.microsoft.com/?kbid=156276 about the message '<UNC path>' is an invalid current directory path. UNC paths are not supported. Defaulting to Windows directory. The article does not seem accurate and I have queried it with MS. I have also previously seen with the logging library (proposed). -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow(a)hetp.u-net.com www.hetp.u-net.com

4 8

Boost regression notification (2005-11-26 [RC_1_33_0])
by Douglas Gregor 26 Nov '05

26 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-26T14:00:21Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-26 [HEAD])
by Douglas Gregor 26 Nov '05

26 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-26T06:00:24Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 168 failures in 14 libraries: concept_check (12) foreach (1) graph (3) io (1) math (1) mpl (1) parameter (12) program_options (35) regex (3) serialization (30) spirit (2) tr1 (45) typeof (18) wave (4) |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 vc-7_1 vc-7_1 |foreach| rvalue_const: intel-win32-9_0 |graph| graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |program_options| cmdline_test: mingw-3_4_2 vc-7_1 vc-7_1 cmdline_test_dll: vc-7_1 vc-7_1 options_description_test: mingw-3_4_2 vc-7_1 vc-7_1 options_description_test_dll: vc-7_1 vc-7_1 parsers_test: mingw-3_4_2 vc-7_1 vc-7_1 parsers_test_dll: vc-7_1 vc-7_1 positional_options_test: mingw-3_4_2 vc-7_1 vc-7_1 positional_options_test_dll: vc-7_1 vc-7_1 unicode_test: vc-7_1 vc-7_1 unicode_test_dll: vc-7_1 vc-7_1 variable_map_test: mingw-3_4_2 vc-7_1 vc-7_1 variable_map_test_dll: vc-7_1 vc-7_1 winmain: mingw-3_4_2 vc-7_1 vc-7_1 winmain_dll: mingw-3_4_2 vc-7_1 vc-7_1 |regex| grep: mingw-3_4_2 vc-7_1 vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave: vc-7_1 vc-7_1 testwave_dll: vc-7_1 vc-7_1

1 0

Re: [boost] [serialization] fast array serialization (10x speedup)
by Robert Ramey 26 Nov '05

26 Nov '05

I've been perusing the files you checked, your example, and this list. Summary ======= First of all, a little more complete narrative description as to what the submission was intended to acommplish and how it would change the way the user uses the library would have been helpful. I'm going to summarize here what I think I understand about this. Please correct me if I get something wrong. a) a new trait is created. template <class Archive, class Type> struct has_fast_array_serialization : public mpl::bool_<false> {}; b) new functions save_array and load_array are implemented in those archives which have the above trait set to true. In this case the following is added to the binary_iarchive.hpp file. The effect is that this trait will return true when a fundamental type is to be saved/loaded to a binary_iarchive. // specialize has_fast_array_serialization // the binary archive provides fast array serialization for all fundamental types template <class Type> struct has_fast_array_serialization<binary_iarchive,Type> : public is_fundamental<Type> {}; c) A user with the following class my_class { valarray<int> m_a; template<class Archive> void save(Archive & ar, const unsigned int){ ar << m_a } ... }; d) In order for this to work, data types which want to exploit bitwise serialization have to look like the following - taken from valarray - serialization. This would have to be applied to serialization template<class Archive, class U> inline boost::disable_if<boost::archive::has_fast_array_serialization<Archive,U> >::type save( Archive & ar, const STD::valarray<U> &t, const unsigned int /* file_version */) { const boost::archive::container_size_type count(t.size()); ar << BOOST_SERIALIZATION_NVP(count); for (std::size_t i=0; i<t.size();+i) ar << t[i]; } // with fast array serialization template<class Archive, class U> inline boost::enable_if<boost::archive::has_fast_array_serialization<Archive,U> >::type save( Archive & ar, const STD::valarray<U> &t, const unsigned int /* file_version */) { const boost::archive::container_size_type count(t.size()); ar << BOOST_SERIALIZATION_NVP(count); if (count) ar.save_array(boost::detail::get_data(t),t.size()); } Presumably this treatment would be applied to: std::vector ublas::vector ublas::matrix mtl::vector blitz::array custom_lib::fast_matrix ... as well as others. For built-in arrays, the core library is tweaked to include code similar to the above for built-in arrays. Some Observations ================= Inmediatly the following come to mind. a) I'm not sure about the portability of enable_if. Would this not break the whole serialization system for those compilers which don't support it? b) what is the the point of save_array? why not just invoke save_binary directly? c) The same could be said for built arrays - just invoke save_binary d) There is no provision for NVP in the non-binary version above while in the binary version there is NVP around count. Presumably, these are oversights. e) The whole thing isn't obvious and its hard to follow. It couples the implementation code in i/o serializer.hpp to a specific kind of archive adding another dimension to be considered while understanding this thing. f) What about bitwise serializble types which aren't fundamental? That is structures which don't have things like pointers in them. They have the same opportunity but aren't addressed. If this is a good idea for fundamental types, someone is going to want to do them as well - which would open up some new problems. g) I don't see endian-ness addressed anywhere. I believe that protocols such as XDR and MPI are designed to transmit binary data between heterogenious machines. Suppose I save an array of ints as a sequence of raw bits on an intel type machine. Then I use load_binary to reload the same seqence of bits into sparc based machine. I won't get back the same data values. So either either the method will have to be limited to collections of bytes or some extra machinery would have to be added to conditionally to the endian translation depending on the source/target machine match/mismatch. f) Similar issues confront bitwise serialization of floats and doubles. I believe the "canonical" format for floats/doubles is ieee 80 bit. (I think that's what XDR uses - I could be wrong.) I believe that many machines store floats as 32 bit word and doubles as 64 bit words. I doubt they all are guarenteed to have the same format as far as exponent, sign and representation of value. So that's something else to be addressed. Of course endian-ness plays into this as well. g) I looked at the "benchmark" results. I notice that they are run with -O2 on the gcc compiler. Documentation for the gcc compiler command line specifies that this optimization level should does not enable automatic inlining for small functions. This is a crucial optimization to be effective in the serialization library. The library is written with the view that compilers will collapse inline code when possible. But this happens only in the gcc compiler when the -O3 optimization switch is used. Furthermore, with this compiler, it might be necessary to also specify max-inline-insns-recursive-auto switch. to gain maximum performance on boost type code. This latter is still under investigation. h) my own rudimentary benchmark (which was posted on this list) used 1000 instances of a structure which contained all C++ primitive data types plus an std::string made up of random characters. It was compiled as a boost test and built with bjam so it used the standard boost options for release mode. It compared timings against using raw stream i/o. Timings for binary_archive and standard stream i/o where comparable. I'm still working on this test. The problem is that standard stream i/o uses text output/input. Of course no one for whom performance is an issue would do this so I have to alter my timing test to use binary i/o to the standard stream as a comparison. But for now, I'm comfortable in asserting that there is not a large performance penalty using serialization as opposed to "rolling your own". As an aside, the test executable doing the same test for 3 different types of archives and all primitive data types only came to 238K. So there isn't a significant code bloat issue either. i) somehow I doubt that this archive type has been tested with all the serialization test suite. Instructions for doing so are in the documenation and the serialization/test directory includes batch files for doing this with one's own archives. Was this done? What where the results? With which compiler? It costs nothing to do this. end of observations =================== Admitedly, this is only a cursory examination. But its more than enough to make me skeptical of the whole idea. I you want, I could expand upon my reasons for this view, but I think they should be obvious. Now if someone feels differently and wants to implement such a thing, they have my full support. There is no need to modify the core library and no benefit - performance or otherwise. The following shows how to go about this. For purposes of this exposition, I am going to limit myself to how one would go about crafting a system similar to the one submitted. That is, I will not address concerns such as binary portability as the are not addressed in the submission as I see it. I'm assuming that the only issue is how best to arrange things so that save_binary/load_binary are invoked in for contiguous collections of fundamental types. Suggestions =========== I do see the utility and merit in what you're trying to do here - finally. Honestly it just wasn't obvious from the initial package. So here is how I would have gone about it. I previously posted a demo "fast_oarchive.hpp" I will expand upon it here. the archive class tree would look like the following (setting aside polymorphic archives). I would envision the following class basic_archive basic_oarchive common_oarchive basic_binary_oarchive binary_oarchive fast_oarchive_impl MPI_oarchive XDR_oarchive ... fast_oarchive_impl is an adaptor which can be applied to any legal archive. The current submission derives from binary_?archive. If this is all that is required then it doesn't have to be a template, it could just as well be derived directly from binary_oarchive. It includes overloads for the following: template<class T> void save_array(T & t, collection_size_t count){ // this version not certified for more complex types !!! BOOST_STATIC_ASSERT(boost::is_primitive<T>::value); // or pointers either !!! BOOST_STATIC_ASSERT(boost::is_pointer<T>::value); ... // if T is NOT a fundamental type - some mpl magic required here // foward call to base class this->Base::save_override(t, 0); // else - *(this->This()) << make_nvp("count", t.size() * sizeof(T)); *(this->This()) << make_nvp(make_binary_object(t.size() * sizeof(T), & t)); // note - the nvp wrappers probably not necessary of we're only // only going to apply this to binary archives. } // here's a way to do it for all vectors in one shot template<class T> void save_override(const std::vector<T> & t, int){ save_array(t, t.size()); } ... boost::valarray? ... // for C++ built-in arrays template<typename T, int N> void save_override(const T (& t)[N] , int){ save_array(t, sizeof(t)); } It might or might not contain similar implementations for std::vector ublas::vector ublas::matrix mtl::vector blitz::array custom_lib::fast_matrix etc For now assume that it does - later we'll relax that assumption. derived from fast_oarchive_impl are your archive classes for specific archive types - MPI_oarchive, .... These would handle the specific features of each particular archive. If it turns out that MPI can only apply the save_binary optimization to types that are no more than a character wide (perhaps for endien issues) then it would include something like: template<class T> void save_override(const std::vector<T> & t, int){ // suppose endian issues preclude save_binary preclude if(sizeof(T) > 1){ // skip over save_binary optimization this->binary_oarchive::save_override(t, 0) } else // just forward to the base class this->fast_oarchive_impl::save_override(t, 0) } So net result is: a) save_binary optimizations are invoked from the fast_oarchive_impl class. They only have to be specified once even though they are used in more than one variation of the binary archive. That is, if there are N types to be subjected to the treatment by M archives - there are only N overrides - regardless of the size of M. b) save_binary optimizations can be overriden for any particular archive types. (It's not clear to me how the current submission would address such a situation). c) There is no need alter the current library. d) It doesn't require that anything in the current library be conditioned on what kind of archive is being used. Insertion of such a coupling would be extremely unfortunate and create a lot of future maintainence work. This would be extremely unfortunate for such a special purpose library. This is especially true since its absolutly unnecessary. e) The implemenation above, could easily be improved to be resolved totally at compile time. Built with a high quality compiler (with the appropriate optimization switches set), this would result in fastest possible code. f) all code for save_binary is in one place - within fast_oarchive_impl. If fast_oarchive_impl is implemented as a template, it could be applied to any existing archive class - even text and xml. I don't know if there would be any interest in doing that - but it's not inconcievable. Note also that including all the save_binary optimizations in for all of std::vector ublas::vector ublas::matrix mtl::vector blitz::array custom_lib::fast_matrix doesn't require that the headers for these libraries be included. The code in the header isn't required until the template is instantiated. So there wouldn't be any "header bloat"(tm) g) Now, f above could also be seen as a disadvantage. That is, it might seem better to let each one involved in serialization of a particular collection keep his stuff separate. There are a couple of options here I will sketch out. i) one could make a new trait is_bitwise_serializable whose default value is false. For each collection type one would specialize this like: template<class T> struct is_bitwise_serializable<vector <T> > { ... is_fundamental<T> ... get_size(){ // override default options which is sizeof(T) .. } Now fast_oarchive_impl would contain something like: // here's a way to do it for all vectors in one shot template<class T> void save_override(const T & t, int){ // if T is NOT bitwise serializable - insert mpl magic required here // foward call to base class this->Base::save_override(t, 0); // else - *(this->This()) << make_nvp("count", t.size() * sizeof(T)); *(this->This()) << make_nvp(make_binary_object(...get_size(), & t)); // note - the nvp wrappers probably not necessary of we're only // only going to apply this to binary archives. } Which would implement the save_binary optimization for all types with the the is_bitwise_serializable trait set. Of course any class derived from fast_oarchive_impl could override this as before. Note that this would address the situation whereby one has something like struct RGB { unsigned char red; unsigned char green; unsigned char blue; }; which certainly would be candidate for save_binary optimization - it would even be portable across machines of incompatible machines - but then there might be alignment issues. Also, if someone tracks an object of type RGB somewhere, then this would work differently on different archives - not a good thing. So this would require some careful documentation on how to use such a trait. This would move the information about save_binary optimization out of the fast_oarchive_impl.hpp header file and into the header file for each particular type - arguable a better choice. ii) another option would be to implement differing serializations depending upon the archive type. So that we might have template<class T> void save(fast_oarchive_impl &ar, const std::vector<T> & t, const unsigned int){ // if T is a fundamental type or .... ar << t.size(); ar.save_binary(t.size() * sizeof(T), t.data?()); } This would basically much simpler substitute for the "fast_archive_trait" proposed by the submission. Wrap up ======= I guess it should be pretty obvious that I believe that a) The applicability and utility of a save/load binary optimization are narrow than claimed. b) The claims of performance improvement are suspect. c) This implementation doesn't address all the issues that need to be addressed for something like this. d) Such an idea could be implemented in a much simpler, more transparent, robust, and efficient manner. e) Such "special" implementation features are easily accommodated by the current library by extension. There is no need to change any of the core library implementation or interface. Finally, I have to comment on the way this has been proposed. Checking a diverse group into the CVS system on a separate branch is not convenient for most people. This would better be a zip file uploaded to the vault. It should also include some sort of document outlining what its intended to do and how it does it. Had this been done, its likely that many more people would have had a look at it and been able to commment. I'm sure the issues i've noted above would be apparent to a lot of people and I wouldn't have had to spend a few hours preparing this critique. If the above weren't bad enough, I'm pretty much been forced to do what really amounts to doing a private consulting job for free for a specific application. I really can't do this anymore. Its one think to point a user in the right direction (which often results in tweak to the manual) or incorporate a bug fix - which some user has tracked down, fixed and submitted. But to have to spend the time to critique something like this - whose problems should be obvious to most of us. is really unfair. I've been through it a couple of times - I'm not doing it again. If you feel that you need to split off the serialization library to do what you want, I've a better idea: How about you and Matthias taking it over yourself? After all, I've achieved all I expect to get from it. Then you would be free to make any changes you want without wasting time on these discussions. Of course if the problems in the above are only obvious to me, then it probably would indicate that I'm out of sync with the boost development community - in which case it really should be taken over by someone else. Robert Ramey

15 114

[Boost-bugs] [ boost-Feature Requests-1366658 ] Support for DevC++
by SourceForge.net 26 Nov '05

26 Nov '05

Feature Requests item #1366658, was opened at 2005-11-25 15:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1366658&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Support for DevC++ Initial Comment: I currently use the wxWidgets enhanced DevC++ here: http://wxdsgn.sourceforge.net/ I'd like to see how a *Boost*ed DevC++ would compare, though I don't see it listed in the supported compilers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1366658&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

2 1

[Boost-bugs] [ boost-Bugs-1365753 ] header problem in boost::test
by SourceForge.net 26 Nov '05

26 Nov '05

Bugs item #1365753, was opened at 2005-11-24 10:39 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=1365753&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: test Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Beman Dawes (beman_dawes) Summary: header problem in boost::test Initial Comment: The macro "BOOST_PARAM_TEST_CASE" of the boost::test library is not included with the header "unit_test_suite.hpp " as statet in the documentation. To use this macro the header "parameterized_test.hpp" has to be included. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1365753&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

2 1

Bug list status
by Marshall Clow 25 Nov '05

25 Nov '05

Six weeks ago: 144 open bugs Five weeks ago: 117 open bugs Four weeks ago: 96 open bugs Three weeks ago: 94 open bugs Two weeks ago: 93 open bugs Last week: 95 open bugs. Today: 77 open bugs. Thanks for fixing bugs, everyone! If you think that a bug has been assigned incorrectly, please let me know. Here are the currently opened bugs, sorted by assignee. Beman Dawes 15 Mike Glassford 12 Doug Gregor 9 Stephen Cleary (shammah) 6 Jonathan Turkanis 4 Joerg Walter 4 Jeff Garland (az_sw_dude) 3 Joel de guzman (djowel) 3 John R. Bandela 2 Eric Friedman (ebf) 2 Jeremy Siek 2 Thorsten Ottosen (nesotto) 2 Vladimir Prus 2 Robert Ramey 2 Gennadiy Rozental (rogeeff) 2 <nobody> 1 Kevlin Henney 1 Hubert Holin 1 Samuel Kremp 1 Jens Maurer 1 John Maddock 1 Rene Rivera (grafik) 1 Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: wrong usage of ios_base::narrow Bug #: 989487 <http://sourceforge.net/tracker/index.php?func=detail&aid=989487&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: date_time type conversion warning Bug #: 1069225 <http://sourceforge.net/tracker/index.php?func=detail&aid=1069225&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: local_adjustor::utc_to_local throws 'Time label invalid' Bug #: 1220011 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220011&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesytem::directory_iterator portability Bug #: 735403 <http://sourceforge.net/tracker/index.php?func=detail&aid=735403&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem fails in posix with files containing ':' Bug #: 776146 <http://sourceforge.net/tracker/index.php?func=detail&aid=776146&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: clock is not portable Bug #: 788762 <http://sourceforge.net/tracker/index.php?func=detail&aid=788762&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Boost::Filesystem fails when last character in path is ':' Bug #: 875970 <http://sourceforge.net/tracker/index.php?func=detail&aid=875970&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesystem::directory_iterator returns incorrect listing Bug #: 937606 <http://sourceforge.net/tracker/index.php?func=detail&aid=937606&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: xtime_cmp: use comparison not subtraction Bug #: 993272 <http://sourceforge.net/tracker/index.php?func=detail&aid=993272&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists is broken on cygwin Bug #: 1010681 <http://sourceforge.net/tracker/index.php?func=detail&aid=1010681&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem is systematically broken Bug #: 1012135 <http://sourceforge.net/tracker/index.php?func=detail&aid=1012135&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::native() should reject '/' on non-Win32 Bug #: 1151823 <http://sourceforge.net/tracker/index.php?func=detail&aid=1151823&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists has bugs with UNC paths Bug #: 1164057 <http://sourceforge.net/tracker/index.php?func=detail&aid=1164057&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::equivalent does not work on w98 Bug #: 1235262 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235262&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: path and directory_iterator doesn't handle windows root path Bug #: 1259176 <http://sourceforge.net/tracker/index.php?func=detail&aid=1259176&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: is_empty sets my paths' _M_p to 0xffffffff Bug #: 1361625 <http://sourceforge.net/tracker/index.php?func=detail&aid=1361625&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Documentation error for the filesystem_error class Bug #: 1363831 <http://sourceforge.net/tracker/index.php?func=detail&aid=1363831&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: header problem in boost::test Bug #: 1365753 <http://sourceforge.net/tracker/index.php?func=detail&aid=1365753&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = setS for adjacency_list does not work Bug #: 1163077 <http://sourceforge.net/tracker/index.php?func=detail&aid=1163077&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors do not handle hidden nodes properly Bug #: 1168431 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168431&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: function.hpp breaks assign.hpp Bug #: 1181272 <http://sourceforge.net/tracker/index.php?func=detail&aid=1181272&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: random_vertex/random_edge are unnecessarily inefficient Bug #: 1204684 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204684&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Document copy_component Bug #: 1204688 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204688&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: reverse_graph and constness of property maps Bug #: 1246336 <http://sourceforge.net/tracker/index.php?func=detail&aid=1246336&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: html docs frequently missing key words Bug #: 1294420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1294420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = has_setS for adjacency_list does not work Bug #: 1352049 <http://sourceforge.net/tracker/index.php?func=detail&aid=1352049&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: predicates without default constructor fail to compile (2) Bug #: 1353875 <http://sourceforge.net/tracker/index.php?func=detail&aid=1353875&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Miss ' = ParserT()' Bug #: 907299 <http://sourceforge.net/tracker/index.php?func=detail&aid=907299&group_id=75…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: spirit insert_key_actor.hpp Bug #: 1059936 <http://sourceforge.net/tracker/index.php?func=detail&aid=1059936&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Another config correction for Sun C++ Bug #: 1220782 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220782&group_id=7…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: boost::blank - missing operators Bug #: 1191356 <http://sourceforge.net/tracker/index.php?func=detail&aid=1191356&group_id=7…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: [variant] Bug in recursive_wrapper_fwd.hpp Bug #: 1359257 <http://sourceforge.net/tracker/index.php?func=detail&aid=1359257&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl to_duration() nsec error Bug #: 548104 <http://sourceforge.net/tracker/index.php?func=detail&aid=548104&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Solaris - once.cpp compile error Bug #: 549162 <http://sourceforge.net/tracker/index.php?func=detail&aid=549162&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: AIX 4.3 SIGSEGV at thread termination Bug #: 551577 <http://sourceforge.net/tracker/index.php?func=detail&aid=551577&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: boost::threads uses msvc only function? Bug #: 568951 <http://sourceforge.net/tracker/index.php?func=detail&aid=568951&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: BCB6 throw EExternelException Bug #: 596149 <http://sourceforge.net/tracker/index.php?func=detail&aid=596149&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: thread_cleanup problems Bug #: 649291 <http://sourceforge.net/tracker/index.php?func=detail&aid=649291&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Mac implementation of threads is CPU hog Bug #: 885045 <http://sourceforge.net/tracker/index.php?func=detail&aid=885045&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: condition variables and recursive_mutex Bug #: 1072605 <http://sourceforge.net/tracker/index.php?func=detail&aid=1072605&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: compiler error on Mac implementation of threads Bug #: 1201779 <http://sourceforge.net/tracker/index.php?func=detail&aid=1201779&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl line 116 copy/paste error Bug #: 1239052 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239052&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Exception safety in class 'thread' Bug #: 1305885 <http://sourceforge.net/tracker/index.php?func=detail&aid=1305885&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: mistake in documentation of condition Bug #: 1364416 <http://sourceforge.net/tracker/index.php?func=detail&aid=1364416&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: boost jam problem with parallel builds Bug #: 1234224 <http://sourceforge.net/tracker/index.php?func=detail&aid=1234224&group_id=7…> Assignee: hubert_holin <http://sourceforge.net/users/hubert_holin/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751289 <http://sourceforge.net/tracker/index.php?func=detail&aid=751289&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Compiler error for tokenizer on Solaris Bug #: 976241 <http://sourceforge.net/tracker/index.php?func=detail&aid=976241&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: token_iterator::at_end() result is inversed Bug #: 1338326 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338326&group_id=7…> Assignee: jmaurer <http://sourceforge.net/users/jmaurer/> Summary: Diff in state of mersenne_twister gen between GCC3.41 & CW9 Bug #: 1115124 <http://sourceforge.net/tracker/index.php?func=detail&aid=1115124&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: bug in ublas/storage.hpp Bug #: 1095697 <http://sourceforge.net/tracker/index.php?func=detail&aid=1095697&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: dead links in uBLAS page Bug #: 1169273 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169273&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: Documentation not available on web site: Bug #: 1228242 <http://sourceforge.net/tracker/index.php?func=detail&aid=1228242&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: uBLAS::subslice doesn't work Bug #: 1292635 <http://sourceforge.net/tracker/index.php?func=detail&aid=1292635&group_id=7…> Assignee: johnmaddock <http://sourceforge.net/users/johnmaddock/> Summary: Adding boost::is_complex to type_traits.hpp Bug #: 1315712 <http://sourceforge.net/tracker/index.php?func=detail&aid=1315712&group_id=7…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: invalid result for File Dependency Examp Bug #: 551110 <http://sourceforge.net/tracker/index.php?func=detail&aid=551110&group_id=75…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: Spelling of Edmonds-Karp-Algorithm Bug #: 1226292 <http://sourceforge.net/tracker/index.php?func=detail&aid=1226292&group_id=7…> Assignee: kevlin <http://sourceforge.net/users/kevlin/> Summary: lexical_cast & pure virtual functions & VC 8 STL Bug #: 1358600 <http://sourceforge.net/tracker/index.php?func=detail&aid=1358600&group_id=7…> Assignee: nesotto <http://sourceforge.net/users/nesotto/> Summary: boost.range and 'const char[]'. Bug #: 1272315 <http://sourceforge.net/tracker/index.php?func=detail&aid=1272315&group_id=7…> Assignee: nesotto <http://sourceforge.net/users/nesotto/> Summary: [Boost.Range]boost::const_begin calls non-qualified 'begin' Bug #: 1361686 <http://sourceforge.net/tracker/index.php?func=detail&aid=1361686&group_id=7…> Assignee: nobody Summary: failure in boost jam unit tests on cygwin Bug #: 940941 <http://sourceforge.net/tracker/index.php?func=detail&aid=940941&group_id=75…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: Compiler warning with gcc on Linux Bug #: 1337412 <http://sourceforge.net/tracker/index.php?func=detail&aid=1337412&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: warning caused by size_t to unsigned int conversion on vc++8 Bug #: 1338178 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338178&group_id=7…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: typo in Boost.Test document Bug #: 629685 <http://sourceforge.net/tracker/index.php?func=detail&aid=629685&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: Don't work multilevel hierarchy of test suites in dll. Bug #: 1076691 <http://sourceforge.net/tracker/index.php?func=detail&aid=1076691&group_id=7…> Assignee: samuel_k <http://sourceforge.net/users/samuel_k/> Summary: format: assert when parsing invalid pattern Bug #: 1326132 <http://sourceforge.net/tracker/index.php?func=detail&aid=1326132&group_id=7…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: ct_gcd_lcm.hpp compilation error Bug #: 558174 <http://sourceforge.net/tracker/index.php?func=detail&aid=558174&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: test_pool_alloc.cpp not compile CW8.1 Bug #: 586779 <http://sourceforge.net/tracker/index.php?func=detail&aid=586779&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: pool::purge_memory() does not reset next_size Bug #: 984124 <http://sourceforge.net/tracker/index.php?func=detail&aid=984124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: Borland compiler error with Pool, boost::pool_allocator Bug #: 988124 <http://sourceforge.net/tracker/index.php?func=detail&aid=988124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: perfomance: memory cleanup for pool takes too long Bug #: 995270 <http://sourceforge.net/tracker/index.php?func=detail&aid=995270&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: boost::pool_allocator breaks with vector of vectors Bug #: 1179641 <http://sourceforge.net/tracker/index.php?func=detail&aid=1179641&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: rational operator&lt; can overflow Bug #: 798357 <http://sourceforge.net/tracker/index.php?func=detail&aid=798357&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: boost::rational documentation typos(?) Bug #: 1043616 <http://sourceforge.net/tracker/index.php?func=detail&aid=1043616&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: no Boolean conversion for boost::rational Bug #: 1239906 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239906&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: problem with boost::iostreams when compiled with Visual C++ Bug #: 1365752 <http://sourceforge.net/tracker/index.php?func=detail&aid=1365752&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: multitoken broken in program_options 1.33 Bug #: 1266877 <http://sourceforge.net/tracker/index.php?func=detail&aid=1266877&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: format_paragraph in options_description.cpp Bug #: 1365338 <http://sourceforge.net/tracker/index.php?func=detail&aid=1365338&group_id=7…> -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Fusion question- equality of tuples vs mpl sequences
by Brian Braatz 25 Nov '05

25 Nov '05

/// Testing remove { typedef vector<Y, char, long, X, bool, double> mpl_vec; BOOST_TEST((fusion::remove(mpl_vec(), identity<X>()) == tuple<Y, char, long, bool, double>())); BOOST_TEST((fusion::remove(mpl_vec(), identity<Y>()) == tuple<char, long, X, bool, double>())); BOOST_TEST((fusion::remove(mpl_vec(), identity<long>()) == tuple<Y, char, X, bool, double>())); } My question is how does the above WORK? What caught my attention is the char,long,bool, and double have undefined values in them. Is it that when performing a ==, if one is comparing a mpl sequence the equality is based solely on TYPE? (is that what is going on?) Thanks, Brian :)

2 1

ENC: build boost with other standard Lib (std)
by Renato Tegon Forti 25 Nov '05

25 Nov '05

Hi John, Thank you (very very very... much) for your help. I have one doubt; I need define one Preprocessor directive to compile with RogueWave STD, and specify lib directory to link with RW libs, then I did try: bjam "-sBUILD=debug <cxxflags>-IC:\RogueWave\SourcePro\Ed8\include <cxxflags>-IC:\RogueWave\SourcePro\Ed8\include\ansi <cxxflags>-IC:\RogueWave\SourcePro\Ed8\lib <cxxflags>-D_RWCONFIG=rmd <runtime-link>dynamic <threading>multi" "-sTOOLS=vc-7_1" but this don't work. Where I should put lib dir(C:\RogueWave\SourcePro\Ed8\) Can you help-me? Sample of error returned: I think that this error is because it don't find RW libs. greg_month.obj : error LNK2019: unresolved external symbol "__declspec(dllimport ) void __cdecl __rw::__rw_deallocate(void *,unsigned int,int)" (__imp_?__rw_deal locate@__rw@@YAXPAXIH@Z) referenced in function "public: void __thiscall std::al locator<struct __rw::__rb_tree<class std::basic_string<char,struct std::char_tra its<char>,class std::allocator<char> >,struct std::pair<class std::basic_string< char,struct std::char_traits<char>,class std::allocator<char> > const ,unsigned short>,struct __rw::__select1st<struct std::pair<class std::basic_string<char,st ruct std::char_traits<char>,class std::allocator<char> > const ,unsigned short>, class std::basic_string<char,struct std::char_traits<char>,class std::allocator< char> > >,struct std::less<class std::basic_string<char,struct std::char_traits< char>,class std::allocator<char> > >,class std::allocator<struct std::pair<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const ,unsigned short> > >::_C_node_buf>::deallocate(struct __rw::__rb_tree<c lass std::basic_string<char,struct std::char_traits<char>,class std::allocator<c har> >,struct std::pair<class std::basic_string<char,struct std::char_traits<cha r>,class std::allocator<char> > const ,unsigned short>,struct __rw::__select1st< struct std::pair<class std::basic_string<char,struct std::char_traits<char>,clas s std::allocator<char> > const ,unsigned short>,class std::basic_string<char,str uct std::char_traits<char>,class std::allocator<char> > >,struct std::less<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > >,class std::allocator<struct std::pair<class std::basic_string<char,struct s td::char_traits<char>,class std::allocator<char> > const ,unsigned short> > >::_ C_node_buf *,unsigned int)" (?deallocate@?$allocator@U_C_node_buf@?$__rb_tree@V? $basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@U?$pair@$$CBV?$b asic _string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@G@2@U?$__select1st@U?$ pair @$$CBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@G@std@@V? $bas ic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@2@@__rw@@U?$less@V?$basic _str ing@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@V?$allocator@U?$pair@$$ CBV? $basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@G@std@@@2@@__rw@ @@st d@@QAEXPAU_C_node_buf@?$__rb_tree@V?$basic_string@DU?$char_traits@D@std@@V?$ allo cator@D@2@@std@@U?$pair@$$CBV?$basic_string@DU?$char_traits@D@std@@V?$alloca tor@ D@2@@std@@G@2@U?$__select1st@U?$pair@$$CBV?$basic_string@DU?$char_traits@D@s td@@ V?$allocator@D@2@@std@@G@std@@V?$basic_string@DU?$char_traits@D@std@@V?$allo cato r@D@2@@2@@__rw@@U?$less@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@ D@2@ @std@@@2@V?$allocator@U?$pair@$$CBV?$basic_string@DU?$char_traits@D@std@@V?$ allo cator@D@2@@std@@G@std@@@2@@__rw@@I@Z) greg_month.obj : error LNK2019: unresolved external symbol "__declspec(dllimport ) public: __thiscall std::ios_base::Init::Init(void)" (__imp_??0Init@ios_base@st d@@QAE@XZ) referenced in function _$E3 greg_month.obj : error LNK2019: unresolved external symbol "__declspec(dllimport ) public: __thiscall __rw::__rw_facet_id::__rw_facet_id(void)" (__imp_??0__rw_fa cet_id@__rw@@QAE@XZ) referenced in function _$E8 greg_month.obj : error LNK2019: unresolved external symbol "__declspec(dllimport ) public: __thiscall std::ios_base::Init::~Init(void)" (__imp_??1Init@ios_base@s td@@QAE@XZ) referenced in function _$E4 bin\boost\libs\date_time\build\boost_date_time.dll\vc-7_1\debug\threading-mu lti\ boost_date_time-vc71-mt-gd-1_33_1.dll : fatal error LNK1120: 80 unresolved exter nals "link" /nologo /INCREMENTAL:NO /DEBUG /DLL /subsystem:console /out:"bin\ boost\libs\date_time\build\boost_date_time.dll\vc-7_1\debug\threading-multi\ boos t_date_time-vc71-mt-gd-1_33_1.dll" /IMPLIB:"bin\boost\libs\date_time\build\boos t_date_time.dll\vc-7_1\debug\threading-multi\boost_date_time-vc71-mt-gd-1_33 _1.l ib" /LIBPATH:"C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\lib" @" bin\boost\libs\date_time\build\boost_date_time.dll\vc-7_1\debug\threading-mu lti\ boost_date_time-vc71-mt-gd-1_33_1.CMD" ...failed vc-Link bin\boost\libs\date_time\build\boost_date_time.dll\vc-7_1\debu g\threading-multi\boost_date_time-vc71-mt-gd-1_33_1.dll bin\boost\libs\date_time \build\boost_date_time.dll\vc-7_1\debug\threading-multi\boost_date_time-vc71 -mt- gd-1_33_1.lib... vc-C++ bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\thread ing-multi\greg_month.obj greg_month.cpp vc-C++ bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\thread ing-multi\greg_weekday.obj greg_weekday.cpp vc-C++ bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\thread ing-multi\date_generators.obj date_generators.cpp vc-Archive bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\th reading-multi\libboost_date_time-vc71-mt-gd-1_33_1.lib Microsoft (R) Library Manager Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. -----Mensagem original----- De: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] Em nome de John Maddock Enviada em: quarta-feira, 23 de novembro de 2005 08:13 Para: boost(a)lists.boost.org Assunto: Re: [boost] build boost with other standard Lib (std) > I need build boost whit other std, have any way to do this? > > I need this because my system use STD provided by RogueWave, than I > need > that boost is build with this std. > > If have way to do this, what is the steps? It depends what commands you need to insert into the command line, but lets say you want /usr/local/rw/include added to your include search path you could do: bjam -sBUILD="<cxxflags>-I/usr/local/rw/include <threading>mutli/single <runtime-link>dynamic release debug" -sTOOLS=gcc which obviously assumes your building on a Unix variant with gcc, just change the toolset name and the cxxflags options according to your needs. If you need to inject more than one command line option then you need to use multiple <cxxflags>-option parts. And finally if you need to add linker options use <linkflags>-option. Clear ? John. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Esta mensagem foi verificada pelo E-mail Protegido Terra. Scan engine: McAfee VirusScan / Atualizado em 22/11/2005 / Versco: 4.4.00/4634 Proteja o seu e-mail Terra: http://mail.terra.com.br/ Esta mensagem foi verificada pelo E-mail Protegido Terra. Scan engine: McAfee VirusScan / Atualizado em 22/11/2005 / Versco: 4.4.00/4634 Proteja o seu e-mail Terra: http://mail.terra.com.br/

2 3

Boost regression notification (2005-11-25 [RC_1_33_0])
by Douglas Gregor 25 Nov '05

25 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-25T13:58:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-25 [HEAD])
by Douglas Gregor 25 Nov '05

25 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-25T06:00:24Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 175 failures in 14 libraries: concept_check (13) foreach (1) graph (3) io (1) math (2) mpl (1) parameter (12) program_options (35) regex (3) serialization (30) spirit (6) tr1 (45) typeof (18) wave (5) |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 vc-7_1 vc-7_1 |foreach| rvalue_const: intel-win32-9_0 |graph| graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos log1p_expm1_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |program_options| cmdline_test: mingw-3_4_2 vc-7_1 vc-7_1 cmdline_test_dll: vc-7_1 vc-7_1 options_description_test: mingw-3_4_2 vc-7_1 vc-7_1 options_description_test_dll: vc-7_1 vc-7_1 parsers_test: mingw-3_4_2 vc-7_1 vc-7_1 parsers_test_dll: vc-7_1 vc-7_1 positional_options_test: mingw-3_4_2 vc-7_1 vc-7_1 positional_options_test_dll: vc-7_1 vc-7_1 unicode_test: vc-7_1 vc-7_1 unicode_test_dll: vc-7_1 vc-7_1 variable_map_test: mingw-3_4_2 vc-7_1 vc-7_1 variable_map_test_dll: vc-7_1 vc-7_1 winmain: mingw-3_4_2 vc-7_1 vc-7_1 winmain_dll: mingw-3_4_2 vc-7_1 vc-7_1 |regex| grep: mingw-3_4_2 vc-7_1 vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| bug_fixes: vc-7_1 file_iterator_tests_debug: vc-7_1 fixed_size_queue_tests: vc-7_1 loops_tests_debug: vc-7_1 traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave: mingw-3_4_2 vc-7_1 vc-7_1 testwave_dll: vc-7_1 vc-7_1

1 0

thread: Checking for thread termination?
by Johannes 25 Nov '05

25 Nov '05

Hi, In my applications I frequently need to check to see if a thread or thread group has terminated. What is the best (or any) way of doing this in boost::thread? /Johannes

1 0

[serialization][documentation] character encoding oddity
by Martin Wille 25 Nov '05

25 Nov '05

Hi, http://boost.org/libs/serialization/doc/contents.html shows three strange characters at the top of the page (ï»¿). Apparently, those characters have the values EF BB BF in hexadecimal notation. Interpreted as UTF-8 sequence, they encode the Unicode codepoint FFFE. This codepoint is used as a marker for the endianness in encodings other than UTF-8. I doubt such a marker would be legal in or would make sense for an UTF-8 encoded document. Also, the document's content-type meta-tag claims the document uses ISO-8859-1. I suspect there's a problem in the toolchain used to create the document (oherwise, I would have fixed it in the repository). Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com

6 6

[Boost-bugs] [ boost-Bugs-1365752 ] problem with boost::iostreams when compiled with Visual C++
by SourceForge.net 24 Nov '05

24 Nov '05

Bugs item #1365752, was opened at 2005-11-24 10:37 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=1365752&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: problem with boost::iostreams when compiled with Visual C++ Initial Comment: There seems to be a problem with boost::iostreams when compiled with Visual C++ 7.1 (Boost Release 1.33.1 Beta). The following code results in a compile error: char array[100]; typedef code_converter<array_sink, Dinkum::conversions::codecvt_utf8<wchar_t> > MyArrayDevice; stream<MyArrayDevice> wCharOut(array, 100); error C2665: 'boost::iostreams::detail::io_mode_impl_helper' : none of the 9 overloads can convert parameter 1 from type 'boost::iostreams::detail::array_adapter<Mode,Ch> ::category' .... The same lines work just fine when compiled with gcc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1365752&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost regression notification (2005-11-24 [RC_1_33_0])
by Douglas Gregor 24 Nov '05

24 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-24T15:09:10Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-24 [HEAD])
by Douglas Gregor 24 Nov '05

24 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-24T06:00:26Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 131 failures in 13 libraries: concept_check (13) foreach (1) graph (3) io (1) math (2) mpl (1) multi_array (1) parameter (12) serialization (31) spirit (2) tr1 (45) typeof (18) wave (1) |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 vc-7_1 vc-7_1 |foreach| rvalue_const: intel-win32-9_0 |graph| graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos log1p_expm1_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |multi_array| concept_checks: mingw-3_4_2 |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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_mi_xml_archive: mingw-3_4_2 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave_dll: mingw-3_4_2

1 0

[Boost-bugs] [ boost-Bugs-1365698 ] serialization demo example can't be used
by SourceForge.net 24 Nov '05

24 Nov '05

Bugs item #1365698, was opened at 2005-11-24 08:47 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=1365698&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: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: serialization demo example can't be used Initial Comment: I want to use boost.serialization module in my project, but I found that I can't use it. Because i test the demo.cpp in \boost_1_33_1 \libs\serialization\example\, it can't run normally in msvc7.1 environment. It always pop memory alloc error. Who know the reason. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1365698&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

lexical_cast on the pocket pc
by Matt Comi 24 Nov '05

24 Nov '05

Hi, I've written a functor (primarily for use with a std::map<string, ?>) that sorts numerically first and alphabetically second using lexical_cast. It looks like this: try { return lexical_cast<double>(lhs) < lexical_cast<double>(rhs); } catch (bad_lexical_cast&) { return lhs < rhs; } ...and it's been working nicely so far. However on the Pocket PC, each time an exception is raised by the lexical_cast, it takes about a quarter of a second to move on to the catch. Not very nice when the map is huge. As far as I can tell, there is no way to say to ensure that a lexical_cast is going to be valid until you actually perform it. I'm hoping that I won't need to resort to duplicating the innards of lexical_cast in order to implement this function on the Pocket PC. Any ideas? Thanks all, Matt. ------------------------------------------------------------------------ -------- Big Bucket Amusement http://members.iinet.net.au/~mattcomi/mt/bigbucket

1 0

Re: [boost] Full MS compiler version info?
by Martin Bonner 24 Nov '05

24 Nov '05

----Original Message---- From: Paul A Bristow [mailto:pbristow@hetp.u-net.com] Sent: 24 November 2005 14:51 To: boost(a)lists.boost.org Subject: Re: [boost] Full MS compiler version info? >> -----Original Message----- >> From: boost-bounces(a)lists.boost.org >> [mailto:boost-bounces@lists.boost.org] On Behalf Of Peter Dimov >> Sent: 24 November 2005 12:46 To: boost(a)lists.boost.org >> Subject: Re: [boost] Full MS compiler version info? >> >> Paul A Bristow wrote: >> >>> Indeed - but I didn't see the MS BUILD number - needed to >>> distinguish between 8.0 beta 1, 2, 2.5 ... and final(s). >> >> Why is it needed? Beta versions don't exist as far as >> official support is concerned. > > Of course, but I am sure I am not alone in wanting to anticipate > problems and improvements in testing new versions before the release. > > Indeed this is how Boost gives 'official' support to new versions as > quickly as it does? > > It may be too, that there is more than one release of "8.0". Indeed. The advice used to be: "don't use Visual C++ unless you have SP2 installed". The advice was good even if SP2 hadn't been released for that version! > The > build number gives assurance that this is NOT a cause of mysterious > differences. > -- 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

[Boost-bugs] [ boost-Bugs-1365338 ] format_paragraph in options_description.cpp
by SourceForge.net 24 Nov '05

24 Nov '05

Bugs item #1365338, was opened at 2005-11-23 23:37 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=1365338&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: format_paragraph in options_description.cpp Initial Comment: function format_paragraph in options_description.cpp triggered assertion _SCL_SECURE_VALIDATE_RANGE failure in microsoft vc8. at line #379, it looks for a space backword to avoid chopping a word in the middle. the expression line_begin - 1 causes assertion failure if line_begin is at the beginning of the description string. here is suggested fix @@ -378,3 +378,3 @@ find(reverse_iterator<string::const_iterator>(line_end - 1), - reverse_iterator<string::const_iterator>(line_begin - 1), + reverse_iterator<string::const_iterator>(line_begin), ' ') @@ -382,3 +382,3 @@ - if (last_space != line_begin - 1) + if (last_space != line_begin) { ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1365338&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[serialization] non-virtual destructors in 1.33.1
by Kim Barrett 23 Nov '05

23 Nov '05

Between 1.33 and 1.33.1_beta, several classes in the serialization library were changed from having virtual destructors to having non-virtual destructors. An example is basic_oserializer. Many of these classes have virtual functions, with the result that "g++ -Wall" now complains about them ("has virtual functions but non-virtual destructor"), so that I now get tons of warnings when compiling code that uses the serialization library. My guess would be that none of these warnings are actually interesting, but that belief doesn't really help all that much. Was there a good reason for this change? Could it be reverted? If not, is there some other thing that could be done to eliminate these warnings? For 1.33.1 release?

8 13

Doubt about regex speed.
by Renato Tegon Forti 23 Nov '05

23 Nov '05

Hi All, I have one system that receive many messages (TCP/IP transport) on one second, and I validate these messages whit a sequence of if,s and switchs, see exemple of message: 19092;1;12345678;1111222233334444;123;0512;10000;1;0 I would like know if I use regex to do this I will have improvement in performance of my system, or I will have delay in my system? My regex to validate this message is: "\\d{1,5};1;\\d{1,8};\\d{16};\\d{3};\\d{4};\\d{1,8};([0-9]|10|11|12);[012]" My code sample (in old version I need same about 300 lines to do the same): class CParser { public: CParser(const std::string& toparser, const RWDBDatabase &database) { if(validate("\\d{1,5};1;\\d{1,8};\\d{16};\\d{3};\\d{4};\\d{1,8};([0-9]|10|11 |12);[012]", toparser)) { CContext<CProcessMessage1> process; } else if(validate("\\d{1,5};3;\\d{16};\\d{11};[01]", toparser)) { } else if(validate("\\d{1,5};5;\\d{16};\\d{11}", toparser)) { } else if(validate("\\d{1,5};7;\\d{16};\\d{11}", toparser)) { } else { throw CParserException("bad_message"); } } protected: bool validate(const std::string& regex, const std::string& to_validate) { try { const boost::regex e(regex); return regex_match(to_validate.c_str(), e); } catch (...) { throw CParserException("bad_regex_syntax"); } } }; Thanks to help _____ Esta mensagem foi verificada pelo E-mail Protegido Terra <http://mail.terra.com.br/> . Scan engine: McAfee VirusScan / Atualizado em 21/11/2005 / Versão: 4.4.00/4633 Proteja o seu e-mail Terra: http://mail.terra.com.br/

3 2

Is there a Boost based solution to this circular reference problem
by Michael Goldshteyn 23 Nov '05

23 Nov '05

Description: I have a class hierarchy which unfortunatelly results in circular dependencies not allowed by C++. Is there any simple way to fix this? Please note, I have trivialized this problem for the purpose of illustration. The actual code that needs this is far more complex. I am quite perplexed, please help: Here is the code made as simple as I can: part.h ------ class Part { }; action.h -------- // The Action class is where the problem arises. It depends on an iterator in a class which is not yet defined. // The class cannot be defined before the Action class, because it depends on the definition of the Action class. class Action { public: typedef std::list<Part> PartsList; private: // I want a back "reference" to the iterator pointing to // the part for which this action applies. This is OK, I can just // typedef PartsList myself and don't need Whole for this PartsList::iterator iPart; // I also want a back "reference" all the way to the iterator // in the NameWholeMap for whose value this action applies // Here, I have a circular reference issue. // Note: Storing the key in the NameWholeMap to eliminate // this problem is not an option. I need a direct reference back // to the association in the map (map iterator), so as not to have // to look it up again. NamedWholes::NameWholeMap::iterator iNamedWhole; }; whole.h -------- // Whole is basically a container of Parts. Action needs an iterator to the list it contains. // Fortunatelly, because the value in this list (i.e. Part) does not depend on Action, I can just // type define the same list (i.e. PartsList) in the Action class and refer to its iterator there. class Whole { public: typedef std::list<Part> PartsList; typedef boost::optional<Action> OptionalAction; typedef std::vector<Action> Actions; void GetActionsOnSomePartsForThisWhole(Actions &actions); private: OptionalAction DecideOnAction() const; Parts m_parts; }; namedwholes.h ---------------- // This is the other half of our circular reference problem. This class has a function which gathers // actions on various parts contained in various wholes contained in its NameWholeMap. Those // actions would like to know directly which iterator in the NameWholeMap they were created // from, so as not to require a search by key later. // The problem is that this class must know how Action is defined and Aciton must know how // this class is defined, creating a circular reference. class NamedWholes { public: typedef std::map<std::string,std::Whole> NameWholeMap; typedef Whole::Actions Actions; void GetAllActions(Actions &actions); private: NameWholeMap m_nameWholeMap; };

3 7

LINK problem (RW STD) -- help
by Renato Tegon Forti 23 Nov '05

23 Nov '05

Hi all, I have one problem, if any one can help-me. I did try use boost (regex) whit my system that use RogueWave STD, but when I try compile my system I receive 5 link errors (see below :error 1), then I did try use this BJAM command line to build LIBS: bjam "-sBUILD=debug <include>-IC:\RogueWave\SourcePro\Ed8 <include>-IC:\RogueWave\SourcePro\Ed8\include <include>-IC:\RogueWave\SourcePro\Ed8\include\ansi <include>-IC:\RogueWave\SourcePro\Ed8\lib <cxxflags>-D_RWCONFIG=rmd <runtime-link>dynamic <threading>multi" "-sTOOLS=vc-7_1" this build libs, but the error continue. I did also try this: bjam "-sBUILD=debug <cxxflags>-IC:\RogueWave\SourcePro\Ed8\include <cxxflags>-IC:\RogueWave\SourcePro\Ed8\include\ansi <cxxflags>-IC:\RogueWave\SourcePro\Ed8\lib<cxxflags>-D_RWCONFIG=rmd <runtime-link>dynamic <threading>multi" "-sTOOLS=vc-7_1" But this did't compile. (see below: error 2) The awkward thing is that the error occur in line 6, if I change line 6 to this (return regex_match("some thing", e);), than compile if I put std::string to_validate the error occurs. Any one cam help-me - please!!! 1: bool validate(const std::string& regex, const std::string& to_validate) 2: { 3: try 4: { 5: const boost::regex e(regex); 6: return regex_match(to_validate, e); 7: } 8: catch (...) 9: { 10: throw CParserException("bad_regex_syntax"); 11: } 12: } If anyone cam give me a light, please. Thanks Error 1: ------ Build started: Project: uratalkservr, Configuration: Debug Win32 ------ Compiling... stdafx.cpp Include: dynamic linking with boost libraries main.cpp Include: dynamic linking with boost libraries Linking to lib file: boost_regex-vc71-mt-gd-1_33_1.lib Generating Code... Linking... main.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::match_results<class __rw::__rw_debug_iter<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,char const *,char *>,class std::allocator<struct boost::sub_match<class __rw::__rw_debug_iter<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,char const *,char *> > > >::~match_results<class __rw::__rw_debug_iter<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,char const *,char *>,class std::allocator<struct boost::sub_match<class __rw::__rw_debug_iter<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,char const *,char *> > > >(void)" (__imp_??1?$match_results@V?$__rw_debug_iter@V?$basic_string@DU?$char_traits @D@std@@V?$allocator@D@2@@std@@PBDPAD@__rw@@V?$allocator@U?$sub_match@V?$__r w_debug_iter@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@P BDPAD@__rw@@@boost@@@std@@@boost@@QAE@XZ) referenced in function "bool __cdecl boost::regex_match<struct std::char_traits<char>,class std::allocator<char>,char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > >(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class boost::basic_regex<char,struct boost::regex_traits<char,class boost::w32_regex_traits<char> > > const &,enum boost::regex_constants::_match_flags)" (??$regex_match@U?$char_traits@D@std@@V?$allocator@D@2@DU?$regex_traits@DV?$ w32_regex_traits@D@boost@@@boost@@@boost@@YA_NABV?$basic_string@DU?$char_tra its@D@std@@V?$allocator@D@2@@std@@ABV?$basic_regex@DU?$regex_traits@DV?$w32_ regex_traits@D@boost@@@boost@@@0@W4_match_flags@regex_constants@0@@Z) ... CONTINUES ..\..\_complication\debug\Ultimate Card System\1.0\def$uratalk/uratalkservr.exe : fatal error LNK1120: 5 unresolved externals Build log was saved at "file://e:\project-Ultimate Card System\_project\Ultimate Card System\server\_complication\debug\Ultimate Card System\1.0\def$uratalk\___VS_ID\BuildLog.htm" uratalkservr - 6 error(s), 0 warning(s) ---------------------- Done ---------------------- Build: 0 succeeded, 1 failed, 0 skipped Error 2: . greg_month.obj : error LNK2019: unresolved external symbol "__declspec(dllimport ) public: class std::basic_string<char,struct std::char_traits<char>,class std:: allocator<char> > __thiscall std::basic_stringbuf<char,struct std::char_traits<c har>,class std::allocator<char> >::str(void)const " (__imp_?str@?$basic_stringbu f@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QBE?AV?$basic_string@DU?$cha r_tr aits@D@std@@V?$allocator@D@2@@2@XZ) referenced in function "public: class std::b asic_string<char,struct std::char_traits<char>,class std::allocator<char> > __th iscall std::basic_stringstream<char,struct std::char_traits<char>,class std::all ocator<char> >::str(void)const " (?str@?$basic_stringstream@DU?$char_traits@D@st d@@V?$allocator@D@2@@std@@QBE?AV?$basic_string@DU?$char_traits@D@std@@V?$all ocat or@D@2@@2@XZ) . CONTINUES "link" /nologo /INCREMENTAL:NO /DEBUG /DLL /subsystem:console /out:"bin\ boost\libs\date_time\build\boost_date_time.dll\vc-7_1\debug\threading-multi\ boos t_date_time-vc71-mt-gd-1_33_1.dll" /IMPLIB:"bin\boost\libs\date_time\build\boos t_date_time.dll\vc-7_1\debug\threading-multi\boost_date_time-vc71-mt-gd-1_33 _1.l ib" /LIBPATH:"C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\lib" @" bin\boost\libs\date_time\build\boost_date_time.dll\vc-7_1\debug\threading-mu lti\ boost_date_time-vc71-mt-gd-1_33_1.CMD" ...failed vc-Link bin\boost\libs\date_time\build\boost_date_time.dll\vc-7_1\debu g\threading-multi\boost_date_time-vc71-mt-gd-1_33_1.dll bin\boost\libs\date_time \build\boost_date_time.dll\vc-7_1\debug\threading-multi\boost_date_time-vc71 -mt- gd-1_33_1.lib... MkDir1 bin\boost\libs\date_time\build\libboost_date_time.lib MkDir1 bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1 MkDir1 bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug MkDir1 bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\thread ing-multi vc-C++ bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\thread ing-multi\greg_month.obj greg_month.cpp vc-C++ bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\thread ing-multi\greg_weekday.obj greg_weekday.cpp vc-C++ bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\thread ing-multi\date_generators.obj date_generators.cpp vc-Archive bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\th reading-multi\libboost_date_time-vc71-mt-gd-1_33_1.lib Microsoft (R) Library Manager Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. "bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\threadin g-mu lti\greg_month.obj" "bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\threadin g-mu lti\greg_weekday.obj" "bin\boost\libs\date_time\build\libboost_date_time.lib\vc-7_1\debug\threadin g-mu lti\date_generators.obj" MkDir1 bin\boost\libs\filesystem MkDir1 bin\boost\libs\filesystem\build MkDir1 bin\boost\libs\filesystem\build\libboost_filesystem.lib MkDir1 bin\boost\libs\filesystem\build\libboost_filesystem.lib\vc-7_1 MkDir1 bin\boost\libs\filesystem\build\libboost_filesystem.lib\vc-7_1\debug MkDir1 bin\boost\libs\filesystem\build\libboost_filesystem.lib\vc-7_1\debug\thre ading-multi vc-C++ bin\boost\libs\filesystem\build\libboost_filesystem.lib\vc-7_1\debug\thre ading-multi\exception.obj exception.cpp other part: convert.obj : error LNK2001: unresolved external symbol "protected: virtual int __thiscall std::codecvt<wchar_t,char,int>::do_length(int &,char const *,char con st *,unsigned int)const " (?do_length@?$codecvt@_WDH@std@@MBEHAAHPBD1I@Z) utf8_codecvt_facet.obj : error LNK2019: unresolved external symbol "__declspec(d llimport) public: __thiscall std::codecvt<wchar_t,char,int>::codecvt<wchar_t,cha r,int>(unsigned int)" (__imp_??0?$codecvt@_WDH@std@@QAE@I@Z) referenced in funct ion "public: __thiscall boost::program_options::detail::utf8_codecvt_facet::utf8 _codecvt_facet(unsigned int)" (??0utf8_codecvt_facet@detail@program_options@boos t@@QAE@I@Z) . 25 unresolved externals

1 0

[Announce] Boost Graph Library Python Bindings Version 0.9
by Douglas Gregor 23 Nov '05

23 Nov '05

Version 0.9 of the Boost Graph Library Python bindings has been released. The BGL-Python bindings provide access to many of the features of the C++ Boost Graph Library from Python, blending the rapid prototyping and application development capabilities of Python with the power and performance of C++. BGL-Python is the successor to the experimental Python bindings found in Boost 1.33.0, providing more algorithms, better data structures, and drastically improved documentation. The BGL-Python bindings are available at: http://www.osl.iu.edu/~dgregor/bgl-python/ Doug

1 0

Boost regression notification (2005-11-23 [RC_1_33_0])
by Douglas Gregor 23 Nov '05

23 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-23T14:54:15Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 4 failures in 2 libraries: multi_array (1) serialization (3) |multi_array| assign: vc-8_0 |serialization| test_list_ptrs_xml_warchive_dll: vc-8_0 test_non_default_ctor2_xml_archive: vc-8_0 test_shared_ptr_text_warchive_dll: vc-8_0

1 0

Boost regression notification (2005-11-23 [HEAD])
by Douglas Gregor 23 Nov '05

23 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-23T06:00:10Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 131 failures in 13 libraries: concept_check (13) foreach (1) graph (3) io (1) math (2) mpl (1) multi_array (1) parameter (12) serialization (31) spirit (2) tr1 (45) typeof (18) wave (1) |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 vc-7_1 vc-7_1 |foreach| rvalue_const: intel-win32-9_0 |graph| graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos log1p_expm1_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |multi_array| concept_checks: mingw-3_4_2 |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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_mi_xml_archive: mingw-3_4_2 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave_dll: mingw-3_4_2

1 0

[wave] problem with long long suffixes
by Alexey Bakhvalov 23 Nov '05

23 Nov '05

Hello, Shouldn't Boost.Wave preprocess "11LL" into two tokens "11" and "LL" if support for long long suffixes is disabled? In a current version I get lexer error. Alexey Bakhvalov

3 4

Boost 1.33.1 Beta released
by Douglas Gregor 23 Nov '05

23 Nov '05

Boost 1.33.1 Beta ----------------- Boost 1.33.1 Beta is now available at http://www.boost.org. This is a bug fix release to 1.33.0, containing updates to existing libraries and additional computer support. Updated Libraries * Any Library: Cast to reference types introduced in 1.33.0 is now documented on any_cast documentation page. * Config Library: Don't undef BOOST_LIB_TOOLSET after use. * Boost.Python: o The build now assumes Python 2.4 by default, rather than 2.2 o Support Python that's built without Unicode support o Support for wrapping classes with overloaded address-of (&) operators * Smart Pointer Library: Fixed problems under Metrowerks CodeWarrior on PowerPC (Mac OS X) with inlining on, GNU GCC on PowerPC 64. * Regex Library: Fixed the supplied makefiles, and other small compiler specific changes. Refer to the regex history page for more information on these and other small changes. * Iostreams Library: Improved the interface for accessing a chain's components, added is_open members to the file and file descriptor devices, fixed memory-mapped files on Windows, and made minor changes to the documentation. * Functional/Hash Library: Fixed the points example. * Multi-index Containers Library: Fixed a problem with multithreaded code, and other minor changes. Refer to the library release notes for further details. * Graph Library: Fixed a problem with the relaxed heap on x86 Linux. Fixed problems with cuthill_mckee_ordering and king_ordering producing no results. * Signals Library: Fixed problems with the use of Signals across shared library boundaries. * Thread library: read_write_mutex has been removed due to problems with deadlocks. Supported Compilers Boost is tested on a wide range of compilers and platforms. Since Boost libraries rely on modern C++ features not available in all compilers, not all Boost libraries will work with every compiler. The following compilers and platforms have been extensively tested with Boost, although many other compilers and platforms will work as well. For more information, see the regression test results. New for this release: Support for building with the newest STLport-5.0 was added. The support includes building with MinGW Runtime 3.8 plus STLport-5.0 improved to support wide character operations. Apple GCC 4.0, HP Tru64 C++, and Microsoft Visual C++ 8.0 are supported platforms. We have added an experimental autoconf-like configure script for Unix-like systems: run configure --help for more information. * Apple GCC 3.3, 4.0 on Mac OS X. * Borland C++ 5.6.4 on Windows. * GNU C++ 2.95.3 (with and without STLport), 3.2.x., 3.3.x, 3.4.x, 4.0.x on Windows, Linux and Solaris. * HP C++ for Tru64 UNIX 7.1. * Intel C++ 8.1, 9.0 on Windows, Linux. * Metrowerks CodeWarrior 8.3, 9.4, 9.5 on Mac OS X and Windows. * Microsoft Visual C++ 6.0 (sp5, with and without STLport), 7.0, 7.1, 8.0. Note: Boost does not support the non-standard "Safe" C++ Library shipping with Visual C++ 8.0, which may result in many spurious warnings from Boost headers and other standards- conforming C++ code. To suppress these warnings, define the macro _SCL_SECURE_NO_DEPRECATE. Acknowledgements Douglas Gregor managed this release. A great number of people contributed their time and expertise to make this release possible. Special thanks go to Aleksey Gurtovoy and Misha Bergal, who managed to keep the regression testing system working throughout the release process; David Abrahams, Beman Dawes, Aleksey Gurtovoy, Bronek Kozicki, Rene Rivera and Jonathan Turkanis for greatly improving the quality of this release; Rene Rivera for the new Boost web page design; and Zoltan "cad" Juhasz for the new Boost logo.

6 7

build boost with other standard Lib (std)
by Renato Tegon Forti 23 Nov '05

23 Nov '05

Hi All, I need build boost whit other std, have any way to do this? I need this because my system use STD provided by RogueWave, than I need that boost is build with this std. If have way to do this, what is the steps? Thanks to all -- :o)

2 1

[Boost-bugs] [ boost-Bugs-1364416 ] mistake in documentation of condition
by SourceForge.net 23 Nov '05

23 Nov '05

Bugs item #1364416, was opened at 2005-11-22 22:57 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=1364416&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: threads Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Mike Glassford (glassfordm) Summary: mistake in documentation of condition Initial Comment: Hello, the documentation (http://www.boost.org/doc/html/condition.html) of class condition contains a mistake: instead of template<typename ScopedLock, typename Pred> bool timed_wait <http://www.boost.org/doc/html/condition.html> (ScopedLock&, Pred); it should be template<typename ScopedLock, typename Pred> bool timed_wait <http://www.boost.org/doc/html/condition.html> (ScopedLock&, const boost::xtime <http://www.boost.org/doc/html/xtime.html> & , Pred); so long, Oliver ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1364416&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost pointer containers compile errors, runtime errors, and compiler warnings
by Axter 22 Nov '05

22 Nov '05

http://www.boost.org/libs/ptr_container/doc/ptr_container.html I'm currently in the middle of writing an article making the comparison between the above boost pointer containers and the following clone smart pointers: http://code.axter.com/copy_ptr.h http://code.axter.com/cow_ptr.h I'm performing my test using boost_1_33_0, and VC++ 7.1 compiler. I'm comparring vector<copy_ptr<T> > to boost::ptr_vector<T> I want to make sure that my article is accurate and complete, so I'm posting this question. When trying to compile using copy constructor for ptr_vector, I get a compile error. boost::ptr_vector<Shape> CopyViaContainerCopyConstructor(ContainerOfOriginalShapes); //Will not compileContainerType boost::ptr_vector<Shape> CopyViaContainerCopyConstructor = ContainerOfOriginalShapes; //Will not compile Is this by design, and if so, why doesn't the boost pointer container have a copy constructor like the STL containers have? Another standard STL container interface that fails to compile using ptr_container is push_back via dereferenced iterator. Example: for(it = ContainerOfOriginalShapes.begin();it != ContainerOfOriginalShapes.end();++it) CopyViaContainerForLoopIterator.push_back(*it); Is this also by designed, and if so, why? I also notice that the follow code fails at runtime. boost::ptr_vector<Shape> CopyViaContainerForLoopOp(ContainerOfOriginalShapes.size()); for(i = 0;i < ContainerOfOriginalShapes.size();++i) CopyViaContainerForLoopOp[i] = ContainerOfOriginalShapes[i]; However, if I do the following, then it works: //Try creating the right size for the container via push_back for(i = 0;i < ContainerOfOriginalShapes.size();++i) CopyViaContainerForLoopOp.push_back(Shape::AbstractFactory(SourceData[i][0], SourceData[i][1])); //Again test copy via for loop using operator[] for(i = 0;i < ContainerOfOriginalShapes.size();++i) CopyViaContainerForLoopOp[i] = ContainerOfOriginalShapes[i]; Is there a problem with the way ptr_vector gets constructed when size argument is used for constructor with out a default value? When using the VC++ 7.1 compiler, I notice I get a compile warning "resolved overload was found by argument-dependent lookup" See full warning in following link: http://code.axter.com/boost_ptr_containers/compilerwarnings.txt Warning for following code: http://code.axter.com/boost_ptr_containers/BoostPolymorphicContainerTest.cpp http://code.axter.com/boost_ptr_containers/shape.h Is this a problem with VC++ 7.1 giving a false warning, or with the ptr_vector code design? I also welcome any additional input that may be useful for the article. Thank you

2 1

[test] please ignore
by Thorsten Ottosen 22 Nov '05

22 Nov '05

-Thorsten

1 0

Possibility of GLR parser combinators? Spirit-2?
by Korcan Hussein 22 Nov '05

22 Nov '05

I was briefly reading GLR Parsing in Haskell and found the library based off the paper HaGLR a GLR parser combinator framework and it got me thinking. With the advent of Phoenix-2 (very nice work guys) and FC++ being worked on (to be re-reviewed for boost in the not to distant future?) there could be a possibility of direct & easy port of the haskell code to C++ using either of these libraries as it's foundation and built & used in a simillar fashion to Spirit ala expression templates (maybe an idea for Spirit 2 even). There might be an issue with Phoenix-2 (i don't know enough about the subject to know for sure) since HaGLR is based on the idea of parser combinators i'd assume it takes a simillar approach to the Parsec library using monads, from what i gather from Phoenix-2 docs there currently is no plains to support monads. So what do you guys think? :-)

5 6

[Boost-bugs] [ boost-Bugs-1364007 ] [Regex] Splitting string: last empty token is "compressed"
by SourceForge.net 22 Nov '05

22 Nov '05

Bugs item #1364007, was opened at 2005-11-22 09:41 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=1364007&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: regex Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: John Maddock (johnmaddock) Summary: [Regex] Splitting string: last empty token is "compressed" Initial Comment: toto_lists(a)hotbox.ru Last empty token is "compressed" when using regex_token_iterator for splitting strings. BCB 5.64, boost 1.33.0 See the example, compare it with string_algo splitting: #include <boost\regex.hpp> #include <string> #include <vector> #include <iostream> #include <boost/algorithm/string/finder.hpp> #include <boost/algorithm/string/find_iterator.hpp> void with_stringAlgo() { using namespace std; vector<string> result; string to_split("&|&_field2_&|&_field3_&|&"); boost::split_iterator<string::iterator> i(to_split.begin(),to_split.end(),boost::first_finder("&|&")),j; for(;i!=j;++i) { result.push_back(boost::copy_range<std::string>(*i)); } cout<<"size is "<<result.size()<<endl; for(int i=0;i<result.size();++i) cout<<result[i]<<endl; } void with_regex() { using namespace std; using namespace boost; using namespace boost::regex_constants; string s("&|&_field2_&|&_field3_&|&"); boost::regex r("&\|&");//use &|& as delimiter boost::sregex_token_iterator i(s.begin(),s.end(),r,-1, match_default),j; // vector<string> v; copy(i,j,back_inserter(v)); // cout<<"size is "<<v.end()-v.begin()<<endl; copy(v.begin(),v.end(),ostream_iterator<string>(cout,"\n")); } int main() { with_stringAlgo(); with_regex(); } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1364007&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[iterator] indirect_iterator->
by Orjan Westin 22 Nov '05

22 Nov '05

I have a question on the indirect_iterator, and what related standards say. I assume this class is primarily aimed for use in algorithms, which is fine. An algorithm typically dereference an iterator to do its thing, be it comparing or passing the dereferenced iterator on to a function or functor. This is great. But it doesn't handle direct usage well. If I have an indirect_iterator i for, say, a pointer to std::string, I cannot treat it as any other iterator to string and empty the string with this call: i->clear(); because the pointer operator is not changed. Instead you have to dereference it and use it as a reference: (*i).clear(); It seems strange to me that one way of getting hold of the iterated object is provided, but not the other. I couldn't find anything about this in a brief look through the standard, but I would expect it to want iterators yield the same results for both formats. Does anybody know if it does say anything on this subject, and why operator->() wasn't included in indirect_iterator? Cheers, Orjan

3 5

[smart pointers] Proposal to add some small utilities
by Ion Gaztañaga 22 Nov '05

22 Nov '05

Hi to all, While developing Shmem I wrote a smart pointer to represent relative pointers and now I'm experimenting with a multi-segment shared memory pointer to create growing multi-segment shared memory containers and allocators. Both pointers are based on boost smart pointer's interface (shared_ptr, etc...). In Shmem and possibly other generic libraries the developer wants pointer-independent code, so that the pointer type is a template parameter and the same code is used for relative, reference counted, intrusive, raw, or multisegment pointers. One of such uses, in Shmem, is for example, a memory allocator (a first fit, best fit algorithm) or an intrusive container. While developing pointer-independent code, however, I've seen that some features are present in boost (for example, get_pointer() function) and other features are missing, and I would like to propose them: 1. Overloads of static_pointer_cast, dynamic_pointer_cast, const_pointer_cast overloads for raw pointers, so that we can use pointer_xxx_cast in a generic way. 2. Add reinterpret_pointer_cast to complete cast family. 3. A protocol to obtain a pointer of the same type from any pointer. For example, if you want to generically use a pointer (for example, raw or relative pointer) in a class and you want to declare another pointer to other type (raw or relative, depending on the source): //typedef typename boost::pointer_to_other //<GenericPointer, NewType>::type MyNewPointer; //A new pointer to float values typedef typename boost::pointer_to_other <SmartPtr, float>::type MyFloatPointer; We should define how this protocol is implemented in boost smart pointers (for example, using overloading or a STL-like rebind mechanism) so that every boost smart pointer developer knows how to make its pointer type protocol-aware. Shmem uses rebind-like mechanism now, but the mechanism is not important. This way, a class can receive a void pointer like a template parameter and can be pointer-independent: template <class VoidPtr> class memory_manager { struct memory_block { //... }; typedef typename boost::pointer_to_other <VoidPtr, memory_block>::type BlockPtr; BlockPtr mp_free_list; }; I think these utilities are simple to develop and quite useful. What do smart pointer experts think? Regards, Ion

2 4

Boost regression notification (2005-11-22 [RC_1_33_0])
by Douglas Gregor 22 Nov '05

22 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-22T14:05:07Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 4 failures in 2 libraries: multi_array (1) serialization (3) |multi_array| assign: vc-8_0 |serialization| test_list_ptrs_xml_warchive_dll: vc-8_0 test_non_default_ctor2_xml_archive: vc-8_0 test_shared_ptr_text_warchive_dll: vc-8_0

1 0

Boost regression notification (2005-11-22 [HEAD])
by Douglas Gregor 22 Nov '05

22 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-22T06:00:11Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 136 failures in 13 libraries: concept_check (13) foreach (2) graph (3) io (1) math (2) mpl (2) multi_array (1) parameter (12) serialization (30) signals (2) spirit (2) tr1 (48) typeof (18) |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 vc-7_1 vc-7_1 |foreach| rvalue_const: intel-win32-9_0 intel-win32-9_0 |graph| graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos log1p_expm1_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin zip_view: mingw-3_4_2 |multi_array| concept_checks: mingw-3_4_2 |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |signals| deletion_test: vc-7_1 ordering_test: vc-7_1 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4

1 0

[Python] VC++ 7.1 workaround needed in boost/python/class.hpp
by Douglas Gregor 22 Nov '05

22 Nov '05

I'm running into problems with Visual C++ 7.1 and class_<..>::add_property() in Boost.Python. The issue pops up in this bit o' code: class_<Graph> graph(name); graph .add_property("vertex_properties", &py_get_vertex_properties<Graph>, "A Python dictionary mapping from vertex property names to\n" "property maps. These properties are \"attached\" to the graph\n" "and will be pickled or serialized along with the graph.") .add_property("edge_properties", &py_get_edge_properties<Graph>, "A Python dictionary mapping from edge property names to\n" "property maps. These properties are \"attached\" to the graph\n" "and will be pickled or serialized along with the graph.") In particular, the compiler chokes when instantiating add_property(), because it can't tell that the third parameter is a docstring (instead of a setter). At line 304 of boost/python/class.hpp (RC_1_33_0 branch), there is a workaround for all Visual C++ versions prior to 7.1 that avoids this problem: if I switch the "1300" to "1310" to include VC++ 7.1, everything works fine. Unfortunately, I wasn't able to create a small test case that exhibits the problem. If you really, really want to reproduce the problem, you can grab the BGL-Python bindings that triggered it with: svn co https://svn.osl.iu.edu/svn/projects/viz/bgl-python Should we do the version bump in the workaround, or could that cause problems? Doug

2 1

serialization: registration of class types via header, or explicitly
by John.Clayton＠ubs.com 22 Nov '05

22 Nov '05

Hi All, I am trying to understand better how I can create a library of objects that can be streamed using boost::serialization (cool work btw). I have written a program that works OK, but there's a catch - I have to explicitly register the class types on the archiver instances before serialization. I had initially thought that the way around this was to use the following macro in the header file, just after declaring the class that will be stream-capable, e.g.: BOOST_CLASS_EXPORT( WatchdogPrimaryVote ) But if this is all I do (see below for what I really really have inside the header), then the write to a stream works OK, but reading back - in the same process space - throws an exception, telling me the class type is unregistered. When I register all known message types with the archiver explicitly, things work ok. e.g.: template < typename Archive > void registerClassTypes( Archive & ar ) { ar.template register_type < WatchdogMsgBase > ( static_cast < WatchdogMsgBase * > ( 0 ) ); ar.template register_type < WatchdogState > ( static_cast < WatchdogState * > ( 0 ) ); ar.template register_type < WatchdogPrimaryVote > ( static_cast < WatchdogPrimaryVote * > ( 0 ) ); } I am using boost_1_33_0 on Win32 with XP and Dev Env 2003 VC 7.1 - my project is a console application that links in the message as a dynamic library. So yes, I'm using __declspec(import/export). I had thought that when one uses the BOOST_CLASS_EXPORT() macro, that the types we're auto-magically added/known to the archivers, because of some definitions that get created the macro itself. Questions: ========== - Any ideas why I would have to do this (is it a problem with __declspec(imp/exp))? - Should I just throw away the idea of a dynamic library ang go static (it's all the same to me)? - With .so's on *nix would I have this same issue? (or maybe that's a little too broad cos it's compiler dependant - I don't know, looking at the details of the templates makes my eyes water sometimes). Thanks for any time that anyone has to read through all of this - sorry to include lots, I did that based on the 'more info is better' idea - although there's probably more detail I should give anyway. John Clayton PS: Here's a little more detailed background, I have : ================================================== - created a series of objects that are streamable, each derived from a common base class, using intrusive serialization - written a series of these objects, to a std::ostream, via ar & obj; - never written an instance of the base object to the stream explicitly - closed the std::ostream and re-opened it again (obviously as a std::istream type object) I am reading objects from the stream like this: WatchdogMsgBase *ptr = 0; archiver & ptr; in WatchdogPrimaryVote (derived from WatchdogMsgBase), I serialize like this: . . . template < class Archive > void serialize( Archive & ar, const unsigned int version ) { REGISTER_DERIVED_AND_BASE( WatchdogPrimaryVote, WatchdogMsgBase ); ar & BOOST_SERIALIZATION_NVP( _voteType ); ar & BOOST_SERIALIZATION_NVP( _responseType ); ar & BOOST_SERIALIZATION_NVP( _isConnected ); ar & BOOST_SERIALIZATION_NVP( _uniqueId ); } . . . BOOST_CLASS_VERSION( WatchdogPrimaryVote, 1 ) BOOST_CLASS_EXPORT( WatchdogPrimaryVote ) BOOST_CLASS_TRACKING( WatchdogPrimaryVote, boost::serialization::track_never ) // end of file and the macro expands to: #define REGISTER_DERIVED_AND_BASE(derived, base)\ boost::serialization::void_cast_register<derived,base>((derived *)0, (base *)0) Thanks John Clayton Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.

2 1

[Boost-bugs] [ boost-Bugs-1363831 ] Documentation error for the filesystem_error class
by SourceForge.net 22 Nov '05

22 Nov '05

Bugs item #1363831, was opened at 2005-11-22 06:43 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=1363831&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: filesystem Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Beman Dawes (beman_dawes) Summary: Documentation error for the filesystem_error class Initial Comment: The documentation on the exception.hpp header indicates that filesystem_error publicly subclasses std::runtime_error. It does not. It subclasses std::exception. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1363831&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

type_traits / MPL interoperability
by David Abrahams 22 Nov '05

22 Nov '05

I just ran into a problem caused by the TR1-ization of the type traits library. I had a function defined this way: template <class T> typename is_fundamental<T>::type f(T) { return mpl::bool_< is_fundamental<T>::value >(); } that wouldn't compile. Eventually I discovered that it was because type traits now yield instances of integral_constant<T,N> (is that documented somewhere now?) integral_constant<T,N> is derived from mpl::integral_c<T,N>, but mpl::bool_<N> is not derived from integral_constant<T,N>. I can understand not wanting to introduce that sort of two-way coupling between the libraries, but it also seems like the only way to make everything work smoothly. Thoughts? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 4

[Wave] Added dll support
by Hartmut Kaiser 22 Nov '05

22 Nov '05

Hi all, This is to notify you all that I've added '<runtime-link>dynamic' support to the Wave library (as recently requested by several of you). Please check it out (Boost::HEAD) and give it a test. This was added to the V1 Jamfiles only, for now. Regards Hartmut

1 0

Re: [boost] Boost.Logging: formal review
by Matt Doyle 22 Nov '05

22 Nov '05

> [mailto:boost-bounces@lists.boost.org]On Behalf Of John Torjo > Gennadiy Rozental wrote: > > > BTW before I start, I recalled couple more issues I forgot > to mention in > > original post: > > > > 1. Design: Lightweight interface > > Log library brings a lot of dependencies. In some case I do > not want this if > > Care to exemplify? What are the dependencies? > > > I need to use the library in header. IMO log needs to > support/implement some > > lightweight debug abstract interface Something like: > > > > struct DebugLog { > > virtual void log( string const& ) = 0; > > virtual void log( int ) = 0; > > }; > > > > struct Log : DebugLog { ... }; > > > > Now I could use DebugLog interface without need to know an > implementation. > > It comes with the price of virtual call. I primarily use > this for debug only > > logging. > > Anybody else wants this? Yes, for me that would be useful. > > 3. Design: hexdump > > I believe log library needs to provide support for dumping > memory in hex > > format on log file. It could be an addon to core functionality. > > > > I can add this, even though I'm not sure why you'd want this. Yes, Yes, I use the log file for an error log. Being able to do a raw (hex) dump of the offending packet would be very useful for postmortem analysis - provided this functionality could still be available in the light-weight version :/ > > > 4. Design: logged assert > > I believe log library needs to provide support for custom > assert. Such > > assert would log into log file and invoke system assert > depends in assert > > level. It could be an addon to core functionality. > > > > Well, I want to adapt SMART_ASSERT to allow for this functionality. Kind of falls in line with what I said in #3. I want to log the recoverable errors but if it was a non-recoverable error then "log & die" would fit nicely. Kind regards, Matt Scanned by Fortigate {X3BTB534}

10 16

Boost regression notification (2005-11-21 [RC_1_33_0])
by Douglas Gregor 22 Nov '05

22 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-21T14:38:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 33 failures in 2 libraries: iostreams (32) serialization (1) |iostreams| array_test: intel-8.1-linux auto_close_test: intel-8.1-linux buffer_size_test: intel-8.1-linux bzip2_test: intel-8.1-linux code_converter_test: intel-8.1-linux component_access_test: intel-8.1-linux compose_test: intel-8.1-linux copy_test: intel-8.1-linux counter_test: intel-8.1-linux direct_adapter_test: intel-8.1-linux example_test: intel-8.1-linux file_descriptor_test: intel-8.1-linux file_test: intel-8.1-linux filtering_stream_test: intel-8.1-linux finite_state_filter_test: intel-8.1-linux flush_test: intel-8.1-linux gzip_test: intel-8.1-linux invert_test: intel-8.1-linux line_filter_test: intel-8.1-linux mapped_file_test: intel-8.1-linux newline_test: intel-8.1-linux null_test: intel-8.1-linux pipeline_test: intel-8.1-linux regex_filter_test: intel-8.1-linux restrict_test: intel-8.1-linux seekable_file_test: intel-8.1-linux seekable_filter_test: intel-8.1-linux stdio_filter_test: intel-8.1-linux symmetric_filter_test: intel-8.1-linux tee_test: intel-8.1-linux wide_stream_test: intel-8.1-linux zlib_test: intel-8.1-linux |serialization| test_nvp_text_archive: vc-8_0

3 3

Re: [boost] multi_index problem in VC 7.1
by JOAQUIN LOPEZ MU?Z 21 Nov '05

21 Nov '05

----- Mensaje original ----- De: Alexander Ivanov <amivanov(a)gmail.com> Fecha: Lunes, Noviembre 21, 2005 9:37 pm Asunto: Re: [boost] multi_index problem in VC 7.1 > I'm having trouple compiling multi_index_container<> with VC++7.1 > Wait, I think I found something... > I started from bidirectional_map example from the library > (http://www.boost.org/libs/multi_index/doc/examples.html#example4) > that compiles and works just fine. > > then i've added third tempate parameter CompareLessT to the > bidirectional map: > > template<typename FromT, typename ToT, typename CompareLessT> > struct bidir_map > { > typedef std::pair<std::string, std::string> value_type; > > typedef multi_index_container< > value_type > , indexed_by< > ordered_unique< > tag<from> > , member<value_type, FromT, &value_type::first> > , CompareLessT> > , ordered_unique< > tag<to> > , member<value_type, ToT, &value_type::second> > ^^^ Here, you are misplacing the second '>'. It should go after CompareLesstT below. > , CompareLessT > > > > type; > }; > HTH Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Re: [boost] multi_index problem in VC 7.1
by JOAQUIN LOPEZ MU?Z 21 Nov '05

21 Nov '05

----- Mensaje original ----- De: Alexander Ivanov <amivanov(a)gmail.com> Fecha: Lunes, Noviembre 21, 2005 9:37 pm Asunto: Re: [boost] multi_index problem in VC 7.1 > I'm having trouple compiling multi_index_container<> with VC++7.1 > > I started from bidirectional_map example from the library > (http://www.boost.org/libs/multi_index/doc/examples.html#example4) > that compiles and works just fine. > > then i've added third tempate parameter CompareLessT to the > bidirectional map: > > template<typename FromT, typename ToT, typename CompareLessT> > struct bidir_map > { > typedef std::pair<std::string, std::string> value_type; > > typedef multi_index_container< > value_type > , indexed_by< > ordered_unique< > tag<from> > , member<value_type, FromT, &value_type::first> > , CompareLessT> > , ordered_unique< > tag<to> > , member<value_type, ToT, &value_type::second> > > , CompareLessT > > > > type; > }; > > and it stops compiling giving me infamous INTERNAL COMPILER ERROR: > e:\edatools\boost\1.32.0\boost\mpl\aux_\preprocessed\plain\apply_wrap.hpp(48) > : fatal error C1001: INTERNAL COMPILER ERROR > (compiler file 'msc1.cpp', line 2712) > Please choose the Technical Support command on the Visual C++ > Help menu, or open the Technical Support help file for > more information > Hi Alexander. MSVC sometimes plays tricks on you, I cannot give specific advice, try shuffling things around. Sometimes, the ICE masks a real coding error, it'd help if you could post your entire snippet to see if you inadvertently missed something (some header, etc.) Joaquín M López Muñoz Telefónica, Investigación Desarrollo

2 1

Re: [boost] multi_index problem in VC 7.1
by JOAQUIN LOPEZ MU?Z 21 Nov '05

21 Nov '05

Hi Brock, ----- Mensaje original ----- De: Brock Peabody <brock.peabody(a)npcinternational.com> Fecha: Lunes, Noviembre 7, 2005 7:07 pm Asunto: [boost] multi_index problem in VC 7.1 > If I try to compile the very first example in multi index I get the > following error: > > c:\Program Files\Microsoft Visual Studio .NET > 2003\Vc7\include\boost\multi_index\detail\node_type.hpp(56) : error > C2903: 'node_class' : symbol is neither a class template nor a > functiontemplate > > I get this with 1.33 and 1.32. I've tried many different compiler > options. Here is my latest command line: > > /Ox /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "NOMINMAX" /D "_AFXDLL" /D > "_MBCS" /FD /EHsc /MD /GS /Fo"Release/" /Fd"Release/vc70.pdb" /W3 > /nologo /c /Wp64 /Zi /TP > > I've dug around a bit and I can't make any sense of this problem. Has > anyone else seen this? > > The exact code I'm compiling is: > > #include <boost/multi_index/key_extractors.hpp> > #include <boost/multi_index_container.hpp> > [...] I think you forgot to #include <boost/multi_index/ordered_index.hpp> Does this solve your problem? Similar difficulties have been reported at times here in the list, maybe I should update the doc snippets so that the necessary #include's are explicitly shown. HTH, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2

Boost 1.34.0 ?
by Rene Rivera 21 Nov '05

21 Nov '05

Since 1.33.0 has been out for a while shouldn't we bump the version on HEAD to be 1.34.0? -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

4 3

Boost regression notification (2005-11-21 [HEAD])
by Douglas Gregor 21 Nov '05

21 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-21T06:00:12Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 141 failures in 14 libraries: concept_check (13) graph (3) io (1) math (2) mpl (2) multi_array (1) parameter (12) serialization (30) spirit (2) tr1 (49) type_traits (1) typeof (18) wave (1) xpressive (6) |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 vc-7_1 vc-7_1 |graph| graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos log1p_expm1_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin zip_view: mingw-3_4_2 |multi_array| concept_checks: mingw-3_4_2 |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_has_virtual_destructor_test: intel-win32-9_0 |type_traits| has_virtual_destructor_test: intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave: vc-7_1 |xpressive| test2u: vc-7_1 test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Re: [boost] [asio] Are the _at_least_n functions useful?
by BRIDGES Dick 21 Nov '05

21 Nov '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of > Christopher Kohlhoff > Sent: Thursday, November 10, 2005 7:18 PM > To: boost(a)lists.boost.org > Subject: [boost] [asio] Are the _at_least_n functions useful? > > > Hello all, > > As part of cleaning up asio's interface I am pondering the utility of > the read_at_least_n/write_at_least_n free functions. I'd appreciate > hearing from anyone who actually uses these functions (or their async > counterparts), and anyone else who has an opinion on the matter :) [snip] > Cheers, > Chris <use_case truncated="yes"> I have done some message passing over TCP where the message headers can be fairly elaborate and there is considerable variation in message size (e.g., DIAMETER RFC 3588). Every time some traffic arrives, one of two questions get asked: "Did we get enough of the header to determine the message length?" or "Given we know the length, do we have the entire message yet?". It would be nice to move this code (and all of the associated anomaly handling) out of the application and *down* into the library. read_at_least_n would certainly be handy. </use_case> As a generalization, I'd say that those two questions get asked almost anytime discrete messages are passed over a stream protocol. <aside humorous="hopefully" sentiment="serious"> I am already using asio on [at least] two projects so I have no stake in hurrying the review process. License is Boost. Great support is available on boost(a)lists.boost.org. Packaging won't change substantially until 1.34. "Accepted" should be a *very* good bet. Take your time. ;) </aside> Regards, Dick Bridges

3 2

Link boost DLL (BOOST_ALL_DYN_LINK) ? Beginner..
by Renato Tegon Forti 21 Nov '05

21 Nov '05

Hi all, I did try use: BOOST_ALL_DYN_LINK, but I did't have success. The boost returns this to me: c:\Boost\include\boost-1_33_1\boost\config\auto_link.hpp(281): fatal error C1189: #error : "Mixing a dll boost library with a static runtime is a really bad idea..." How I fix this? My code: // BoostDefines.hpp : Defines the entry point for the console application. // //-------------------------------------------------------------------------- -- // //-------------------------------------------------------------------------- -- // Filename: BoostDefines.hpp // Type: Declaration // Language: Microsoft Visual C++ V7.1 // Module: //-------------------------------------------------------------------------- -- // Description: class BoostDefines //-------------------------------------------------------------------------- -- #ifndef BOOSTDEFINES_HPP #define BOOSTDEFINES_HPP #pragma once #define BOOST_ALL_DYN_LINK #define BOOST_THREAD_USE_DLL //thread header not compliant with 'BOOST_ALL_DYN_LINK' #define BOOST_LIB_DIAGNOSTIC #ifdef BOOST_ALL_DYN_LINK #pragma message("Include: dynamic linking with boost libraries") #endif #endif //BOOSTDEFINES_HPP // test.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include "BoostDefines.hpp" #include <boost/lexical_cast.hpp> #include <boost/regex.hpp> int _tmain(int argc, _TCHAR* argv[]) { //... //use boost //... return 0; }

2 1

c++/cli boost subproject?
by relative＠gmx.net 21 Nov '05

21 Nov '05

is there, or are there plans for, a boost c++/cli subproject? i've played around with boost and the cli compiler, a lot of libraries work with unmanaged data types (with a lot of warnings, but work), others don't. none work with managed data types of course although that wouldn't be a big problem I suppose. (e.g. boost::tuple) the spec is there, at least one compiler exists(mono?) and there is a STL called STL.NET by dinkumware(distributed by microsoft) for c++/cli. I haven't found anything on the website or the mailing list archives, is this beyond the scope of the boost project? -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen f�r GMX Partner: http://www.gmx.net/de/go/partner

7 10

boost::thread - mistake in documentation
by Oliver.Kowalke＠infineon.com 21 Nov '05

21 Nov '05

Hello, the documentation (http://www.boost.org/doc/html/condition.html) of class condition contains a mistake: instead of template<typename ScopedLock, typename Pred> bool timed_wait <http://www.boost.org/doc/html/condition.html> (ScopedLock&, Pred); it should be template<typename ScopedLock, typename Pred> bool timed_wait <http://www.boost.org/doc/html/condition.html> (ScopedLock&, const boost::xtime <http://www.boost.org/doc/html/xtime.html> & , Pred); so long, Oliver

1 0

contribution - sync. queue between producer/consumer threads
by Oliver.Kowalke＠infineon.com 21 Nov '05

21 Nov '05

Hello, I would contribute this code. The queue synchronizes the access between producer threads (putting items into the queue) and consumer threads (removing items from queue). I would be glad if you add this code to boost::thread library. With regards, Oliver <<queue.hpp>> <<test.cpp>>

1 0

Re: [boost] [multi_index] ordered_index should be noncopyable?
by JOAQUIN LOPEZ MU?Z 21 Nov '05

21 Nov '05

----- Mensaje original ----- De: Dylan Trotter <trotterdylan(a)yahoo.ca> Fecha: Domingo, Noviembre 20, 2005 8:17 pm Asunto: [boost] [multi_index] ordered_index should be noncopyable? > I just had a really irritating time tracking down bad memory access > in > ordered_index because I foolishly wrote something like this: > > typedef client_set::nth_index<0>::type address_index_type; > address_index_type addressIndex = clients_.get<0>(); > address_index_type::iterator iter = addressIndex.find(addr); > > The problem here is that I got my addressIndex by value in the > second > line. I may be overlooking something here, but I think it might be > useful to make ordered_index noncopyable so that this would be > detected > at compile time instead of runtime. I nearly threw my monitor out > the > window over this one. > Hi Dylan, I'm sorry you had a hard time with that. The truth is, indices are not copyable; moreover, I comment on this very mistake you have stumbled upon at the end of the following section: http://boost.org/libs/multi_index/doc/tutorial.html#multipe_sort So, how come you can compile even when the docs state you shouldn't? The problem is that some compilers have problems with template friends (signaled by Boost.Config macro BOOST_NO_MEMBER_TEMPLATE_FRIENDS) that force me to make (on these compilers only) some internal index ctors public, hence your problem. What compiler are you using? MSVC 6.5/7.x/8.0 all have this problem. Most others don't, and on those a nice compiler error would have popped up when compiling your snippet. Again, I'm sorry for the time you might have wasted. At least, you have refrained from throwing the monitor out of the window :) Thanx for using Boost.MultiIndex. Best, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Re: [boost] [serialization] fast array serialization (10x speedup)
by bwood 21 Nov '05

21 Nov '05

Matthias Troyer wrote: >> >> i) somehow I doubt that this archive type has been tested with all >> the serialization test suite. Instructions for doing so are in the >> documenation and the serialization/test directory includes batch files >> for doing this with one's own archives. Was this done? What where >> the >> results? With which compiler? It costs nothing to do this. > > >Just ask if you had a doubt. The short answer is "I have done this". >After adding the fast array serialization to the binary and >polymorphic archives, I ran all your regression tests, without any >problem (using gcc 4 under MacOS X). Have you done this with vector also? I would be surprised if you have. It seems to me there is a standards issue to be addressed in this area. It is no problem to send the data in a vector of int as a unit, but I don't know of a way to add/receive the data into a vector correctly. It is possible to stuff the data into the correct place, but the vector's internal state/size does not get set properly since you didn't call push_back or some other method to get the data into place. Adding something like push_n_back to vector might help when it comes this. Brian www.webEbenezer.net

2 1

[multi_index] ordered_index should be noncopyable?
by Dylan Trotter 20 Nov '05

20 Nov '05

I just had a really irritating time tracking down bad memory access in ordered_index because I foolishly wrote something like this: typedef client_set::nth_index<0>::type address_index_type; address_index_type addressIndex = clients_.get<0>(); address_index_type::iterator iter = addressIndex.find(addr); The problem here is that I got my addressIndex by value in the second line. I may be overlooking something here, but I think it might be useful to make ordered_index noncopyable so that this would be detected at compile time instead of runtime. I nearly threw my monitor out the window over this one. Thanks, Dylan Trotter

1 0

serialization - NaN, +/Inf and others
by Robert Ramey 20 Nov '05

20 Nov '05

Troy S. and I have been looking at the question of implementing serialization of NaN, +/-Inf for floats, and doubles for portable text or binary archives. Turns out there's a fly in the ointment. For determining if a given double contains a "special" value, float.h contains the following handy function int _fpclass( double x ); which returns one of the following values: _FPCLASS_SNAN Signaling NaN _FPCLASS_QNAN Quiet NaN _FPCLASS_NINF Negative infinity ( -INF) _FPCLASS_NN Negative normalized non-zero _FPCLASS_ND Negative denormalized _FPCLASS_NZ Negative zero ( - 0) _FPCLASS_PZ Positive 0 (+0) _FPCLASS_PD Positive denormalized _FPCLASS_PN Positive normalized non-zero _FPCLASS_PINF Positive infinity (+INF) So we could write a flag to the archive indicating if its a special value. So far, so good. When the archive is read back, we can read the flag and initialize the variable with the appropriate value. BUT - I can't find any "official" to initialize a float/double to any of these values. They seem to be the result of operations and its certainly not obvious that all compilers would be on the same page here. Note that this same problem arises whenever a float/double is written/read to/from a stream in a way designed to be portable. So it must have come up before. What's the solution here? Robert Ramey

6 6

which libs to use for g++ 2.95
by PerzonalJezus 19 Nov '05

19 Nov '05

Hi. I´ve written an app using g++ 3 which uses the BGL. Now I need to compile my stuff (and make changes to the code if necessary) for g++ 2.95. Which version of the BGL lib (and any other boost lib for that matter) work with g++ 2.95? Thanks for any answer. Ed. PS: I´ve searched but haven´t found any helpful posts... -- perzonaljezus

1 0

[Boost-bugs] [ boost-Bugs-1361730 ] Problems in regex in MS Visual Studio.NET 2005
by SourceForge.net 19 Nov '05

19 Nov '05

Bugs item #1361730, was opened at 2005-11-20 00:24 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=1361730&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: regex Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mighty BOBKA (mbobka) Assigned to: John Maddock (johnmaddock) Summary: Problems in regex in MS Visual Studio.NET 2005 Initial Comment: When I try to run this code: #include "stdafx.h" #define BOOST_REGEX_MATCH_EXTRA #include <boost\regex.hpp> int _tmain(int argc, _TCHAR* argv[]) { boost::regex re( "^(?:(.+?),)*(.+?)$" ); boost::cmatch matches; if( boost::regex_match( "hello", matches, re ) ) { for( boost::cmatch::iterator pos = matches.begin() + 1; pos != matches.end(); pos++ ) { } return 1; } return 0; } compiled by Visual Studio.NET 2005, assertion will be failed at boost_1_33_1_beta\boost/regex/v4/match_results.hpp, line 282 (Assertion failed: pos+2 < m_subs.size()). If I undefine BOOST_REGEX_MATCH_EXTRA, then all is OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1361730&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Bugs-1361686 ] [Boost.Range]boost::const_begin calls non-qualified 'begin'
by SourceForge.net 19 Nov '05

19 Nov '05

Bugs item #1361686, was opened at 2005-11-20 05:13 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=1361686&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: MB (mb2sync) Assigned to: Nobody/Anonymous (nobody) Summary: [Boost.Range]boost::const_begin calls non-qualified 'begin' Initial Comment: boost::const_begin calls non-qualified 'begin'. So it triggers unintended ADL. boost::const_end also calls 'end' without qualification. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1361686&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Bugs-1361625 ] is_empty sets my paths' _M_p to 0xffffffff
by SourceForge.net 19 Nov '05

19 Nov '05

Bugs item #1361625, was opened at 2005-11-19 10:44 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=1361625&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: filesystem Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Beman Dawes (beman_dawes) Summary: is_empty sets my paths' _M_p to 0xffffffff Initial Comment: Env: FreeBSD 5.4 gcc 3.4.2 boost: 1.33.0 Before calling is_empty on a valid dir, I have a path with _M_p set to a valid address. After calling is_empty _M_p points to 0xffffffff In libs/filesystem/src/operations_posix_windows.cpp we have the dir_itr_init function at line 273. At linie 302 it calls: m_imp->entry_path.m_path_append( "dummy", no_check ); When returning from this function _M_p is no longer valid (points to 0xffffffff). I'm guessing more info is needed, so you are welcome to write me and I will help in any way I can. Best regards db ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1361625&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] "Re: serialization performance"
by bwood 19 Nov '05

19 Nov '05

A few days ago I posted some numbers that compared the build times between Boost.serialization and Ebenezer Enterprises. http://lists.boost.org/Archives/boost/2005/11/96781.php Since then I realized I made a mistake in those tests. Originally, I said it took 42 seconds for the Boost version of the "list<int>" test to build. That should have been 27 seconds. I had a file included in the original test that was not needed. The time with the webEbenezer version didn't change - it is 12 seconds. I rechecked the "list<int> and deque<int>" test and those numbers didn't change. Sorry about that. Brian

1 0

backtrace library
by Neal Becker 19 Nov '05

19 Nov '05

We had discussed here some time ago a desire for obtaining nice human readable backtraces, perhaps to use with logging or with testing. I just saw this and I think it may be helpful: http://freshmeat.net/redir/libebt/61646/url_homepage/libebt.berlios.de

2 1

Re: [boost] [serialization] portability
by Martin Bonner 19 Nov '05

19 Nov '05

----Original Message---- From: troy d. straszheim [mailto:troy@resophonic.com] Sent: 18 November 2005 11:41 > > But floats and doubles are no problem. They have the same size and > layout whereever you are, and since you're just flipping bytes and > writing/loading binary, you don't have to worry about NaN or inf or > any of that, the archive remains blissfully ignorant. IBM format? VAX floating point? (Not forgetting that the VAX had TWO 64-bit floating point types :-) -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

4 4

VC++ compiler error with boost graph library
by Chris Alvers 19 Nov '05

19 Nov '05

Hi, I tried to do a depth_first_search with the following graph type and visitor: struct CycleDetector : public boost::default_dfs_visitor { CycleDetector( bool& cycle ) : m_hasCycle(cycle) {}; void back_edge( T_Edge, const T_Graph& ) { m_hasCycle = true; } bool& m_hasCycle; }; typedef boost::adjacency_list< boost::setS, boost::listS, boost::bidirectionalS> T_Graph; bool hasCycle(false); CycleDetector cd(hasCycle); boost::depth_first_search(m_graph, visitor(cd)); Compiling this on VC++ 7.1.3 (.NET Framework 1.1) results in the following error message: \boost\boost\property_map.hpp(349): error C2678: binary '+' : no operator found which takes a left-hand operand of type 'const std::vector<_Ty>::iterator' (or there is no acceptable conversion) with [ _Ty=boost::default_color_type ] ---------------------- Changing the graph type definition to: typedef boost::adjacency_list< boost::setS, boost::vecS, boost::bidirectionalS> T_Graph; (i.e. replacing the listS by vecS) works perfectly. Is this a known restriction of the library ? Best regards Alex ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

3 2

Bug list status
by Marshall Clow 18 Nov '05

18 Nov '05

Five weeks ago: 144 open bugs Four weeks ago: 117 open bugs Three weeks ago: 96 open bugs Two weeks ago: 94 open bugs Last week: 93 open bugs Today: 95 open bugs. We've stopped making progress; in fact, we're regressing! Please look at the bugs assigned to you! If you think that a bug has been assigned incorrectly, please let me know. Here are the currently opened bugs, sorted by assignee. Doug Gregor 17 Mike Glassford 14 Beman Dawes 12 John R. Bandela 7 Stephen Cleary (shammah) 6 Jonathan Turkanis 5 Rene Rivera (grafik) 4 Joerg Walter 4 Jeff Garland (az_sw_dude) 3 Joel de guzman (djowel) 3 Eric Friedman (ebf) 2 Jeremy Siek 2 Mark Rodgers 2 <nobody> 2 Robert Ramey 2 Gennadiy Rozental (rogeeff) 2 Vladimir Prus 2 Kevlin Henney 1 Jens Maurer 1 John Maddock 1 Thorsten Ottosen (nesotto) 1 Samuel Kremp 1 Darryl Walker 1 P.S. I need someone to fix the bugs in the tokenizer library. Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: wrong usage of ios_base::narrow Bug #: 989487 <http://sourceforge.net/tracker/index.php?func=detail&aid=989487&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: date_time type conversion warning Bug #: 1069225 <http://sourceforge.net/tracker/index.php?func=detail&aid=1069225&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: local_adjustor::utc_to_local throws 'Time label invalid' Bug #: 1220011 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220011&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesytem::directory_iterator portability Bug #: 735403 <http://sourceforge.net/tracker/index.php?func=detail&aid=735403&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem fails in posix with files containing ':' Bug #: 776146 <http://sourceforge.net/tracker/index.php?func=detail&aid=776146&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: clock is not portable Bug #: 788762 <http://sourceforge.net/tracker/index.php?func=detail&aid=788762&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Boost::Filesystem fails when last character in path is ':' Bug #: 875970 <http://sourceforge.net/tracker/index.php?func=detail&aid=875970&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesystem::directory_iterator returns incorrect listing Bug #: 937606 <http://sourceforge.net/tracker/index.php?func=detail&aid=937606&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: xtime_cmp: use comparison not subtraction Bug #: 993272 <http://sourceforge.net/tracker/index.php?func=detail&aid=993272&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists is broken on cygwin Bug #: 1010681 <http://sourceforge.net/tracker/index.php?func=detail&aid=1010681&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem is systematically broken Bug #: 1012135 <http://sourceforge.net/tracker/index.php?func=detail&aid=1012135&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::native() should reject '/' on non-Win32 Bug #: 1151823 <http://sourceforge.net/tracker/index.php?func=detail&aid=1151823&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists has bugs with UNC paths Bug #: 1164057 <http://sourceforge.net/tracker/index.php?func=detail&aid=1164057&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::equivalent does not work on w98 Bug #: 1235262 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235262&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: path and directory_iterator doesn't handle windows root path Bug #: 1259176 <http://sourceforge.net/tracker/index.php?func=detail&aid=1259176&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: no conversion from type to const_type Bug #: 547743 <http://sourceforge.net/tracker/index.php?func=detail&aid=547743&group_id=75…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = setS for adjacency_list does not work Bug #: 1163077 <http://sourceforge.net/tracker/index.php?func=detail&aid=1163077&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: adjacency_matrix should model BidirectionalGraph Bug #: 1168411 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168411&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors for undirected graphs Bug #: 1168420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA adaptors for node_array, edge_array Bug #: 1168424 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168424&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors do not handle hidden nodes properly Bug #: 1168431 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168431&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Generate patches for Graph bugs in 1.32.0 Bug #: 1169920 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169920&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Investigate other kinds of heaps for dijkstra_shortest_paths Bug #: 1170106 <http://sourceforge.net/tracker/index.php?func=detail&aid=1170106&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: function.hpp breaks assign.hpp Bug #: 1181272 <http://sourceforge.net/tracker/index.php?func=detail&aid=1181272&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: vertex bundle properties do not work with VC++.NET 2003 Bug #: 1190394 <http://sourceforge.net/tracker/index.php?func=detail&aid=1190394&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: BGL graph types do not support allocators Bug #: 1193883 <http://sourceforge.net/tracker/index.php?func=detail&aid=1193883&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: random_vertex/random_edge are unnecessarily inefficient Bug #: 1204684 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204684&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Document copy_component Bug #: 1204688 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204688&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: reverse_graph and constness of property maps Bug #: 1246336 <http://sourceforge.net/tracker/index.php?func=detail&aid=1246336&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: html docs frequently missing key words Bug #: 1294420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1294420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = has_setS for adjacency_list does not work Bug #: 1352049 <http://sourceforge.net/tracker/index.php?func=detail&aid=1352049&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: predicates without default constructor fail to compile (2) Bug #: 1353875 <http://sourceforge.net/tracker/index.php?func=detail&aid=1353875&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Miss ' = ParserT()' Bug #: 907299 <http://sourceforge.net/tracker/index.php?func=detail&aid=907299&group_id=75…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: spirit insert_key_actor.hpp Bug #: 1059936 <http://sourceforge.net/tracker/index.php?func=detail&aid=1059936&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Another config correction for Sun C++ Bug #: 1220782 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220782&group_id=7…> Assignee: dlwalker <http://sourceforge.net/users/dlwalker/> Summary: template problems with common_factor.hpp Bug #: 491637 <http://sourceforge.net/tracker/index.php?func=detail&aid=491637&group_id=75…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: boost::blank - missing operators Bug #: 1191356 <http://sourceforge.net/tracker/index.php?func=detail&aid=1191356&group_id=7…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: [variant] Bug in recursive_wrapper_fwd.hpp Bug #: 1359257 <http://sourceforge.net/tracker/index.php?func=detail&aid=1359257&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl to_duration() nsec error Bug #: 548104 <http://sourceforge.net/tracker/index.php?func=detail&aid=548104&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Solaris - once.cpp compile error Bug #: 549162 <http://sourceforge.net/tracker/index.php?func=detail&aid=549162&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: pthread_delay_np() parm incorrect Bug #: 551157 <http://sourceforge.net/tracker/index.php?func=detail&aid=551157&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Bosot.Thread.condition(win32).notify_all Bug #: 551308 <http://sourceforge.net/tracker/index.php?func=detail&aid=551308&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: AIX 4.3 SIGSEGV at thread termination Bug #: 551577 <http://sourceforge.net/tracker/index.php?func=detail&aid=551577&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: boost::threads uses msvc only function? Bug #: 568951 <http://sourceforge.net/tracker/index.php?func=detail&aid=568951&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: threads unnecessary #include Bug #: 571615 <http://sourceforge.net/tracker/index.php?func=detail&aid=571615&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: BCB6 throw EExternelException Bug #: 596149 <http://sourceforge.net/tracker/index.php?func=detail&aid=596149&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: thread_cleanup problems Bug #: 649291 <http://sourceforge.net/tracker/index.php?func=detail&aid=649291&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Mac implementation of threads is CPU hog Bug #: 885045 <http://sourceforge.net/tracker/index.php?func=detail&aid=885045&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: condition variables and recursive_mutex Bug #: 1072605 <http://sourceforge.net/tracker/index.php?func=detail&aid=1072605&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: compiler error on Mac implementation of threads Bug #: 1201779 <http://sourceforge.net/tracker/index.php?func=detail&aid=1201779&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl line 116 copy/paste error Bug #: 1239052 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239052&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Exception safety in class 'thread' Bug #: 1305885 <http://sourceforge.net/tracker/index.php?func=detail&aid=1305885&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: 'failed fileclone' when building with -j on 1.32.0 Bug #: 1102389 <http://sourceforge.net/tracker/index.php?func=detail&aid=1102389&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: boost jam problem with parallel builds Bug #: 1234224 <http://sourceforge.net/tracker/index.php?func=detail&aid=1234224&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: crach build bjam from mingw 3.4.4 Bug #: 1341560 <http://sourceforge.net/tracker/index.php?func=detail&aid=1341560&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: crach build bjam from mingw 3.4.4 with python Bug #: 1341568 <http://sourceforge.net/tracker/index.php?func=detail&aid=1341568&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer fails with wchar_t Bug #: 446155 <http://sourceforge.net/tracker/index.php?func=detail&aid=446155&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer not works with Dinkumware 308 Bug #: 458236 <http://sourceforge.net/tracker/index.php?func=detail&aid=458236&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: boost::tokenizer implicit typename Bug #: 912368 <http://sourceforge.net/tracker/index.php?func=detail&aid=912368&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Tokenizer.hpp doesn't work with BOOST_ENABLE_ASSERT_HANDLER Bug #: 972406 <http://sourceforge.net/tracker/index.php?func=detail&aid=972406&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Compiler error for tokenizer on Solaris Bug #: 976241 <http://sourceforge.net/tracker/index.php?func=detail&aid=976241&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer and signed char Bug #: 1003889 <http://sourceforge.net/tracker/index.php?func=detail&aid=1003889&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: token_iterator::at_end() result is inversed Bug #: 1338326 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338326&group_id=7…> Assignee: jmaurer <http://sourceforge.net/users/jmaurer/> Summary: Diff in state of mersenne_twister gen between GCC3.41 & CW9 Bug #: 1115124 <http://sourceforge.net/tracker/index.php?func=detail&aid=1115124&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: bug in ublas/storage.hpp Bug #: 1095697 <http://sourceforge.net/tracker/index.php?func=detail&aid=1095697&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: dead links in uBLAS page Bug #: 1169273 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169273&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: Documentation not available on web site: Bug #: 1228242 <http://sourceforge.net/tracker/index.php?func=detail&aid=1228242&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: uBLAS::subslice doesn't work Bug #: 1292635 <http://sourceforge.net/tracker/index.php?func=detail&aid=1292635&group_id=7…> Assignee: johnmaddock <http://sourceforge.net/users/johnmaddock/> Summary: Adding boost::is_complex to type_traits.hpp Bug #: 1315712 <http://sourceforge.net/tracker/index.php?func=detail&aid=1315712&group_id=7…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: invalid result for File Dependency Examp Bug #: 551110 <http://sourceforge.net/tracker/index.php?func=detail&aid=551110&group_id=75…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: Spelling of Edmonds-Karp-Algorithm Bug #: 1226292 <http://sourceforge.net/tracker/index.php?func=detail&aid=1226292&group_id=7…> Assignee: kevlin <http://sourceforge.net/users/kevlin/> Summary: lexical_cast & pure virtual functions & VC 8 STL Bug #: 1358600 <http://sourceforge.net/tracker/index.php?func=detail&aid=1358600&group_id=7…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751269 <http://sourceforge.net/tracker/index.php?func=detail&aid=751269&group_id=75…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751289 <http://sourceforge.net/tracker/index.php?func=detail&aid=751289&group_id=75…> Assignee: nesotto <http://sourceforge.net/users/nesotto/> Summary: boost.range and 'const char[]'. Bug #: 1272315 <http://sourceforge.net/tracker/index.php?func=detail&aid=1272315&group_id=7…> Assignee: nobody Summary: failure in boost jam unit tests on cygwin Bug #: 940941 <http://sourceforge.net/tracker/index.php?func=detail&aid=940941&group_id=75…> Assignee: nobody Summary: Can't build on cygwin Bug #: 1145183 <http://sourceforge.net/tracker/index.php?func=detail&aid=1145183&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: Compiler warning with gcc on Linux Bug #: 1337412 <http://sourceforge.net/tracker/index.php?func=detail&aid=1337412&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: warning caused by size_t to unsigned int conversion on vc++8 Bug #: 1338178 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338178&group_id=7…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: typo in Boost.Test document Bug #: 629685 <http://sourceforge.net/tracker/index.php?func=detail&aid=629685&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: Don't work multilevel hierarchy of test suites in dll. Bug #: 1076691 <http://sourceforge.net/tracker/index.php?func=detail&aid=1076691&group_id=7…> Assignee: samuel_k <http://sourceforge.net/users/samuel_k/> Summary: format: assert when parsing invalid pattern Bug #: 1326132 <http://sourceforge.net/tracker/index.php?func=detail&aid=1326132&group_id=7…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: ct_gcd_lcm.hpp compilation error Bug #: 558174 <http://sourceforge.net/tracker/index.php?func=detail&aid=558174&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: test_pool_alloc.cpp not compile CW8.1 Bug #: 586779 <http://sourceforge.net/tracker/index.php?func=detail&aid=586779&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: pool::purge_memory() does not reset next_size Bug #: 984124 <http://sourceforge.net/tracker/index.php?func=detail&aid=984124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: Borland compiler error with Pool, boost::pool_allocator Bug #: 988124 <http://sourceforge.net/tracker/index.php?func=detail&aid=988124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: perfomance: memory cleanup for pool takes too long Bug #: 995270 <http://sourceforge.net/tracker/index.php?func=detail&aid=995270&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: boost::pool_allocator breaks with vector of vectors Bug #: 1179641 <http://sourceforge.net/tracker/index.php?func=detail&aid=1179641&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Self division wrong in template rational Bug #: 504411 <http://sourceforge.net/tracker/index.php?func=detail&aid=504411&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Rational sum not optimal for overflows Bug #: 519635 <http://sourceforge.net/tracker/index.php?func=detail&aid=519635&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: rational operator&lt; can overflow Bug #: 798357 <http://sourceforge.net/tracker/index.php?func=detail&aid=798357&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: boost::rational documentation typos(?) Bug #: 1043616 <http://sourceforge.net/tracker/index.php?func=detail&aid=1043616&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: no Boolean conversion for boost::rational Bug #: 1239906 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239906&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: call to split_winmain raises exception for 8-bit locale Bug #: 1206663 <http://sourceforge.net/tracker/index.php?func=detail&aid=1206663&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: multitoken broken in program_options 1.33 Bug #: 1266877 <http://sourceforge.net/tracker/index.php?func=detail&aid=1266877&group_id=7…> -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

4 5

Re: [boost] asio networking proposal 0.3.5
by Moore, J. David 18 Nov '05

18 Nov '05

While the supported platforms says gcc 3.3 and higher, I had no trouble with linux (2.4 and 2.6), gcc 3.2.3, with the exception of the http server example. The error is below, which is pretty easy to work around. if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"asio\" -DVERSION=\"0.3.5\" -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -I. -I. -I/home/servicesot/ThirdParty/boost/include/boost-1_33/ -I./../include -g -O2 -pthread -ftemplate-depth-256 -MT examples/http/server/mime_types.o -MD -MP -MF "$depbase.Tpo" -c -o examples/http/server/mime_types.o examples/http/server/mime_types.cpp; \ then mv -f "$depbase.Tpo" "$depbase.Po"; else rm -f "$depbase.Tpo"; exit 1; fi examples/http/server/mime_types.cpp: In function `std::string http::server::mime_types::extension_to_type(const std::string&)': examples/http/server/mime_types.cpp:36: no matching function for call to ` find_type(http::server::mime_types::mapping[5], const std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)' -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Christopher Kohlhoff Sent: Friday, November 18, 2005 7:06 AM To: boost(a)lists.boost.org Subject: [boost] asio networking proposal 0.3.5 Hello all, I have just released asio 0.3.5. You can download it, or view the documentation online, at http://asio.sourceforge.net. The download page includes packages named boost-asio-proposal-*, which contain a version of asio converted into boost format. You can copy the contents of one of these into a boost_1_33_0 distribution and build it there, but it should also support building in its own directory, provided you set a BOOST_ROOT environment variable. The Jamfiles are a little rough, but they should work in theory. The size of the release is actually less than 0.3.4, which I think is a good sign :) In detail, the changes since asio 0.3.4 include: - Consolidated the free functions read(), read_n() and read_at_least_n() into a function named read(); write(), write_n() and write_at_least_n() into just write(); and likewise for their asynchronous counterparts. The default behaviour of read() and write() is now to attempt to transfer all of the data (i.e. equivalent to old read_n() and write_n()). The _at_least_n() behaviour can be obtained by passing a Completion_Condition function object: asio::read(s, bufs, asio::transfer_at_least(32)); - Renamed the Stream concept's read(), async_read(), write() and async_write() functions to read_some(), async_read_some(), write_some() and async_write_some() respectively. This was done to make it obvious to a library user that the operation can result in a short read or write. The name write() in particular was found to be error prone, since most of the time it will successfully transfer all of the data. Only occasional calls would result in a short write, leading to hard to find bugs. - Graceful connection closure now causes a read to complete with an error code (asio::error::eof) rather than returning 0. This removes the need for separate total_bytes_transferred and last_bytes_transferred handler parameters. It allows a function, such as asio::read() and asio::write(), to return an error to indicate that it is unable to fulfil its contract due to EOF. - Removed the asio::buffers() function and the ability to automatically chain buffer objects together. Instead, the asio::buffer() function now returns a type that meets the Const_Buffers or Mutable_Buffers concepts as appropriate. Scatter-gather I/O should now be performed by explicitly placing const_buffer or mutable_buffer objects into a container (such as std::vector, std::list or boost::array). To read into a single buffer you would now write: sock.read(asio::buffer(data, length)); To send multiple buffers you would use something like: std::vector<asio::const_buffer> bufs; bufs.push_back(asio::buffer(data1, length1)); bufs.push_back(asio::buffer(data2, length2)); sock.write(bufs); - Added comparison operators to the asio::ipv4::tcp::endpoint and asio::ipv4::udp::endpoint classes. - Removed the error handling expression templates. This functionality is better covered by a library such as Boost.Lambda. - Removed the fixed_buffer class from the library's public interface. The underlying buffer storage is no longer a template parameter on the buffered*_stream classes. - Removed the wrapped_handler class from the library's public interface. - Removed the consuming_buffers class from the libary's public interface. - Added new certificates for the SSL example, as the original ones expired after one month. - Used implementation-defined types rather than void* in the Socket_Option and IO_Control_Command concepts to avoid losing type safety. - Various code cleanup and bug fixes. - Added support for MSVC 8.0. - Documentation improvements. Cheers, Chris _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

1 0

asio networking proposal 0.3.5
by Christopher Kohlhoff 18 Nov '05

18 Nov '05

Hello all, I have just released asio 0.3.5. You can download it, or view the documentation online, at http://asio.sourceforge.net. The download page includes packages named boost-asio-proposal-*, which contain a version of asio converted into boost format. You can copy the contents of one of these into a boost_1_33_0 distribution and build it there, but it should also support building in its own directory, provided you set a BOOST_ROOT environment variable. The Jamfiles are a little rough, but they should work in theory. The size of the release is actually less than 0.3.4, which I think is a good sign :) In detail, the changes since asio 0.3.4 include: - Consolidated the free functions read(), read_n() and read_at_least_n() into a function named read(); write(), write_n() and write_at_least_n() into just write(); and likewise for their asynchronous counterparts. The default behaviour of read() and write() is now to attempt to transfer all of the data (i.e. equivalent to old read_n() and write_n()). The _at_least_n() behaviour can be obtained by passing a Completion_Condition function object: asio::read(s, bufs, asio::transfer_at_least(32)); - Renamed the Stream concept's read(), async_read(), write() and async_write() functions to read_some(), async_read_some(), write_some() and async_write_some() respectively. This was done to make it obvious to a library user that the operation can result in a short read or write. The name write() in particular was found to be error prone, since most of the time it will successfully transfer all of the data. Only occasional calls would result in a short write, leading to hard to find bugs. - Graceful connection closure now causes a read to complete with an error code (asio::error::eof) rather than returning 0. This removes the need for separate total_bytes_transferred and last_bytes_transferred handler parameters. It allows a function, such as asio::read() and asio::write(), to return an error to indicate that it is unable to fulfil its contract due to EOF. - Removed the asio::buffers() function and the ability to automatically chain buffer objects together. Instead, the asio::buffer() function now returns a type that meets the Const_Buffers or Mutable_Buffers concepts as appropriate. Scatter-gather I/O should now be performed by explicitly placing const_buffer or mutable_buffer objects into a container (such as std::vector, std::list or boost::array). To read into a single buffer you would now write: sock.read(asio::buffer(data, length)); To send multiple buffers you would use something like: std::vector<asio::const_buffer> bufs; bufs.push_back(asio::buffer(data1, length1)); bufs.push_back(asio::buffer(data2, length2)); sock.write(bufs); - Added comparison operators to the asio::ipv4::tcp::endpoint and asio::ipv4::udp::endpoint classes. - Removed the error handling expression templates. This functionality is better covered by a library such as Boost.Lambda. - Removed the fixed_buffer class from the library's public interface. The underlying buffer storage is no longer a template parameter on the buffered*_stream classes. - Removed the wrapped_handler class from the library's public interface. - Removed the consuming_buffers class from the libary's public interface. - Added new certificates for the SSL example, as the original ones expired after one month. - Used implementation-defined types rather than void* in the Socket_Option and IO_Control_Command concepts to avoid losing type safety. - Various code cleanup and bug fixes. - Added support for MSVC 8.0. - Documentation improvements. Cheers, Chris

1 0

Help setting up boost for vc7
by Marcelo Juchem 18 Nov '05

18 Nov '05

Hi, I had some problems when trying to build boost-jam under WinXP SP2 with MSVC7.1. I searched the boost mailing list and found this message: "I have MS VC++ 7.1 installed to the default location (C:\Program Files\Microsoft Visual Studio .NET 2003), O/S WinXPSP2 However, when I run Build.bat from the command line, it returns " \Utilities\Bin\x86 was unexpected at this time." This occurs if I let the script auto-detect and also if I specify the toolset as vc7. Can someone please steer me in the right direction? regards Chris Ward" By debbuging the build.bat script, I could figure out what the problem is. It seems to be a problem with PATH environment variables that contains parenthesis '(' or ')'. This is the PATH I had when the problem occurred: "PATH=C:\Program Files\Microsoft DirectX 9.0 SDK (October 2005)\Utilities\Bin\x86;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\cygwin\bin;C:\Program Files\Common Files\GTK\2.0\bin;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin" Just by removing "C:\Program Files\Microsoft DirectX 9.0 SDK (October 2005)", the build.bat script started working perfectly. This is caused because all the variables are expanded inline in a .bat file, so the parenthesis are understood as scope delimiters and messes up with the if () statements as in: if not "_%BOOST_JAM_TOOLSET_ROOT%_" == "__" ( set PATH=%BOOST_JAM_TOOLSET_ROOT%Other Metrowerks Tools\Command Line Tools;%PATH%) This code is expanded as if not "_%BOOST_JAM_TOOLSET_ROOT%_" == "__" ( set PATH=c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\\..\..\VC7\Other Metrowerks Tools\Command Line Tools;C:\Program Files\Microsoft DirectX 9.0 SDK (October 2005)\Utilities\Bin\x86;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\cygwin\bin;C:\Program Files\Common Files\GTK\2.0\bin;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin) what leaves the script broken. I hope I could be able to make myself clear when trying to explain this. A quick workaround is to remove paths that contains parenthesis from the PATH environment variable, before running the script. Thanks, Marcelo Juchem

1 0

help naming new library (math / computer science experts needed)
by Eric Niebler 18 Nov '05

18 Nov '05

I am working on a new library. It is a computational framework where the computations follow the following pattern: - Users build a computational object by selecting the computations they are interested in (or author their own computational primimtives which fit within the framework). - Users push data into the object one sample at a time - The object computes the requested quantities in the most efficient method possible (resolving dependencies between requested calculations, cacheing intermediate results, etc.) - The object may or may not be stateful. What should such a library be called? Is there an accepted term for such a computational model? -- Eric Niebler Boost Consulting www.boost-consulting.com

6 5

Re: [boost] [parameter] - catching accidental duplicate parameters at compile time
by Daniel Earwicker 18 Nov '05

18 Nov '05

David Abrahams: > On conforming compilers, the library uses overloading to look up the > value associated with any given keyword. I assumed that having two of > the same keyword would cause an ambiguity error at lookup time: 7.3.3/12 of the standard appears to deal with this: "When a using-declaration brings names from a base class into a derived class scope, member functions in the derived class override and/or hide member functions with the same name and parameter types in a base-class (rather than conflicting)." i.e. a working model of the same keyword twice on an arg_list: struct keyword {}; struct base { int operator[](const keyword &) { return 1; } }; struct derived : public base { using base::operator[]; int operator[](const keyword &) { return 2; } }; int main() { return derived()[keyword()]; } > The problem with this (aside from the use of an ALL_CAPS name for > something other than a macro) Thanks for the tip! > is that it costs O(N^2) instantiations, > where N is the number of arguments. OTOH you could do it with > overloading (or just use an mpl::set, which uses overloading > internally) to do it in O(N). Oooh, that's much better. With used_keywords as an empty set in empty_arg_list, all it needs in arg_list is: BOOST_STATIC_ASSERT((!boost::mpl::has_key< typename Next::used_keywords, key_type>::type::value)); typedef typename mpl::insert<typename Next::used_keywords, key_type>::type used_keywords; Or is there already something that captures the above pattern, i.e. refuses to insert a duplicate? --Daniel.

3 9

[Boost-bugs] [ boost-Bugs-1359257 ] [variant] Bug in recursive_wrapper_fwd.hpp
by SourceForge.net 17 Nov '05

17 Nov '05

Bugs item #1359257, was opened at 2005-11-17 12:13 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=1359257&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [variant] Bug in recursive_wrapper_fwd.hpp Initial Comment: I've been tracking down an preprocessor warning involving the redefinition of BOOST_TT_AUX_BOOL_TRAIT_DEF1. It appears to me that variant/recursive_wrapper_fwd.hpp is misusing: #include "boost/type_traits/detail/bool_trait_def.hpp" The usual include pattern for this header is: // should be the last #include #include "boost/type_traits/detail/bool_trait_def.hpp" ... #include "boost/type_traits/detail/bool_trait_undef.hpp" But recursive_wrapper_fwd.hpp has: #include "boost/type_traits/detail/bool_trait_def.hpp" #include "boost/mpl/aux_/lambda_support.hpp" ... and no include for bool_trait_undef.hpp. This is causing a redefinition warning on Apple darwin for BOOST_TT_AUX_BOOL_TRAIT_DEF1. Changing recursive_wrapper_fwd.hpp to the usual use pattern of bool_trait_def.hpp as described above silences the warning. Thanks, Howard hinnant(a)twcny.rr.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1359257&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Test] BOOST_CHECK_CLOSE Feature request
by John Maddock 17 Nov '05

17 Nov '05

I have a couple of feature requests for Boost.Test: 1) Can BOOST_CHECK_CLOSE please print the actual difference between the values (as a percent to match the tolerance) as well as the values themselves? The reason this is important, is that it's not always easy to get this value from the input values - because the precision of the machine on which the test is run far outstrips that of the author's machine, so his calculator isn't any use :-( 2) Can we please have a BOOST_CHECK_EPSILON, that uses a whole number of epsilon as the tolerance? IMO BOOST_CHECK_CLOSE should have been written this way to begin with, but it's too late now. Again it should print out the actual relative error as a multiple of epsilon as well as the input values. Actually while we're at it the absolute error may be useful to have in some situations as well :-) BTW, in case it helps: I've switched to using std::pow(two, 1-std::numeric_limits<T>::digits) to calculate machine epsilon, because of the strange behaviour on Darwin with long doubles if you use numeric_limits<>::epsilon() (see http://lists.boost.org/Archives/boost/2005/09/93390.php) Thanks! John.

6 13

Boost regression notification (2005-11-17 [RC_1_33_0])
by Douglas Gregor 17 Nov '05

17 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-17T14:40:15Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 2 failures in 2 libraries: multi_index (1) serialization (1) |multi_index| test_conv_iterators: vc-8_0 |serialization| test_multiple_ptrs_binary_archive: vc-8_0

2 1

Boost regression notification (2005-11-17 [HEAD])
by Douglas Gregor 17 Nov '05

17 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-17T06:00:17Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 141 failures in 13 libraries: concept_check (12) date_time (2) graph (2) io (1) math (2) mpl (1) parameter (12) serialization (34) spirit (2) tr1 (49) type_traits (1) typeof (18) xpressive (5) |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 vc-7_1 |date_time| testwcustom_time_zone: mingw-3_4_2 testwposix_time_zone: mingw-3_4_2 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos log1p_expm1_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |serialization| test_array_text_warchive_dll: vc-7_1 test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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_demo_auto_ptr: vc-7_1 test_demo_auto_ptr_dll: vc-7_1 test_demo_dll: vc-7_1 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_has_virtual_destructor_test: intel-win32-9_0 |type_traits| has_virtual_destructor_test: intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[Review] Boost.Logging review result
by Hartmut Kaiser 17 Nov '05

17 Nov '05

Hi all, today I got the following message from John Torjo: <quote> Due to the feedback I got, I would like you to declare the library as rejected. In the light of what Gennady and others have said, indeed, another interface would be best suited for the Boost Log library. With what I know now, I would like to redesign the library from ground up, and ask for another review, probably 6 months from now or so. </quote> In the light of this announcement the review of the proposed Boost.Logging library submitted by John is closed. The library is not included into Boost. I very much hope John will find the time and energy to redesign and resubmit the library in the future. Regards Hartmut Review Manager

4 4

Re: [boost] mpl help needed - doing the impossible?
by Martin Bonner 17 Nov '05

17 Nov '05

----Original Message---- From: Manfred Doudar [mailto:manfred.doudar@metoceanengineers.com] Sent: 16 November 2005 11:35 To: boost(a)lists.boost.org Subject: Re: [boost] mpl help needed - doing the impossible? > Manfred Doudar wrote: > >> >> /* Now, how do I get T out when Rank == 1, ... compiler complains >> about seeing a MyArray/blitz::Array of <T, Rank = 0> >> (, which is not defined for blitz Arrays) >> */ >> template <typename T, int Rank> >> typename boost::mpl::if_ >> < typename boost::mpl::equal_to >> < boost::mpl::int_<Rank> >> , boost::mpl::int_<1> >> >::type >> , T >> , blitz::Array<T, >> >> boost::mpl::int_<Rank>::prior::value> >> >> > > ^ > Oops typo, should be: > MyArray<T, > > boost::mpl::int_<Rank>::prior::value> > > ... but nonetheless, the problem remains ... > >> >::type >> MyArray<T, Rank> :: operator[] (const int& index) throw(); { >> // Slicing How about a helper traits class? template <typename T, int Rank> struct SliceType { typedef typename MyArray<T, Rank-1> type; }; template <typename T> struct SliceType<T,1> { typedef T type; }; template <typename T, int Rank> typename SliceType<T,Rank>::type MyArray<T,Rank> :: operator[] (const int& index) throw(); -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 5

Boost regression notification (2005-11-16 [RC_1_33_0])
by Douglas Gregor 17 Nov '05

17 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-16T14:08:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 3 failures in 3 libraries: multi_index (1) serialization (1) thread (1) |multi_index| test_conv_iterators: vc-8_0 |serialization| test_multiple_ptrs_binary_archive: vc-8_0 |thread| test_mutex_lib: tru64cxx71-006

3 2

[Boost-bugs] [ boost-Support Requests-1358740 ] boost_1_33_0 regex runtime assertion fail.
by SourceForge.net 17 Nov '05

17 Nov '05

Support Requests item #1358740, was opened at 2005-11-17 07:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1358740&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: mindaou (mindaou) Assigned to: Nobody/Anonymous (nobody) Summary: boost_1_33_0 regex runtime assertion fail. Initial Comment: Hi, I am new in boost. I use boost_1_33_0 and VC7.1. When I run the regex sample code(string split and credit card number check), assertion failed. I dont know how to solve it. I build and install boost like this: bjam "-sTOOLS=vc-7_1" install Then I set the include path and library path in VC7.1. I can compile and build(debug mode) the program successfully, but fail to execute it. The assertion fail message is as following: Assertion failed: r == 1 << 8, file C:\boost_1_33_0\libs\regex\build\../src/w32_ regex_traits.cpp, line 108 ------ Then I tried using another boost library "tokenizer". It works good. I think I install boost properly. I just can't figure out why I can't use regex. My VC7.1 environment settings are all default. I tried another VC6-built boost, and it has the same assertion fail with my VC6. Can anyone help me with this? Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1358740&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Bugs-1358600 ] lexical_cast & pure virtual functions & VC 8 STL
by SourceForge.net 17 Nov '05

17 Nov '05

Bugs item #1358600, was opened at 2005-11-17 11:39 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=1358600&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sergey Shandar (sergey_shandar) Assigned to: Nobody/Anonymous (nobody) Summary: lexical_cast & pure virtual functions & VC 8 STL Initial Comment: VC 8.0 can't compile the valid code: ===== ===== #include <boost/lexical_cast.hpp> class A { public: virtual void out(std::ostream &) const = 0; }; class B: public A { public: virtual void out(std::ostream &O) const { O << "B"; } }; std::ostream &operator<<(std::ostream &O, const A &a) { a.out(O); return O; }; int main() { const A &a = B(); boost::lexical_cast<std::string>(a); return 0; } ===== ===== The problem occurs in VC STL: ===== ===== c:\program files\microsoft visual studio 8\vc\include\limits(102) : error C2259: 'A' : cannot instantiate abstract class ===== ===== However, should boost::lexical_cast use std::numeric_cast in this case? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1358600&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] "Re: serialization performance"
by bwood 17 Nov '05

17 Nov '05

Caleb Epstein wrote: >On Tue, 15 Nov 2005 02:08:52 00100 (CET), bwood <brass_at_[hidden]> wrote: > > >> I'm not sure if I understand your first question. I assume >> you read the previous posts. I compared the time it takes to >> serialize/send a list of ints using Boost and Ebenezer approaches. >> I timed the following >> Boost: >> oArch & lst; // using boost 1.33.0 >> Ebenezer: >> msgs.Send(buffer, lst); >> >> >> Without making any modifications to the two "vanilla" approaches, >> Boost takes more than twice as long than Ebenezer. On the > > >Someone has proposed an enhancement for Serialization that would speed up >array/vector operations by an order of magnitude. I don't think such a >simple test is indicative of the overall performance or feature-set of >either of these two libraries. Perhaps Boost.Serialization does not >perform >well with a list of ints, but Ebenezer does. Maybe >Boost.Serializationperforms better with scalar values, or with tracked >objects, or with the XML >based archive, who knows. That enhancement sounds familiar. Is the aim to take advantage of the contiguous data? WebEbenezer already implements a limited form of this with arrays and vectors. Certainly Boost.Serialization is better with XML. We don't support XML and don't plan to. > >> It may be that gcc doesn't optimize the Boost code >> very well and another compiler would produce results that >> are better. > > >Who knows, but what you are benchmarking is far to small to be meaningful >IMHO. "A single accurate measurement is worth a thousand expert opinions." I hope to add to the tests over time and add a page to webEbenezer that will cover the results. > > >> As far as build times, I agree that they aren't the most >> important factor. In my opinion they aren't trivial either. > > >Features are much more important to me and I am sure many others. I have a >hard time believing that "Ebenezer" can compete with >Boost.Serializationwhich: > > > - Has an extensive unit-test suite and compiles on a broad range of > platforms/compilers We have a variety of tests. Our approach to serialization is different than the library approach. We don't need to port a library to different platforms/compilers. We don't use areas of C++ that are dark corners in terms of the code that is output, so I think it reasonable to believe we have a broader reach than Boost.Serialization in this respect. This is ironic as we don't have to work hard, like Boost does, to achieve this. > - Supports several different archive formats (e.g. text, binary, xml) > - Supports object versioning S11n.net, CORBA and webEbenezer don't find a place for "versioning." I think code like what you wrote when I asked about changing a member's type between releases should go into a utility program that gets run once. If you stick that code into an application it gets run over and over, but adds nothing as far as functionality. > - Supoprts pointer serialization/tracking We support pointer serialization but not tracking yet. > - Is not coupled to a transport (the Ebenezer example code I can see > seems very socket or file-centric) > True, but that could change if needed. Brian

1 0

Boost regression notification (2005-11-16 [HEAD])
by Douglas Gregor 16 Nov '05

16 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-16T06:00:27Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 137 failures in 14 libraries: concept_check (12) date_time (2) graph (2) io (1) iostreams (2) iterator (2) math (5) mpl (1) serialization (30) spirit (2) tr1 (52) type_traits (3) typeof (18) xpressive (5) |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 vc-7_1 |date_time| testwcustom_time_zone: mingw-3_4_2 testwposix_time_zone: mingw-3_4_2 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |iostreams| auto_close_test: vc-7_1 finite_state_filter_test: vc-7_1 |iterator| iterator_traits_test: vc-7_1 permutation_iterator_test: vc-7_1 |math| complex_test: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos log1p_expm1_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_has_virtual_destructor_test: gcc-3_4_3-sunos intel-win32-9_0 mingw-3_4_2 |type_traits| has_virtual_destructor_test: gcc-3_4_3-sunos intel-win32-9_0 mingw-3_4_2 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

3 2

[website] broken links on version history page.
by Rene Rivera 16 Nov '05

16 Nov '05

An FYI... when the 1.33.0 changes got moved from the front page to the history page the links did not get adjusted so they now point to nothing. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

2 2

Some simple logging performance tests
by Andrew Schweitzer 16 Nov '05

16 Nov '05

Using GetTickCount and GetThreadTimes on Windows XP Pro, recorded time to execute some simple pieces of logging code in a loop. Divided by loop iterations to get time per iteration. This is a 3Ghz Pentium. Not sure how good these tests are, but here's the results: results: elapsed ms thread time ms ns / call (GetTickCount) (GetThreadTimes) (in thread) cout 1329 421 42100 enabled log 1469 453 45300 cout "disabled" 15 15 15 disabled log 531 531 531 Here's a little detail on tests cout, 10,000 times, l_dw increments each loop: cout << l_dw << endl; enabled log, 10,000 times: //outside loop: enable_logs("lgTest"); //in loop: BOOST_SCOPEDLOG(l_lgTest) << l_dw << endl; cout "disabled", 1,000,000 times: //outside loop: bool l_bEnabled = false; //in loop: if(l_bEnabled) { cout << l_dw << endl; } disabled log, 1,000,000 times: //outside loop: disable_logs("lgTest"); //this not in loop //in loop: BOOST_SCOPEDLOG(l_lgTest) << l_dw << endl;

6 9

[Review] The review of the Boost.Logging library starts today, November 7th
by Hartmut Kaiser 16 Nov '05

16 Nov '05

Hi all, today starts the review of the Boost.Logging library written by John Torjo. It will end on November 16th. --------------------------------------------------- About the library: As applications are becoming more and more complex, logging is more and more of a must, in nowadays software. The Boost Logging Library is a library that: * makes it very easy to declare/define logs * allows you very simple access to logs * allows you to easily use/manipulate log levels (like, dbg/err/info/etc.) * allows for log hierarchies, and for manipulating log hierarchies * is thread-safe To get you started, here's some basic usage: BOOST_LOGL(app,dbg) << "debugging: " << i << '-' << j << std::endl; BOOST_LOG(app) << "I just wanted to tell you something...."; BOOST_LOGL(app,err) << "this is an error!"; The latest version of the lib can be found here: http://torjo.com/code/logging.zip --------------------------------------------------- Please always state in your review, whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Regards Hartmut Review Manager

14 46

mpl help needed - doing the impossible?
by Manfred Doudar 16 Nov '05

16 Nov '05

I'm Re-posting ... sorry for the noise, but this seemingly, earlier went against the unit lib thread .. (don't quite know how). Boosters: I'm hoping someone here might be of help, and enlighten me with some more MPL trickery ... What I'm doing: Have a class MyArray derived from blitz::Array, and among other things, I'm trying to add the operator[] to slice through a multi-dim array ... pretty much have it, with one exception - once I get to applying [] on a 1-dimensional (linear) array, I of course expect a scalar, but therein lies the problem - the compiler also "sees" a 0-dimensional array (not good!), and that's where I run into problems... Brief snippets of code: Please ignore the return by value for the moment - I can clean that up later, not to mention the Boost PP extensions I can add. Below is a cut-down class definition, and method implementation follows. Class Declaration: ------------------ template <typename T, int Rank = 1> class MyArray : public blitz::Array<T, boost::mpl::int_<Rank>::value> { public: // ... methods }; (Partial Listing) Implementation: --------------------------------- template <typename T, int Rank> MyArray<T, Rank> :: Array(const blitz::Array<T, boost::mpl::int_<Rank>::value>& btz ) throw() : blitz::Array<T, boost::mpl::int_<Rank>::value> (const_cast<T *> (btz.data()) , btz.shape() , blitz::duplicateData ) { // Copy Ctor } template <typename T, int Rank> void MyArray<T, Rank> :: getParamList(blitz::TinyVector< boost::variant< blitz::Range , blitz::nilArraySection > , 2 >& plist ) { // Aides us in setting up the parameter list for slicing plist(boost::mpl::int_<0>::value) = blitz::Range::all(); plist(boost::mpl::int_<1>::value) = blitz::nilArraySection(); } /* Now, how do I get T out when Rank == 1, ... compiler complains about seeing a MyArray/blitz::Array of <T, Rank = 0> (, which is not defined for blitz Arrays) */ template <typename T, int Rank> typename boost::mpl::if_ < typename boost::mpl::equal_to < boost::mpl::int_<Rank> , boost::mpl::int_<1> >::type , T , MyArray<T, boost::mpl::int_<Rank>::prior::value> >::type MyArray<T, Rank> :: operator[] (const int& index) throw(); { // Slicing // this bit of indirection is useful blitz::TinyVector<boost::variant<blitz::Range, blitz::nilArraySection>, 2> plist; this->getParamList(plist); /* pseudocode: (kind of) **************** return // cast for return type static_cast< (Rank == 1 ? T : MyArray<T, Rank - 1>) > ( // cast _this_ ptr * static_cast<const blitz::Array<T, Rank> *> (this) // the blitz Array parameter list (index, //the param list *boost::get<blitz::Range *or* blitz::nilArraySection>(&plist(0 *or* 1), ... ) ) Sample usage: MyArray<float, 3> arr(btzArray); arr[10]; // gives MyArray<float, 2> out arr[10][2] // gives MyArray<float, 1> out arr[10][2][7] // expect a float to be output ********************/ return static_cast< typename boost::mpl::if_< typename boost::mpl::equal_to< boost::mpl::int_<Rank> , boost::mpl::int_<1> >::type , T , MyArray<T, boost::mpl::int_<Rank>::prior::value> >::type > ((* static_cast<const blitz::Array<T, boost::mpl::int_<Rank>::value> *> (this)) /* the parameter list */ (index, *boost::get< typename boost::mpl::if_< typename boost::mpl::less< boost::mpl::int_<1> , boost::mpl::int_<Rank> >::type , blitz::Range , blitz::nilArraySection >::type > (&plist(boost::mpl::if_< typename boost::mpl::less< boost::mpl::int_<1> , boost::mpl::int_<Rank> >::type , boost::mpl::int_<0> , boost::mpl::int_<1> >::type::value ) ) /* , ... we can extend the parameter list with Boost.PP */ ); ************* (Partial) Compiler Error Messages: --------------------------------- `boost::mpl::algo_::if_<boost::mpl::equal_to<boost::mpl::int_<Rank>, boost::mpl::int_<1> >::type, T, blitz::Array<T, typename boost::mpl::int_<Rank>::prior::value> >::type moe::Array<T, Rank>::operator[](const S&) [with S = int, T = int, int Rank = 1]': arr.cc:172: instantiated from here arr.cc:666: invalid static_cast from type `blitz::Array<int, 0>' to type `int' /usr/local/include/blitz/array/storage.h: In constructor `blitz::GeneralArrayStorage<N_rank>::GeneralArrayStorage() [with int N_rank = 0]': <snip ... more messages> /usr/local/include/blitz/array/storage.h:60: no match for call to `( blitz::TinyVector<int, 0>) (int&)' <snip ... more messages> ******************* So ... can anyone tell me if what I'm trying to do is possible ? Is there some MPL trickery to do it ? The above does work up until I apply the operator[] on a 1-d linear array. Help and ideas would be appreciated. Ah yes, using gcc 3.2.2, and Boost version 1.31 (maybe 1.32) .. downloaded in August 2004 (yes, I know that's ancient - but managment can be a real pain sometimes) P.S. tried to format this message as best I could, hope it's readable. With Thanks, -- Manfred Doudar MetOcean Engineers www.metoceanengineers.com

1 0

Weak_ptr and operator==
by Dan Day 15 Nov '05

15 Nov '05

Why was operator== never added to weak_ptr? Couldn't the operator easily be implemented in terms of operator<? -- ------------------------------------------- Dan Day http://razzerblog.blogspot.com

3 2

Re: [boost] Too many library variants
by Rene Rivera 15 Nov '05

15 Nov '05

Taking this to the devel list... Jeff Garland wrote: > On Mon, 14 Nov 2005 20:17:00 -0500, David Abrahams wrote > >>Rene Rivera <grafik.list(a)redshift-software.com> writes: >> >> >>>Merrill Cornish wrote: >>> >>>>When I built Boost 1.33.0 for MinGW, I just specified the toolset. >>>>As a result I got 28! variants on the set of Boost libraries. >>>> >>>> >>>>>From the various file names, I can figure out most of the variants: >>>>> >>>> >>>>d = debug mt = multi-threaded s = static but there are other variants >>>>which aren't as obvious. >>> >>>It's all explained in >>><http://www.boost.org/more/getting_started.html#Results>. >> >>Rene, I get the impression that 28 variants is a lot more than most >>people want, at least at first. Maybe we shouldn't build all of them >>by default, and just supply enough to "get started?" > > I think at one point Doug suggested that a single variant is the most common > case, and I agree. OK, but which ever variant one picks, dynamic, static, etc., will mean that some subset of the libraries will not get built as not all libraries support building in any variant. What was the variant that Doug suggested? By the way it's only 16 variants that get built. The rest are the result of not having the version tag so those are just either copies or symlinks. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

2 1

Proposal: property_tree rev.2 uploaded to vault and sandbox cvs
by Marcin Kalicinski 15 Nov '05

15 Nov '05

Hi All, Thanks to everybody who took time to look at the library, and especially to those who sent me feedback. Second revision of property_tree is now in the vault as property_tree_rev2.zip (it is now also in boost-sandbox cvs). Outline of the changes: - new methods get_o, get_own_o, get_child_o, which return boost::optional (suggested by Pavel Vozenilek) - added locales support to get and put methods (suggested by Martin) - pointer to bool removed from get_d (suggested by Daniel Wesslen) - ptree/wptree are now case sensitive by default. Added iptree/wiptree which are case-insensitive (suggested by Daniel Wesslen) - fixed multiple definitions bug when including some of the headers in more than one translation unit (spotted by Daniel Wesslen) - added more examples - updated docs and regressions to match current state of library (that was the biggest job actually :-) - hopefully kept the quality high Outstanding work: - XPath-like syntax for retrieving XML attributes (suggested by Caleb Epstein) - ptree mathematical relations (difference, union, intersection) - nice e.g. for tracking config file changes, or combining configs Original message (posted with revision 1): Property tree is a data structure - a tree of (key, value) pairs. It differs from its cousin, "usual" PropertyMap, because it is hierarchical, not linear. Thus, it is more like a minimalistic Document Object Model, but not bound to any specific file format. It can store contents of XML files, windows registry, INI files, even command line parameters. The library contains parsers for all these formats, and more. I tried to make the library as high quality as possible before posting here, so it contains a (hopefully) full documentation, and a comprehensive set of regression tests - more than 300 test cases. By any chance it is not a substitute for (upcoming?) boost XML library - it only supports a fairly narrow subset of XML, and focuses rather on being format-independent. For more curious, excerpt from the doc: Property tree is a recursive data structure that stores a single data string, and an ordered list of (key, value) pairs, where value is a property tree itself. It therefore forms a tree, hence the name. It is a versatile structure that can store in uniform way data coming from various sources, such as XML or INI files, as well as windows registry, program command line etc. Property tree interface is similar to the interface of a standard C++ container. It supports iterators, insertion, erasing, searching etc. One can think of it as a sort of Document Object Model, which is minimalistic, not bound to any specific file format, designed to be easy to use, and comes as Boost-compatible, headers only C++ library. Many software projects develop a similar tool at some point of their lifetime, and property tree long ago originated the same way. I hope the library can save many from reinventing the wheel. cheers, Marcin Kalicinski

1 0

Re: [boost] Boost.Logging hex dumps (Was: Boost.Logging: formalre view)
by Martin Bonner 15 Nov '05

15 Nov '05

----Original Message---- From: Pavel Antokolsky aka Zigmar [mailto:zigmar@gmail.com] Sent: 15 November 2005 14:55 To: boost(a)lists.boost.org Subject: Re: [boost] Boost.Logging hex dumps (Was: Boost.Logging: formalreview) > On 11/15/05, Caleb Epstein <caleb.epstein(a)gmail.com> wrote: >> On 11/15/05, Darryl Green <darryl.green(a)unitab.com.au> wrote: >>> >>>>>>>> Ok, will do. >>>>>>> >>>>>>> But note that will can bloat the library. Showing hex data is a >>>>>>> much harder >>> >>> Hex data formatting (or any data formatting) shouldn't be part of >>> the library. Or if it should, it probably means the lib shouldn't >>> be dragging in all that std streams stuff that is supposed to be >>> responsible for formatting... >> >> >> The proposed Boost.Log library already depends (rightly, IMHO) on >> iostreams for message formatting and buffering of >> partially-formatted messages. I can't see why or how this dependency >> could be reasonably eliminated without major sacrifices to the >> usefulness of the library. >> >> The necessary code to do hex dumps on an iostream should hardly be >> considered bloat. I agree with Gennadiy's assesment that 50 lines of >> code should be more than adequate to do it. These can be in a >> separate header file that is included only by the user. What >> possible harm could this be? > > It would not hard of course, but I think this code does not belong to > the logging library. It's such a common requirement that I think it does. > For example, in some cases I do not want to print non-ascii > characters in hex dump, in others I do. ? How does a hex dump contain anything other than hex digits and space (to separate bytes). You might want a way of controlling whether to use upper or lower case letters (but I wouldn't bother). > The grouping depends on length > of the data worlds I'm working with, and also should be configured, > and so on. > My point is that the simple solution is not even worth implementing, > and general solution is definitely out of scope of logging library. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 4

[string_algo] error in example code
by Caleb Epstein 15 Nov '05

15 Nov '05

In: *http://tinyurl.com/b9tjl *Example code shows: typedef split_iterator<string::iterator> string_split_iterator; for( string_find_iterator It= make_split_iterator(str1, first_finder("-*-", is_iequal())); It!=string_find_iterator (); ++It) { cout << copy_range<std::string>(*It) << endl; } string_find_iterator should be string_split_iterator here. -- Caleb Epstein caleb dot epstein at gmail dot com

1 0

Boost regression notification (2005-11-15 [RC_1_33_0])
by Douglas Gregor 15 Nov '05

15 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-15T14:29:09Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-15 [HEAD])
by Douglas Gregor 15 Nov '05

15 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-15T06:00:10Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 141 failures in 13 libraries: concept_check (12) date_time (2) graph (2) io (1) math (6) mpl (1) serialization (30) spirit (8) thread (4) tr1 (51) tuple (1) typeof (18) xpressive (5) |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 vc-7_1 |date_time| testwcustom_time_zone: mingw-3_4_2 testwposix_time_zone: mingw-3_4_2 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 mingw-3_4_2 vc-7_1 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

"Re: serialization performance"
by bwood 15 Nov '05

15 Nov '05

Martin Slater wrote: >> //build oArch. >> Ebenezer: >> msgs.Send(buffer, lst); // where I didn't remove anything >> // from Send's implementation. >> >> I think as you say, whether a flush gets embedded in the Send >> function should be configurable, but right now it just is. >> I'll admit it would be better if I didn't have to remove (#if 0) >> the end of the Send function, but I don't think that invalidates >> anything. > >This I humbly disagree with, from a user point of view I would not >want to patch either library to get optimal performance, If it is >there and required then tests need to be done with it in. It would >be simple to speed up boost.serialization by #if 0'ing out per class >meta information lookups (versioning etc) but would still be >extremely artificial. Either way, with or without the embedded flush code, Boost serialization is less efficient than Ebenezer's Send in both tests. Today I timed how long it takes to build the two testcases mentioned in the original post on Nov. 8th. I used the date command so the numbers are only in seconds. list<int> list<int> and deque<int> ----------------------------------------------------------- Boost 42 61 ----------------------------------------------------------- Ebenezer 12 20 >>>It would be interesting to see what the results are with a vanilla >>>version of your library as well as a feature by feature comparision to >>>see if you really are comparing apples to apples. >>> >> Both Boost and s11n.net support things like XML that Ebenezer doesn't. >> Boost in my opinion mistakenly tries to support "versioning." We >> don't and I don't think s11n does either. > >Well since I use versioning heavily with boost.serialization this is >a must have feature for me. What happens if you want to change the type of an existing data member between releases - say from char to short? Brian www.webEbenezer.net

3 3

[multi_index][rfc] random access indices preview
by Joaquín Mª López Muñoz 15 Nov '05

15 Nov '05

Hello, Some months ago I prompted for interest in a new type of indices for Boost.MultiIndex featuring random access facilities, and received a couple of expressions of itnerest. The preliminary specification was published at: http://195.235.93.150/rnd_indices_spec.html I've just uploaded a preview version of random access indices at FileVault -> Containers (http://tinyurl.com/9zlmj) This preview follows the previous specification save for one point: reserve/capacity is provided for control of an internal array of pointers to the nodes, as explained in http://195.235.93.150/rnd_indices_spec.html#interface. There's no docs yet on this type of indices, but the usage should be straightforward from the preliminay specification notes. Random access indices act as a functional drop-in replacement of sequenced indices, so you can start playing with them very easily. My requests: * Do you find these indices worth including in Boost.MultiIndex? * If so, do you have comments on the specification? Things you'd change/add? There's a list of concrete issues at the end of the specification page, * Do you envision any interesting use case for random access indices? Have you experimented with them? Thank you very much for your feddback, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 6

Howto set SONAME (DLLVERSION)?
by Neal Becker 15 Nov '05

15 Nov '05

I want to set SONAME to 1.33, since 1.33.1 should be compatible with 1.33.0. Where/how can I set this?

6 8

[Boost-bugs] [ boost-Feature Requests-1357106 ] darwin 64 bit support
by SourceForge.net 15 Nov '05

15 Nov '05

Feature Requests item #1357106, was opened at 2005-11-15 05:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1357106&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ian Fasel (ianfasel) Assigned to: Nobody/Anonymous (nobody) Summary: darwin 64 bit support Initial Comment: To get 64-bit support, I was able to get a large chunk of boost-1_33_1 to build on darwin by inserting -arch ppc64 in strategic places in the darwin-tools.jam file. This was sufficient to be able to use the filesystem and program-options libraries in a 64-bit app I've built that needs to access > 4GB. Some libraries failed to build however, and I don't really know what I'm doing. Attached is a patch file showing what I added where. Also, it would probably be best to add -arch ppc -arch ppc64 to get "fat" binaries that work for both 32-bit and 64-bit code. However I'm no pro with these things. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1357106&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] "Re: serialization performance"
by bwood 15 Nov '05

15 Nov '05

On Mon, 14 Nov 2005 22:24:41 00100 (CET), bwood <brass_at_[hidden]> wrote: >> >> Either way, with or without the embedded flush code, Boost >> serialization is less efficient than Ebenezer's Send in both >> tests. >What are we comparing here? You really need to give the Boost commuinity >more visibility into your code if you expect your arguments to be taken >seriously. There is nothing on http://www.webebenezer.net that resembles >documentation or a complete test application that can be compiled. Hi, Caleb, I'm not sure if I understand your first question. I assume you read the previous posts. I compared the time it takes to serialize/send a list of ints using Boost and Ebenezer approaches. I timed the following Boost: oArch & lst; // using boost 1.33.0 Ebenezer: msgs.Send(buffer, lst); Without making any modifications to the two "vanilla" approaches, Boost takes more than twice as long than Ebenezer. On the surface, the two lines above look similar, but the Ebenezer line is flushing the buffer at the end of the Send function. So the Ebenezer side is doing more functionally in less time. (I've tested this by killing both test cases internally with a raise(9) right after the above lines. The Boost output file has 0 bytes in it. The Ebenezer file has all the data.) So in order to compare apples to apples, I #if 0ed out the flush code. In that case the Boost code is 7 times slower than the Ebenezer and both files have 0 bytes in them. If you want the code I used in these tests I will send it to you. It may be that gcc doesn't optimize the Boost code very well and another compiler would produce results that are better. The documentation is not very good. We hope to work on that. The "Send Sample" compiled last time I checked it. The code in the file MsgManager.h is generated by the site. It is not difficult to obtain that from the site. As far as build times, I agree that they aren't the most important factor. In my opinion they aren't trivial either. Brian

2 1

logging library link error
by Andrew Schweitzer 15 Nov '05

15 Nov '05

I just upgraded to the latest .zip file from John's web site. Now I can't seem to link. It can't find add_appender. This code built previously. Any idea what's going on? Am I not building the logging library correctly? I just cd to boot_root\libs\log\build, call "vcvars32.bat", then "bjam". It seems to build. If this line is uncommented: manipulate_logs("*").add_appender(write_to_cout); I get: AppMsg.obj : error LNK2019: unresolved external symbol "void __cdecl boost::logging::add_appender(struct boost::logging::default_log_manager &,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class boost::function2<void,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class std::allocator<class boost::function_base> >,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,int)" (?add_appender@logging@boost@@YAXAAUdefault_log_manager@12@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V?$function2@XABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@ABV12@V?$allocator@Vfunction_base@boost@@@2@@2@1H@Z) referenced in function "void __cdecl boost::logging::add_appender(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class boost::function2<void,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class std::allocator<class boost::function_base> >,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,int)" (?add_appender@logging@boost@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V?$function2@XABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@ABV12@V?$allocator@Vfunction_base@boost@@@2@@2@0H@Z)

2 2

Boost.Logging: formal review
by Gennadiy Rozental 15 Nov '05

15 Nov '05

Hi, Being the author of at least 3 different solution for logging/tracing myself, I do believe it's one of the most important general purpose library in big project development. Unfortunately proposed submission in no way came close to being an acceptable choice. Numerous design and implementation issues, weak user and absent reference documentation and absent test suite (last two points is something that review manager is responsible for IMO. No tests or docs - no review. That's it) result in: My vote is NO. Please read further for detailed analysis. I. Design Flaws ------------------ 1. Filtering support I understand that author strived to minimize the solution, but IMO it lead to minimal value. IMO proper log system should support arbitrary user defined filtering of log entries. At the bare minimum it should support: entry level - levels set is ordered set of values indication importance of information provided. Filtering is based on threshold. Examples: DEBUG, INFO, MAJOR entry category - categories set is a set of unique values indicating kind of information provided Filtering is based on masking. Examples: ARGS, RETURN_VALUE, ERROR_LOG, DATA_FLOW, PROG_FLOW entry keyword - keyword set is set of user defined keywords (most frequently strings) identifying area of the program. Filtering is based on match of keywords. Keywords usually are used to mark specific part of application. Example: "NetworkLevel", "UI", "ABC" to mark class abc, "dfg.cpp" Also multithreaded application should support filtering based on thread id. The best solution would allow to plug-in at compile time any user defined Filter (in a form of Policy). This way I could have a log that filter nothing (no filters defined) or log that filter based on time of the day if I want. This submission does support level filtering - and that's it. 2. Configuration support Submitted solution supports configuration in a form of arbitrary modifiers that user could register in log. While this looks like very inflexible it's also as very inconvenient. In most cases I prefer log to be configured at run time from within configuration file. his would be very cumbersome with modifiers model. Not only each modifier needs to be added separately. I also need to keep track of it's name to be able to remove it and it's index to know how modifiers are ordered. This ability to configure log remotely in many locations makes it impossible to really know what and how is written into log. My preferred way to configure the log is with use of configuration string. First of all it's simplify an interface and you immediately see how your log entries going to look like. Here is an example: "keyword=*,-ACD;categ=prog_flow,return value,-details;l=debug;track=on;roll=10000;prefix=file ( line ) - time :;timeformat=%s:%m". Using pluggable factory pattern you could implement this to be as flexible. Eventually as an add-on you could provide an ability to register any custom modifiers, but that is not necessary in first draft. 3. Per output configuration. Log may have multiple appenders attached (BTW - I very much prefer term used by iostreams library - sink). what if I want different entry formatting/prefixing/filtering in different outputs. I may have errors_output which contains only errors. I may have end_user_log that contains only major information for end user with detailed time and date of the entry. And I may have developer_output that contains performance warnings with file and line information. Submitted library have no support for this. 4. Internationalization support I do see some vague traces in code that indicate that author new this needs to be supported. But since documentation have exactly zero information and I couldn't figure out how to do it myself, I assume that library doesn't support this. IMO it's required for industrial strength solution. 5. File and line This solution completely ignores file and line number of trace entry. IMO They are essential and should be collected for every entry (may not be reported - depends on prefix format) 6. Misfeature: pre-init cashing Library starts with cashing turned on to support pre-init logging. IMO this is too dangerous. Now developer needs to remember how many log entries are printed. Otherwise some of them will just start disappearing (could be different in every run). And it may start happening only at the user site. Much more reliable solution is to use some kind of startup log that does not require configuration. 7. Misfeature: log hierarchies I personally never have a need for that and have some difficulties to imagine why would anyone have. You could probably have it on top of existent solution as add-on. If it doesn't require any new interfaces (or some minimal addition). IMO library pays way to much attention to this. All these manipulate_logs(...) by name that is analyzed not needed. In my experience I never wonted to configure more than one log identically. And it's much more preferable to keep all the configuration of one log in one place. So I wouldn't look around to see what and how was configured. 8. Misfeature: compile-time log support As it clear from above IMO log is (almost) never always enabled (and in any case there is a way to implement this without any additional support). And always disabled log could be implemented on macro level. Based on this I believe all the compile_tile machinery employed by library is unnecessary and just complicate implementation 9. Interface IMO primary interface advertised by library should be macro-less. Documentation does need to cover how these macros needs to be written, but with user defined filters user will need to do the job oneself. Also in my experience I found that on some systems Even if( ... ) <actual log here> could be unsatisfactory from performance standpoint. I employ one global Boolean is_log_on flag to guard all my log entries. and it should be a part of these macros 10. Performance. I am not sure wheather it's design or implementation issue, but library does a lot of premature pessimizations, which could be avoided. See in more details bellow. II. Implementation flaws ------------------ 1. File appender hierarchy To implement custom rolling library employs inheritance. This is clear example where delegation would be much better choice. Single file_sink that could be initialized with file_roller. 2. Multithreading support implementation a) For some unclear reason author chose to reimplement some of Boost.Threads functionality in some places (and in some places Boost.Thread is used always). I believe log library shouldn't do this. b) I noticed some fishy construct (m_destroyed data member). It opens some thread safety issues IMO. c) static manager_type & manager() doesn't look thread safe. 3 . enabled_logger::m_stream For some reason enabled_logger allocates m_stream dynamically for each log entry. I do not see why we need to do this. Even more: why not reuse a single instance per thread? 4. collection in use appender_array and modifier_array are better be implemented using lists 5. exception support try { LOG << "aaa" << foo() } catch(...) { LOG << "exception" } This construct doesn't seems generate what is expected if foo() throws an exception 5. appender_array appender_array seems to be defined in 2 placed 6. Appenders copying. >From code it seems that each logger has its own copy of each appender. Why would we need that? If we do why all the appenders are so heavy? 7. #ifdef UNICODE #ifdef UNICODE are spread all over the code. It needs to be centralized 8. shared_memory.hpp This header refer to the library that is not part of boost yet. I don't think it should be part of this submission. 9. Time string cashing prepend_time and prepend_time_strf calls are not cashed. It's a lot of work for nothing. 10. write_msg locking write_msg shouldn't lock on appenders writing. Each appender should be locked independently instead. Documentation is better be commented by somebody else. I thing though : no reference docs whatsoever. As well as no test suite. Hope my comments were constructive. Regards, Gennadiy

4 18

Boost regression notification (2005-11-12 [HEAD])
by Douglas Gregor 15 Nov '05

15 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-12T06:00:12Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 225 failures in 13 libraries: concept_check (12) date_time (2) graph (2) io (1) mpl (1) python (56) serialization (30) spirit (8) thread (4) tr1 (73) tuple (1) typeof (18) xpressive (17) |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 vc-7_1 |date_time| testwcustom_time_zone: mingw-3_4_2 testwposix_time_zone: mingw-3_4_2 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |python| andreas_beyer: vc-7_1 args: vc-7_1 auto_ptr: vc-7_1 back_reference: vc-7_1 ben_scott1: vc-7_1 bienstman1: vc-7_1 bienstman2: vc-7_1 bienstman3: vc-7_1 builtin_converters: vc-7_1 callbacks: vc-7_1 const_argument: vc-7_1 crossmod_exception: vc-7_1 data_members: vc-7_1 defaults: vc-7_1 dict: vc-7_1 docstring: vc-7_1 enum: vc-7_1 exception_translator: vc-7_1 extract: vc-7_1 implicit: vc-7_1 injected: vc-7_1 iterator: vc-7_1 keywords: vc-7_1 list: vc-7_1 long: vc-7_1 map_indexing_suite: vc-7_1 minimal: vc-7_1 multi_arg_constructor: vc-7_1 nested: vc-7_1 numpy: vc-7_1 object: vc-7_1 opaque: vc-7_1 operators: vc-7_1 pearu1: vc-7_1 pickle1: vc-7_1 pickle2: vc-7_1 pickle3: vc-7_1 pickle4: vc-7_1 pointer_vector: vc-7_1 polymorphism: vc-7_1 polymorphism2: vc-7_1 polymorphism2_auto_ptr: vc-7_1 properties: vc-7_1 raw_ctor: vc-7_1 return_arg: vc-7_1 shared_ptr: vc-7_1 slice: vc-7_1 staticmethod: vc-7_1 stl_iterator: vc-7_1 str: vc-7_1 test_pointer_adoption: vc-7_1 try: vc-7_1 tuple: vc-7_1 vector_indexing_suite: vc-7_1 virtual_functions: vc-7_1 wrapper_held_type: vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux intel-win32-9_0 mingw-3_4_2 std_run_random: gcc-2.95.3-linux gcc-3.4.4-linux mingw-3_4_2 std_test_bind: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_boost: gcc-2.95.3-linux std_test_complex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_function: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_hash: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_mem_fn: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_reference_wrapper: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_shared_ptr: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_tr1_include: gcc-2.95.3-linux mingw-3_4_2 std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_complex: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux tr1_remove_bounds_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 mingw-3_4_2 vc-7_1 |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| misc1: mingw-3_4_2 test1: mingw-3_4_2 test2: mingw-3_4_2 test3: mingw-3_4_2 test3u: gcc-3_3-darwin test4: mingw-3_4_2 test4u: gcc-3_3-darwin test5: mingw-3_4_2 test5u: gcc-3_3-darwin test6: mingw-3_4_2 test6u: gcc-3_3-darwin test7: mingw-3_4_2 test8: mingw-3_4_2 test9: mingw-3_4_2 test9u: gcc-3_3-darwin test_cycles: mingw-3_4_2 test_non_char: mingw-3_4_2

3 2

[iostreams] bug: is_open() should be const
by Alberto Ganesh Barbati 14 Nov '05

14 Nov '05

Hi, [referring to latest CVS version] in both class templates boost::iostreams::detail::direct_streambuf and boost::iostreams::detail::indirect_streambuf, member function is_open() is not declared const. However, boost::iostreams::stream<>::is_open() is declared const, so it won't compile as it calls one the former on a data member. Therefore, either all three members are declared const or none of them. The all-const approach makes more sense, IMHO. HTH, Ganesh

3 5

[Boost-bugs] [ boost-Bugs-1353875 ] predicates without default constructor fail to compile (2)
by SourceForge.net 14 Nov '05

14 Nov '05

Bugs item #1353875, was opened at 2005-11-11 03:54 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=1353875&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: predicates without default constructor fail to compile (2) Initial Comment: The first time I submitted I forgot to check the box for uploading the zip archive... I want to draw your attention to a possible flaw in the implementation of the write_graphviz method from the Boost Graph Library. The current implementation uses the assignment operator for the vertex and edge iterators. This is natural, but some examples fail to compile with this version. The problem comes from the predicates witch don't have default constructors. When trying to assign a vertex iterator of a graph filtered with such a predicate, the compiler issues an error: C2512:'positive_edge_weight_pred<MyEdgeWeightMap>' : no appropriate default constructor available with [ MyEdgeWeightMap=EdgeWeightMapT ] If a small modification in the write_graphviz implementation is made (using copy constructors instead of assignement operators), the example compiles and runs sucesfully. I am using the Microsoft Visual C++ 7.1 compiler. In conclusion, I think that this modification should be made, as it grows the flexibility of the library and doesn't add any overhead. I have attached the example (main.cpp) and the patch for graphviz.hpp (graphviz.hpp.patch). My e-mail adress is pdumitrache(a)bphx.ro ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1353875&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

2 1

[variant] Bug in recursive_wrapper_fwd.hpp?
by Howard Hinnant 14 Nov '05

14 Nov '05

I've been tracking down an preprocessor warning involving the redefinition of BOOST_TT_AUX_BOOL_TRAIT_DEF1. It appears to me, in boost 1.33.0, that recursive_wrapper_fwd.hpp is misusing: #include "boost/type_traits/detail/bool_trait_def.hpp" The usual include pattern for this header is: // should be the last #include #include "boost/type_traits/detail/bool_trait_def.hpp" ... #include "boost/type_traits/detail/bool_trait_undef.hpp" But recursive_wrapper_fwd.hpp has: #include "boost/type_traits/detail/bool_trait_def.hpp" #include "boost/mpl/aux_/lambda_support.hpp" ... and no include for bool_trait_undef.hpp. Is that as intended? Thanks, Howard

1 0

Memory Leak problems on VC7.1 of code uses boost 1.33.0
by Vernucci, Anthony 14 Nov '05

14 Nov '05

I am running a program that links to boost_thread-vc71-mt-gd-1_33.lib. The following code is the main driver. #include <test_virtualnetwork.h> #include <test_stringglobbing.h> #include <test_internals.h> #include <test_networking.h> #include <boost/test/unit_test.hpp> using boost::unit_test::test_suite; #define _CRTDBG_MAP_ALLOC #include <stdlib.h> #include <crtdbg.h> struct leak_reporter { static leak_reporter instance; leak_reporter(){ _CrtSetDbgFlag ( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF ); } ~leak_reporter(){ _CrtDumpMemoryLeaks(); // replaced by the above } }; leak_reporter leak_reporter::instance; test_suite* init_unit_test_suite( int, char* [] ) { test_suite* test= BOOST_TEST_SUITE( "Master Test Suite" ); test->add( new test_virtualnetwork ); test->add( new test_stringglobbing ); test->add( new test_internals ); test->add( new test_networking ); return test; } The output is: Detected memory leaks! Dumping objects -> {140} normal block at 0x003657A8, 24 bytes long. Data: < | > C0 CA 97 7C FF FF FF FF 00 00 00 00 00 00 00 00 {139} normal block at 0x003658F0, 8 bytes long. Data: < W6 > A8 57 36 00 01 CD CD CD Object dump complete. At MSDN I did read that if you #define _CRTDBG_MAP_ALLOC parameter, the memory leak dump will include the filename and line number info. But I did not get the file information even though I defined _CRTDBG_MAP_ALLOC. How do I get the filename and line number to display in the output? Thanks, - tony

1 0

Boost regression notification (2005-11-14 [RC_1_33_0])
by Douglas Gregor 14 Nov '05

14 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-14T13:59:09Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

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

14 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-14T06:00:47Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 197 failures in 14 libraries: concept_check (12) date_time (2) graph (2) io (1) math (5) mpl (1) python (56) serialization (30) spirit (8) thread (4) tr1 (52) tuple (1) typeof (18) xpressive (5) |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 vc-7_1 |date_time| testwcustom_time_zone: mingw-3_4_2 testwposix_time_zone: mingw-3_4_2 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 mingw-3_4_2 |mpl| size_t: gcc-4_0-darwin |python| andreas_beyer: vc-7_1 args: vc-7_1 auto_ptr: vc-7_1 back_reference: vc-7_1 ben_scott1: vc-7_1 bienstman1: vc-7_1 bienstman2: vc-7_1 bienstman3: vc-7_1 builtin_converters: vc-7_1 callbacks: vc-7_1 const_argument: vc-7_1 crossmod_exception: vc-7_1 data_members: vc-7_1 defaults: vc-7_1 dict: vc-7_1 docstring: vc-7_1 enum: vc-7_1 exception_translator: vc-7_1 extract: vc-7_1 implicit: vc-7_1 injected: vc-7_1 iterator: vc-7_1 keywords: vc-7_1 list: vc-7_1 long: vc-7_1 map_indexing_suite: vc-7_1 minimal: vc-7_1 multi_arg_constructor: vc-7_1 nested: vc-7_1 numpy: vc-7_1 object: vc-7_1 opaque: vc-7_1 operators: vc-7_1 pearu1: vc-7_1 pickle1: vc-7_1 pickle2: vc-7_1 pickle3: vc-7_1 pickle4: vc-7_1 pointer_vector: vc-7_1 polymorphism: vc-7_1 polymorphism2: vc-7_1 polymorphism2_auto_ptr: vc-7_1 properties: vc-7_1 raw_ctor: vc-7_1 return_arg: vc-7_1 shared_ptr: vc-7_1 slice: vc-7_1 staticmethod: vc-7_1 stl_iterator: vc-7_1 str: vc-7_1 test_pointer_adoption: vc-7_1 try: vc-7_1 tuple: vc-7_1 vector_indexing_suite: vc-7_1 virtual_functions: vc-7_1 wrapper_held_type: vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_remove_bounds_test: vc-7_1 |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

1.33.1 Final Release Plan
by Doug Gregor 14 Nov '05

14 Nov '05

Boost 1.33.1 Final will be released on December 5, 2005. Not "around" December 5, 2005; not "a week after" December 5, 2005; on December 5, 2005. As with the other releases in the 1.33.x series, it will come from the RC_1_33_0 branch. Minor bug fixes and documentation patches can be committed to the branch with my approval. If a change causes new failures, it will be reverted. A timeline: November 8: Boost 1.33.1 Beta released November 9: RC_1_33_0 open for bug fixes, documentation updates with prior approval November 28: RC_1_33_0 branch completely frozen. Final regression test results. December 2: Boost 1.33.1 release candidate. December 5: Boost 1.33.1 release. Doug

2 1

shared_ptr - allocator template argument
by Michael Schneider 14 Nov '05

14 Nov '05

Is there a reason why shred_ptr does not accept an allocator? shared_ptr seems to allocate sp_counted_impl_p<...> using new, it it took in an allocator, then the allocator could be assigned the responsibility to allocate the memory for sp_counter_impl_p. We have an application requirement that all application memory must be managed by our memory allocation system. We have a secondary requirement that we can't replace global new and delete. It seems like this requirement could be satisfied by adding an allocator to shared_ptr. I could make this change locally, but it seems like this would be a common requirement that would be useful for several application domains. Couple of quick questions: - am I off in the weeds with this suggestion? Is there a simple way to meet our memory requirement without modifying shared_ptr?? - If a change is required, what can I do to help make this change in boos (I am new to the boost community)? If this is not useful to the community, please let me know. I can code this in internal code if that is best for the boost community. Thanks Mike -- The greatest performance improvement occurs on the transition of from the non-working state to the working state.

3 2

Proposal: XML APIs in boost
by Stefan Seefeld 14 Nov '05

14 Nov '05

Some years ago I proposed a XML-related APIs for inclusion into boost (http://lists.boost.org/Archives/boost/2003/06/48955.php) Everybody agreed that such APIs would be very useful as part of boost. Unfortunately, though, after some weeks of discussing a number of details, I got distracted, and so I never managed to submit an enhancement. I'v now started to look into this topic again, and wrote down a start of a DOM-like API as I believe would be suitable for boost. Here are some highlights: * User access dom nodes as <>_ptr objects. All memory management is hidden, and only requires the document itself to be managed. * The API is modular to allow incremental addition of new modules with minimal impact on existing ones. This implies that implementations may only support a subset of the API. (For example, no validation.) * All classes are parametrized around the (unicode) string type, so the code can be bound to arbitrary unicode libraries, or even std::string, if all potential input will be ASCII only. * The Implementation uses existing libraries (libxml2, to be specific), since writing a XML DOM library requires substantial efford. A first sketch at a XML API is submitted to the boost file vault under the 'Programming Interfaces' category. It contains demo code, as well as some auto-generated documentation. I'm aware that this requires some more work before I can attempt a formal submission. This is simply to see whether there is still any interest into such an API, and to get some discussion on the design. Regards, Stefan

19 93

Re: [boost] Compilation problems on VC7 of code uses boost 1.31.0
by Miko Nahum 14 Nov '05

14 Nov '05

Thanks John. Your answer helped us great deal. I have removed the allocator stuff and problem solved. Concerning the 'collate' issue, still considering if to make changes to boost enum. Regards, Miko -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of John Maddock Sent: Thursday, November 10, 2005 1:05 PM To: boost(a)lists.boost.org Subject: Re: [boost] Compilation problems on VC7 of code uses boost 1.31.0 > We have the following piece of code that uses boost (copy/paste): I'm afraid I don't have a copy of 1.31 lying around anymore, but your problems are almost certainly allocator related. Can you remove the allocator related code? As it stands your code doesn't actually "do" anything. Or or you actually using a custom allocator? As for the HP aCC problem: it's very similar to one that occurs with VC7 when there's a "using namespace std;" declaration before including regex: the compiler is then unable to differentiate between std::collate (the template) and boost::collate (the constant), and it's a compiler bug. Otherwise your workaround is as good as any I guess. Are you in a position to upgrade to Boost-1.33.1 ? The bad news is that your code as it stands will likely need some porting to make the change (reg_expression has been deprecated in favour of basic_regex for example, but the typedefs like boost::regex boost::wregex etc are all the same). The good news is that the regex matching code has been substantially re-written to be much faster, and hardly does any memory allocation at all (or even none at all under ideal conditions), so custom allocators are very much a thing of the past. It would simplify your code to: #include "boost/regex.hpp" using namespace boost; using namespace std; typedef boost::regex re_type; long example_func(long pos, const std::string& regE, long& reslen, long max) { long res; boost::match_results <PData::iterator> m; re_type e; e.assign (regE, regbase::normal); if (regex_search (begin (), end (), m, e, match_not_dot_newline | match_not_dot_null)) { res = pos + m.position(); reslen = m.length(); return res; } Sorry I can't be more helpful about this: diagnosing these kinds of deep template instantiation errors are next to impossible sometimes, but are almost always errors in the template argument list. Hope this helps a little at least, John. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Static Member declaration GCC
by Bernd Martin Wollny 14 Nov '05

14 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hello, I tried to declare a boost:shared_ptr as a static member of a template function. If I compile the program with Visual Studio all are Ok. If I try to compile the code with gcc, gcc failed with: t1.cpp:71: error: too few template-parameter-lists t1.cpp:72: error: too few template-parameter-lists There is a small mistake in my code but I can't find the error. Can someone help me? Bye Bernd - ------------------ code ----------------------------- #include <boost/thread/mutex.hpp> #include <boost/shared_ptr.hpp> template <class T> class SimpleSingleton { public: SimpleSingleton() { } ~SimpleSingleton() { } T * instance() { boost::mutex::scoped_lock sp_lock(inst_mutex); if (!as.get()) { boost::shared_ptr<T> temp(new T); as=temp; } return as.get(); } protected: static boost::shared_ptr<T>(as); static boost::mutex inst_mutex; }; class test { protected: test(void) { a_=0; } public: ~test(void) { } int Get(void) { return a_; } void Set(int a) { a_ = a; } protected: int a_; friend class SimpleSingleton<test>; }; boost::shared_ptr<test> SimpleSingleton<test>::as; boost::mutex SimpleSingleton<test>::inst_mutex; int main(void) { SimpleSingleton<test> t; t.instance()->Set(45); int b=t.instance()->Get(); return b; } - ------------------ code ----------------------------- - -- TRIOPTICS GmbH Bernd Martin Wollny Software Designer Hafenstrasse 39, 22880 Wedel/GERMANY phone / fax: +49 (0)4103 18006-26 /-20 e-mail: bm.wollny(a)trioptics.com All E-Mails from bm.wollny(a)trioptics.com are digital signed. If you get a unsigned E-Mail, this E-Mail are a fake. Look at http://www.gnupg.org . -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDdKc4CjfVnTPD3b4RA+0HAKC4jcBEeYvc75ZqJj4q2cNALGFElwCfZANJ X2i8t+fFa5o/rQQyha0KDqs= =BUfl -----END PGP SIGNATURE-----

3 3

RTL and example are updated in the file vault
by Arkadiy Vertleyb 14 Nov '05

14 Nov '05

Hi all, I spent some time optimizing the RTL example discussed some time ago, as well as related parts of the library. The result (according to my estimate) is almost 10 times increase in performance. Jose, if you could time it again on your PC, we would have more accurate result. Among other optimizations, I also switched to a faster but less accurate formula for distance calculations, which lead to a slight change in the result -- apparently two stations are located at the distance of almost exactly 5 km. The library and example are at their usual place in the file vault, http://tinyurl.com/8lbmg. As always, comments are welcome. Regards, Arkadiy

1 0

Re: [boost] Gender neutral documentation
by Martin Bonner 13 Nov '05

13 Nov '05

Angus Leeming wrote: > > Returning to the original example: > This means for example that the client can completely > discard Bind if she does not need it. > I'd suggest rewriting it as: > This means that the user can discard Bind completely > if it is not needed. > > That would get rid of a split infinitive too, but that's a whole other > ball game :) a) I don't see a split infinitive in the original. b) Your rewrite has transformed a clause in the active voice ("she does not need it") to the passive voice ("it is not needed"). The problem with documentation in the passive voice is that it doesn't make clear /who/ doesn't need Bind. My rewrite would be: This means, for example, that the client can completely discard Bind if they don't need it. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

9 10

singleton and active objects
by Jason Hise 13 Nov '05

13 Nov '05

It occurred to me recently that having the option to make a singleton an active object may be vital in order to make an efficient multi-threaded singleton viable. By having function calls on the singleton enqueue requests and return future variables, threads should be able to access the singleton reasonably often without creating a bottleneck. The question is, should I try to develop and submit an active object library before trying to get singleton accepted? I suspect that having an efficient multi-threaded solution available would help the next singleton review substantially. -Jason

2 1

Boost Test - yet more mostly spurious warnings.
by Paul A Bristow 13 Nov '05

13 Nov '05

To get quiet compilations (MSVC 8.0 release 140050727, level 4, no MS extensions), I have had to disable persistent warnings from boost\test\detail\test_tools.hpp by adding to supress_warning.hpp # pragma warning(disable: 4127) // conditional expression is constant. Entirely correct and expected. # pragma warning(disable: 4180) // qualifier applied to function type has no meaning; ignored at: const_string message() const { return !m_message ? const_string() : const_string( m_message->str() ); } ^^ const not useful? but not wrong. # pragma warning(disable: 4224) // nonstandard extension used : formal parameter 'tool_level' was previously defined as a type i:\boost_1_33_0\boost/test/test_tools.hpp(385) : warning C4224: nonstandard extension used : formal parameter 'tool_level' was previously defined as a type i:\boost_1_33_0\boost/test/test_tools.hpp(427) : warning C4224: nonstandard extension used : formal parameter 'tool_level' was previously defined as a type i:\boost_1_33_0\boost/test/test_tools.hpp(427) : warning C4224: nonstandard extension used : formal parameter 'tool_level' was previously defined as a type i:\boost_1_33_0\boost/test/test_tools.hpp(427) : warning C4224: nonstandard extension used : formal parameter 'tool_level' was previously defined as a type i:\boost_1_33_0\boost/test/test_tools.hpp(427) : warning C4224: nonstandard extension used : formal parameter 'tool_level' was previously defined as a type i:\boost_1_33_0\boost/test/test_tools.hpp(427) : warning C4224: nonstandard extension used : formal parameter 'tool_level' was previously defined as a type Is it complaining about re-using the name tool_level? void check_impl( predicate_result const& pr, wrap_stringstream& check_descr, const_string file_name, std::size_t line_num, tool_level tool_level, check_type ct, <<<<<<<<<<<<<< std::size_t num_args, ... ); Of these, only the latter might be worth worrying about? Still works fine, but if you are tidying up sometime... Paul -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow(a)hetp.u-net.com www.hetp.u-net.com

2 4

Boost regression notification (2005-11-13 [RC_1_33_0])
by Douglas Gregor 13 Nov '05

13 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-13T13:51:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-13 [HEAD])
by Douglas Gregor 13 Nov '05

13 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-13T06:00:08Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 223 failures in 13 libraries: concept_check (12) date_time (2) graph (2) io (1) mpl (1) python (56) serialization (30) spirit (8) thread (4) tr1 (71) tuple (1) typeof (18) xpressive (17) |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 vc-7_1 |date_time| testwcustom_time_zone: mingw-3_4_2 testwposix_time_zone: mingw-3_4_2 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |python| andreas_beyer: vc-7_1 args: vc-7_1 auto_ptr: vc-7_1 back_reference: vc-7_1 ben_scott1: vc-7_1 bienstman1: vc-7_1 bienstman2: vc-7_1 bienstman3: vc-7_1 builtin_converters: vc-7_1 callbacks: vc-7_1 const_argument: vc-7_1 crossmod_exception: vc-7_1 data_members: vc-7_1 defaults: vc-7_1 dict: vc-7_1 docstring: vc-7_1 enum: vc-7_1 exception_translator: vc-7_1 extract: vc-7_1 implicit: vc-7_1 injected: vc-7_1 iterator: vc-7_1 keywords: vc-7_1 list: vc-7_1 long: vc-7_1 map_indexing_suite: vc-7_1 minimal: vc-7_1 multi_arg_constructor: vc-7_1 nested: vc-7_1 numpy: vc-7_1 object: vc-7_1 opaque: vc-7_1 operators: vc-7_1 pearu1: vc-7_1 pickle1: vc-7_1 pickle2: vc-7_1 pickle3: vc-7_1 pickle4: vc-7_1 pointer_vector: vc-7_1 polymorphism: vc-7_1 polymorphism2: vc-7_1 polymorphism2_auto_ptr: vc-7_1 properties: vc-7_1 raw_ctor: vc-7_1 return_arg: vc-7_1 shared_ptr: vc-7_1 slice: vc-7_1 staticmethod: vc-7_1 stl_iterator: vc-7_1 str: vc-7_1 test_pointer_adoption: vc-7_1 try: vc-7_1 tuple: vc-7_1 vector_indexing_suite: vc-7_1 virtual_functions: vc-7_1 wrapper_held_type: vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 mingw-3_4_2 std_run_random: gcc-2.95.3-linux mingw-3_4_2 std_test_bind: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_boost: gcc-2.95.3-linux std_test_complex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_function: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_hash: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_mem_fn: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_reference_wrapper: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_shared_ptr: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_tr1_include: gcc-2.95.3-linux mingw-3_4_2 std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_complex: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux tr1_remove_bounds_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 mingw-3_4_2 vc-7_1 |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| misc1: mingw-3_4_2 test1: mingw-3_4_2 test2: mingw-3_4_2 test3: mingw-3_4_2 test3u: gcc-3_3-darwin test4: mingw-3_4_2 test4u: gcc-3_3-darwin test5: mingw-3_4_2 test5u: gcc-3_3-darwin test6: mingw-3_4_2 test6u: gcc-3_3-darwin test7: mingw-3_4_2 test8: mingw-3_4_2 test9: mingw-3_4_2 test9u: gcc-3_3-darwin test_cycles: mingw-3_4_2 test_non_char: mingw-3_4_2

1 0

Re: [boost] serialization performance
by David Abrahams 13 Nov '05

13 Nov '05

bwood <brass(a)mailvault.com> writes: > Hi, Dave, Hi Brian > I work on www.webEbenezer.net. I noticed today that Robert > Ramey said "So far so good" regarding some performance tests > he is doing. You might want to encourage him to consider > some of the competition as far as performance. You should probably be doing that, actually ;-) I'm helpfully cross-posting this reply to the Boost developers' list, but next time, please do it yourself so that you get "in the mix" there. Having these kinds of reports in the public record, and having people like you involved in the ensuing discussion, are crucial for the Boost process. Thanks again for writing. > Some recent tests I've done that compare Ebenezer Enterprises > and Boost.serialization's performance show the > Boost.serialization approach to be 7 to 9 times slower than the > Ebenezer Enterprises approach. I'm using Linux 2.6.12, > gcc 4.0.2 (with -O3) and a Boost.serialization library from the > release tree. A test that compared the times to serialize/send > a list<int> took 7.4 times longer with Boost than Ebenezer. > I timed the following > Boost: > oArch & lst; // oArch is a binary_oarchive > > Ebenezer: > msgs.Send(buffer, lst); // In order to compare apples to apples, > // I removed a section of code at the end > > // of the Send function that flushes the > buffer. > > > In a second test I added a deque of int... > Boost: > oArch & lst; > oArch & dq; // std::deque<int> dq; > > Ebenezer: > msgs.Send(buffer, lst, dq); > > In this case Boost took 9.1 times longer than Ebenezer Enterprises > approach. If you want to run these tests with other compilers I > think that would be helpful. I've been warned not to put too much > emphasis on numbers from gcc. > > Regards, > Brian Wood -- Dave Abrahams Boost Consulting www.boost-consulting.com

4 11

Re: [boost] serialization performance
by Martin Slater 12 Nov '05

12 Nov '05

> //build oArch. > Ebenezer: > msgs.Send(buffer, lst); // where I didn't remove anything > // from Send's implementation. > > I think as you say, whether a flush gets embedded in the Send > function should be configurable, but right now it just is. > I'll admit it would be better if I didn't have to remove (#if 0) > the end of the Send function, but I don't think that invalidates > anything. This I humbly disagree with, from a user point of view I would not want to patch either library to get optimal performance, If it is there and required then tests need to be done with it in. It would be simple to speed up boost.serialization by #if 0'ing out per class meta information lookups (versioning etc) but would still be extremely artificial. >>It would be interesting to see what the results are with a vanilla >>version of your library as well as a feature by feature comparision to > > >>see if you really are comparing apples to apples. >> > > Both Boost and s11n.net support things like XML that Ebenezer doesn't. > > Boost in my opinion mistakenly tries to support "versioning." We > don't and I don't think s11n does either. > Well since I use versioning heavily with boost.serialization this is a must have feature for me. This conversation really should be kept to the boost list where there are many knowlegedable experts in this area and both libraries could potentially benifit from the discussion, you can sign up at http://lists.boost.org/mailman/listinfo.cgi/boost cheers Martin -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.0/167 - Release Date: 11/11/2005

1 0

Boost regression notification (2005-11-12 [RC_1_33_0])
by Douglas Gregor 12 Nov '05

12 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-12T14:42:09Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

[ptr_container] Semicolons after macros
by Boris Burger 12 Nov '05

12 Nov '05

Hello, the issue with extra semicolons at namespace or class scope is surely nothing new and has been discussed extensively. Still, I am not able to handle its incarnation in ptr_container sources, with G++ 3.4.5 (-ansi -pedantic). It goes like this: In ptr_map_adapter.hpp (and elsewhere), definition of class template ptr_map_adapter_base contains: BOOST_PTR_CONTAINER_DEFINE_CONSTRUCTORS( ptr_map_adapter_base, base_type ); at class scope. G++ 3.4.5 reports the extra semicolon as an error (-ansi -pedantic warning level is rather strict here). Due to our company's policy lowering the warning levels is not an option. Patching the ptr_container classes would do the trick but that would require rather painful process of going through the Boost sources with each new version and removing extra semicolons. What is your opinion on this, please? Regards, Boris

4 7

libmdc Preview Release
by Michael Crawford 12 Nov '05

12 Nov '05

libmdc is a set of utility and debugging classes that I expect would be useful in most C++ programs. Mostly it consists of assertion bottlenecks to help you eliminate pointer and memory bugs from your programs. There will be more soon to help with class invariant and design by contract assertions. libmdc - Mike Crawford's C++ Library http://www.goingware.com/libmdc/ It's also meant to make unit testing easier. It includes CPPUnit.mk and CPPUnit.t.mk, sub-makefiles which ease building CPPUnit unit tests with GNU make. My assertion_failed exception class includes a macro which can be used by your own assertion macros to throw an exception upon assertion failure. This enables one to use CPPUnit to test assertion failures without aborting the tests. My mdc_assert can do this. libmdc is Free Software, released under the Boost Software License. It's my intention that when I'm finished writing it, I will submit it for review for possible inclusion in Boost itself. It is not nearly done yet, but this preview release is provided to solicit comments. My question for you is, do you see any obvious mistakes? How can I do better? My valid_ptr template is a non-owning smart pointer that cannot be NULL. I'm also going to write a template I'll call checked_ptr that CAN be NULL. valid_ptr uses and checked_ptr will use the legal_addr template which reads the first byte addressed by any reference or non-NULL pointer. Given an unmapped address, it causes an immediate crash, but probably sooner and easier to debug than letting it snowball through your program. Used with a memory debugger like valgrind, Purify or Spotlight, you can find and fix bad memory references with ease. I have used this technique before and while it's dead-simple, it is also very powerful. libmdc doesn't have proper documentation yet, but there is some in the form of comments in the header files. The unit tests also serve as sample code. The Makefile is extensively commented to show you how to use CPPUnit.mk to build unit tests for your classes. CPPUnit.mk itself contains complete documentation for its use. I build unit tests the way John Lakos advises in Large Scale C++ Software Design: I only link in the class under direct test, and those sources which are absolutely required to make the test link. For reasons that Lakos eloquently explains, I DON'T link in my entire project, as I think is the more common practice. To keep this manageable, I need a separate makefile to build each unit test. CPPUnit.t.mk encapsulates what is common to building all unit tests, so that the *.t.mk unit test makefiles need have little more in them than a list of the dependencies. Following is from the README file: libmdc is a set of utility and debugging classes likely to be useful in many C++ projects. Everything is in the namespace mdc. There aren't any dependencies on anything outside this directory except for the standard C++ library, Boost and CPPUnit for the unit tests. You will need to build and install the Boost C++ library and the CPPUnit automated test framework before you can build this code: http://www.boost.org/ http://cppunit.sourceforge.net/cppunit-wiki/ To build the executables, just take "make". To build and then run the tests (both unit tests and other tests) type "make test". There is no "make install" yet. The library so far contains: CPPUnit.mk, CPPUnit.t.mk Sub-makefiles to make it a lot easier to build CPPUnit unit tests with GNU make. valid_ptr non-owning smart pointer; forbids NULL pointers. legal_addr pointer debugging, best used with valgrind, purify or spotlight. null_ptr_checker throws an exception when given a NULL pointer. null_ptr_exception The exception it throws. mdc_assert Debugging macro, aborts or drops into debugger when its assertion evaluates to false. This is used instead of the standard library assert so it may be separately disabled. Assertions are enabled by default, for release builds, #define MDC_NO_ASSERT 1 or pass -DMDC_NO_ASSERT=1 to the C++ compiler. assertion_failed meant for testing failed assertions in unit tests. You can configure mdc_assert to throw this exception with #define MDC_ASSERTION_EXCEPTION 1 errno_exception on POSIX systems, throw this exception after a system call fails so that the catcher can print a good error message string_invariant The beginning of class invariant assertions for the Standard Library valid_ptr is a smart pointer like auto_ptr, scoped_ptr or shared_ptr, except that it doesn't take ownership of the pointer it holds. Instead, construct a valid_ptr from a pointer that your class or function is given to use, but not manage. It will throw a null_ptr_exception and optionally assert if the pointer is ever NULL. Besides validating the pointer it is given, valid_ptrs serve as documentation to help make ownership issues clear. Using valid_ptrs as class member variables indicates that the pointers are used by, but not owned by the class. Similarly, declaring them as function parameters indicates that the pointers passed in cannot be NULL, and again that ownership of them is not captured by the receiving function. Use either scoped_ptr, shared_ptr or auto_ptr for situations where pointer ownership is required. Which one to use depends on the requirements of each situation. There is sample code too: the tests. There are unit tests for most of the classes that use the CPPUnit automated test framework. There is also a simple program called HeaderCheck that I used to debug some problems with my header files while I was first writing valid_ptr.h. CPPUnit does some extreme macro and template magic, so HeaderCheck serves as a simpler testbed. Enjoy! -- Mike -- Michael D. Crawford GoingWare Inc. - Expert Software Development and Consulting http://www.goingware.com/ crawford(a)goingware.com Tilting at Windmills for a Better Tomorrow.

1 0

[MPL] interest in algo that creates all possible permutations of a type?
by Kevin Sopp 11 Nov '05

11 Nov '05

Hi, I just joined the list and I would like to show you what I have done here. Given a type T which is a model of MPL lambda expression, permute<T, Args1, ..., ArgsN>::type is an MPL vector that contains all possible permutations of type T, where ArgsN is a model of an MPL forward sequence. Example: template<class X, class Y> struct base{}; permute< base<_1,_2>, vector<int, float>, vector<double, bool> >::type types; types is an MPL vector containing all possible permutations of base with the supplied argument lists: vector< base<int,double>, base<int,bool>, base<float,double>, base<float,bool> > (not necessarily in this order) I believe I can easily extend this algo to n-ary lambda expressions with some preprocessor macros. The version for binary expressions is attached below because the code is short. I tested the code with gcc 3.4.4. Example usage: I use this algo to create a typelist that is given to my renderer which instantiates a 'dispatch table' (see More Effective C++, Item 31) and the appropriate render functions for these types. Then at runtime the entities to be rendered are dispatched based on their dynamic type to the specialized render functions which only work on concrete types. #ifndef permute_h #define permute_h #include <boost/mpl/apply.hpp> #include <boost/mpl/at.hpp> #include <boost/mpl/bool.hpp> #include <boost/mpl/if.hpp> #include <boost/mpl/eval_if.hpp> #include <boost/mpl/int.hpp> #include <boost/mpl/modulus.hpp> #include <boost/mpl/push_back.hpp> #include <boost/mpl/size.hpp> #include <boost/mpl/vector.hpp> template<class T, class Args1, class Args2, class Seq, int N, int K> struct permute_impl { typedef typename boost::mpl::modulus< boost::mpl::int_<N>,boost::mpl::size<Args2> >::type args2_index; typedef typename boost::mpl::push_back< Seq , typename boost::mpl::apply< T , typename boost::mpl::at_c<Args1, K>::type , typename boost::mpl::at<Args2, args2_index>::type >::type >::type Seq2; typedef typename boost::mpl::eval_if_c< N == 0 , Seq , permute_impl< T , Args1,Args2 , Seq2 , N-1 , boost::mpl::if_c< args2_index::value == 1 , boost::mpl::int_<K+1> , boost::mpl::int_<K> >::type::value > >::type type; }; template<class T, class Args1, class Args2> struct permute { typedef typename permute_impl< T, Args1, Args2, boost::mpl::vector<>, boost::mpl::size<Args1>::value*boost::mpl::size<Args2>::value, 0 >::type type; }; #endif _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

4 4

any interest in BOOST_FINALLY?
by Alexander Nasonov 11 Nov '05

11 Nov '05

Is there an interest to write something like this int i = 2, j = 1; BOOST_FINALLY_BEGIN( (i)(j) ) { std::cerr << i + j << '\n'; } BOOST_FINALLY_END in a code to make sure that a code inside finally block is always executed when leaving a scope? Code is here: http://files.rsdn.ru/21403/finally.cpp Note that it depends on typeof. Preprocessed output is below: // Not thread-safe yet void* _finally_last_params = 0; int main() { int i = 2, j = 1; typedef typeof(i) _finally_typeof_46i; typedef typeof(j) _finally_typeof_46j; struct _finally_params_46 { _finally_typeof_46i & i ; _finally_typeof_46j & j ; } _finally_params_46 = { i, j }; _finally_last_params = &_finally_params_46; struct _finally_guard_46 { void* _finally_params; ~_finally_guard_46() { typedef struct _finally_params_46 params; params* p= static_cast<params*>(_finally_params); _finally_body(p -> i , p -> j , 0); } static void _finally_body( _finally_typeof_46i & i , _finally_typeof_46j & j , int) { // USER CODE HERE std::cerr << i + j << '\n'; } } _finally_guard_48 = { _finally_last_params }; } -- Alexander

4 9

[MPL.Math] updates for double
by Cromwell Enage 11 Nov '05

11 Nov '05

I've now added a BOOST_MPL_CFC_NO_MATH_DOUBLE macro that is defined in <boost/mpl/aux_/config/math_double.hpp> when it is known that BOOST_MPL_MATH_DOUBLE won't compile. Please send me your compiler-platform configuration if BOOST_MPL_MATH_DOUBLE doesn't work for you. Peder, The double_::aux::get_value function still returns a number 2^16 times too big on MSVC 7.1 when the input is a whole number. Cromwell D. Enage __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

3 17

Boost regression notification (2005-11-11 [RC_1_33_0])
by Douglas Gregor 11 Nov '05

11 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-11T15:11:40Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 1 failure in 1 library: serialization (1) |serialization| test_contained_class_xml_warchive: vc-7_1

1 0

Boost regression notification (2005-11-11 [HEAD])
by Douglas Gregor 11 Nov '05

11 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-11T06:00:26Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 167 failures in 13 libraries: bind (1) concept_check (13) date_time (2) graph (3) io (1) mpl (1) serialization (30) spirit (8) thread (8) tr1 (64) tuple (1) typeof (18) xpressive (17) |bind| bind_dm3_test: intel-win32-9_0 |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 vc-7_1 vc-7_1 |date_time| testwcustom_time_zone: mingw-3_4_2 testwposix_time_zone: mingw-3_4_2 |graph| graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_read_write_mutex: mingw-3_4_2 vc-7_1 test_read_write_mutex_lib: mingw-3_4_2 vc-7_1 test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux mingw-3_4_2 std_run_random: gcc-2.95.3-linux gcc-3.4.4-linux mingw-3_4_2 std_test_bind: gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 std_test_boost: gcc-2.95.3-linux std_test_complex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_function: gcc-2.95.3-stlport-4.6.2-linux std_test_hash: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_mem_fn: gcc-2.95.3-stlport-4.6.2-linux std_test_reference_wrapper: gcc-2.95.3-stlport-4.6.2-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux mingw-3_4_2 std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_bind: intel-win32-9_0 test_complex: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux tr1_remove_bounds_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 vc-7_1 |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| misc1: mingw-3_4_2 test1: mingw-3_4_2 test2: mingw-3_4_2 test3: mingw-3_4_2 test3u: gcc-3_3-darwin test4: mingw-3_4_2 test4u: gcc-3_3-darwin test5: mingw-3_4_2 test5u: gcc-3_3-darwin test6: mingw-3_4_2 test6u: gcc-3_3-darwin test7: mingw-3_4_2 test8: mingw-3_4_2 test9: mingw-3_4_2 test9u: gcc-3_3-darwin test_cycles: mingw-3_4_2 test_non_char: mingw-3_4_2

1 0

Some notes on TR1 tests
by Peter Dimov 11 Nov '05

11 Nov '05

test_shared_ptr: derived_deleter should take a derived*, not base*. concrete should use virtual inheritance. test_bind: All function tests use bind( &test_proc... ), bind( test_proc... ) should be tested too. -- Peter Dimov http://www.pdimov.com

2 14

[asio] Are the _at_least_n functions useful?
by Christopher Kohlhoff 11 Nov '05

11 Nov '05

Hello all, As part of cleaning up asio's interface I am pondering the utility of the read_at_least_n/write_at_least_n free functions. I'd appreciate hearing from anyone who actually uses these functions (or their async counterparts), and anyone else who has an opinion on the matter :) The rationale for their existence is the use case where you want to ensure that a minimum number of bytes are transferred, but are willing to receive more than that minimum in order to minimise the number of system calls. However I have never used them in practice, and suspect that an application that needed that level of control might prefer to use the lower level (i.e. partial-read/write) functions directly. I'm considering taking them out for now on the following basis: - I want to simplify the asio interface to improve clarity and ease-of-use. - I want to get asio ready for review asap. Including the functionality requires much more thought on how to make it elegant. - asio is obviously useful without them. So essentially I am proposing that the version of asio submitted for boost review does not include this functionality. If a compelling use case emerges in practice then the functionality can be added back after more careful consideration of the design (and with, I believe, no impact on other functionality). If somebody has a need right now, then I'll look at keeping them in, but it will delay getting a version ready for review submission. Cheers, Chris

2 1

cvs access down?
by John Maddock 11 Nov '05

11 Nov '05

I'm seeing strange errors trying to access cvs: cvs update: failed to create lock directory for `/cvsroot/boost/boost' (/cvsroot/boost/boost/#cvs.lock): Read-only file system cvs update: failed to obtain dir lock in repository `/cvsroot/boost/boost' cvs [update aborted]: read lock failed - giving up Anyone else seeing this or is it just me? John.

2 1

[Boost-bugs] [ boost-Bugs-1353854 ] predicates without default constructor fail to compile
by SourceForge.net 11 Nov '05

11 Nov '05

Bugs item #1353854, was opened at 2005-11-11 03:21 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=1353854&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: predicates without default constructor fail to compile Initial Comment: I want to draw your attention to a possible flaw in the implementation of the write_graphviz method from the Boost Graph Library. The current implementation uses the assignment operator for the vertex and edge iterators. This is natural, but some examples fail to compile with this version. The problem comes from the predicates witch don't have default constructors. When trying to assign a vertex iterator of a graph filtered with such a predicate, the compiler issues an error: C2512:'positive_edge_weight_pred<MyEdgeWeightMap>' : no appropriate default constructor available with [ MyEdgeWeightMap=EdgeWeightMapT ] If a small modification in the write_graphviz implementation is made (using copy constructors instead of assignement operators), the example compiles and runs sucesfully. I am using the Microsoft Visual C++ 7.1 compiler. In conclusion, I think that this modification should be made, as it grows the flexibility of the library and doesn't add any overhead. I have attached the example (main.cpp) and the patch for graphviz.hpp (graphviz.hpp.patch). My e-mail adress is pdumitrache(a)bphx.ro ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1353854&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Proposal: property_tree (property_tree.zip uploaded to vault)
by Marcin Kalicinski 11 Nov '05

11 Nov '05

Hi Everybody, Property tree is a data structure - a tree of (key, value) pairs. It differs from its cousin, "usual" PropertyMap, because it is hierarchical, not linear. Thus, it is more like a minimalistic Document Object Model, but not bound to any specific file format. It can store contents of XML files, windows registry, INI files, even command line parameters. The library contains parsers for all these formats, and more. I tried to make the library as high quality as possible before posting here, so it contains a (hopefully) full documentation, and a comprehensive set of regression tests - more than 300 test cases. By any chance it is not a substitute for (upcoming?) boost XML library - it only supports a fairly narrow subset of XML, and focuses rather on being format-independent. I uploaded it to the vault root dir, file name is property_tree.zip. For more curious, excerpt from the doc: Property tree is a recursive data structure that stores a single data string, and an ordered list of (key, value) pairs, where value is a property tree itself. It therefore forms a tree, hence the name. It is a versatile structure that can store in uniform way data coming from various sources, such as XML or INI files, as well as windows registry, program command line etc. Property tree interface is similar to the interface of a standard C++ container. It supports iterators, insertion, erasing, searching etc. One can think of it as a sort of Document Object Model, which is minimalistic, not bound to any specific file format, designed to be easy to use, and comes as Boost-compatible, headers only C++ library. Many software projects develop a similar tool at some point of their lifetime, and property tree long ago originated the same way. I hope the library can save many from reinventing the wheel. cheers, Marcin Kalicinski

4 7

Re: [boost] New boost webpage
by Janusz Piwowarski 11 Nov '05

11 Nov '05

Rene Rivera <grafik.list_at_[hidden]> writes: > Sam Partington wrote: >> You also need to add this to httpd.conf, otherwise IE will just keep >> on downloading images, over and over and over again, even when they've >> been loaded at page load time. >> >> #this stops background-image flicker in IE >> BrowserMatch "MSIE" brokenvary=1 >> BrowserMatch "Mozilla/4.[0-9]{2}" brokenvary=1 >> BrowserMatch "Opera" !brokenvary >> SetEnvIf brokenvary 1 force-no-vary >> ExpiresActive On >> ExpiresByType image/gif A2592000 >> ExpiresByType image/jpeg A2592000 >> ExpiresByType image/png A2592000 > > Unfortunately that level of server setup is beyond our control. We can > only hope that SF has such configuration already present on their servers. I see background image flickering is still a problem. I've discovered that you can put above lines to .htaccess file. Regards, Janusz

2 3

[Bind] TR1 and overload ambiguity.
by John Maddock 10 Nov '05

10 Nov '05

The following short program works fine for VC7.1, but for several well regarded compilers including Intel-8/9 and gcc-3.4 fails to compile due to "ambiguous overload" errors. It's causing errors in the TR1/Bind concept tests, and I'd like to figure out if it's the compiler or Boost.Bind that's at fault so I can file defect reports with the compiler vendors if necessary. Here's the test case: #include <boost/bind.hpp> template <class Functor> void consume(Functor f); double test_proc(int a, char b, long c) { return a+b+c; } struct from_double { from_double(double){} }; int main() { consume(boost::bind<double>(&test_proc, 0, 0, 0)); consume(boost::bind<float>(&test_proc, 0, 0, 0)); consume(boost::bind<long double>(&test_proc, 0, 0, 0)); consume(boost::bind<from_double>(&test_proc, 0, 0, 0)); } And a typical error message from Intel-9 is: $ icl -GX -c -Ic:\\data\\boost\\develop\\boost bind.cpp Intel(R) C++ Compiler for 32-bit applications, Version 9.0 Build 20050912Z Pa ckage ID: W_CC_C_9.0.024 Copyright (C) 1985-2005 Intel Corporation. All rights reserved. 30 DAY EVALUATION LICENSE bind.cpp bind.cpp(21): error: more than one instance of overloaded function "boost::bind" matches the argument list: function template "boost::bind<R,F,A1,A2,A3>(F, A1, A2, A3)" function template "boost::bind(R (*)(B1, B2, B3), A1, A2, A3)" argument types are: (double (*)(int, char, long), int, int, int) consume(boost::bind<double>(&test_proc, 0, 0, 0)); ^ compilation aborted for bind.cpp (code 2) Note that it's the presence of the function pointer overloads that causes the error: in other words it's an artefact of the implementation that causes the error, not the TR1 specification itself. Anyone any ideas whose at fault here? Thanks, John.

3 8

vc8 failure in boost_python-dll-vc-8_0
by Bronek Kozicki 10 Nov '05

10 Nov '05

There is single error at http://tinyurl.com/9u6nd : use_ansi.h(49) : fatal error C1189: #error : You have included some C++/C library header files with _DEBUG defined and some with _DEBUG not defined. This will not work correctly. Please have _DEBUG set or clear consistently. ... which renders whole Boost.Python unusable under vc8. It looks as if parts of the library were build with DEBUG macro set, and other parts without it (which might lead to ODR violation). I do not know if this is jamfile problem or something else. Compiler being used is RTM version. Dave, do you need help tracing the problem? B.

6 22

Bug list status
by Marshall Clow 10 Nov '05

10 Nov '05

Four weeks ago: 144 open bugs Three weeks ago: 117 open bugs Two weeks ago: 96 open bugs Last week: 94 open bugs Today: 93 open bugs Thanks to everyone who dealt with the bugs! [ But we're slowing down - I blame the 1.33.1 release process ;-) ] If you think that a bug has been assigned incorrectly, please let me know. Bugs by assignee: Doug Gregor 16 Mike Glassford 14 Beman Dawes 12 John R. Bandela 7 Stephen Cleary 5 Jonathan Turkanis 5 Rene Rivera 4 Joerg Walter 4 Jeff Garland 3 Joel de guzman 3 Jeremy Siek 2 Mark Rodgers 2 <nobody> 2 Robert Ramey 2 Gennadiy Rozental 2 Vladimir Prus 2 Thorsten Ottosen 1 Darryl Walker 1 Eric Friedman 1 Jens Maurer 1 John Maddock 1 Samuel Krempp 1 Here are the currently opened bugs, sorted by assignee. P.S. I need someone to fix the bugs in the tokenizer library!! Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: wrong usage of ios_base::narrow Bug #: 989487 <http://sourceforge.net/tracker/index.php?func=detail&aid=989487&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: date_time type conversion warning Bug #: 1069225 <http://sourceforge.net/tracker/index.php?func=detail&aid=1069225&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: local_adjustor::utc_to_local throws 'Time label invalid' Bug #: 1220011 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220011&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesytem::directory_iterator portability Bug #: 735403 <http://sourceforge.net/tracker/index.php?func=detail&aid=735403&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem fails in posix with files containing ':' Bug #: 776146 <http://sourceforge.net/tracker/index.php?func=detail&aid=776146&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: clock is not portable Bug #: 788762 <http://sourceforge.net/tracker/index.php?func=detail&aid=788762&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Boost::Filesystem fails when last character in path is ':' Bug #: 875970 <http://sourceforge.net/tracker/index.php?func=detail&aid=875970&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesystem::directory_iterator returns incorrect listing Bug #: 937606 <http://sourceforge.net/tracker/index.php?func=detail&aid=937606&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: xtime_cmp: use comparison not subtraction Bug #: 993272 <http://sourceforge.net/tracker/index.php?func=detail&aid=993272&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists is broken on cygwin Bug #: 1010681 <http://sourceforge.net/tracker/index.php?func=detail&aid=1010681&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem is systematically broken Bug #: 1012135 <http://sourceforge.net/tracker/index.php?func=detail&aid=1012135&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::native() should reject '/' on non-Win32 Bug #: 1151823 <http://sourceforge.net/tracker/index.php?func=detail&aid=1151823&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists has bugs with UNC paths Bug #: 1164057 <http://sourceforge.net/tracker/index.php?func=detail&aid=1164057&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::equivalent does not work on w98 Bug #: 1235262 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235262&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: path and directory_iterator doesn't handle windows root path Bug #: 1259176 <http://sourceforge.net/tracker/index.php?func=detail&aid=1259176&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: no conversion from type to const_type Bug #: 547743 <http://sourceforge.net/tracker/index.php?func=detail&aid=547743&group_id=75…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = setS for adjacency_list does not work Bug #: 1163077 <http://sourceforge.net/tracker/index.php?func=detail&aid=1163077&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: adjacency_matrix should model BidirectionalGraph Bug #: 1168411 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168411&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors for undirected graphs Bug #: 1168420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA adaptors for node_array, edge_array Bug #: 1168424 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168424&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors do not handle hidden nodes properly Bug #: 1168431 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168431&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Generate patches for Graph bugs in 1.32.0 Bug #: 1169920 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169920&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Investigate other kinds of heaps for dijkstra_shortest_paths Bug #: 1170106 <http://sourceforge.net/tracker/index.php?func=detail&aid=1170106&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: function.hpp breaks assign.hpp Bug #: 1181272 <http://sourceforge.net/tracker/index.php?func=detail&aid=1181272&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: vertex bundle properties do not work with VC++.NET 2003 Bug #: 1190394 <http://sourceforge.net/tracker/index.php?func=detail&aid=1190394&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: BGL graph types do not support allocators Bug #: 1193883 <http://sourceforge.net/tracker/index.php?func=detail&aid=1193883&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: random_vertex/random_edge are unnecessarily inefficient Bug #: 1204684 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204684&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Document copy_component Bug #: 1204688 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204688&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: reverse_graph and constness of property maps Bug #: 1246336 <http://sourceforge.net/tracker/index.php?func=detail&aid=1246336&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: html docs frequently missing key words Bug #: 1294420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1294420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = has_setS for adjacency_list does not work Bug #: 1352049 <http://sourceforge.net/tracker/index.php?func=detail&aid=1352049&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Miss ' = ParserT()' Bug #: 907299 <http://sourceforge.net/tracker/index.php?func=detail&aid=907299&group_id=75…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: spirit insert_key_actor.hpp Bug #: 1059936 <http://sourceforge.net/tracker/index.php?func=detail&aid=1059936&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Another config correction for Sun C++ Bug #: 1220782 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220782&group_id=7…> Assignee: dlwalker <http://sourceforge.net/users/dlwalker/> Summary: template problems with common_factor.hpp Bug #: 491637 <http://sourceforge.net/tracker/index.php?func=detail&aid=491637&group_id=75…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: boost::blank - missing operators Bug #: 1191356 <http://sourceforge.net/tracker/index.php?func=detail&aid=1191356&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl to_duration() nsec error Bug #: 548104 <http://sourceforge.net/tracker/index.php?func=detail&aid=548104&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Solaris - once.cpp compile error Bug #: 549162 <http://sourceforge.net/tracker/index.php?func=detail&aid=549162&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: pthread_delay_np() parm incorrect Bug #: 551157 <http://sourceforge.net/tracker/index.php?func=detail&aid=551157&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Bosot.Thread.condition(win32).notify_all Bug #: 551308 <http://sourceforge.net/tracker/index.php?func=detail&aid=551308&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: AIX 4.3 SIGSEGV at thread termination Bug #: 551577 <http://sourceforge.net/tracker/index.php?func=detail&aid=551577&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: boost::threads uses msvc only function? Bug #: 568951 <http://sourceforge.net/tracker/index.php?func=detail&aid=568951&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: threads unnecessary #include Bug #: 571615 <http://sourceforge.net/tracker/index.php?func=detail&aid=571615&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: BCB6 throw EExternelException Bug #: 596149 <http://sourceforge.net/tracker/index.php?func=detail&aid=596149&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: thread_cleanup problems Bug #: 649291 <http://sourceforge.net/tracker/index.php?func=detail&aid=649291&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Mac implementation of threads is CPU hog Bug #: 885045 <http://sourceforge.net/tracker/index.php?func=detail&aid=885045&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: condition variables and recursive_mutex Bug #: 1072605 <http://sourceforge.net/tracker/index.php?func=detail&aid=1072605&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: compiler error on Mac implementation of threads Bug #: 1201779 <http://sourceforge.net/tracker/index.php?func=detail&aid=1201779&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl line 116 copy/paste error Bug #: 1239052 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239052&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Exception safety in class 'thread' Bug #: 1305885 <http://sourceforge.net/tracker/index.php?func=detail&aid=1305885&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: 'failed fileclone' when building with -j on 1.32.0 Bug #: 1102389 <http://sourceforge.net/tracker/index.php?func=detail&aid=1102389&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: boost jam problem with parallel builds Bug #: 1234224 <http://sourceforge.net/tracker/index.php?func=detail&aid=1234224&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: crach build bjam from mingw 3.4.4 Bug #: 1341560 <http://sourceforge.net/tracker/index.php?func=detail&aid=1341560&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: crach build bjam from mingw 3.4.4 with python Bug #: 1341568 <http://sourceforge.net/tracker/index.php?func=detail&aid=1341568&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer fails with wchar_t Bug #: 446155 <http://sourceforge.net/tracker/index.php?func=detail&aid=446155&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer not works with Dinkumware 308 Bug #: 458236 <http://sourceforge.net/tracker/index.php?func=detail&aid=458236&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: boost::tokenizer implicit typename Bug #: 912368 <http://sourceforge.net/tracker/index.php?func=detail&aid=912368&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Tokenizer.hpp doesn't work with BOOST_ENABLE_ASSERT_HANDLER Bug #: 972406 <http://sourceforge.net/tracker/index.php?func=detail&aid=972406&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Compiler error for tokenizer on Solaris Bug #: 976241 <http://sourceforge.net/tracker/index.php?func=detail&aid=976241&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer and signed char Bug #: 1003889 <http://sourceforge.net/tracker/index.php?func=detail&aid=1003889&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: token_iterator::at_end() result is inversed Bug #: 1338326 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338326&group_id=7…> Assignee: jmaurer <http://sourceforge.net/users/jmaurer/> Summary: Diff in state of mersenne_twister gen between GCC3.41 & CW9 Bug #: 1115124 <http://sourceforge.net/tracker/index.php?func=detail&aid=1115124&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: bug in ublas/storage.hpp Bug #: 1095697 <http://sourceforge.net/tracker/index.php?func=detail&aid=1095697&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: dead links in uBLAS page Bug #: 1169273 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169273&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: Documentation not available on web site: Bug #: 1228242 <http://sourceforge.net/tracker/index.php?func=detail&aid=1228242&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: uBLAS::subslice doesn't work Bug #: 1292635 <http://sourceforge.net/tracker/index.php?func=detail&aid=1292635&group_id=7…> Assignee: johnmaddock <http://sourceforge.net/users/johnmaddock/> Summary: Adding boost::is_complex to type_traits.hpp Bug #: 1315712 <http://sourceforge.net/tracker/index.php?func=detail&aid=1315712&group_id=7…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: invalid result for File Dependency Examp Bug #: 551110 <http://sourceforge.net/tracker/index.php?func=detail&aid=551110&group_id=75…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: Spelling of Edmonds-Karp-Algorithm Bug #: 1226292 <http://sourceforge.net/tracker/index.php?func=detail&aid=1226292&group_id=7…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751269 <http://sourceforge.net/tracker/index.php?func=detail&aid=751269&group_id=75…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751289 <http://sourceforge.net/tracker/index.php?func=detail&aid=751289&group_id=75…> Assignee: nesotto <http://sourceforge.net/users/nesotto/> Summary: boost.range and 'const char[]'. Bug #: 1272315 <http://sourceforge.net/tracker/index.php?func=detail&aid=1272315&group_id=7…> Assignee: nobody Summary: failure in boost jam unit tests on cygwin Bug #: 940941 <http://sourceforge.net/tracker/index.php?func=detail&aid=940941&group_id=75…> Assignee: nobody Summary: Can't build on cygwin Bug #: 1145183 <http://sourceforge.net/tracker/index.php?func=detail&aid=1145183&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: Compiler warning with gcc on Linux Bug #: 1337412 <http://sourceforge.net/tracker/index.php?func=detail&aid=1337412&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: warning caused by size_t to unsigned int conversion on vc++8 Bug #: 1338178 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338178&group_id=7…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: typo in Boost.Test document Bug #: 629685 <http://sourceforge.net/tracker/index.php?func=detail&aid=629685&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: Don't work multilevel hierarchy of test suites in dll. Bug #: 1076691 <http://sourceforge.net/tracker/index.php?func=detail&aid=1076691&group_id=7…> Assignee: samuel_k <http://sourceforge.net/users/samuel_k/> Summary: format: assert when parsing invalid pattern Bug #: 1326132 <http://sourceforge.net/tracker/index.php?func=detail&aid=1326132&group_id=7…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: ct_gcd_lcm.hpp compilation error Bug #: 558174 <http://sourceforge.net/tracker/index.php?func=detail&aid=558174&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: test_pool_alloc.cpp not compile CW8.1 Bug #: 586779 <http://sourceforge.net/tracker/index.php?func=detail&aid=586779&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: pool::purge_memory() does not reset next_size Bug #: 984124 <http://sourceforge.net/tracker/index.php?func=detail&aid=984124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: Borland compiler error with Pool, boost::pool_allocator Bug #: 988124 <http://sourceforge.net/tracker/index.php?func=detail&aid=988124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: perfomance: memory cleanup for pool takes too long Bug #: 995270 <http://sourceforge.net/tracker/index.php?func=detail&aid=995270&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: boost::pool_allocator breaks with vector of vectors Bug #: 1179641 <http://sourceforge.net/tracker/index.php?func=detail&aid=1179641&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Self division wrong in template rational Bug #: 504411 <http://sourceforge.net/tracker/index.php?func=detail&aid=504411&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Rational sum not optimal for overflows Bug #: 519635 <http://sourceforge.net/tracker/index.php?func=detail&aid=519635&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: rational operator&lt; can overflow Bug #: 798357 <http://sourceforge.net/tracker/index.php?func=detail&aid=798357&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: boost::rational documentation typos(?) Bug #: 1043616 <http://sourceforge.net/tracker/index.php?func=detail&aid=1043616&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: no Boolean conversion for boost::rational Bug #: 1239906 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239906&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: call to split_winmain raises exception for 8-bit locale Bug #: 1206663 <http://sourceforge.net/tracker/index.php?func=detail&aid=1206663&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: multitoken broken in program_options 1.33 Bug #: 1266877 <http://sourceforge.net/tracker/index.php?func=detail&aid=1266877&group_id=7…> -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Unresolved externals using a signals template
by Ashok Thirumurthi 10 Nov '05

10 Nov '05

Dear Boost, Could I trouble the list with a question that may be no more than my programming error? I am using VC++7.1 with the boost.signals 1_33_0 library. I successfully wrote a class to wrap custom signals. Upon generalizing the class as a template, VC++ reports unresolved externals. My predicament is that I am unable to match a mangled name of a template instance with the signals library export. What does one do in this case other than identify the problem by inspection? For instance, given a link error that includes a mangled name such as: ?ConnectToNotify@?$TQueryNotifyEvent@V?$signal@$$A6AKAAVCChromaBoostData@Ashok@@@ZU?$last_value@K@boost@@HU?$less@H@std@@V?$function@$$A6AKAAVCChromaBoostData@Ashok@@@ZV?$allocator@X@std@@@4@@boost@@V?$slot@V?$function@$$A6AKAAVCChromaBoostData@Ashok@@@ZV?$allocator@X@std@@@boost@@@2@VCChromaBoostData@Ashok@@@Ashok@@QAEAAVconnection@signals@boost@@ABV?$slot@V?$function@$$A6AKAAVCChromaBoostData@Ashok@@@ZV?$allocator@X@std@@@boost@@@5@@Z What mangled name in the dumpbin output for the boost library should I look for? Even with the promise of undname.exe, the template instantiation makes it difficult to identify the export that I'm not matching. The above unresolved external was referenced by the call to ConnectToNotify in the namespace Ashok: if (CChromaBoostEvent* pNotify = dynamic_cast <CChromaBoostEvent*> (pEventMgr->GetObject (kEvent_ChromaBoost))) { pNotify->ConnectToNotify (boost::bind (&CChromaBoostSlot::OnNotifyChromaBoost, this, _1)); // LNK2019 } However, the link error doesn't occur if CChromaBoostEvent is a class. It does occur if CChromaBoostEvent is an instance of a TQueryNotifyEvent template. More specifically: ***************************** Here's what does work: ***************************** struct strChromaBoostData { strChromaBoostData () : m_nCBoosterLevel (0), m_nCAutoBoosterLevel (-1), m_bBoostForPeople (true) {} int m_nCBoosterLevel; int m_nCAutoBoosterLevel; bool m_bBoostForPeople; }; #define NKNEF_ENTRY __declspec(dllexport) class NKNEF_ENTRY CChromaBoostEvent : public CImageEvt { typedef boost::signal<NKRESULT (const strChromaBoostData&), maximum<NKRESULT> > sigNotify_ChromaBoost; public: CChromaBoostEvent (); virtual ~CChromaBoostEvent (); boost::signals::connection & ConnectToNotify (const sigNotify_ChromaBoost::slot_type& slot); private: sigNotify_ChromaBoost sigNotify; boost::signals::connection conNotify; }; boost::signals::connection & ConnectToNotify(const sigNotify_ChromaBoost::slot_type & slot) { return (conNotify = sigNotify.connect (slot)); } ***************************** Here's what doesn't work: ***************************** template <class TSignal, class TSlot, class TData> class NKNEF_ENTRY TQueryNotifyEvent : public CImageEvt { public: TQueryNotifyEvent (); virtual ~TQueryNotifyEvent (); boost::signals::connection & ConnectToNotify (const TSlot & slot); private: TSignal sigNotify; boost::signals::connection conNotify; }; class CChromaBoostData { public: CChromaBoostData () : m_nCBoosterLevel (0), m_nCAutoBoosterLevel (-1), m_bBoostForPeople (true) {} int m_nCBoosterLevel; int m_nCAutoBoosterLevel; bool m_bBoostForPeople; }; typedef boost::signal<NKRESULT (CChromaBoostData&)> CChromaBoostSignal; typedef TQueryNotifyEvent <CChromaBoostSignal, CChromaBoostSignal::slot_type, CChromaBoostData> CChromaBoostEvent; template <class TSignal, class TSlot, class TData> boost::signals::connection & TQueryNotifyEvent<TSignal, TSlot, TData>::ConnectToNotify(const TSlot & slot) { return (conNotify = sigNotify.connect (slot)); } Thanks for your thoughts, - Ashok Thirumurthi

1 0

[Boost-bugs] [ boost-Bugs-1352426 ] poly archives + stl containers broken once again...
by SourceForge.net 10 Nov '05

10 Nov '05

Bugs item #1352426, was opened at 2005-11-09 10:06 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=1352426&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: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: poly archives + stl containers broken once again... Initial Comment: Hello, fetched fresh boost_1_33_1_beta.tar.gz Compilation (using vc 7.1) stopped. boost\boost\serialization\collections_load_imp.hpp(70) : error C2039: 'reset_object_address' : is not a member of 'boost::archive::polymorphic_iarchive' Seems once again boost::serialization has been broken (can't remember how many times...) making boost pretty much useless for me. My snapshot "boost-RC_1_33_0-05-10-03-1807" (some rc1). Works flawlessly cross-platform (vc 7.1, gcc x86, gcc arm). While fixing this one ... could you please do id:1312222 too .. that messages are really annoying while compiling with -pedantic. Regards, A. Focht ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1352426&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

3 3

Boost regression notification (2005-11-10 [RC_1_33_0])
by Douglas Gregor 10 Nov '05

10 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-10T14:02:16Z 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. functional io array any utility conversion tokenizer dynamic_bitset format integer pool crc Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 1381 failures in 59 libraries: algorithm/minmax (2) algorithm/string (7) any (2) array (5) assign (12) bind (16) concept_check (2) config (5) conversion (3) crc (1) date_time (68) disjoint_sets (1) dynamic_bitset (4) filesystem (6) format (4) function (18) functional (1) functional/hash (15) graph (34) integer (3) io (2) iostreams (31) iterator (20) lambda (15) logic (3) math (5) mpl (88) multi_array (15) multi_index (22) numeric/conversion (6) numeric/interval (15) numeric/ublas (8) optional (4) parameter (5) pool (1) preprocessor (14) program_options (7) property_map (2) ptr_container (12) python (70) random (2) range (11) rational (2) regex (39) serialization (495) signals (6) smart_ptr (9) spirit (113) static_assert (3) test (19) thread (13) timer (1) tokenizer (6) tuple (2) type_traits (67) utility (16) utility/enable_if (8) variant (12) wave (3) |algorithm/minmax| minmax: mingw-3_4_2 minmax_element: mingw-3_4_2 |algorithm/string| conv: mingw-3_4_2 find: mingw-3_4_2 predicate: mingw-3_4_2 regex: mingw-3_4_2 replace: mingw-3_4_2 split: mingw-3_4_2 trim: mingw-3_4_2 |any| any_test: mingw-3_4_2 any_to_ref_test: mingw-3_4_2 |array| array1: mingw-3_4_2 array2: mingw-3_4_2 array3: mingw-3_4_2 array4: mingw-3_4_2 array5: mingw-3_4_2 |assign| basic: mingw-3_4_2 email_example: mingw-3_4_2 list_inserter: mingw-3_4_2 list_of: mingw-3_4_2 list_of_workaround: mingw-3_4_2 multi_index_container: mingw-3_4_2 my_vector_example: mingw-3_4_2 ptr_list_inserter: mingw-3_4_2 ptr_list_of: mingw-3_4_2 static_list_of: mingw-3_4_2 std: mingw-3_4_2 tuple_list_of: mingw-3_4_2 |bind| bind_const_test: mingw-3_4_2 bind_cv_test: mingw-3_4_2 bind_dm2_test: mingw-3_4_2 bind_dm_test: mingw-3_4_2 bind_eq_test: mingw-3_4_2 bind_function_test: mingw-3_4_2 bind_lookup_problem_test: mingw-3_4_2 bind_not_test: mingw-3_4_2 bind_rel_test: mingw-3_4_2 bind_stateful_test: mingw-3_4_2 bind_test: mingw-3_4_2 mem_fn_derived_test: mingw-3_4_2 mem_fn_dm_test: mingw-3_4_2 mem_fn_eq_test: mingw-3_4_2 mem_fn_test: mingw-3_4_2 mem_fn_void_test: mingw-3_4_2 |concept_check| class_concept_check_test: mingw-3_4_2 concept_check_test: mingw-3_4_2 |config| abi_test: mingw-3_4_2 config_info: mingw-3_4_2 config_link_test: mingw-3_4_2 config_test: mingw-3_4_2 limits_test: mingw-3_4_2 |conversion| cast_test: mingw-3_4_2 implicit_cast: mingw-3_4_2 lexical_cast_test: mingw-3_4_2 |crc| crc_test: mingw-3_4_2 |date_time| testc_local_adjustor: mingw-3_4_2 testclock: mingw-3_4_2 testclocks: mingw-3_4_2 testconstrained_value: mingw-3_4_2 testcustom_time_zone: mingw-3_4_2 testdate: mingw-3_4_2 testdate_dll: mingw-3_4_2 testdate_duration: mingw-3_4_2 testdate_duration_dll: mingw-3_4_2 testdate_facet_new: mingw-3_4_2 testdate_facet_new_dll: mingw-3_4_2 testdate_input_facet: mingw-3_4_2 testdate_input_facet_dll: mingw-3_4_2 testdate_iterator: mingw-3_4_2 testdate_iterator_dll: mingw-3_4_2 testdst_rules: mingw-3_4_2 testdst_transition_day_rule: mingw-3_4_2 testduration: mingw-3_4_2 testfiletime_functions: mingw-3_4_2 testformatters: mingw-3_4_2 testformatters_dll: mingw-3_4_2 testgenerators: mingw-3_4_2 testgenerators_dll: mingw-3_4_2 testgeneric_period: mingw-3_4_2 testgreg_cal: mingw-3_4_2 testgreg_cal_dll: mingw-3_4_2 testgreg_day: mingw-3_4_2 testgreg_day_dll: mingw-3_4_2 testgreg_duration_operators: mingw-3_4_2 testgreg_durations: mingw-3_4_2 testgreg_durations_dll: mingw-3_4_2 testgreg_month: mingw-3_4_2 testgreg_month_dll: mingw-3_4_2 testgreg_serialize: mingw-3_4_2 vc-7_1 testgreg_serialize_xml: mingw-3_4_2 vc-7_1 testgreg_year: mingw-3_4_2 testgreg_year_dll: mingw-3_4_2 testgregorian_calendar: mingw-3_4_2 testint_adapter: mingw-3_4_2 testiterator: mingw-3_4_2 testlocal_adjustor: mingw-3_4_2 testlocal_time: mingw-3_4_2 testlocal_time_facet: mingw-3_4_2 testlocal_time_input_facet: mingw-3_4_2 testmicrosec_time_clock: mingw-3_4_2 testparse_date: mingw-3_4_2 testparse_time: mingw-3_4_2 testperiod: mingw-3_4_2 testperiod_dll: mingw-3_4_2 testposix_time_zone: mingw-3_4_2 testtime: mingw-3_4_2 testtime_facet: mingw-3_4_2 testtime_formatters: mingw-3_4_2 testtime_input_facet: mingw-3_4_2 testtime_period: mingw-3_4_2 testtime_resolution_traits: mingw-3_4_2 testtime_serialize: mingw-3_4_2 vc-7_1 testtime_serialize_std_config: mingw-3_4_2 vc-7_1 testtime_serialize_xml: mingw-3_4_2 vc-7_1 testtime_serialize_xml_std_config: mingw-3_4_2 vc-7_1 testtz_database: mingw-3_4_2 testwrapping_int: mingw-3_4_2 |disjoint_sets| disjoint_set_test: mingw-3_4_2 |dynamic_bitset| dyn_bitset_unit_tests1: mingw-3_4_2 dyn_bitset_unit_tests2: mingw-3_4_2 dyn_bitset_unit_tests3: mingw-3_4_2 dyn_bitset_unit_tests4: mingw-3_4_2 |filesystem| convenience_test: mingw-3_4_2 default_name_check_test: mingw-3_4_2 fstream_test: mingw-3_4_2 large_file_support_test: mingw-3_4_2 operations_test: mingw-3_4_2 path_test: mingw-3_4_2 |format| format_test1: mingw-3_4_2 format_test2: mingw-3_4_2 format_test3: mingw-3_4_2 format_test_wstring: mingw-3_4_2 |function| allocator_test: mingw-3_4_2 contains2_test: mingw-3_4_2 contains_test: mingw-3_4_2 function_30: mingw-3_4_2 function_arith_cxx98: mingw-3_4_2 function_arith_portable: mingw-3_4_2 function_n_test: mingw-3_4_2 function_ref_cxx98: mingw-3_4_2 function_ref_portable: mingw-3_4_2 lambda_test: mingw-3_4_2 lib_function_test: mingw-3_4_2 mem_fun_cxx98: mingw-3_4_2 mem_fun_portable: mingw-3_4_2 stateless_test: mingw-3_4_2 std_bind_cxx98: mingw-3_4_2 std_bind_portable: mingw-3_4_2 sum_avg_cxx98: mingw-3_4_2 sum_avg_portable: mingw-3_4_2 |functional| function_test: mingw-3_4_2 |functional/hash| hash_built_in_array_test: mingw-3_4_2 hash_custom_test: mingw-3_4_2 hash_deque_test: mingw-3_4_2 hash_float_test: mingw-3_4_2 hash_function_pointer_test: mingw-3_4_2 hash_list_test: mingw-3_4_2 hash_map_test: mingw-3_4_2 hash_number_test: mingw-3_4_2 hash_pointer_test: mingw-3_4_2 hash_range_test: mingw-3_4_2 hash_set_test: mingw-3_4_2 hash_string_test: mingw-3_4_2 hash_value_array_test: mingw-3_4_2 hash_vector_test: mingw-3_4_2 link_test: mingw-3_4_2 |graph| adj_list_cc: mingw-3_4_2 adj_matrix_cc: mingw-3_4_2 adjacency_matrix_test: mingw-3_4_2 astar_search_test: mingw-3_4_2 bellman-test: mingw-3_4_2 betweenness_centrality_test: mingw-3_4_2 bfs: mingw-3_4_2 bfs_cc: mingw-3_4_2 biconnected_components_test: mingw-3_4_2 bundled_properties: mingw-3_4_2 copy: mingw-3_4_2 cuthill_mckee_ordering: mingw-3_4_2 dag_longest_paths: mingw-3_4_2 dfs: mingw-3_4_2 dfs_cc: mingw-3_4_2 dijkstra_cc: mingw-3_4_2 dijkstra_heap_performance: mingw-3_4_2 edge_list_cc: mingw-3_4_2 filtered_graph_cc: mingw-3_4_2 floyd_warshall_test: mingw-3_4_2 graph: mingw-3_4_2 graph_concepts: mingw-3_4_2 graphviz_test: mingw-3_4_2 gursoy_atun_layout_test: mingw-3_4_2 isomorphism: mingw-3_4_2 king_ordering: mingw-3_4_2 layout_test: mingw-3_4_2 property_iter: mingw-3_4_2 relaxed_heap_test: mingw-3_4_2 reverse_graph_cc: mingw-3_4_2 sequential_vertex_coloring: mingw-3_4_2 subgraph: mingw-3_4_2 transitive_closure_test: mingw-3_4_2 vector_graph_cc: mingw-3_4_2 |integer| cstdint_test: mingw-3_4_2 integer_test: mingw-3_4_2 integer_traits_test: mingw-3_4_2 |io| ios_state_test: mingw-3_4_2 ios_state_unit_test: mingw-3_4_2 |iostreams| array_test: mingw-3_4_2 auto_close_test: mingw-3_4_2 buffer_size_test: mingw-3_4_2 bzip2_test: mingw-3_4_2 component_access_test: mingw-3_4_2 compose_test: mingw-3_4_2 copy_test: mingw-3_4_2 counter_test: mingw-3_4_2 direct_adapter_test: mingw-3_4_2 example_test: mingw-3_4_2 file_descriptor_test: mingw-3_4_2 file_test: mingw-3_4_2 filtering_stream_test: mingw-3_4_2 finite_state_filter_test: mingw-3_4_2 flush_test: mingw-3_4_2 gzip_test: mingw-3_4_2 invert_test: mingw-3_4_2 line_filter_test: mingw-3_4_2 mapped_file_test: mingw-3_4_2 newline_test: mingw-3_4_2 null_test: mingw-3_4_2 pipeline_test: mingw-3_4_2 positioning_test: mingw-3_4_2 regex_filter_test: mingw-3_4_2 restrict_test: mingw-3_4_2 seekable_file_test: mingw-3_4_2 seekable_filter_test: mingw-3_4_2 stdio_filter_test: mingw-3_4_2 symmetric_filter_test: mingw-3_4_2 tee_test: mingw-3_4_2 zlib_test: mingw-3_4_2 |iterator| concept_tests: mingw-3_4_2 counting_iterator_test: mingw-3_4_2 filter_iterator_test: mingw-3_4_2 indirect_iter_member_types: mingw-3_4_2 indirect_iterator_test: mingw-3_4_2 interoperable: mingw-3_4_2 is_convertible_fail: mingw-3_4_2 is_lvalue_iterator: mingw-3_4_2 is_readable_iterator: mingw-3_4_2 iterator_adaptor_cc: mingw-3_4_2 iterator_adaptor_test: mingw-3_4_2 iterator_archetype_cc: mingw-3_4_2 iterator_facade: mingw-3_4_2 iterator_traits_test: mingw-3_4_2 permutation_iterator_test: mingw-3_4_2 pointee: mingw-3_4_2 reverse_iterator_test: mingw-3_4_2 transform_iterator_test: mingw-3_4_2 unit_tests: mingw-3_4_2 zip_iterator_test: mingw-3_4_2 |lambda| algorithm_test: mingw-3_4_2 bind_tests_advanced: mingw-3_4_2 bind_tests_simple: mingw-3_4_2 bind_tests_simple_f_refs: mingw-3_4_2 bll_and_function: mingw-3_4_2 constructor_tests: mingw-3_4_2 control_structures: mingw-3_4_2 exception_test: mingw-3_4_2 extending_rt_traits: mingw-3_4_2 is_instance_of_test: mingw-3_4_2 lambda_cast_test: mingw-3_4_2 member_pointer_test: mingw-3_4_2 operator_tests_simple: mingw-3_4_2 phoenix_control_structures: mingw-3_4_2 switch_construct: mingw-3_4_2 |logic| tribool_io_test: mingw-3_4_2 tribool_rename_test: mingw-3_4_2 tribool_test: mingw-3_4_2 |math| common_factor_test: mingw-3_4_2 octonion_test: mingw-3_4_2 quaternion_mult_incl_test: mingw-3_4_2 quaternion_test: mingw-3_4_2 special_functions_test: mingw-3_4_2 |mpl| advance: mingw-3_4_2 always: mingw-3_4_2 apply: mingw-3_4_2 apply_wrap: mingw-3_4_2 arithmetic: mingw-3_4_2 as_sequence: mingw-3_4_2 assert: mingw-3_4_2 at: mingw-3_4_2 back: mingw-3_4_2 bind: mingw-3_4_2 bitwise: mingw-3_4_2 bool: mingw-3_4_2 comparison: mingw-3_4_2 contains: mingw-3_4_2 copy: mingw-3_4_2 copy_if: mingw-3_4_2 count: mingw-3_4_2 count_if: mingw-3_4_2 deque: mingw-3_4_2 distance: mingw-3_4_2 empty: mingw-3_4_2 equal: mingw-3_4_2 erase: mingw-3_4_2 erase_range: mingw-3_4_2 eval_if: mingw-3_4_2 filter_view: mingw-3_4_2 find: mingw-3_4_2 find_if: mingw-3_4_2 fold: mingw-3_4_2 for_each: mingw-3_4_2 front: mingw-3_4_2 has_xxx: mingw-3_4_2 identity: mingw-3_4_2 if: mingw-3_4_2 index_of: mingw-3_4_2 inherit: mingw-3_4_2 insert: mingw-3_4_2 insert_range: mingw-3_4_2 int: mingw-3_4_2 integral_c: mingw-3_4_2 is_placeholder: mingw-3_4_2 is_sequence: mingw-3_4_2 iterator_tags: mingw-3_4_2 joint_view: mingw-3_4_2 lambda: mingw-3_4_2 lambda_args: mingw-3_4_2 largest_int: mingw-3_4_2 list: mingw-3_4_2 list_c: mingw-3_4_2 logical: mingw-3_4_2 lower_bound: mingw-3_4_2 map: mingw-3_4_2 max_element: mingw-3_4_2 min_max: mingw-3_4_2 msvc_is_class: mingw-3_4_2 multiset: mingw-3_4_2 next: mingw-3_4_2 no_has_xxx: mingw-3_4_2 numeric_ops: mingw-3_4_2 pair_view: mingw-3_4_2 partition: mingw-3_4_2 pop_front: mingw-3_4_2 push_front: mingw-3_4_2 quote: mingw-3_4_2 range_c: mingw-3_4_2 remove: mingw-3_4_2 remove_if: mingw-3_4_2 replace: mingw-3_4_2 replace_if: mingw-3_4_2 reverse: mingw-3_4_2 same_as: mingw-3_4_2 set: mingw-3_4_2 set_c: mingw-3_4_2 single_view: mingw-3_4_2 size: mingw-3_4_2 size_t: mingw-3_4_2 sizeof: mingw-3_4_2 sort: mingw-3_4_2 stable_partition: mingw-3_4_2 template_arity: mingw-3_4_2 transform: mingw-3_4_2 transform_view: mingw-3_4_2 unique: mingw-3_4_2 unpack_args: mingw-3_4_2 upper_bound: mingw-3_4_2 vector: mingw-3_4_2 vector_c: mingw-3_4_2 zip_view: mingw-3_4_2 |multi_array| access: mingw-3_4_2 assign: mingw-3_4_2 assign_to_array: mingw-3_4_2 compare: mingw-3_4_2 concept_checks: mingw-3_4_2 constructors: mingw-3_4_2 idxgen1: mingw-3_4_2 index_bases: mingw-3_4_2 iterators: mingw-3_4_2 range1: mingw-3_4_2 reshape: mingw-3_4_2 resize: mingw-3_4_2 slice: mingw-3_4_2 stl_interaction: mingw-3_4_2 storage_order: mingw-3_4_2 |multi_index| test_basic: mingw-3_4_2 test_capacity: mingw-3_4_2 test_comparison: mingw-3_4_2 test_composite_key: mingw-3_4_2 test_conv_iterators: mingw-3_4_2 test_copy_assignment: mingw-3_4_2 test_hash_ops: mingw-3_4_2 test_iterators: mingw-3_4_2 test_key_extractors: mingw-3_4_2 test_list_ops: mingw-3_4_2 test_modifiers: mingw-3_4_2 test_mpl_ops: mingw-3_4_2 test_observers: mingw-3_4_2 test_projection: mingw-3_4_2 test_range: mingw-3_4_2 test_safe_mode: mingw-3_4_2 test_serialization: mingw-3_4_2 vc-7_1 test_set_ops: mingw-3_4_2 test_special_list_ops: mingw-3_4_2 test_special_set_ops: mingw-3_4_2 test_update: mingw-3_4_2 |numeric/conversion| bounds_test: mingw-3_4_2 converter_test: mingw-3_4_2 numeric_cast_test: mingw-3_4_2 traits_test: mingw-3_4_2 udt_example_0: mingw-3_4_2 udt_support_test: mingw-3_4_2 |numeric/interval| add: mingw-3_4_2 cmp: mingw-3_4_2 cmp_exn: mingw-3_4_2 cmp_exp: mingw-3_4_2 cmp_lex: mingw-3_4_2 cmp_set: mingw-3_4_2 cmp_tribool: mingw-3_4_2 det: mingw-3_4_2 fmod: mingw-3_4_2 integer: mingw-3_4_2 mul: mingw-3_4_2 overflow: mingw-3_4_2 pi: mingw-3_4_2 pow: mingw-3_4_2 test_float: mingw-3_4_2 |numeric/ublas| concepts: mingw-3_4_2 placement_new: mingw-3_4_2 test1: mingw-3_4_2 test2: mingw-3_4_2 test3: mingw-3_4_2 test4: mingw-3_4_2 test5: mingw-3_4_2 test6: mingw-3_4_2 |optional| optional_test: mingw-3_4_2 optional_test_inplace: mingw-3_4_2 optional_test_ref: mingw-3_4_2 optional_test_tie: mingw-3_4_2 |parameter| basics: mingw-3_4_2 macros: mingw-3_4_2 sfinae: mingw-3_4_2 tutorial: mingw-3_4_2 unwrap_cv_reference: mingw-3_4_2 |pool| test_pool_alloc: mingw-3_4_2 |preprocessor| arithmetic: mingw-3_4_2 array: mingw-3_4_2 comparison: mingw-3_4_2 control: mingw-3_4_2 debug: mingw-3_4_2 facilities: mingw-3_4_2 iteration: mingw-3_4_2 list: mingw-3_4_2 logical: mingw-3_4_2 repetition: mingw-3_4_2 selection: mingw-3_4_2 seq: mingw-3_4_2 slot: mingw-3_4_2 tuple: mingw-3_4_2 |program_options| cmdline_test: mingw-3_4_2 options_description_test: mingw-3_4_2 parsers_test: mingw-3_4_2 positional_options_test: mingw-3_4_2 variable_map_test: mingw-3_4_2 winmain: mingw-3_4_2 winmain_dll: mingw-3_4_2 |property_map| dynamic_properties_test: mingw-3_4_2 property_map_cc: mingw-3_4_2 |ptr_container| incomplete_type_test: mingw-3_4_2 indirect_fun: mingw-3_4_2 iterator_test: mingw-3_4_2 ptr_array: mingw-3_4_2 ptr_deque: mingw-3_4_2 ptr_list: mingw-3_4_2 ptr_map: mingw-3_4_2 ptr_set: mingw-3_4_2 ptr_vector: mingw-3_4_2 tree_test: mingw-3_4_2 tut1: mingw-3_4_2 view_example: mingw-3_4_2 |python| andreas_beyer: mingw-3_4_2 args: mingw-3_4_2 auto_ptr: mingw-3_4_2 back_reference: mingw-3_4_2 bases: mingw-3_4_2 ben_scott1: mingw-3_4_2 bienstman1: mingw-3_4_2 bienstman2: mingw-3_4_2 bienstman3: mingw-3_4_2 borrowed: mingw-3_4_2 builtin_converters: mingw-3_4_2 callbacks: mingw-3_4_2 const_argument: mingw-3_4_2 copy_ctor_mutates_rhs: mingw-3_4_2 crossmod_exception: mingw-3_4_2 data_members: mingw-3_4_2 defaults: mingw-3_4_2 destroy_test: mingw-3_4_2 dict: mingw-3_4_2 docstring: mingw-3_4_2 embedding: mingw-3_4_2 enum: mingw-3_4_2 exception_translator: mingw-3_4_2 extract: mingw-3_4_2 if_else: mingw-3_4_2 implicit: mingw-3_4_2 indirect_traits_test: mingw-3_4_2 injected: mingw-3_4_2 iterator: mingw-3_4_2 keywords: mingw-3_4_2 list: mingw-3_4_2 long: mingw-3_4_2 minimal: mingw-3_4_2 multi_arg_constructor: mingw-3_4_2 nested: mingw-3_4_2 numpy: mingw-3_4_2 object: mingw-3_4_2 object_manager: mingw-3_4_2 opaque: mingw-3_4_2 operators: mingw-3_4_2 pearu1: mingw-3_4_2 pickle1: mingw-3_4_2 pickle2: mingw-3_4_2 pickle3: mingw-3_4_2 pickle4: mingw-3_4_2 pointee: mingw-3_4_2 pointer_type_id_test: mingw-3_4_2 pointer_vector: mingw-3_4_2 polymorphism: mingw-3_4_2 polymorphism2: mingw-3_4_2 polymorphism2_auto_ptr: mingw-3_4_2 properties: mingw-3_4_2 raw_ctor: mingw-3_4_2 result: mingw-3_4_2 return_arg: mingw-3_4_2 select_arg_to_python_test: mingw-3_4_2 select_from_python_test: mingw-3_4_2 select_holder: mingw-3_4_2 shared_ptr: mingw-3_4_2 slice: mingw-3_4_2 staticmethod: mingw-3_4_2 str: mingw-3_4_2 string_literal: mingw-3_4_2 test_pointer_adoption: mingw-3_4_2 try: mingw-3_4_2 tuple: mingw-3_4_2 upcast: mingw-3_4_2 vector_indexing_suite: mingw-3_4_2 virtual_functions: mingw-3_4_2 wrapper_held_type: mingw-3_4_2 |random| random_demo: mingw-3_4_2 random_test: mingw-3_4_2 |range| algorithm_example: mingw-3_4_2 array: mingw-3_4_2 const_ranges: mingw-3_4_2 extension_mechanism: mingw-3_4_2 iterator_pair: mingw-3_4_2 iterator_range: mingw-3_4_2 partial_workaround: mingw-3_4_2 reversible_range: mingw-3_4_2 std_container: mingw-3_4_2 string: mingw-3_4_2 sub_range: mingw-3_4_2 |rational| rational_example: mingw-3_4_2 rational_test: mingw-3_4_2 |regex| bad_expression_test: mingw-3_4_2 captures_example: mingw-3_4_2 captures_test: mingw-3_4_2 collate_info: mingw-3_4_2 concept_check: mingw-3_4_2 credit_card_example: mingw-3_4_2 grep: mingw-3_4_2 icu_concept_check: mingw-3_4_2 icu_example: mingw-3_4_2 mfc_example: mingw-3_4_2 object_cache_test: mingw-3_4_2 partial_regex_grep: mingw-3_4_2 partial_regex_match: mingw-3_4_2 posix_api_check: mingw-3_4_2 posix_api_check_cpp: mingw-3_4_2 recursion_test: mingw-3_4_2 regex_config_info: mingw-3_4_2 regex_dll_config_info: mingw-3_4_2 regex_grep_example_1: mingw-3_4_2 regex_grep_example_2: mingw-3_4_2 regex_grep_example_3: mingw-3_4_2 regex_grep_example_4: mingw-3_4_2 regex_iterator_example: mingw-3_4_2 regex_match_example: mingw-3_4_2 regex_merge_example: mingw-3_4_2 regex_regress: mingw-3_4_2 regex_regress_dll: mingw-3_4_2 vc-8_0 regex_replace_example: mingw-3_4_2 regex_search_example: mingw-3_4_2 regex_split_example_1: mingw-3_4_2 regex_split_example_2: mingw-3_4_2 regex_timer: mingw-3_4_2 regex_token_iterator_eg_1: mingw-3_4_2 regex_token_iterator_eg_2: mingw-3_4_2 static_mutex_test: mingw-3_4_2 unicode_iterator_test: mingw-3_4_2 wide_posix_api_check_c: mingw-3_4_2 wide_posix_api_check_cpp: mingw-3_4_2 |serialization| test_array_binary_archive: mingw-3_4_2 vc-7_1 test_array_binary_archive_dll: mingw-3_4_2 test_array_text_archive: mingw-3_4_2 vc-7_1 test_array_text_archive_dll: mingw-3_4_2 test_array_text_warchive: vc-7_1 test_array_xml_archive: mingw-3_4_2 vc-7_1 test_array_xml_archive_dll: mingw-3_4_2 test_array_xml_warchive: vc-7_1 test_binary_binary_archive: mingw-3_4_2 vc-7_1 test_binary_binary_archive_dll: mingw-3_4_2 test_binary_text_archive: mingw-3_4_2 vc-7_1 test_binary_text_archive_dll: mingw-3_4_2 test_binary_text_warchive: vc-7_1 test_binary_xml_archive: mingw-3_4_2 vc-7_1 test_binary_xml_archive_dll: mingw-3_4_2 test_binary_xml_warchive: vc-7_1 test_class_info_load_binary_archive: mingw-3_4_2 vc-7_1 test_class_info_load_binary_archive_dll: mingw-3_4_2 test_class_info_load_text_archive: mingw-3_4_2 vc-7_1 test_class_info_load_text_archive_dll: mingw-3_4_2 test_class_info_load_text_warchive: vc-7_1 test_class_info_load_xml_archive: mingw-3_4_2 vc-7_1 test_class_info_load_xml_archive_dll: mingw-3_4_2 test_class_info_load_xml_warchive: vc-7_1 test_class_info_save_binary_archive: mingw-3_4_2 vc-7_1 test_class_info_save_binary_archive_dll: mingw-3_4_2 test_class_info_save_text_archive: mingw-3_4_2 vc-7_1 test_class_info_save_text_archive_dll: mingw-3_4_2 test_class_info_save_text_warchive: vc-7_1 test_class_info_save_xml_archive: mingw-3_4_2 vc-7_1 test_class_info_save_xml_archive_dll: mingw-3_4_2 test_class_info_save_xml_warchive: vc-7_1 test_const_pass: mingw-3_4_2 test_contained_class_binary_archive: mingw-3_4_2 vc-7_1 test_contained_class_binary_archive_dll: mingw-3_4_2 test_contained_class_text_archive: mingw-3_4_2 vc-7_1 test_contained_class_text_archive_dll: mingw-3_4_2 test_contained_class_text_warchive: vc-7_1 test_contained_class_xml_archive: mingw-3_4_2 vc-7_1 test_contained_class_xml_archive_dll: mingw-3_4_2 test_contained_class_xml_warchive: vc-7_1 test_cyclic_ptrs_binary_archive: mingw-3_4_2 vc-7_1 test_cyclic_ptrs_binary_archive_dll: mingw-3_4_2 test_cyclic_ptrs_text_archive: mingw-3_4_2 vc-7_1 test_cyclic_ptrs_text_archive_dll: mingw-3_4_2 test_cyclic_ptrs_text_warchive: vc-7_1 test_cyclic_ptrs_xml_archive: mingw-3_4_2 vc-7_1 test_cyclic_ptrs_xml_archive_dll: mingw-3_4_2 test_cyclic_ptrs_xml_warchive: vc-7_1 test_delete_pointer_binary_archive: mingw-3_4_2 vc-7_1 test_delete_pointer_binary_archive_dll: mingw-3_4_2 test_delete_pointer_text_archive: mingw-3_4_2 vc-7_1 test_delete_pointer_text_archive_dll: mingw-3_4_2 test_delete_pointer_text_warchive: vc-7_1 test_delete_pointer_xml_archive: mingw-3_4_2 vc-7_1 test_delete_pointer_xml_archive_dll: mingw-3_4_2 test_delete_pointer_xml_warchive: vc-7_1 test_demo: mingw-3_4_2 vc-7_1 test_demo_auto_ptr: mingw-3_4_2 vc-7_1 test_demo_auto_ptr_dll: mingw-3_4_2 test_demo_dll: mingw-3_4_2 test_demo_exception: mingw-3_4_2 vc-7_1 test_demo_exception_dll: mingw-3_4_2 test_demo_fast_archive: mingw-3_4_2 vc-7_1 test_demo_fast_archive_dll: mingw-3_4_2 test_demo_pimpl: mingw-3_4_2 vc-7_1 test_demo_pimpl_dll: mingw-3_4_2 test_demo_polymorphic: mingw-3_4_2 vc-7_1 test_demo_polymorphic_dll: mingw-3_4_2 test_demo_portable_archive: mingw-3_4_2 vc-7_1 test_demo_portable_archive_dll: mingw-3_4_2 test_demo_shared_ptr: mingw-3_4_2 vc-7_1 test_demo_shared_ptr_dll: mingw-3_4_2 test_demo_xml: mingw-3_4_2 vc-7_1 test_demo_xml_dll: mingw-3_4_2 test_demo_xml_load: mingw-3_4_2 vc-7_1 test_demo_xml_load_dll: mingw-3_4_2 vc-8_0 test_demo_xml_save: mingw-3_4_2 vc-7_1 test_demo_xml_save_dll: mingw-3_4_2 vc-8_0 test_deque_binary_archive: mingw-3_4_2 vc-7_1 test_deque_binary_archive_dll: mingw-3_4_2 test_deque_text_archive: mingw-3_4_2 vc-7_1 test_deque_text_archive_dll: mingw-3_4_2 test_deque_text_warchive: vc-7_1 test_deque_xml_archive: mingw-3_4_2 vc-7_1 test_deque_xml_archive_dll: mingw-3_4_2 test_deque_xml_warchive: vc-7_1 test_derived_binary_archive: mingw-3_4_2 vc-7_1 test_derived_binary_archive_dll: mingw-3_4_2 test_derived_class_binary_archive: mingw-3_4_2 vc-7_1 test_derived_class_binary_archive_dll: mingw-3_4_2 test_derived_class_ptr_binary_archive: mingw-3_4_2 vc-7_1 test_derived_class_ptr_binary_archive_dll: mingw-3_4_2 test_derived_class_ptr_text_archive: mingw-3_4_2 vc-7_1 test_derived_class_ptr_text_archive_dll: mingw-3_4_2 test_derived_class_ptr_text_warchive: vc-7_1 test_derived_class_ptr_xml_archive: mingw-3_4_2 vc-7_1 test_derived_class_ptr_xml_archive_dll: mingw-3_4_2 test_derived_class_ptr_xml_warchive: vc-7_1 test_derived_class_text_archive: mingw-3_4_2 vc-7_1 test_derived_class_text_archive_dll: mingw-3_4_2 test_derived_class_text_warchive: vc-7_1 test_derived_class_xml_archive: mingw-3_4_2 vc-7_1 test_derived_class_xml_archive_dll: mingw-3_4_2 test_derived_class_xml_warchive: vc-7_1 test_derived_text_archive: mingw-3_4_2 vc-7_1 test_derived_text_archive_dll: mingw-3_4_2 test_derived_text_warchive: vc-7_1 test_derived_xml_archive: mingw-3_4_2 vc-7_1 test_derived_xml_archive_dll: mingw-3_4_2 test_derived_xml_warchive: vc-7_1 test_diamond_binary_archive: mingw-3_4_2 vc-7_1 test_diamond_binary_archive_dll: mingw-3_4_2 test_diamond_text_archive: mingw-3_4_2 vc-7_1 test_diamond_text_archive_dll: mingw-3_4_2 test_diamond_text_warchive: vc-7_1 test_diamond_xml_archive: mingw-3_4_2 vc-7_1 test_diamond_xml_archive_dll: mingw-3_4_2 test_diamond_xml_warchive: vc-7_1 test_exported_binary_archive: mingw-3_4_2 vc-7_1 test_exported_binary_archive_dll: mingw-3_4_2 test_exported_text_archive: mingw-3_4_2 vc-7_1 test_exported_text_archive_dll: mingw-3_4_2 test_exported_text_warchive: vc-7_1 test_exported_xml_archive: mingw-3_4_2 vc-7_1 test_exported_xml_archive_dll: mingw-3_4_2 test_exported_xml_warchive: vc-7_1 test_exported_xml_warchive_dll: vc-8_0 test_inclusion: mingw-3_4_2 test_iterators: mingw-3_4_2 test_iterators_base64: mingw-3_4_2 test_list_binary_archive: mingw-3_4_2 vc-7_1 test_list_binary_archive_dll: mingw-3_4_2 test_list_ptrs_binary_archive: mingw-3_4_2 vc-7_1 test_list_ptrs_binary_archive_dll: mingw-3_4_2 test_list_ptrs_text_archive: mingw-3_4_2 vc-7_1 test_list_ptrs_text_archive_dll: mingw-3_4_2 test_list_ptrs_text_warchive: vc-7_1 test_list_ptrs_xml_archive: mingw-3_4_2 vc-7_1 test_list_ptrs_xml_archive_dll: mingw-3_4_2 test_list_ptrs_xml_warchive: vc-7_1 test_list_text_archive: mingw-3_4_2 vc-7_1 test_list_text_archive_dll: mingw-3_4_2 test_list_text_warchive: vc-7_1 test_list_xml_archive: mingw-3_4_2 vc-7_1 test_list_xml_archive_dll: mingw-3_4_2 test_list_xml_warchive: vc-7_1 test_map_binary_archive: mingw-3_4_2 vc-7_1 test_map_binary_archive_dll: mingw-3_4_2 test_map_text_archive: mingw-3_4_2 vc-7_1 test_map_text_archive_dll: mingw-3_4_2 test_map_text_warchive: vc-7_1 test_map_xml_archive: mingw-3_4_2 vc-7_1 test_map_xml_archive_dll: mingw-3_4_2 test_map_xml_warchive: vc-7_1 test_mi_binary_archive: mingw-3_4_2 vc-7_1 test_mi_binary_archive_dll: mingw-3_4_2 test_mi_text_archive: mingw-3_4_2 vc-7_1 test_mi_text_archive_dll: mingw-3_4_2 test_mi_text_warchive: vc-7_1 test_mi_xml_archive: mingw-3_4_2 vc-7_1 test_mi_xml_archive_dll: mingw-3_4_2 test_mi_xml_warchive: vc-7_1 test_mult_archive_types: mingw-3_4_2 vc-7_1 test_mult_archive_types_dll: mingw-3_4_2 test_multiple_ptrs_binary_archive: mingw-3_4_2 vc-7_1 test_multiple_ptrs_binary_archive_dll: mingw-3_4_2 test_multiple_ptrs_text_archive: mingw-3_4_2 vc-7_1 test_multiple_ptrs_text_archive_dll: mingw-3_4_2 test_multiple_ptrs_text_warchive: vc-7_1 test_multiple_ptrs_xml_archive: mingw-3_4_2 vc-7_1 test_multiple_ptrs_xml_archive_dll: mingw-3_4_2 test_multiple_ptrs_xml_warchive: vc-7_1 test_no_rtti_binary_archive: mingw-3_4_2 vc-7_1 test_no_rtti_binary_archive_dll: mingw-3_4_2 test_no_rtti_text_archive: mingw-3_4_2 vc-7_1 test_no_rtti_text_archive_dll: mingw-3_4_2 test_no_rtti_text_warchive: vc-7_1 test_no_rtti_xml_archive: mingw-3_4_2 vc-7_1 test_no_rtti_xml_archive_dll: mingw-3_4_2 test_no_rtti_xml_warchive: vc-7_1 test_non_default_ctor2_binary_archive: mingw-3_4_2 vc-7_1 test_non_default_ctor2_binary_archive_dll: mingw-3_4_2 test_non_default_ctor2_text_archive: mingw-3_4_2 vc-7_1 test_non_default_ctor2_text_archive_dll: mingw-3_4_2 test_non_default_ctor2_text_warchive: vc-7_1 test_non_default_ctor2_xml_archive: mingw-3_4_2 vc-7_1 test_non_default_ctor2_xml_archive_dll: mingw-3_4_2 test_non_default_ctor2_xml_warchive: vc-7_1 test_non_default_ctor_binary_archive: mingw-3_4_2 vc-7_1 test_non_default_ctor_binary_archive_dll: mingw-3_4_2 test_non_default_ctor_text_archive: mingw-3_4_2 vc-7_1 test_non_default_ctor_text_archive_dll: mingw-3_4_2 test_non_default_ctor_text_warchive: vc-7_1 test_non_default_ctor_xml_archive: mingw-3_4_2 vc-7_1 test_non_default_ctor_xml_archive_dll: mingw-3_4_2 test_non_default_ctor_xml_warchive: vc-7_1 test_non_intrusive_binary_archive: mingw-3_4_2 vc-7_1 test_non_intrusive_binary_archive_dll: mingw-3_4_2 test_non_intrusive_text_archive: mingw-3_4_2 vc-7_1 test_non_intrusive_text_archive_dll: mingw-3_4_2 test_non_intrusive_text_warchive: vc-7_1 test_non_intrusive_xml_archive: mingw-3_4_2 vc-7_1 test_non_intrusive_xml_archive_dll: mingw-3_4_2 test_non_intrusive_xml_warchive: vc-7_1 test_null_ptr_binary_archive: mingw-3_4_2 vc-7_1 test_null_ptr_binary_archive_dll: mingw-3_4_2 test_null_ptr_text_archive: mingw-3_4_2 vc-7_1 test_null_ptr_text_archive_dll: mingw-3_4_2 test_null_ptr_text_warchive: vc-7_1 test_null_ptr_xml_archive: mingw-3_4_2 vc-7_1 test_null_ptr_xml_archive_dll: mingw-3_4_2 test_null_ptr_xml_warchive: vc-7_1 test_nvp_binary_archive: mingw-3_4_2 vc-7_1 test_nvp_binary_archive_dll: mingw-3_4_2 test_nvp_text_archive: mingw-3_4_2 vc-7_1 test_nvp_text_archive_dll: mingw-3_4_2 test_nvp_text_warchive: vc-7_1 test_nvp_xml_archive: mingw-3_4_2 vc-7_1 test_nvp_xml_archive_dll: mingw-3_4_2 test_nvp_xml_warchive: vc-7_1 test_object_binary_archive: mingw-3_4_2 vc-7_1 test_object_binary_archive_dll: mingw-3_4_2 test_object_text_archive: mingw-3_4_2 vc-7_1 test_object_text_archive_dll: mingw-3_4_2 test_object_text_warchive: vc-7_1 test_object_xml_archive: mingw-3_4_2 vc-7_1 test_object_xml_archive_dll: mingw-3_4_2 test_object_xml_warchive: vc-7_1 test_optional_binary_archive: mingw-3_4_2 vc-7_1 test_optional_binary_archive_dll: mingw-3_4_2 test_optional_text_archive: mingw-3_4_2 vc-7_1 test_optional_text_archive_dll: mingw-3_4_2 test_optional_text_warchive: vc-7_1 test_optional_xml_archive: mingw-3_4_2 vc-7_1 test_optional_xml_archive_dll: mingw-3_4_2 test_optional_xml_warchive: vc-7_1 test_polymorphic_binary_archive: mingw-3_4_2 vc-7_1 test_polymorphic_binary_archive_dll: mingw-3_4_2 test_polymorphic_text_archive: mingw-3_4_2 vc-7_1 test_polymorphic_text_archive_dll: mingw-3_4_2 test_polymorphic_text_warchive: vc-7_1 test_polymorphic_xml_archive: mingw-3_4_2 vc-7_1 test_polymorphic_xml_archive_dll: mingw-3_4_2 test_polymorphic_xml_warchive: vc-7_1 test_primitive_binary_archive: mingw-3_4_2 vc-7_1 test_primitive_binary_archive_dll: mingw-3_4_2 test_primitive_text_archive: mingw-3_4_2 vc-7_1 test_primitive_text_archive_dll: mingw-3_4_2 test_primitive_text_warchive: vc-7_1 test_primitive_xml_archive: mingw-3_4_2 vc-7_1 test_primitive_xml_archive_dll: mingw-3_4_2 test_primitive_xml_warchive: vc-7_1 test_private_ctor: mingw-3_4_2 vc-7_1 test_private_ctor_dll: mingw-3_4_2 test_recursion_binary_archive: mingw-3_4_2 vc-7_1 test_recursion_binary_archive_dll: mingw-3_4_2 test_recursion_text_archive: mingw-3_4_2 vc-7_1 test_recursion_text_archive_dll: mingw-3_4_2 test_recursion_text_warchive: vc-7_1 test_recursion_xml_archive: mingw-3_4_2 vc-7_1 test_recursion_xml_archive_dll: mingw-3_4_2 test_recursion_xml_warchive: vc-7_1 test_registered_binary_archive: mingw-3_4_2 vc-7_1 test_registered_binary_archive_dll: mingw-3_4_2 test_registered_text_archive: mingw-3_4_2 vc-7_1 test_registered_text_archive_dll: mingw-3_4_2 test_registered_text_warchive: vc-7_1 test_registered_xml_archive: mingw-3_4_2 vc-7_1 test_registered_xml_archive_dll: mingw-3_4_2 test_registered_xml_warchive: vc-7_1 test_reset_object_address: mingw-3_4_2 vc-7_1 test_reset_object_address_dll: mingw-3_4_2 test_set_binary_archive: mingw-3_4_2 vc-7_1 test_set_binary_archive_dll: mingw-3_4_2 test_set_text_archive: mingw-3_4_2 vc-7_1 test_set_text_archive_dll: mingw-3_4_2 test_set_text_warchive: vc-7_1 test_set_xml_archive: mingw-3_4_2 vc-7_1 test_set_xml_archive_dll: mingw-3_4_2 test_set_xml_warchive: vc-7_1 test_shared_ptr_132_binary_archive: mingw-3_4_2 vc-7_1 test_shared_ptr_132_binary_archive_dll: mingw-3_4_2 test_shared_ptr_132_text_archive: mingw-3_4_2 vc-7_1 test_shared_ptr_132_text_archive_dll: mingw-3_4_2 test_shared_ptr_132_text_warchive: vc-7_1 test_shared_ptr_132_xml_archive: mingw-3_4_2 vc-7_1 test_shared_ptr_132_xml_archive_dll: mingw-3_4_2 test_shared_ptr_132_xml_warchive: vc-7_1 test_shared_ptr_binary_archive: mingw-3_4_2 vc-7_1 test_shared_ptr_binary_archive_dll: mingw-3_4_2 test_shared_ptr_text_archive: mingw-3_4_2 vc-7_1 test_shared_ptr_text_archive_dll: mingw-3_4_2 test_shared_ptr_text_warchive: vc-7_1 test_shared_ptr_xml_archive: mingw-3_4_2 vc-7_1 test_shared_ptr_xml_archive_dll: mingw-3_4_2 test_shared_ptr_xml_warchive: vc-7_1 test_simple_class_binary_archive: mingw-3_4_2 vc-7_1 test_simple_class_binary_archive_dll: mingw-3_4_2 test_simple_class_ptr_binary_archive: mingw-3_4_2 vc-7_1 test_simple_class_ptr_binary_archive_dll: mingw-3_4_2 test_simple_class_ptr_text_archive: mingw-3_4_2 vc-7_1 test_simple_class_ptr_text_archive_dll: mingw-3_4_2 test_simple_class_ptr_text_warchive: vc-7_1 test_simple_class_ptr_xml_archive: mingw-3_4_2 vc-7_1 test_simple_class_ptr_xml_archive_dll: mingw-3_4_2 test_simple_class_ptr_xml_warchive: vc-7_1 test_simple_class_text_archive: mingw-3_4_2 vc-7_1 test_simple_class_text_archive_dll: mingw-3_4_2 test_simple_class_text_warchive: vc-7_1 test_simple_class_xml_archive: mingw-3_4_2 vc-7_1 test_simple_class_xml_archive_dll: mingw-3_4_2 test_simple_class_xml_warchive: vc-7_1 test_smart_cast: mingw-3_4_2 test_split_binary_archive: mingw-3_4_2 vc-7_1 test_split_binary_archive_dll: mingw-3_4_2 test_split_text_archive: mingw-3_4_2 vc-7_1 test_split_text_archive_dll: mingw-3_4_2 test_split_text_warchive: vc-7_1 test_split_xml_archive: mingw-3_4_2 vc-7_1 test_split_xml_archive_dll: mingw-3_4_2 test_split_xml_warchive: vc-7_1 test_static_warning: mingw-3_4_2 test_tracking_binary_archive: mingw-3_4_2 vc-7_1 test_tracking_binary_archive_dll: mingw-3_4_2 test_tracking_text_archive: mingw-3_4_2 vc-7_1 test_tracking_text_archive_dll: mingw-3_4_2 test_tracking_text_warchive: vc-7_1 test_tracking_xml_archive: mingw-3_4_2 vc-7_1 test_tracking_xml_archive_dll: mingw-3_4_2 test_tracking_xml_warchive: vc-7_1 test_traits_pass: mingw-3_4_2 test_unregistered_binary_archive: mingw-3_4_2 vc-7_1 test_unregistered_binary_archive_dll: mingw-3_4_2 test_unregistered_text_archive: mingw-3_4_2 vc-7_1 test_unregistered_text_archive_dll: mingw-3_4_2 test_unregistered_text_warchive: vc-7_1 test_unregistered_xml_archive: mingw-3_4_2 vc-7_1 test_unregistered_xml_archive_dll: mingw-3_4_2 test_unregistered_xml_warchive: vc-7_1 test_variant_binary_archive: mingw-3_4_2 vc-7_1 test_variant_binary_archive_dll: mingw-3_4_2 test_variant_text_archive: mingw-3_4_2 vc-7_1 test_variant_text_archive_dll: mingw-3_4_2 test_variant_text_warchive: vc-7_1 test_variant_xml_archive: mingw-3_4_2 vc-7_1 test_variant_xml_archive_dll: mingw-3_4_2 test_variant_xml_warchive: vc-7_1 test_vector_binary_archive: mingw-3_4_2 vc-7_1 test_vector_binary_archive_dll: mingw-3_4_2 test_vector_text_archive: mingw-3_4_2 vc-7_1 test_vector_text_archive_dll: mingw-3_4_2 test_vector_text_warchive: vc-7_1 test_vector_xml_archive: mingw-3_4_2 vc-7_1 test_vector_xml_archive_dll: mingw-3_4_2 test_vector_xml_warchive: vc-7_1 test_void_cast: mingw-3_4_2 vc-7_1 test_void_cast_dll: mingw-3_4_2 |signals| dead_slot_test: mingw-3_4_2 deletion_test: mingw-3_4_2 ordering_test: mingw-3_4_2 signal_n_test: mingw-3_4_2 signal_test: mingw-3_4_2 trackable_test: mingw-3_4_2 |smart_ptr| atomic_count_test: mingw-3_4_2 get_deleter_test: mingw-3_4_2 intrusive_ptr_test: mingw-3_4_2 lw_mutex_test: mingw-3_4_2 shared_from_this_test: mingw-3_4_2 shared_ptr_basic_test: mingw-3_4_2 shared_ptr_test: mingw-3_4_2 smart_ptr_test: mingw-3_4_2 weak_ptr_test: mingw-3_4_2 |spirit| action_tests: mingw-3_4_2 action_tests_debug: mingw-3_4_2 ast_calc_tests: mingw-3_4_2 ast_calc_tests_debug: mingw-3_4_2 bug_000008: mingw-3_4_2 bug_fixes: mingw-3_4_2 bug_fixes_debug: mingw-3_4_2 char_strings_test: mingw-3_4_2 char_strings_test_debug: mingw-3_4_2 chset_tests: mingw-3_4_2 chset_tests_debug: mingw-3_4_2 closure_tests: mingw-3_4_2 closure_tests_debug: mingw-3_4_2 confix_tests: mingw-3_4_2 confix_tests_debug: mingw-3_4_2 directives_tests: mingw-3_4_2 directives_tests_debug: mingw-3_4_2 distinct_tests: mingw-3_4_2 distinct_tests_debug: mingw-3_4_2 epsilon_tests: mingw-3_4_2 epsilon_tests_debug: mingw-3_4_2 escape_char_parser_tests: mingw-3_4_2 escape_char_parser_tests_debug: mingw-3_4_2 exception_tests: mingw-3_4_2 exception_tests_debug: mingw-3_4_2 file_iterator_tests: mingw-3_4_2 file_iterator_tests_debug: mingw-3_4_2 fixed_size_queue_tests: mingw-3_4_2 fixed_size_queue_tests_debug: mingw-3_4_2 for_p_as_parser_tests: mingw-3_4_2 for_tests: mingw-3_4_2 for_tests_debug: mingw-3_4_2 fundamental_tests: mingw-3_4_2 fundamental_tests_debug: mingw-3_4_2 grammar_def_test: mingw-3_4_2 grammar_def_test_debug: mingw-3_4_2 grammar_mt_tests: mingw-3_4_2 grammar_multi_instance_tst: mingw-3_4_2 grammar_multi_instance_tst_debug: mingw-3_4_2 grammar_tests: mingw-3_4_2 grammar_tests_debug: mingw-3_4_2 group_match_bug: mingw-3_4_2 group_match_bug_debug: mingw-3_4_2 if_p_as_parser_tests: mingw-3_4_2 if_p_int_as_condition_test: mingw-3_4_2 if_p_int_as_condition_test_debug: mingw-3_4_2 if_tests: mingw-3_4_2 if_tests_debug: mingw-3_4_2 lazy_tests: mingw-3_4_2 lazy_tests_debug: mingw-3_4_2 loops_tests: mingw-3_4_2 loops_tests_debug: mingw-3_4_2 match_tests: mingw-3_4_2 match_tests_debug: mingw-3_4_2 multi_pass_compile_tests: mingw-3_4_2 multi_pass_tests: mingw-3_4_2 multi_pass_tests_debug: mingw-3_4_2 negated_eps_p_test: mingw-3_4_2 negated_eps_p_test_debug: mingw-3_4_2 numerics_tests: mingw-3_4_2 numerics_tests_debug: mingw-3_4_2 operators_tests: mingw-3_4_2 operators_tests_debug: mingw-3_4_2 owi_mt_tests: mingw-3_4_2 owi_st_tests: mingw-3_4_2 owi_st_tests_debug: mingw-3_4_2 parametric_tests: mingw-3_4_2 parametric_tests_debug: mingw-3_4_2 parser_context_test: mingw-3_4_2 parser_context_test_debug: mingw-3_4_2 parser_traits_tests: mingw-3_4_2 parser_traits_tests_debug: mingw-3_4_2 position_iterator_tests: mingw-3_4_2 position_iterator_tests_debug: mingw-3_4_2 primitives_tests: mingw-3_4_2 primitives_tests_debug: mingw-3_4_2 repeat_ast_tests: mingw-3_4_2 repeat_ast_tests_debug: mingw-3_4_2 rule_tests: mingw-3_4_2 rule_tests_debug: mingw-3_4_2 scanner_tests: mingw-3_4_2 scanner_tests_debug: mingw-3_4_2 scoped_lock_tests: mingw-3_4_2 scoped_lock_tests_debug: mingw-3_4_2 select_p_with_rule: mingw-3_4_2 select_p_with_rule_debug: mingw-3_4_2 sf_bug_720917: mingw-3_4_2 sf_bug_720917_debug: mingw-3_4_2 shortest_alternative_tests: mingw-3_4_2 shortest_alternative_tests_debug: mingw-3_4_2 subrule_tests: mingw-3_4_2 subrule_tests_debug: mingw-3_4_2 switch_problem: mingw-3_4_2 switch_problem_debug: mingw-3_4_2 switch_tests_eps_default: mingw-3_4_2 switch_tests_eps_default_debug: mingw-3_4_2 switch_tests_general_def: mingw-3_4_2 switch_tests_general_def_debug: mingw-3_4_2 switch_tests_single: mingw-3_4_2 switch_tests_single_debug: mingw-3_4_2 switch_tests_wo_default: mingw-3_4_2 switch_tests_wo_default_debug: mingw-3_4_2 symbols_add_null: mingw-3_4_2 symbols_add_null_debug: mingw-3_4_2 symbols_find_null: mingw-3_4_2 symbols_find_null_debug: mingw-3_4_2 symbols_tests: mingw-3_4_2 symbols_tests_debug: mingw-3_4_2 traverse_tests: mingw-3_4_2 traverse_tests_debug: mingw-3_4_2 while_p_as_parser_tests: mingw-3_4_2 while_tests: mingw-3_4_2 while_tests_debug: mingw-3_4_2 |static_assert| static_assert_example_2: mingw-3_4_2 static_assert_example_3: mingw-3_4_2 static_assert_test: mingw-3_4_2 |test| algorithms_test: mingw-3_4_2 auto_unit_test_test: mingw-3_4_2 auto_unit_test_test_mult: mingw-3_4_2 basic_cstring_test: mingw-3_4_2 boost_check_equal_str: mingw-3_4_2 class_properties_test: mingw-3_4_2 custom_exception_test: mingw-3_4_2 errors_handling_test: mingw-3_4_2 fixed_mapping_test: mingw-3_4_2 foreach_test: mingw-3_4_2 ifstream_line_iterator_test: mingw-3_4_2 online_test: mingw-3_4_2 output_test_stream_test: mingw-3_4_2 parameterized_test_test: mingw-3_4_2 result_report_test: mingw-3_4_2 test_case_template_test: mingw-3_4_2 test_fp_comparisons: mingw-3_4_2 test_tools_test: mingw-3_4_2 token_iterator_test: mingw-3_4_2 |thread| test_barrier: mingw-3_4_2 test_barrier_lib: mingw-3_4_2 test_condition: mingw-3_4_2 test_condition_lib: mingw-3_4_2 test_mutex: mingw-3_4_2 test_mutex_lib: mingw-3_4_2 test_once: mingw-3_4_2 test_once_lib: mingw-3_4_2 test_thread: mingw-3_4_2 test_thread_lib: mingw-3_4_2 test_tss: mingw-3_4_2 test_xtime: mingw-3_4_2 test_xtime_lib: mingw-3_4_2 |timer| timer_test: mingw-3_4_2 |tokenizer| examples: mingw-3_4_2 simple_example_1: mingw-3_4_2 simple_example_2: mingw-3_4_2 simple_example_3: mingw-3_4_2 simple_example_4: mingw-3_4_2 simple_example_5: mingw-3_4_2 |tuple| io_test: mingw-3_4_2 tuple_test_bench: mingw-3_4_2 |type_traits| add_const_test: mingw-3_4_2 add_cv_test: mingw-3_4_2 add_pointer_test: mingw-3_4_2 add_reference_test: mingw-3_4_2 add_volatile_test: mingw-3_4_2 aligned_storage_test: mingw-3_4_2 alignment_of_test: mingw-3_4_2 decay_test: mingw-3_4_2 extent_test: mingw-3_4_2 function_traits_test: mingw-3_4_2 has_nothrow_assign_test: mingw-3_4_2 has_nothrow_constr_test: mingw-3_4_2 has_nothrow_copy_test: mingw-3_4_2 has_trivial_assign_test: mingw-3_4_2 has_trivial_constr_test: mingw-3_4_2 has_trivial_copy_test: mingw-3_4_2 has_trivial_destructor_test: mingw-3_4_2 has_virtual_destructor_test: mingw-3_4_2 is_abstract_test: mingw-3_4_2 is_arithmetic_test: mingw-3_4_2 is_array_test: mingw-3_4_2 is_base_and_derived_test: mingw-3_4_2 is_base_of_test: mingw-3_4_2 is_class_test: mingw-3_4_2 is_compound_test: mingw-3_4_2 is_const_test: mingw-3_4_2 is_convertible_test: mingw-3_4_2 is_empty_test: mingw-3_4_2 is_enum_test: mingw-3_4_2 is_float_test: mingw-3_4_2 is_floating_point_test: mingw-3_4_2 is_function_test: mingw-3_4_2 is_fundamental_test: mingw-3_4_2 is_integral_test: mingw-3_4_2 is_member_func_test: mingw-3_4_2 is_member_obj_test: mingw-3_4_2 is_member_pointer_test: mingw-3_4_2 is_object_test: mingw-3_4_2 is_pod_test: mingw-3_4_2 is_pointer_test: mingw-3_4_2 is_polymorphic_test: mingw-3_4_2 is_reference_test: mingw-3_4_2 is_same_test: mingw-3_4_2 is_scalar_test: mingw-3_4_2 is_signed_test: mingw-3_4_2 is_stateless_test: mingw-3_4_2 is_union_test: mingw-3_4_2 is_unsigned_test: mingw-3_4_2 is_void_test: mingw-3_4_2 is_volatile_test: mingw-3_4_2 rank_test: mingw-3_4_2 remove_all_extents_test: mingw-3_4_2 remove_bounds_test: mingw-3_4_2 remove_const_test: mingw-3_4_2 remove_cv_test: mingw-3_4_2 remove_extent_test: mingw-3_4_2 remove_pointer_test: mingw-3_4_2 remove_reference_test: mingw-3_4_2 remove_volatile_test: mingw-3_4_2 tricky_abstract_type_test: mingw-3_4_2 tricky_add_pointer_test: mingw-3_4_2 tricky_function_type_test: mingw-3_4_2 tricky_incomplete_type_test: mingw-3_4_2 tricky_is_enum_test: mingw-3_4_2 tricky_partial_spec_test: mingw-3_4_2 type_with_alignment_test: mingw-3_4_2 udt_specialisations: mingw-3_4_2 |utility| addressof_test: mingw-3_4_2 assert_test: mingw-3_4_2 base_from_member_test: mingw-3_4_2 binary_search_test: mingw-3_4_2 call_traits_test: mingw-3_4_2 compressed_pair_test: mingw-3_4_2 current_function_test: mingw-3_4_2 iterators_test: mingw-3_4_2 next_prior_test: mingw-3_4_2 numeric_traits_test: mingw-3_4_2 operators_test: mingw-3_4_2 ref_ct_test: mingw-3_4_2 ref_test: mingw-3_4_2 result_of_test: mingw-3_4_2 shared_iterator_test: mingw-3_4_2 value_init_test: mingw-3_4_2 |utility/enable_if| constructors: mingw-3_4_2 dummy_arg_disambiguation: mingw-3_4_2 lazy: mingw-3_4_2 lazy_test: mingw-3_4_2 member_templates: mingw-3_4_2 namespace_disambiguation: mingw-3_4_2 no_disambiguation: mingw-3_4_2 partial_specializations: mingw-3_4_2 |variant| recursive_variant_test: mingw-3_4_2 variant_comparison_test: mingw-3_4_2 variant_reference_test: mingw-3_4_2 variant_test1: mingw-3_4_2 variant_test2: mingw-3_4_2 variant_test3: mingw-3_4_2 variant_test4: mingw-3_4_2 variant_test5: mingw-3_4_2 variant_test6: mingw-3_4_2 variant_test7: mingw-3_4_2 variant_test8: mingw-3_4_2 variant_visit_test: mingw-3_4_2 |wave| test_re2c_lexer: mingw-3_4_2 test_slex_lexer: mingw-3_4_2 testwave: mingw-3_4_2

1 0

Boost regression notification (2005-11-10 [HEAD])
by Douglas Gregor 10 Nov '05

10 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-10T06:01:47Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 194 failures in 12 libraries: bind (1) concept_check (11) graph (2) io (1) mpl (1) serialization (31) spirit (8) thread (4) tr1 (111) tuple (1) typeof (18) xpressive (5) |bind| bind_dm3_test: intel-win32-9_0 |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 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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_demo_portable_archive: gcc-3_3-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_bind: gcc-2.95.3-linux intel-win32-9_0 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_bind: intel-win32-9_0 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_bounds_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux tr1_tricky_abstract_type_test: gcc-2.95.3-linux tr1_tricky_add_pointer_test: gcc-2.95.3-linux tr1_tricky_incomplete_type_test: gcc-2.95.3-linux tr1_tricky_partial_spec_test: gcc-2.95.3-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Re: [boost] serialization performance
by bwood 10 Nov '05

10 Nov '05

On 10-Nov-2005 11:11:13 +0100, you wrote: > > >>Some recent tests I've done that compare Ebenezer Enterprises > >>and Boost.serialization's performance show the > >>Boost.serialization approach to be 7 to 9 times slower than the > >>Ebenezer Enterprises approach. I'm using Linux 2.6.12, > >>gcc 4.0.2 (with -O3) and a Boost.serialization library from the > >>release tree. A test that compared the times to serialize/send > >>a list<int> took 7.4 times longer with Boost than Ebenezer. > >>I timed the following > >>Boost: > >> oArch & lst; // oArch is a binary_oarchive > >> > >>Ebenezer: > >> msgs.Send(buffer, lst); // In order to compare apples to apples, > >> // I removed a section of code at the end > >> > >> // of the Send function that flushes the > >>buffer. > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > This seems wrong to me, comparing library to library as it is written > and as the user see's it would be much more interesting and to me makes > this test pointless. If you can really just remove the flush then it > probably shouldnt be there in the first place or configurable by the > user on an archive by archive basis. > To the best of my knowledge the following are functionally equivalent. Boost: oArch & lst; oFile.flush(); //oFile is an ofstream used to //build oArch. Ebenezer: msgs.Send(buffer, lst); // where I didn't remove anything // from Send's implementation. I think as you say, whether a flush gets embedded in the Send function should be configurable, but right now it just is. I'll admit it would be better if I didn't have to remove (#if 0) the end of the Send function, but I don't think that invalidates anything. > >> > >> > >>In a second test I added a deque of int... > >>Boost: > >> oArch & lst; > >> oArch & dq; // std::deque<int> dq; > >> > >>Ebenezer: > >> msgs.Send(buffer, lst, dq); > >> > >>In this case Boost took 9.1 times longer than Ebenezer Enterprises > >>approach. If you want to run these tests with other compilers I > >>think that would be helpful. I've been warned not to put too much > >>emphasis on numbers from gcc. > >> > > It would be interesting to see what the results are with a vanilla > version of your library as well as a feature by feature comparision to > see if you really are comparing apples to apples. > Both Boost and s11n.net support things like XML that Ebenezer doesn't. Boost in my opinion mistakenly tries to support "versioning." We don't and I don't think s11n does either. Brian

1 0

[database]
by Brock Peabody 10 Nov '05

10 Nov '05

Hi, I've added the code for the database project to the sandbox. I've also made the following changes based on feedback from Caleb and Jonathan: 1) fixed <: digraphs 2) added transaction functions to the abstract interface. Added a reference_counted_transaction_manager class for use in implementations that don't support nested transactions. 3) made the interface support null field detection via boost.optional 4) iteration supports BiDirectional model instead of RandomAccess 5) added a transaction class for scoped transaction management on the to-do list: 1) documentation - this is going to be a word document or something at first since I know nothing about html. 2) make .jam files 3) test cases - I'm not sure how these are going to work. 4) investigate possibility of supporting a prepare_statement function

5 8

alignment trouble with boost::optional
by Michael Shepanski 10 Nov '05

10 Nov '05

The code below fails a compile-time assertion in boost 1.32.0 on MSVC 7.1. This is because, internally, boost::optional uses boost::alignment_of, which produces the number 12, which is then passed as a template parameter to boost::type_with_alignment, which won't accept 12. Not sure where the blame lies. Is it with boost::alignment_of, for producing 12 in the first place? Perhaps not, since 12 is a multiple of 4, and the doco says boost::alignment_of is allowed to produce any multiple of the actual alignment value. So is the fault with boost::type_with_alignment, for not accepting 12? Or is there something wrong with the app? #include <boost/optional.hpp> class D { virtual ~D(); }; class E : virtual public D { virtual ~E(); unsigned long long m_i; }; boost::optional<E> s_optE; Cheers, --- Michael Shepanski

4 16

Compilation problems on VC7 of code uses boost 1.31.0
by Miko Nahum 10 Nov '05

10 Nov '05

Hi I need your example in compilation errors on code uses boost under Windows VC7 and HP-UX 11.11 aCC 3.55 in 64 bit mode. We have the boost 1.31.0 successfully installed and used in our products, in SunOS using Forte 6.5.3 CC, HP 11.11 using aCC 3.33, Windows (W2k, XP) using VC6. While porting our code to 64 bit, we have upgraded the development env` to Forte 8.5.5 CC on Sun, aCC 3.55 on HP and VC7 on Windows. Compilation of boost itself had no problem. However, compilation of our products that using it has been failed on HP and Windows. 1. Problems on Windows: We have the following piece of code that uses boost (copy/paste): #include "boost/regex.h" #include "boost/regex.hpp" using namespace boost; using namespace std; typedef boost::reg_expression<char> re_type; typedef re_type::allocator_type allocator_type; long example_func(long pos, const std::string& regE, long& reslen, long max) { long res; boost::match_results <PData::iterator, allocator_type> m; allocator_type (a); re_type e (a); e.set_expression (regE, regbase::normal); if (regex_search (begin (), end (), m, e, match_not_dot_newline | match_not_dot_null)) <-- line 4790 { res = pos + m.position(); reslen = m.length(); return res; } . . . Compiling the above produce the following error: parser.cpp z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\perl_ma tcher_common.hpp(208) : error C2228: left of '.second' must have class/struct/union type type is 'const std::allocator<_Ty>::value_type' with [ _Ty=char ] z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\basic_r egex.hpp(243) : while compiling class-template member function 'bool boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2> ::find_imp(void)' with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char> ] c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xlocmon(190) : while compiling class-template member function 'boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2 >::perl_matcher(BidiIterator,BidiIterator,boost::match_results<BidiItera tor,Allocator> &,const boost::reg_expression<charT> &,boost::regex_constants::match_flag_type)' with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char>, charT=char ] z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\regex_s earch.hpp(38) : see reference to class template instantiation 'boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2 >' being compiled with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char> ] z:\med2\dev\ParserLib\parser.cpp(4790) : see reference to function template instantiation 'bool boost::regex_search<PData::iterator,allocator_type,char,boost::regex_tra its<charT>,std::allocator<_Ty>>(BidiIterator,BidiIterator,boost::match_r esults<BidiIterator,Allocator> &,const boost::reg_expression<charT> &,boost::regex_constants::match_flag_type)' being compiled with [ charT=char, _Ty=char, BidiIterator=PData::iterator, Allocator=allocator_type ] "z:\med2\dev\ParserLib\parser.cpp(4790)" is marked above with red. "z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\regex_ search.hpp(38)" is listed below: template <class BidiIterator, class Allocator, class charT, class traits, class Allocator2> bool regex_search(BidiIterator first, BidiIterator last, match_results<BidiIterator, Allocator>& m, const reg_expression<charT, traits, Allocator2>& e, match_flag_type flags = match_default) { if(e.flags() & regex_constants::failbit) return false; re_detail::perl_matcher<BidiIterator, Allocator, traits, Allocator2> matcher(first, last, m, e, flags); <-- line 38 return matcher.find(); } "z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\perl_m atcher_common.hpp(208)" is part of the following function: template <class BidiIterator, class Allocator, class traits, class Allocator2> bool perl_matcher<BidiIterator, Allocator, traits, Allocator2>::find_imp() and the line (208) is listed below: // start again: search_base = position = m_result[0].second; <-- line 208 // If last match was null and match_not_null was not set then increment // our start position, otherwise we go into an infinite loop: Searching Google for this problem did not help very much, so I was wondering if you have encounter it and put more light on it and the solution? 2. Problems on HP: 2.1. Error 24: "/VOBS/netrac2_3rd_party/boost/delivery/include/boost/regex/v4/regbase.h pp", line 53 # '<identifier>' expected instead of 'collate'. perlex = collate << 1, // perl extensions ^^^^^^^ Error 164: "/VOBS/netrac2_3rd_party/boost/delivery/include/boost/regex/v4/regbase.h pp", line 53 # Integral type expected for operator '<<'; types found were '<no type>' and 'int'. perlex = collate << 1, // perl extensions ^^^^ We do not understand why the error occurs, can you help with that? from some reason, HP's aCC doesn't like the "collate". Again, same as with problem #1, google it did not produce any useful information. We have workaround this problem as follow: changed: collate = icase << 1, // use locale specific collation perlex = collate << 1, // perl extensions to: collate = icase << 1, // use locale specific collation _collate = icase << 1, perlex = _collate << 1, // perl extensions What do you think about this solution? 2.2. Fixing above problem have exposed a problem similar to the Windows problem. Btw, both problems #1 and #2.2 were solved when set #define BOOST_NO_STD_ALLOCATOR Regards, Miko Nahum

2 1

[thread] auto-link configuration macro
by Pedro Lamarão 10 Nov '05

10 Nov '05

Contrary to what http://www.boost.org/more/getting_started.html#auto-link makes you think, BOOST_THREAD_DYN_LINK doesn't cause the Boost.Thread auto-link configuration to choose the DLL version. Inspecting the config.hpp header in the detail directory, one finds: #if defined(BOOST_THREAD_BUILD_DLL) //Build dll #elif defined(BOOST_THREAD_BUILD_LIB) //Build lib #elif defined(BOOST_THREAD_USE_DLL) //Use dll #elif defined(BOOST_THREAD_USE_LIB) //Use lib #else //Use default (...) The attached patch "fixes" this behaviour, in a backwards compatible manner. Is it correct? Am I missing something? -- Pedro Lamarão Desenvolvimento Intersix Technologies S.A. SP: (55 11 3803-9300) RJ: (55 21 3852-3240) www.intersix.com.br Your Security is our Business Index: boost/thread/detail/config.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/thread/detail/config.hpp,v retrieving revision 1.15 diff -u -r1.15 config.hpp --- boost/thread/detail/config.hpp 22 Jan 2005 13:22:29 -0000 1.15 +++ boost/thread/detail/config.hpp 8 Nov 2005 16:53:49 -0000 @@ -17,6 +17,11 @@ // insist on threading support being available: #include <boost/config/requires_threads.hpp> +#if defined(BOOST_THREAD_DYN_DLL) || defined(BOOST_ALL_DYN_LINK) +# undef BOOST_THREAD_USE_LIB +# define BOOST_THREAD_USE_DLL +#endif + #if defined(BOOST_THREAD_BUILD_DLL) //Build dll #elif defined(BOOST_THREAD_BUILD_LIB) //Build lib #elif defined(BOOST_THREAD_USE_DLL) //Use dll

2 1

Re: [boost] New boost webpage
by Janusz Piwowarski 10 Nov '05

10 Nov '05

Janusz Piwowarski wrote: > if ($ext = "jpg") $ext = "jpeg"; and this one: if ($ext == "jpg") $ext = "jpeg"; Too many script languages this week, sorry. -- Regards, Janusz

1 0

Re: [boost] New boost webpage
by Janusz Piwowarski 10 Nov '05

10 Nov '05

Janusz Piwowarski wrote: > $ext = substring($QUERY_STRING, strrpos($QUERY_STRING, ".") + 1); This line should be: $ext = substr($QUERY_STRING, strrpos($QUERY_STRING, ".") + 1); -- Regards, Janusz

1 0

[Serialization] [1.33.1-beta] Does not compile with GCC 2.95.4
by Simon Barner 10 Nov '05

10 Nov '05

Hi, I tried to build boost 1.33.1 with gcc 2.95.4, using STL-port and Spirit 1.6.2. It worked quite well, but I had to comment out the following lines: --- boost/archive/detail/oserializer.hpp.orig Thu Nov 10 00:40:32 2005 +++ boost/archive/detail/oserializer.hpp Thu Nov 10 00:43:15 2005 @@ -330,9 +330,9 @@ { static const basic_pointer_oserializer * register_type(Archive & /* ar */){ // it has? to be polymorphic - BOOST_STATIC_ASSERT( - boost::serialization::type_info_implementation<T>::type::is_polymorphic::value - ); + //BOOST_STATIC_ASSERT( + //boost::serialization::type_info_implementation<T>::type::is_polymorphic::value + //); return static_cast<const basic_pointer_oserializer *>(NULL); } }; As far as I understand this will not affect the runtime behaviour, but it will disable some compile time assertation check. Perhaps you want to fix it. Please Cc: me in your replies, I am not on the list. -- Best regards / Viele Grüße, barner(a)FreeBSD.org Simon Barner barner(a)gmx.de

2 1

XML APIs: use cases, and wishes
by Andreas Pokorny 09 Nov '05

09 Nov '05

Hi there, Stefan Seefeld recently presented his set of Dom classes. Personally I do not have any need for a DOM API. To focus the discussion on other APIs I started this new thread (and also because I could not find a good entry point in the previous disucussions). Last time I had to process XML I wrote my own wrapper on top of SAX, which forwarded higher level events to xml-unaware structures. The model served well to directly map a fixed XML-format to C++ structures (also XML writing was supported). The wrapper that forwarded all SAX events to the datastructures was generated from a single C++ expression, or several if recursion was required. I adopted a lot of spirits techinques to make it look nice. There were no intermediate data structures. In retrospective I also dislike my attempt, although it was better than working on xml document classes. It only worked with full xml documents, no partial parsing was supported. Furthermore it required a nearly direct mapping of xml elements to datastructures, different use cases which do not include a mapping of xml<->c++ werent considered. I currently do not need to fiddle with XML, but I would like to see at least these different APIs: * on-demand parsing, a parser drived by a cursor, that allows to navigate through a document, without loading it completly (I dont see a need for prior validation, here) * xml path / query like api to fastly grep for certain subtrees or elements of the xml * direct mapper of c++ structures to a certain format, so a kind of xml serialization, As you can see my view on XML is very limited, it boils down to a flexilbe form of reading XML. Regards, Andreas Pokorny

6 7

Boost regression notification (2005-11-09 [RC_1_33_0])
by Douglas Gregor 09 Nov '05

09 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-09T13:48:12Z 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. utility Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 7 failures in 6 libraries: graph (2) random (1) regex (1) serialization (1) utility (1) wave (1) |graph| betweenness_centrality_test: vc-8_0 floyd_warshall_test: vc-8_0 |random| random_test: mingw-3_4_2 |regex| regex_regress_dll: vc-8_0 |serialization| test_exported_xml_warchive_dll: vc-8_0 |utility| operators_test: vc-8_0 |wave| testwave: mingw-3_4_2

1 0

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

09 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-09T06:00:59Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 191 failures in 12 libraries: bind (1) concept_check (10) graph (1) io (1) mpl (1) serialization (30) spirit (8) thread (4) tr1 (111) tuple (1) typeof (18) xpressive (5) |bind| bind_dm3_test: intel-win32-9_0 |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 |graph| layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_bind: gcc-2.95.3-linux intel-win32-9_0 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_bind: intel-win32-9_0 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_bounds_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux tr1_tricky_abstract_type_test: gcc-2.95.3-linux tr1_tricky_add_pointer_test: gcc-2.95.3-linux tr1_tricky_incomplete_type_test: gcc-2.95.3-linux tr1_tricky_partial_spec_test: gcc-2.95.3-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

threads - suggestion for producer/consumer pattern - synchronisation channel
by Oliver.Kowalke＠infineon.com 09 Nov '05

09 Nov '05

Hello, I've a suggestion for an implementation of the synchronization channel between producer and consumer threads. It is adopted from several books - the only problem is how to tell the consumer threads, that all producer have finished their jobs. You can signal it from outside (deactive member function) or each producer thread has to register on the message_queue (and unregister if it has finished its job). With best regards, Oliver <<test.cpp>> <<message_queue.h>>

2 1

How to contact with Review Wizard?
by Alexander Nasonov 09 Nov '05

09 Nov '05

I wrote two letters to Tom Brinkman from different e-mail addresses but has no reply. -- Alexander

2 2

[Boost-bugs] [ boost-Bugs-1352049 ] EdgeListS = has_setS for adjacency_list does not work
by SourceForge.net 09 Nov '05

09 Nov '05

Bugs item #1352049, was opened at 2005-11-09 02:11 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=1352049&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: graph Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Jeremy Siek (jsiek) Summary: EdgeListS = has_setS for adjacency_list does not work Initial Comment: hash_set header isn't in #include <hash_set> for every compilers. Example to include the correct header for gcc: # if defined __cplusplus # if defined __GNUC__ && __GNUC__ >= 3 # include <ext/hash_set> # if __GNUC__ >= 4 || __GNUC_MINOR__ >= 2 namespace std { using ::__gnu_cxx::hash; using ::__gnu_cxx::hash_set; } # endif # else # include <hash_set> # endif /* defined __GNUC__ and __GNUC__ == 3 */ # endif /* defined __cplusplus */ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1352049&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] Gender neutral documentation
by Martin Bonner 09 Nov '05

09 Nov '05

----Original Message---- From: brangdon(a)cix.compulink.co.uk [mailto:brangdon@cix.compulink.co.uk] Sent: 08 November 2005 21:58 To: boost(a)lists.boost.org Subject: Re: [boost] Gender neutral documentation > In-Reply-To: <dkl36d$2ak$1(a)sea.gmane.org> > andy(a)servocomm.freeserve.co.uk (Andy Little) wrote (abridged): >> Where it is used 'she' always refers to 'the user'. > > If you have two protagonists (author and user) it can help to give > them different genders and to be consistent about which way round > they are. > > >> I dont use that convention myself for obvious reasons ! > > Hmm. I suspect we could argue about this for weeks. > Weeks? I would have said that was out by about two orders of magnitude :-) My prediction is that a consensus will emerge on how to handle this across the English speaking(writing) world - by about the middle of this century. -- 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

linker problem ob HP/UX - wrong extension
by Oliver.Kowalke＠infineon.com 09 Nov '05

09 Nov '05

Hello, I compiled boost on HP/UX 11.11 (PA RISC) with gcc. I got a linker error if I tried to link against the regex library: /usr/ccs/bin/ld: Invalid loader fixup in text space needed in output file for symbol "__gxx_personality_sj0" in input file "/opt/boost/lib/libboost_regex-gcc." What I found out was: 1) 'bjam "-sTOOLS=gcc" install' creates libraries with wrong extension (*.so instead of *.sl) /opt/boost/lib/libboost_regex-gcc.a /opt/boost/lib/libboost_regex-gcc.so 2) It seams that the linker chooses the static library if I declare '- boost_regex-gcc', so I get the linker error as described in my prevoíous email! 3) Building boost with 'bjam "-sSUFDLL=.sl" "-sTOOLS=gcc" install' creates /usr/local/lib/libboost_regex-gcc-1_33.a /usr/local/lib/libboost_regex-gcc-1_33.s /usr/local/lib/libboost_regex-gcc.a Shared library /usr/local/lib/libboost_regex-gcc.sl is missing! 4) Now linking with '- boost_regex-gcc-1_33' works (no linker error). Conclusion: 1) The extension for HP/UX libraries should be fixed. 2) The shared library without version in its name is missing. So long, Oliver

1 0

Re: [boost] Gender neutral documentation
by brangdon＠cix.compulink.co.uk 08 Nov '05

08 Nov '05

In-Reply-To: <dkl36d$2ak$1(a)sea.gmane.org> andy(a)servocomm.freeserve.co.uk (Andy Little) wrote (abridged): > Where it is used 'she' always refers to 'the user'. If you have two protagonists (author and user) it can help to give them different genders and to be consistent about which way round they are. > I dont use that convention myself for obvious reasons ! Hmm. I suspect we could argue about this for weeks. -- Dave Harris, Nottingham, UK.

1 0

Re: [boost] Gender neutral documentation
by brangdon＠cix.compulink.co.uk 08 Nov '05

08 Nov '05

In-Reply-To: <u1x1ua1zr.fsf(a)boost-consulting.com> dave(a)boost-consulting.com (David Abrahams) wrote (abridged): > >> For example, if Bind is unneeded the user can discard it > >> completely. > >> > >> is much more to the point. > > > > But "is unneeded" again fails to say who doesn't need it, and hence > > fails to say why it isn't needed. > > I don't see how saying who doesn't need it would indicate anything > about why it isn't needed. If it is you who needs it, you also know why you need it. If it is the library which sometimes needs it, you have to guess when. -- Dave Harris, Nottingham, UK.

1 0

[any] library update is not on main page
by Alexander Nasonov 08 Nov '05

08 Nov '05

any_cast has been updated to support reference types. This change is included into 1.33.0 but this fact is not documented. It will be documented in 1.33.1. I'm going to update 'Updated Libraries' page (if it's not too late for RC_1_33_0). In 1.33.1 section: any: Cast to reference types introduced in 1.33.0 is now documented on any_cast documentation page. In 1.33.0 section: any: any_cast is enhanced to get direct access to any's held value. Does it look good? -- Alexander

2 2

Boost regression notification (2005-11-08 [RC_1_33_0])
by Douglas Gregor 08 Nov '05

08 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-08T14:51:31Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 2 failures in 2 libraries: python (1) regex (1) |python| map_indexing_suite: vc-8_0 |regex| regex_grep_example_2: vc-8_0

1 0

Boost regression notification (2005-11-08 [HEAD])
by Douglas Gregor 08 Nov '05

08 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-08T06:00:36Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 193 failures in 12 libraries: bind (1) concept_check (11) graph (2) io (1) mpl (1) serialization (30) spirit (8) thread (4) tr1 (111) tuple (1) typeof (18) xpressive (5) |bind| bind_dm3_test: intel-win32-9_0 |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 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_bind: gcc-2.95.3-linux intel-win32-9_0 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_bind: intel-win32-9_0 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_bounds_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux tr1_tricky_abstract_type_test: gcc-2.95.3-linux tr1_tricky_add_pointer_test: gcc-2.95.3-linux tr1_tricky_incomplete_type_test: gcc-2.95.3-linux tr1_tricky_partial_spec_test: gcc-2.95.3-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[1.33.1 beta] RC_1_33_0 is completely frozen
by Douglas Gregor 08 Nov '05

08 Nov '05

The RC_1_33_0 is completely frozen. Do not commit anything to this branch. I'm tagging for the 1.33.1 beta and will be building release tarballs today. Doug

1 0

Tokenizer: feature request
by CN 08 Nov '05

08 Nov '05

Hi! I need to get non-null tokens from std::basic_string deliminated by null characters. For example, hopefully the following code string str=string("X;Y\0\0Z\0",7); typedef tokenizer<boost::escaped_list_separator<char> > Tok; escaped_list_separator<char> sep(string(),string("\0;",2),string()); Tok tokens(str, sep); for(Tok::iterator i = tokens.begin();i != tokens.end();++i) cout << "<" << *i << ">"; will yield <X><Y><Z> instead of <X><Y><><Z><> . An expert told me that changing the tokenizer constructors in BOOST from char* to std::basic_string should do the job. //Quote The escaped_list_separator is designed to seperated fields for CSV-like inputs, which allow empty fields. You cannot use this type of separator here. The default char_separator would do the trick, but the problem is that it does not allow the null character ('\0') as a separator because of the way the string of separators is passed to its constructor (that is, a const Char*, null-terminated strings). But since the internal representation is a ::std::basic_string<>, then I wonder why the parameter type for the constructor is not the same. It would then solve the problem. //End Quote Thank you! CN -- http://www.fastmail.fm - Accessible with your email software or over the web

2 2

sorry for OT - vc8 is free to download from Microsoft website
by Bronek Kozicki 08 Nov '05

08 Nov '05

Everyone may download it from http://msdn.microsoft.com/vstudio/express/visualc/download/ . It comes with IDE (nice one - this is actually Visual Studio .NET 2005 stripped from some bells and whistles), optimizing compiler, runtime (static and dynamic) and standard C++ library. And also C++/CLI and .NET 2.0 (but maybe you do not mind). However, it does not come with Windows API headers and libraries. In order to compile Windows applications (and boost) one has to download Platform SDK separately (fat one), there is a link and instruction on above page. This might be interesting news for those who want to test vc-8_0 toolkit. Now I shut my mounth and sorry for spamming here. B.

1 0

[type_map] Interest in container indexed by type?
by Tony D 08 Nov '05

08 Nov '05

Hi people, A couple years ago I wrote a container indexed by type, which I've come to consider a basic building block for reusable code. Effectively, code can use "type_maps" to handle an arbitrary structure, without needing to know member identifiers, and gets the speed benefit of compile-time access resolution. A simple implementation follows: namespace NS { namespace Private { class no_type2 { }; class no_type3 { }; class no_type4 { }; class no_type5 { }; template <typename T> class type_map_base { public: void operator=(const T& t) { t_ = t; } operator const T&() const { return t_; } private: T t_; }; template<> class type_map_base<no_type2> { }; template<> class type_map_base<no_type3> { }; template<> class type_map_base<no_type4> { }; template<> class type_map_base<no_type5> { }; } template <typename T1, typename T2 = Private::no_type2, typename T3 = Private::no_type3, typename T4 = Private::no_type4, typename T5 = Private::no_type5> class type_map : public Private::type_map_base<T1>, public Private::type_map_base<T2>, public Private::type_map_base<T3>, public Private::type_map_base<T4>, public Private::type_map_base<T5> { public: using Private::type_map_base<T1>::operator=; using Private::type_map_base<T2>::operator=; using Private::type_map_base<T3>::operator=; using Private::type_map_base<T4>::operator=; using Private::type_map_base<T5>::operator=; }; } // sample usage... #include <iostream> #include <string> using namespace std; int main() { NS::type_map<int, string> tmid; tmid = 3; tmid = "hello"; string s = tmid; cout << (int)tmid << ' ' << (string)tmid << ' ' << s << endl; cout << sizeof(tmid) << " vs " << sizeof(int) << '+' << sizeof(string) << endl; } I've found typemaps useful for writing things like a logging system that allows arbitrary criterion for cataloging errors. To store several data items of the same type, simply wrap each instance in a distinct class (possibly using the template w/ unique number idiom). Implementation note: the empty base class optimisation makes it practical to have a single template, avoiding typelists (mpl sequences), preprocessing etc.. Cheers, Tony ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com

3 4

[range] Inconsistent range_iterator metafunction
by David Abrahams 08 Nov '05

08 Nov '05

I note the following: typedef std::vector<int> vint; typedef int aint[4]; range_iterator<vint const>::type ==> std::vector<int>::iterator range_iterator<aint const>::type ==> int const* It seems like it should be range_iterator<vint const>::type ==> std::vector<int>::const_iterator I know we discussed this before. Thorsten, are you planning to make this change? -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 3

compiler_status_2
by Robert Ramey 07 Nov '05

07 Nov '05

I've recently uploaded the program compiler_status_2.cpp to the vault. It was there before but due to things beyond our control files in the vault were lost so I uploaded it again. Previously it had a respectable number of downloads. The difference between the version and the official compiler_status.cpp is that the table generated displays results of all the builds rather than just one. I find it very helpful since different compilers require different builds (static/dynamic, etc) and I also occasionally build for release. This lets me easily see which problems are associated with particular build settings. It also allows me to leave all my build/test results permantently on my machine. Every time I run a test the table is updated and I can see all my tests at once. I had hoped that these improvements might be incorporated into the "official" version. I still hope that this or something like it can occur. Its not a huge issue for me as it has worked well for me as is but I think this "superset" of the original would be valuable to others. Robert Ramey

2 1

[iostreams] Why devices must be copy-constructible?
by Alberto Ganesh Barbati 07 Nov '05

07 Nov '05

Hi, I started using the iostreams library for a pet project. I thinks it's a great piece of software. However, I immediately stumbled in what I think it may be a defect. Consider this simple source device: #include <boost/iostreams/stream.hpp> struct Source : boost::noncopyable { typedef char char_type; typedef boost::iostreams::source_tag category; Source(int); // ctor std::streamsize read(char* s, std::streamsize n) { // implementation here } private: /* ... private members here */ }; int main() { boost::iostreams::stream<Source> s(0); } the boost::noncopyable up there has been put because the device keeps handles to OS resources whose duplication can be very expensive. I was amazed that the code above doesn't compile. This is the error message reported by VC7.1: C:\lib\Boost\include\boost-1_33\boost\iostreams\detail\wrap_unwrap.hpp(52) : error C2558: struct 'Source' : no copy constructor available or copy constructor is declared 'explicit' (full error message is very long and is reported, for reference, at the end of the message) It seems that a device must be copy-constructibile. In particular, the code above makes at least three short-lived copies of the device. Question is: why? I believe this requirement is unintended and not due to a conscious design choice, my arguments are: 1) it's not documented, there is no mention of such requirement in http://www.boost.org/libs/iostreams/doc/concepts/device.html 2) it's unnatural and I believe my case (where copying the device could be expensive) occurs more often in practice than the opposite case 3) from the error messages it seems that a copy is only required as a side-effect of the template machinery used in BOOST_IOSTREAMS_FORWARD. In fact, the offending line detail\wrap_unwrap.hpp(52) is: inline T wrap(const T& t BOOST_IOSTREAMS_DISABLE_IF_STREAM(T)) { return t; } that requires T to be copy-constructible. Am I missing something? Thanks in advance, Ganesh ----- full error messaage follows C:\lib\Boost\include\boost-1_33\boost\iostreams\detail\wrap_unwrap.hpp(52) : error C2558: struct 'Source' : no copy constructor available or copy constructor is declared 'explicit' C:\lib\Boost\include\boost-1_33\boost\iostreams\stream_buffer.hpp(90) : see reference to function template instantiation 'T boost::iostreams::detail::wrap<T>(const T &,boost::disable_if_c<B,void>::type *)' being compiled with [ T=Source, B=false ] C:\lib\Boost\include\boost-1_33\boost\iostreams\stream_buffer.hpp(90) : while compiling class-template member function 'void boost::iostreams::stream_buffer<T,Tr,Alloc>::open(const T &,int,int)' with [ T=Source, Tr=std::char_traits<char>, Alloc=std::allocator<char> ] C:\lib\Boost\include\boost-1_33\boost\utility\base_from_member.hpp(69) : see reference to class template instantiation 'boost::iostreams::stream_buffer<T,Tr,Alloc>' being compiled with [ T=Source, Tr=std::char_traits<char>, Alloc=std::allocator<char> ] C:\lib\Boost\include\boost-1_33\boost\iostreams\stream.hpp(61) : see reference to class template instantiation 'boost::base_from_member<MemberType>' being compiled with [ MemberType=boost::iostreams::stream_buffer<Source,std::char_traits<char>,std::allocator<char>> ] C:\lib\Boost\include\boost-1_33\boost\iostreams\stream.hpp(98) : see reference to class template instantiation 'boost::iostreams::detail::stream_base<Device,Tr,Alloc>' being compiled with [ Device=Source, Tr=std::char_traits<char>, Alloc=std::allocator<char> ] TestVc2.cpp(26) : see reference to class template instantiation 'boost::iostreams::stream<Device>' being compiled with [ Device=Source ]

2 4

bjam question
by Robert Ramey 07 Nov '05

07 Nov '05

I have made some tests to compare serialization of different types of data different archives and to compare against raw i/o. So far so good. Now I would like to alter my test/Jamfile to achieve the following: a) I would like to run a command after the test run to display the size of the test executable. b) I would like to run a command (gprof) after the test for certain tests. I would hope that the output of these post processing command would appear in the output log of the standard output. c) I would like to inhibit the running of these tests when the build is in debug mode. d) I intend to uses these in my own environment as this would impose extra burden on testing and I don't really need to run this stuff except for once in a while. However, I'm am curious how one achieves the effect of the config_info test on the main test matrix whereby the test passes but still produces a link to the test output. Robert Ramey

2 1

Re: [boost] Global object initialization [was: Phoenix-2 prerelease]
by David Abrahams 07 Nov '05

07 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Any links to the thread? No, we've been doing this offline. I'll try to forward something to you. >> 1. The placeholders are statically initialized const POD objects in >> an unnamed namespace and you have likely ODR violation when used >> by templates in multiple translation units. >> 2. The placeholders are dynamically initialized references in an >> unnamed namespace and you risk undefined behavior when they are >> used without initialization due to initialization order issues >> 3. The placeholders are dynamically initialized objects in an >> unnamed >> namespace, and you have likely ODR violation *and* initialization >> order issues >> Seems from the doc like you have #3, which is the worst of both >> worlds. No? > > Actually it is 4: > > 4. The placeholders are dynamically initialized *const* objects in > namespace phoenix That's essentially 1, in that you get a different object in each TU and are likely to end up with an ODR violation. > Well, we can easilly make them PODs, so: > > 5. The placeholders are statically initialized *const* POD objects > in namespace phoenix Same problem. > So, question: how does this code below constitute ODR violation? > > namespace x // named > { > T const pod = T(); // T is a POD > } It does not. You need two translation units and a template, instantiated in each one, that uses your object "pod." > is this link relevant?: > http://lists.boost.org/Archives/boost/2004/06/67159.php Precisely. > how about: > http://lists.boost.org/Archives/boost/2001/05/12609.php I don't think so. Internal linkage doesn't save you from an ODR violation. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Re: [boost] Gender neutral documentation
by brangdon＠cix.compulink.co.uk 07 Nov '05

07 Nov '05

In-Reply-To: <uacgkh76q.fsf(a)boost-consulting.com> dave(a)boost-consulting.com (David Abrahams) wrote (abridged): > Angus' version is better. > > This means that if Bind is unneeded the user can discard it > completely. > > Of course, "this" needs an antecedent :) > > > For example, if Bind is unneeded the user can discard it > completely. > > is much more to the point. But "is unneeded" again fails to say who doesn't need it, and hence fails to say why it isn't needed. It's vague. I think clarity and precision are more important than good grammar or political correctness. -- Dave Harris, Nottingham, UK.

3 3

[test] --catch_system_errors=no doesn't work with minimal test
by David Abrahams 07 Nov '05

07 Nov '05

When using boost/test/minimal.hpp, it doesn't respond to the presence of --catch_system_errors=no, which makes it unreasonably difficult to debug problems on Windows. All I get is an exception caught by the test library, with all of the info about the real cause of the error lost, which is absolutely unhelpful. It seems to me that the minimal configuration ought to at least be useful for writing and debugging simple test cases. -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 8

[mpl] apply as a placeholder expression?
by Eric Niebler 07 Nov '05

07 Nov '05

I have an MPL sequence of metafunction classes. I want to apply<> each with mpl::transform. So I did this: struct metafnclass { template<typename T> struct apply { typedef T type; }; }; typedef mpl::vector<metafnclass, metafnclass> metafnclasses; typedef mpl::transform< metafnclasses , mpl::apply<mpl::_1, int> >::type transmetafnclasses; This fails horribly, and I don't know why. If I add an indirection like this: template<typename T,typename U> struct indirect_apply : mpl::apply<T, U> {}; typedef mpl::transform< metafnclasses , indirect_apply<mpl::_1, int> >::type transmetafnclasses; then it works fine. Why should that be? Is something getting evaluated too eagerly? -- Eric Niebler Boost Consulting www.boost-consulting.com

5 7

multi_index problem in VC 7.1
by Brock Peabody 07 Nov '05

07 Nov '05

If I try to compile the very first example in multi index I get the following error: c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\boost\multi_index\detail\node_type.hpp(56) : error C2903: 'node_class' : symbol is neither a class template nor a function template I get this with 1.33 and 1.32. I've tried many different compiler options. Here is my latest command line: /Ox /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "NOMINMAX" /D "_AFXDLL" /D "_MBCS" /FD /EHsc /MD /GS /Fo"Release/" /Fd"Release/vc70.pdb" /W3 /nologo /c /Wp64 /Zi /TP I've dug around a bit and I can't make any sense of this problem. Has anyone else seen this? The exact code I'm compiling is: #include <boost/multi_index/key_extractors.hpp> #include <boost/multi_index_container.hpp> #include <string> struct employee { int id; std::string name; employee(int id,const std::string& name):id(id),name(name){} bool operator<(const employee& e)const{return id<e.id;} }; using namespace boost::multi_index; // define a multiply indexed set with indices by id and name typedef multi_index_container< employee, indexed_by< // sort by employee::operator< ordered_unique<identity<employee> >, // sort by less<string> on name ordered_non_unique<member<employee,std::string,&employee::name> > > > employee_set; employee_set e; Thanks!

1 0

Boost regression notification (2005-11-07 [RC_1_33_0])
by Douglas Gregor 07 Nov '05

07 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-07T14:04:14Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 2 failures in 2 libraries: program_options (1) python (1) |program_options| variable_map_test: vc-8_0 |python| map_indexing_suite: vc-8_0

1 0

Boost regression notification (2005-11-07 [HEAD])
by Douglas Gregor 07 Nov '05

07 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-07T06:00:45Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 202 failures in 12 libraries: bind (1) concept_check (11) graph (2) io (1) mpl (1) serialization (30) spirit (8) thread (4) tr1 (120) tuple (1) typeof (18) xpressive (5) |bind| bind_dm3_test: intel-win32-9_0 |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 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_bind: 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 intel-win32-9_0 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_bind: 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 intel-win32-9_0 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_bounds_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux tr1_tricky_abstract_type_test: gcc-2.95.3-linux tr1_tricky_add_pointer_test: gcc-2.95.3-linux tr1_tricky_incomplete_type_test: gcc-2.95.3-linux tr1_tricky_partial_spec_test: gcc-2.95.3-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

execution_monitor and threads
by Raymond Haeb 07 Nov '05

07 Nov '05

Hi, Is there any defined behavior of the execution_monitor if the controlled function starts new threads? Does every thread need its own monitor or is one for the main thread from where the others are started sufficient? Thanks in advance, Raymond

2 1

Report from Mont Tremblant C++ Committee meeting
by Beman Dawes 07 Nov '05

07 Nov '05

The C++ Standards Committee met this past week in Mont Tremblant, Quebec, Canada. Many Boosters were present, and Boost continues to get praise and encouragement from non-Boost committee members. The Library Working Group (LWG) is starting serious work on TR2. Initial proposals for several Boost libraries were evaluated: Filesystem : Interested? Yes 17, No 0 Date-Time : Interested? Yes 9, No 0 Range : Want a C++03 version aimed at TR2, but still interested in a version based on new language features (Concepts perhaps?). String-algo : Interested, but concern over interface and choice of functions, generic vs basic_string.5.3 separate proposal numeric_cast<> : Interested? Yes 10, No 0 Interval : Interested? Yes 7, No 4. Concerns about sufficiently large user base to justify standardizing. Optional : Interested? Strong yes 9, weak yes 2, weak no 3, strong no 0 Significant concerns about the interface: Pointer interface. Two ways of doing the same thing. Depends on nullptr - is there a backup plan. Dubious of use of references. "Boost style" Threads : Pursue? Strong yes 9, weak yes 5, weak no 0, strong no 1 Also: minmax and / or algorithm std::minmax_element In favor 13, Not in favor 0 TR2 0 2 1 0 C++0X 1 8 0 0 Kevlin Henney Threads : Ask for fleshed-out proposal? Strong yes 3, weak yes 6, weak no 2, strong no 1 The next C++ Committee meeting will be in Berlin, Germany, the first week of April 2006. The meeting after that will be in Portland, Oregon, US, in October 2006. --Beman

34 139

Boost regression notification (2005-11-06 [RC_1_33_0])
by Douglas Gregor 06 Nov '05

06 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-06T15:15:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 2 failures in 2 libraries: python (1) serialization (1) |python| map_indexing_suite: vc-8_0 |serialization| test_non_default_ctor_binary_archive: vc-8_0

1 0

Boost regression notification (2005-11-06 [HEAD])
by Douglas Gregor 06 Nov '05

06 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-06T06:00:29Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 245 failures in 13 libraries: bind (1) concept_check (11) graph (2) io (1) mpl (1) serialization (30) spirit (8) thread (4) tr1 (105) tuple (1) type_traits (58) typeof (18) xpressive (5) |bind| bind_dm3_test: intel-win32-9_0 |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 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: 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 intel-win32-9_0 vc-7_1 std_test_bind: 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 intel-win32-9_0 std_test_bind_tricky: 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 intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: 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 intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: 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 intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: 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 intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: 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 intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_bind: 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 intel-win32-9_0 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Re: [boost] Gender neutral documentation
by brangdon＠cix.compulink.co.uk 06 Nov '05

06 Nov '05

In-Reply-To: <E562FCEE3A42D61192880002A5FB433302D7B0ED(a)kite.pigroup.co.uk> martin.bonner(a)pitechnology.com (Martin Bonner) wrote (abridged): > As used by the British royal family, "one" is a first person singular > pronoun. It's also worth considering "you", as second person singular (or plural): This means for example that you can completely discard Bind if you do not need it. Whether "you" works in this situation depends on whether the context makes it clear that "you", the reader of the documentation, is the tool's user rather than the tool's author. Personally I don't have a problem with "she". It only seems strange because it is unusual. If we use it more it won't be so unusual. -- Dave Harris, Nottingham, UK.

2 1

Boost's position/work on a Standard GUI Library for C++0x
by David Wehite 05 Nov '05

05 Nov '05

In his article "The Design of C++0x", published in C/C++ Users Journal, May 2005, the author of C++ Bjarne Stroustrup wrote, "The most commonly requested new feature for C++ is a standard GUI". I am new to Boost and will appreciate if some folks here would give me a summary of Boost organization's standing on such a standard GUI library. If and how was it addressed and pointers to work on the subject if such has been done. I just want to clarify, that when I say "standard", I mean that as long as my application source code adheres to that standard, if I take it and walk into any machine that has a C++ compiler (at least one that deserves that title), compilation would at least not fail for syntax reasons, w/o me changing a single character in the source (not even changing the case of a character), no matter how complex and/or large that source is. I don't know how to avoid a sea of answers with this mailing list arrangement (not that I think that my 2.6GB gmail box would soon fill up...), may be the few answers can be posted on the newsgroup forum? Thanks in advance for the education, David

33 162

[PREPROCESSOR]:New sequence handler
by Alex Mekhed 05 Nov '05

05 Nov '05

Hello, sorry if I will be wrong, I am new to boost. As far as I know, BOOST_PP_SEQ_FOR_EACH_I works only with 256 elements, well, I've wrote macro that works with unlimited (256, 512, well it may be limited by some compilers options, like string length, maybe) number of elements (while testing I'vnt met bugs...). But if You're interested in, I can email the code (here?). P.S.: Also, there is some difference: #define ENUM_SWITCH_CASE(x) case x: return #x; #define ENUMR(x) x, #define ENUM(E, x) \ enum E { NEWL(ENUMR,x) }; \ inline const char *to_string(day_t e)\ {\ switch(e)\ {\ NEWL(ENUM_SWITCH_CASE, x)\ };\ }; #define ENUMRSEQQ1_END #define ENUM_SWITCH_CASESEQQ1_END #define ENUM_SWITCH_CASE_ENDET default: return "<invalid>"; ENUM(day_t,(Monday)(Tuesday)(Wednesday)(Thursday)(Friday)(Saturday)(Sunday)) There is 3 defines in the end, NEWL (my macro) - make's the code with 2 constants in the end ( (a)(b)(c) -> a,b,c, C1 C2 ), so first define eliminates one unneeded constant (one will be used for enum ending), second and third defines does almost the same, but ENDET used for making default case in switch. P.P.S: And another difference is that name of one of the constants in the end variyng from the number of the elements in sequence. (Maybe one of the constants can be removed...)

2 1

Boost regression notification (2005-11-05 [RC_1_33_0])
by Douglas Gregor 05 Nov '05

05 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-05T14:58:07Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-05 [HEAD])
by Douglas Gregor 05 Nov '05

05 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-05T06:00:35Z 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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 287 failures in 13 libraries: bind (1) concept_check (11) graph (2) io (1) mpl (1) serialization (30) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (18) xpressive (5) |bind| bind_dm3_test: intel-win32-9_0 |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 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: 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: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: 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 intel-win32-9_0 vc-7_1 std_test_bind: 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 intel-win32-9_0 std_test_bind_tricky: 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 intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: 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 intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: 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 intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: 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 intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: 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 intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: 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 intel-win32-9_0 vc-7_1 test_bind: 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 intel-win32-9_0 test_bind_tricky: 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 intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: 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 intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: 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 intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: 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 intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: 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 intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0