- Boost - lists.boost.org

Re: [boost] static assert
by Philippe Mori 04 Jul '05

04 Jul '05

> Even though I'm surely not the first one that came up to this, I've got a > feature suggestion for the Static Assert library. > > It would probably be nice to have a variation of the macro that has a second > argument with a short description of the problem that caused the assertion. > > > For example: > > ... > #elif defined(BOOST_MSVC) > #define BOOST_STATIC_ASSERT2( B, explanation ) \ > typedef ::boost::static_assert_test<\ > sizeof(::boost::BOOST_JOIN(STATIC_ASSERTION_FAILURE__, explanation)< (bool)( > B ) >)>\ > BOOST_JOIN(boost_static_assert_typedef_, __COUNTER__) > ... > > static_assert(2 > 3, two_not_larger_than_three); > > error C2039: 'STATIC_ASSERTION_FAILURE__two_not_larger_than_three' : is not a > member of 'boost' > > > > Comments? > > Well, I tend to prefer a solution in the line of : STATIC_ASSERT_GT(2, 3); My implementation is based on conversion on template classes : template <long> struct Value { }; template <long p1, long p2, bool p3> struct ValueCond { }; #define STATIC_ASSERT_EQUAL(a, b) \ Value<(a)>(((void)0, Value<(b)>())) #define STATIC_ASSERT_GREATER(a, b) \ ValueCond<(a), (b), ((a) > (b))> \ (((void)0, ValueCond<(a), (b), true>())) Well, this solution needs some improvments : 1) Ensure it works on most compiler. It works with Visual C++ 7.1 and CodeWarrior for Palm 9.03. 2) Ensure that error message is meaningfull or try to find alternate solution for that compiler. 3) Make it BOOST compliant 4) Make it works with larger integers. Part of the solution is using the biggest integers availables at compile-time but it does still restrict the range of checks (it won't works for very big unsigned numbers). It should be done generally so that the user won't have to uses differents set of amcros for big unsignbed number as this would require the user to know the type of every constants he wants to check. In practice, this is not often a big constraint as we can always uses existing assertions for special cases and also because most check are relatively small number (for example, checking the size of a buffer). Philippe

2 1

static assert
by Goran Mitrovic 04 Jul '05

04 Jul '05

Even though I'm surely not the first one that came up to this, I've got a feature suggestion for the Static Assert library. It would probably be nice to have a variation of the macro that has a second argument with a short description of the problem that caused the assertion. For example: ... #elif defined(BOOST_MSVC) #define BOOST_STATIC_ASSERT2( B, explanation ) \ typedef ::boost::static_assert_test<\ sizeof(::boost::BOOST_JOIN(STATIC_ASSERTION_FAILURE__, explanation)< (bool)( B ) >)>\ BOOST_JOIN(boost_static_assert_typedef_, __COUNTER__) ... static_assert(2 > 3, two_not_larger_than_three); error C2039: 'STATIC_ASSERTION_FAILURE__two_not_larger_than_three' : is not a member of 'boost' Comments? P.S. With the usage of __VA_ARGS__, an implementation that would allow, with some programmer's discipline, both forms merged together might be done!

2 2

[ANN] xpressive 0.9.3 in boost-sandbox
by Eric Niebler 04 Jul '05

04 Jul '05

<< Background >> xpressive is a TR1 regex work-alike that also accepts regexes as expression templates and lets regexes nest and call each other recursively. << Significant changes since 0.9.2 >> - TR1-style regex_traits interface - Speed enhancements - syntax_option_type::ignore_white_space << Download >> xpressive.zip at: http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler << Docs >> http://boost-sandbox.sf.net/libs/xpressive -- Eric Niebler Boost Consulting www.boost-consulting.com

2 2

[Serialization] base_object.hpp fix
by Douglas Gregor 04 Jul '05

04 Jul '05

