- Boost - lists.boost.org

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