- Boost - lists.boost.org

Re: [boost] BOOST_ASSERT and __assume on MSVC
by brangdon＠cix.compulink.co.uk 26 Sep '05

26 Sep '05

In-Reply-To: <200509211851.j8LIp8VY019052(a)shannonhoon.balstatdev.susq.com> stewart(a)sig.com (Rob Stewart) wrote (abridged): > That misses what BOOST_ASSUME should do when > BOOST_DISABLE_ASSERTS is not defined. With BOOST_ASSERT enabled, > BOOST_ASSUME should call both BOOST_ASSERT and __assume(): Why? Consider the sequence: BOOST_ASSERT(e); __assume(e) Suppose (e) is true. Then BOOST_ASSERT does nothing, so why invoke it? If (e) is false, then the __assume tells us the sequence won't be executed at all, and both it and the BOOST_ASSERT can be optimised away. Whatever it is you want BOOST_ASSERT to do, you can't rely on it happening. It will depend on how clever the optimiser is, which will vary from platform to platform. In addition, it evaluates (e) twice. That's bad practice for a macro. It would be acceptable if it were necessary (and we certainly hope (e) has no side effects and that its value doesn't change between the assert and the assume) but here there is no need for it. -- Dave Harris, Nottingham, UK.

2 1

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

26 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-26T14:54: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… 78 failures in 7 libraries: bind (1) foreach (1) graph (5) iostreams (11) random (1) range (3) serialization (56) |bind| bind_cv_test: gcc-4_0-darwin |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: gcc-3.4.4-linux dag_longest_paths: gcc-3.4.4-linux dijkstra_cc: gcc-3.4.4-linux dijkstra_heap_performance: gcc-3.4.4-linux relaxed_heap_test: gcc-3.4.4-linux |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux vc-7_1 |random| random_test: gcc-3.3.6-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_contained_class_xml_archive: gcc-3.2.3-linux test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5

2 1

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

26 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-26T05:00:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 191 failures in 15 libraries: bind (14) concept_check (14) filesystem (8) foreach (7) graph (4) math (3) mpl (2) parameter (18) python (1) regex (1) serialization (43) spirit (2) thread (24) typeof (46) wave (4) |bind| bind_rv_sp_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 gcc-3_4_3-sunos mingw-3_4_2 mem_fn_rv_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 gcc-3_4_3-sunos mingw-3_4_2 |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 |filesystem| convenience_test: msvc default_name_check_test: msvc fstream_test: msvc large_file_support_test: msvc operations_test: msvc operations_test_dll: msvc path_test: msvc path_test_dll: msvc |foreach| user_defined: cw-8_3 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-6_5-stlport vc-7_0 |graph| graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |math| octonion_test: gcc-4_0-darwin quaternion_test: gcc-4_0-darwin special_functions_test: gcc-4_0-darwin |mpl| size_t: gcc-4_0-darwin gcc-4_0-darwin |parameter| basics: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-4_0-darwin msvc macros: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc unnamed: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| data_members: msvc |regex| static_mutex_test: msvc |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc test_no_rtti_text_archive: vc-7_1 test_no_rtti_text_warchive: vc-7_1 test_non_intrusive_xml_warchive_dll: vc-7_1 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_barrier: msvc test_barrier_lib: intel-9.0-linux msvc test_condition: msvc test_condition_lib: intel-9.0-linux msvc test_mutex: msvc test_mutex_lib: intel-9.0-linux msvc test_once: msvc test_once_lib: intel-9.0-linux msvc test_read_write_mutex: msvc test_read_write_mutex_lib: intel-9.0-linux msvc test_thread: msvc test_thread_lib: intel-9.0-linux msvc test_tss: msvc test_tss_lib: intel-9.0-linux msvc test_xtime: msvc test_xtime_lib: intel-9.0-linux msvc |typeof| data_member_emulation: cw-9_4 data_member_native: intel-win32-9_0 intel-win32-9_0 function_emulation: cw-9_4 function_native: intel-win32-9_0 intel-win32-9_0 msvc function_ptr_emulation: cw-9_4 function_ptr_native: intel-win32-9_0 intel-win32-9_0 function_ref_emulation: cw-9_4 function_ref_native: intel-win32-9_0 intel-win32-9_0 lvalue_emulation: cw-9_4 lvalue_native: intel-win32-9_0 intel-win32-9_0 msvc member_function_emulation: cw-9_4 member_function_native: intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: intel-win32-9_0 std_native: intel-win32-9_0 template_dependent_native: intel-win32-9_0 template_enum_native: intel-win32-9_0 template_int_emulation: cw-9_4 template_int_native: intel-win32-9_0 intel-win32-9_0 template_multiword_native: intel-win32-9_0 template_tpl_emulation: cw-9_4 template_tpl_native: intel-win32-9_0 intel-win32-9_0 msvc template_type_emulation: cw-9_4 template_type_native: intel-win32-9_0 intel-win32-9_0 type_emulation: cw-8_3 cw-9_4 cw-9_4 type_native: intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux intel-9.0-linux

1 0

[config] Borland's standard library bug
by Robert Kawulak 26 Sep '05

26 Sep '05

Hi, I've discovered a bug of Borland's compiler (version 5.6.4 for Win32) standard library implementation - the errno is not a macro (as it should be according to The Standard - 17.4.1.2. p. 5), furthermore it's only in the std namespace (17.4.1.2. p. 4). Because of the second problem I'd suggest to add using std::errno line to the boost/config/compiler/borland.hpp file to make errno global as it should be, or maybe a macro BOOST_ERRNO which would evaluate to std::errno for Borland and just errno for other implementations. Am I right and how to do this/who's responsible for that? Thanks and best regards, Robert ---------------------------------------------------------------------- Jestem niesamowita... ;-) >>> http://link.interia.pl/f18b8