I've checked in the following patch, which fixes several multi_index tests on the OSL machines. Doug > > Index: base_object.hpp > =================================================================== > RCS file: /cvsroot/boost/boost/boost/serialization/base_object.hpp,v > retrieving revision 1.12 > retrieving revision 1.13 > diff -u -d -r1.12 -r1.13 > --- base_object.hpp 4 Jul 2005 05:32:13 -0000 1.12 > +++ base_object.hpp 4 Jul 2005 18:18:20 -0000 1.13 > @@ -39,7 +39,7 @@ > > #if ! defined(BOOST_ARCHIVE_BASIC_ARCHIVE_HPP) > template<class Derived, class Base> > - const void_caster & void_cast_register( > + void void_cast_register( > const Derived * /* dnull = NULL */, > const Base * /* bnull = NULL */ > );

1 0

Re: [boost] Refering to Boost.Build in print
by Bjorn.Karlsson＠readsoft.com 04 Jul '05

04 Jul '05

> From: Jonathan Turkanis [mailto:technews@kangaroologic.com] > > > > I guess the most consistent thing would be to capitalize "Build" and > > leave the rest as you have written it. > > Really? To me it seems a bit odd to treat the works "build" > and "system" > differently, when they are both components on the term "build > system." My > instinct would have been to use either "Boost Build System" > or "Boost build > system." I think that "the Boost build system" is correct. There's no need to apply rules for [writing about] Boost library names to the term "build system". Bjorn

2 1

Re: [boost] Regressions in your Boost libraries as of 2005-07-02
by David Abrahams 03 Jul '05

03 Jul '05

Douglas Gregor <dgregor(a)cs.indiana.edu> writes: > You are receiving this report because one or more of the libraries you > maintain has regression test failures that are not accounted for. > A full version of the report is sent to the Boost developer's mailing > list. > > Detailed report: > http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… > > There are failures in these libraries you maintain: > python (4) > > |python| > extract: gcc-3.3.6-linux > list: gcc-3.3.6-linux > operators: gcc-3.3.6-linux > slice: gcc-3.3.6-linux Doug, this surprises me, since I tested Boost.Python on the machine you indicated and all tests passed. Did you adjust the toolset in the way I indicated was necessary? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 2

more/separate_compilation.html
by David Abrahams 03 Jul '05

03 Jul '05

in http://boost-consulting.com/boost/more/separate_compilation.html (wow, I didn't know we had this file!) there are many mentions of the "common names" rule in the comments (which I assume should be "common-names") but no usages of it -- instead there are many instances of common-variant. That doesn't seem quite right. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Boost regression notification (2005-07-03)
by Douglas Gregor 03 Jul '05

03 Jul '05