2 1

Re: [boost] [math] Proposed TR1 additions
by ajb＠spamcop.net 26 Sep '05

26 Sep '05

G'day all. John Maddock wrote: > Those of a mathematical inclination, might be interested to note that the > only substantive code in the TR1 submission currently under review is some > proposed additions to Boost.Math: mainly the inverse complex number trig > functions. Sorry, I haven't been keeping up with this. Do I read it as meaning that [tr.num.sf] is not present in the current submission? Cheers, Andrew Bromage

3 2

g++4 problems?
by Darren Cook 26 Sep '05

26 Sep '05

Has anyone had trouble with complex template code when moving from gcc 3.4 to gcc 4.0.1? I don't see anything in the release notes that matches the problem I'm getting, which looks like this (fuller error message attached below): no matching function for call to boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>::destroy(std::pair<const int, boost::smart_assert::assert_context_func>*) candidates are: void __gnu_cxx::__mt_alloc_base<_Tp>::destroy(_Tp*) [with _Tp = boost::smart_assert::assert_context_func] (despite the namespace this is not an official boost library, but I hope this does not count as too off-topic) Darren g++ -Wall -Werror -g3 -DBOOST_SMART_ASSERT_MODE=1 -DBWIDTH=9 -DBHEIGHT=9 -Wno-reorder -c -o test_main.9.o test_main.cpp /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_tree.h: In member function 'void std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::destroy_node(std::_Rb_tree_node<_Val>*) [with _Key = int, _Val = std::pair<const int, boost::smart_assert::assert_context_func>, _KeyOfValue = std::_Select1st<std::pair<const int, boost::smart_assert::assert_context_func> >, _Compare = std::less<int>, _Alloc = boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>]': /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_tree.h:1096: instantiated from 'void std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_M_erase(std::_Rb_tree_node<_Val>*) [with _Key = int, _Val = std::pair<const int, boost::smart_assert::assert_context_func>, _KeyOfValue = std::_Select1st<std::pair<const int, boost::smart_assert::assert_context_func> >, _Compare = std::less<int>, _Alloc = boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>]' /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_tree.h:570: instantiated from 'std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::~_Rb_tree() [with _Key = int, _Val = std::pair<const int, boost::smart_assert::assert_context_func>, _KeyOfValue = std::_Select1st<std::pair<const int, boost::smart_assert::assert_context_func> >, _Compare = std::less<int>, _Alloc = boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>]' /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_map.h:92: instantiated from here /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/bits/stl_tree.h:389: error: no matching function for call to 'boost::smart_assert::Private::smart_assert_alloc<boost::smart_assert::assert_context_func>::destroy(std::pair<const int, boost::smart_assert::assert_context_func>*)' /usr/lib/gcc/i386-redhat-linux/4.0.1/../../../../include/c++/4.0.1/ext/mt_allocator.h:614: note: candidates are: void __gnu_cxx::__mt_alloc_base<_Tp>::destroy(_Tp*) [with _Tp = boost::smart_assert::assert_context_func] ... (then more of the same) ...

1 1

thread yield
by Jason Hise 26 Sep '05

26 Sep '05

Can the yield function of boost::thread be used to immediately wake up a thread that is sleeping? I would like to use this to make sure that certain threads get the chance to exit before the process terminates, without join resulting in the whole program sleeping. -Jason

5 14

[cstdint] uintptr_t and intptr_t are missing
by Maxim Yegorushkin 26 Sep '05

26 Sep '05

Is this intentional that uintptr_t and intptr_t types are missing in cstdint.hpp? If it is so, why? http://www.opengroup.org/onlinepubs/009695399/basedefs/stdint.h.html

3 4

[math] Proposed TR1 additions
by John Maddock 26 Sep '05

26 Sep '05

Those of a mathematical inclination, might be interested to note that the only substantive code in the TR1 submission currently under review is some proposed additions to Boost.Math: mainly the inverse complex number trig functions. Just a heads up in case the "TR1" moniker didn't get your attention. John.

2 2

[mpl] The concept of laziness
by Cromwell Enage 26 Sep '05

26 Sep '05

I remember a thread that ran for a while on this topic, and I need to make sure I've wrapped my head around it correctly. Here are my takes on laziness: <take id="point-1"> A metafunction returns lazily if it can be used interchangeably with its return type. Numeric metatypes such as integral_c are examples of metafunctions that return lazily, e.g. "int_<6>" is the same as "typename int_<6>::type". Metafunctions such as next/prior, however, do not return lazily because they cannot be used interchangeably with their return types. For example, "times<next<int_<4> >,prior<long_<8> > >" is illegal; the expression must be "times<typename next<int_<4> >::type,typename prior<long_<8> >::type>". </take> <take id="point-2"> A metafunction evaluates a certain template argument lazily if it does not require the argument to be a fully instantiated type; otherwise, the evaluation is strict. The eval_if metafunction will strictly evaluate the second argument if the first argument is equivalent to false_; otherwise, it will strictly evaluate the third argument. </take> I'm less sure about point-2 than I am about point-1. In any case, feel free to correct any knowledge deficiencies I've exhibited, to make these definitions more complete. More examples would also be a great help. Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2