Boost regression test failures ------------------------------ Report time: 2005-07-03T15:28:23Z 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. random preprocessor io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 279 failures in 12 libraries: date_time (1) graph (2) io (2) numeric/ublas (6) preprocessor (1) program_options (12) random (3) serialization (235) spirit (6) test (6) thread (1) wave (4) |date_time| testlocal_time_input_facet: cw-9_4 |graph| astar_search_test: vc-8_0 graphviz_test: intel-win32-8_1 |io| ios_state_unit_test: intel-win32-8_1 intel-win32-8_1 |numeric/ublas| test1: cw-9_4 intel-win32-8_1 test3: cw-9_4 test4: cw-9_4 test5: cw-9_4 test6: cw-9_4 |preprocessor| seq: cw-8_3 |program_options| cmdline_test: vc-7_0 cmdline_test_dll: mingw-3_4_2 vc-7_0 parsers_test: vc-7_0 parsers_test_dll: vc-7_0 positional_options_test_dll: mingw-3_4_2 unicode_test: vc-7_0 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin vc-7_0 variable_map_test: vc-7_0 variable_map_test_dll: vc-7_0 |random| random_test: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 |serialization| test_array_text_archive_dll: cw-9_5-darwin test_array_text_warchive_dll: cw-9_5-darwin test_array_xml_archive_dll: cw-9_5-darwin test_array_xml_warchive_dll: cw-9_5-darwin test_binary_text_archive_dll: cw-9_5-darwin test_binary_text_warchive_dll: cw-9_5-darwin test_binary_xml_archive_dll: cw-9_5-darwin test_binary_xml_warchive_dll: cw-9_5-darwin test_class_info_load_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_binary_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-6_5 test_class_info_load_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_save_text_archive_dll: cw-9_5-darwin test_class_info_save_text_warchive_dll: cw-9_5-darwin test_class_info_save_xml_warchive_dll: cw-9_5-darwin test_const_load_fail1: borland-5_6_4 test_const_load_fail1_nvp: borland-5_6_4 test_const_load_fail2: borland-5_6_4 test_const_load_fail2_nvp: borland-5_6_4 test_const_save_fail1: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail2: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail3: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_contained_class_text_archive_dll: cw-9_5-darwin test_contained_class_text_warchive_dll: cw-9_5-darwin test_contained_class_xml_archive_dll: cw-9_5-darwin test_contained_class_xml_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_text_archive_dll: cw-9_5-darwin test_cyclic_ptrs_text_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_archive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_warchive_dll: cw-9_5-darwin test_delete_pointer_binary_archive_dll: vc-8_0 test_delete_pointer_text_archive_dll: cw-9_5-darwin test_delete_pointer_text_warchive_dll: cw-9_5-darwin test_delete_pointer_xml_archive_dll: cw-9_5-darwin test_delete_pointer_xml_warchive_dll: cw-9_5-darwin test_demo_auto_ptr_dll: cw-9_5-darwin test_demo_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_exception_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_fast_archive_dll: msvc vc-6_5 test_demo_pimpl_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_demo_polymorphic_dll: cw-9_5-darwin test_demo_portable_archive: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 vc-7_0 vc-7_1 vc-8_0 test_demo_portable_archive_dll: borland-5_6_4 intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 test_demo_shared_ptr: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_shared_ptr_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-7_0 test_deque_text_archive_dll: cw-9_5-darwin test_deque_text_warchive_dll: cw-9_5-darwin test_deque_xml_archive_dll: cw-9_5-darwin test_deque_xml_warchive_dll: cw-9_5-darwin test_derived_class_ptr_text_archive_dll: cw-9_5-darwin test_derived_class_ptr_text_warchive_dll: cw-9_5-darwin test_derived_class_ptr_xml_archive_dll: cw-9_5-darwin test_derived_class_ptr_xml_warchive_dll: cw-9_5-darwin test_derived_class_text_archive_dll: cw-9_5-darwin test_derived_class_text_warchive_dll: cw-9_5-darwin test_derived_class_xml_archive_dll: cw-9_5-darwin test_derived_class_xml_warchive_dll: cw-9_5-darwin test_derived_text_archive_dll: cw-9_5-darwin test_derived_text_warchive_dll: cw-9_5-darwin test_derived_xml_warchive_dll: cw-9_5-darwin test_diamond_binary_archive: cw-8_3 cw-9_5-darwin test_diamond_binary_archive_dll: cw-9_5-darwin test_diamond_text_archive: cw-8_3 cw-9_5-darwin test_diamond_text_archive_dll: cw-9_5-darwin test_diamond_text_warchive: cw-8_3 cw-9_5-darwin test_diamond_text_warchive_dll: cw-9_5-darwin test_diamond_xml_archive: cw-8_3 cw-9_5-darwin test_diamond_xml_archive_dll: cw-9_5-darwin test_diamond_xml_warchive: cw-8_3 cw-9_5-darwin test_diamond_xml_warchive_dll: cw-9_5-darwin test_list_ptrs_text_archive_dll: cw-9_5-darwin test_list_ptrs_text_warchive_dll: cw-9_5-darwin test_list_ptrs_xml_archive_dll: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: cw-9_5-darwin test_list_text_archive_dll: cw-9_5-darwin test_list_text_warchive_dll: cw-9_5-darwin test_list_xml_archive_dll: cw-9_5-darwin test_list_xml_warchive_dll: cw-9_5-darwin test_map_binary_archive_dll: msvc vc-6_5 vc-7_0 test_map_text_archive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_text_warchive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_xml_archive_dll: cw-9_5-darwin test_map_xml_warchive_dll: cw-9_5-darwin test_mi_text_warchive_dll: intel-win32-8_1 test_mult_archive_types: cw-9_4 cw-9_4 cw-9_5-darwin test_mult_archive_types_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 test_multiple_ptrs_text_archive_dll: cw-9_5-darwin test_multiple_ptrs_text_warchive_dll: cw-9_5-darwin test_multiple_ptrs_xml_archive_dll: cw-9_5-darwin test_multiple_ptrs_xml_warchive_dll: cw-9_5-darwin test_no_rtti_text_archive_dll: intel-win32-8_1 test_non_default_ctor_text_archive_dll: cw-9_5-darwin test_non_default_ctor_text_warchive_dll: cw-9_5-darwin test_non_default_ctor_xml_archive_dll: cw-9_5-darwin test_non_default_ctor_xml_warchive_dll: cw-9_5-darwin test_non_intrusive_text_archive_dll: cw-9_5-darwin test_non_intrusive_text_warchive_dll: cw-9_5-darwin test_non_intrusive_xml_archive_dll: cw-9_5-darwin test_non_intrusive_xml_warchive_dll: cw-9_5-darwin test_null_ptr_text_archive_dll: cw-9_5-darwin test_null_ptr_text_warchive_dll: cw-9_5-darwin test_null_ptr_xml_warchive_dll: cw-9_5-darwin test_nvp_text_archive_dll: cw-9_5-darwin test_nvp_text_warchive_dll: cw-9_5-darwin test_nvp_xml_archive_dll: cw-9_5-darwin test_nvp_xml_warchive_dll: cw-9_5-darwin test_object_text_warchive_dll: cw-9_5-darwin test_object_xml_warchive_dll: cw-9_5-darwin test_optional_text_archive_dll: cw-9_5-darwin test_optional_text_warchive_dll: cw-9_5-darwin test_optional_xml_archive_dll: cw-9_5-darwin test_optional_xml_warchive_dll: cw-9_5-darwin test_polymorphic_text_archive_dll: cw-9_5-darwin test_polymorphic_text_warchive_dll: cw-9_5-darwin test_polymorphic_xml_archive_dll: cw-9_5-darwin test_polymorphic_xml_warchive_dll: cw-9_5-darwin test_primitive_text_warchive_dll: cw-9_5-darwin test_primitive_xml_warchive_dll: cw-9_5-darwin test_private_ctor_dll: cw-9_5-darwin test_recursion_text_archive_dll: cw-9_5-darwin test_recursion_text_warchive_dll: cw-9_5-darwin test_recursion_xml_archive_dll: cw-9_5-darwin test_recursion_xml_warchive_dll: cw-9_5-darwin test_reset_object_address_dll: cw-9_5-darwin test_set_text_archive_dll: cw-9_5-darwin test_set_text_warchive_dll: cw-9_5-darwin test_set_xml_archive_dll: cw-9_5-darwin test_set_xml_warchive_dll: cw-9_5-darwin test_shared_ptr_132_binary_archive: borland-5_6_4 test_shared_ptr_132_binary_archive_dll: borland-5_6_4 test_shared_ptr_132_text_archive: borland-5_6_4 test_shared_ptr_132_text_archive_dll: borland-5_6_4 test_shared_ptr_132_text_warchive: borland-5_6_4 test_shared_ptr_132_text_warchive_dll: borland-5_6_4 test_shared_ptr_132_xml_archive: borland-5_6_4 test_shared_ptr_132_xml_archive_dll: borland-5_6_4 test_shared_ptr_132_xml_warchive: borland-5_6_4 intel-win32-8_1 test_shared_ptr_132_xml_warchive_dll: borland-5_6_4 test_simple_class_ptr_text_archive_dll: cw-9_5-darwin test_simple_class_ptr_text_warchive_dll: cw-9_5-darwin test_simple_class_ptr_xml_archive_dll: cw-9_5-darwin test_simple_class_ptr_xml_warchive_dll: cw-9_5-darwin test_simple_class_text_archive_dll: cw-9_5-darwin test_simple_class_text_warchive_dll: cw-9_5-darwin test_simple_class_xml_archive_dll: cw-9_5-darwin test_simple_class_xml_warchive_dll: cw-9_5-darwin test_split_text_archive_dll: cw-9_5-darwin test_split_text_warchive_dll: cw-9_5-darwin test_split_xml_warchive_dll: cw-9_5-darwin test_tracking_text_archive_dll: cw-9_5-darwin test_tracking_text_warchive_dll: cw-9_5-darwin test_tracking_xml_warchive_dll: cw-9_5-darwin test_variant_text_archive_dll: cw-9_5-darwin test_variant_text_warchive_dll: cw-9_5-darwin test_variant_xml_archive_dll: cw-9_5-darwin test_variant_xml_warchive_dll: cw-9_5-darwin test_vector_text_archive_dll: cw-9_5-darwin test_vector_text_warchive_dll: cw-9_5-darwin test_vector_xml_archive_dll: cw-9_5-darwin test_vector_xml_warchive_dll: cw-9_5-darwin |spirit| bug_fixes: cw-9_5-darwin bug_fixes_debug: cw-9_5-darwin numerics_tests: gcc-3.2.3-linux numerics_tests_debug: gcc-3.2.3-linux owi_mt_tests: cw-9_4 gcc-3_3-darwin |test| errors_handling_test: cw-9_5-darwin vc-8_0 test_fp_comparisons: borland-5_6_4 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin |thread| test_read_write_mutex: borland-5_6_4 |wave| testwave: cw-8_3 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux

1 0

Re: [boost] Boost regression notification (2005-06-28)
by JOAQUIN LOPEZ MU?Z 03 Jul '05

03 Jul '05

----- Mensaje original ----- De: Joel de Guzman <joel(a)boost-consulting.com> Fecha: Martes, Junio 28, 2005 8:16 pm Asunto: Re: [boost] Boost regression notification (2005-06-28) > Douglas Gregor wrote: > > Boost regression test failures > > > > |spirit| > > action_tests: vc-6_5 > > action_tests_debug: vc-6_5 > > ast_calc_tests: vc-6_5 > > ast_calc_tests_debug: vc-6_5 > [...] > > traverse_tests: vc-6_5 > > traverse_tests_debug: vc-6_5 > > while_p_as_parser_tests: vc-6_5 > > while_tests: vc-6_5 > > while_tests_debug: vc-6_5 > > Yaiks! What happened? VC6.5 is supposed to be an unsupported > (unusable) compiler for Spirit 1.8.x. > metacomm has begun using the vc-6_5 toolset, which is an alias of the old msvc toolset. Markup in status/explicit-failures-markup.xml has to be duplicated for this alternative name. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

5 4

Re: [boost] [function_type] Tag types documentation
by Dave Gomboc 03 Jul '05

03 Jul '05

> Tag Types: > ---------- > > The Function Type library uses tag types to represent one > more attributive > properties of a type, such as its variadicness or its calling > convention. "one more"? Did you mean "one or more"? "a type"? It might be one type per tag, but tagging can be applied to more than one type, so this should be rephrased. "variadicness"? I think you meant "variadicity". I'm not thrilled by "attributive properties" either. My discomforture with this phrase is due to its perceived redundancy. Is it common for properties to exist that attribute nothing? I propose: The Function Type library uses tag types to denote properties of types. For example, the tag tag<fastcall, variadic> may be used to denote use of the fast calling convention in combination with variadicity. > When several tags for the same property appear in the > argument list, only the last > one is used; others are ignored. > > tag<nonvariadic,variadic> // same as 'variadic' The semantics of tag<nonvariadic, variadic> should be identical to the semantics of tag<variadic, nonvariadic>. It strikes me as erroneous that this combination of denotations would not yield a compilation error. Have you a well-founded argument for this choice? I'm new to this thread; apologies if I'm rehashing something that was settled earlier. Dave Gomboc

2 2