February 2006 - Boost - lists.preview.boost.org

[Range] initial feedback on return values of algorithms
by Thorsten Ottosen 19 Feb '06

19 Feb '06

Dear all, The plan is to include range-based overloads of std algorithms in the next boost.range. We have several options for specifying the return type of functions that normally return an iterator that I would like your feedback on. 1. leave the return type as it is. 2. return an iterator_range describing the range [found,end) this allows us to do stuff like namespace br = boost::ranges; br::erase( rng, br::unique(rng) ); 3. inspired by John Torjo's range lib, provide a whole list of possible return values: std::vector<int> v; namespace br = boost::ranges; br::unique(v); br::unique<br::return_found>(v); br::unique<br::return_next>(v); br::unique<br::return_prior>(v); br::unique<br::return_begin_found>(v); br::unique<br::return_begin_next>(v); br::unique<br::return_begin_prior>(v); br::unique<br::return_found_end>(v); br::unique<br::return_next_end>(v); br::unique<br::return_prior_end>(v); the default would be the range [found,end), but the you can pick different slices or simply iterators. In the above scheme, "found" is the iterator normally returnes by the algorithm, "next" means boost::next(found) and "prior" means boost::prior(found). The advantage of the latter approach is - flexibility/power - safety (we can tjeck that next(found) and prior(found) stays in range) The disadvantage is that it will require twice as many overloads in C++03 (since we can't put defaults template arguments in function templates). Any opinions? -Thorsten

5 29

[pkg-boost-devel] Boost on Debian
by Steve M. Robbins 19 Feb '06

19 Feb '06

Hello Dave, I'm responding to your message on boost mailing list http://lists.boost.org/Archives/boost/2006/02/100262.php Domenico Andreoli also contributed to this response. Apologies for the tardy response. I read the list very infrequently via web archives and I have only just noticed the message. So you ask: I am going to be trying to write some new "getting started" documentation for Boost for the upcoming release. I would really like to include some information about what people can expect when they get Boost packages from their Debian, RedHat, whatever distribution. All of our documentation so far is written from the perspective that users have a complete Boost CVS tree, but I guess that's not true for everyone? Can you fill us in? The short answer is: someone wishing to develop code using Boost under Debian need install the package libboost-dev (and, possibly, other -dev packages like libboost-filesystem-dev). The headers as well as static and shared library files are all installed into standard linux locations. Compilation and linking is done with no special options other than specifying the library; e.g. "-lboost_filesystem". Our goal is to make the Debian Boost library packages as much like standard libraries as possible. For Debian, this means that headers and link-time library files are contained in a "-dev" package. In addition, for each library that builds a shared object, we have a separate, versioned package, e.g. "libboost-filesystem1.33.1". Normally, however, one isn't concerned with the library package because the "-dev" package depends on the shared library package and installing the former automatically brings in the latter. The list of all -dev packages can be obtained by looking at what libboost-dev suggests with standard Debian tools like "aptitude" or "apt-cache". The "-dev" package contains the "release" build with both single- and multi-threaded versions, in both static and shared flavours for a total of 4 libraries. So the developer may choose to link using "-llibboost_filesystem-gcc-1_33_1" or " "-llibboost_filesystem-gcc-mt-1_33_1", shared or static. We also provide a shorthand symbolic link for the multithreaded version; you can use just "-llibboost_filesystem" (shared or static). In addition to the "-dev" packages, we have libboost-doc (documentation) bcp boost-jam boost-build (v2) Finally, there is a "libboost-dbg" package that contains the debug build of all the shared libraries, both single- and multi-threaded. Hope this is helpful, -Steve _______________________________________________ pkg-boost-devel mailing list pkg-boost-devel(a)lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-boost-devel

1 0

[serialization] exception-safety of container-serialization
by Thorsten Ottosen 19 Feb '06

19 Feb '06

Dear All, I have just added serialization to Boost.Ptr container. I briefly discussed an issue with Robert, namely that the current implementation calls clear() before reading the new values. The alternative is to provide roll-back guarantee by default by creating a local container and swap() in the end. By default this would temporarily use more memory. IMO we should go for the strong guarantee. Any thoughts? -Thorsten

5 13

Re: [boost] [serialization] exception-safety of container-serialization
by JOAQUIN LOPEZ MU?Z 18 Feb '06

18 Feb '06

----- Mensaje original ----- De: bwood <brass(a)mailvault.com> Fecha: Sábado, Febrero 18, 2006 7:42 pm Asunto: Re: [boost] [serialization] exception-safety of container-serialization > Joaquín M López Muñoz wrote: > >I would NOT go for the strong guarantee for the following > two reasons: > > > >1. Given the basic guarantee, all-or-nothing semantics can > >be implemented externally, and as efficiently as you'd do it > >internally. > >2. It might be of interest to keep a partially recovered object. > >For instance, think of the situation in which a container is > being > >marshalled thru a socket and you lose internet conectivity. > > I started to reply to this and then wondered if I understood > what you meant. Were you talking about the container as the > "partially recovered object" or an object that will be stored > by the container? The former. > The subsequent discussion I guess points to > the latter. I think the first case is interesting. If a program > sends 100 objects and another receives 99 of them no problem, > it would probably be helpful to get that information back to > the sender so the whole thing isn't repeated. Does Boost:: > serialization support this? > It does, at least for STL containers: if an error is found during the process of loading elements into a container, the container retains the elements succesfully loaded so far. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

A small utility for template policy selection
by Spencer Collyer 18 Feb '06

18 Feb '06

Whilst working on a policy-based sparse-array class (which I hope to submit to Boost at some point), I had the problem that there did not seem to be any sensible way to organise the policies such that sensible defaults could be coded in the template. Rather than always forcing the users to specify the earlier policies, even when the default would be fine, simply because they wanted to use a different policy for one of the later parameters, I came up with the following little utility. =============================================================== #include <boost/mpl/find_if.hpp> #include <boost/mpl/deref.hpp> #include <boost/type_traits/is_base_of.hpp> using namespace boost; using namespace boost::mpl; template<typename Base, typename Types, typename DefType> class PolicySelector { private: typedef typename find_if< Types, is_base_of<Base,_1> >::type pos; typedef typename end<Types>::type end_pos; public: typedef typename if_< is_same<pos, end_pos>, DefType, typename deref<pos>::type >::type type; }; =============================================================== Basically, you pass a boost::mpl sequence in the Types argument (I usually use a mpl::vector), along with the base class for the policy classes and a default class to use if none is found otherwise, and the 'type' member gives the selected policy. The only restriction it imposes is that all classes implementing a particular policy type have to inherit from a single base class. A (slightly contrived :-) ) example to show how this is used: =============================================================== #include <boost/mpl/find_if.hpp> #include <boost/mpl/deref.hpp> #include <boost/type_traits/is_base_of.hpp> #include <boost/mpl/vector.hpp> #include <boost/mpl/placeholders.hpp> #include <iostream> using namespace boost; using namespace boost::mpl; template<typename Base, typename Types, typename DefType> class PolicySelector { private: typedef typename find_if< Types, is_base_of<Base,_1> >::type pos; typedef typename end<Types>::type end_pos; public: typedef typename if_< is_same<pos, end_pos>, DefType, typename deref<pos>::type >::type type; }; class a_base { }; class a1 : public a_base { }; class a2 : public a_base { }; class a3 : public a1 { }; class b_base { }; class b1 : public b_base { }; class b2 : public b_base { }; class b3 : public b_base { }; // Select the 'A' policy. Default is a3. template<typename Types> class A_Selector { public: typedef typename PolicySelector< a_base , typename Types::type , a3>::type type; }; // Select the 'B' policy. Default is b2. template<typename Types> class B_Selector { public: typedef typename PolicySelector< b_base , typename Types::type , b2>::type type; }; // Utility class to ease building a mpl::vector. template<class p1=na, class p2=na> class sel_types { public: typedef typename vector<p1,p2>::type type; }; // Test class template. template<class Policies> class testit : public A_Selector<Policies>::type , public B_Selector<Policies>::type { public: typedef typename A_Selector<Policies>::type APolicy; typedef typename B_Selector<Policies>::type BPolicy; }; int main() { // Test policies listed in 'normal' order typedef testit<sel_types<a1, b1> > types1; typedef types1::APolicy A1; typedef types1::BPolicy B1; A1 aa1; std::cout << "Got " << typeid(aa1).name() << "\n"; std::cout << "Expected " << typeid(a1).name() << "\n"; B1 bb1; std::cout << "Got " << typeid(bb1).name() << "\n"; std::cout << "Expected " << typeid(b1).name() << "\n"; // Test missing 'B' policy - should use default typedef testit<sel_types<a2> > types2; typedef types1::APolicy A2; typedef types1::BPolicy B2; A2 aa2; std::cout << "Got " << typeid(aa2).name() << "\n"; std::cout << "Expected " << typeid(a2).name() << "\n"; B2 bb2; std::cout << "Got " << typeid(bb2).name() << "\n"; std::cout << "Expected " << typeid(b2).name() << "\n"; // Test missing 'A' policy - should use default typedef testit<sel_types<b1> > types3; typedef types1::APolicy A3; typedef types1::BPolicy B3; A3 aa3; std::cout << "Got " << typeid(aa3).name() << "\n"; std::cout << "Expected " << typeid(a3).name() << "\n"; B3 bb3; std::cout << "Got " << typeid(bb3).name() << "\n"; std::cout << "Expected " << typeid(b1).name() << "\n"; // Test policies in 'reversed' order. typedef testit<sel_types<b1, a1> > types4; typedef types1::APolicy A4; typedef types1::BPolicy B4; A4 aa4; std::cout << "Got " << typeid(aa4).name() << "\n"; std::cout << "Expected " << typeid(a1).name() << "\n"; B4 bb4; std::cout << "Got " << typeid(bb4).name() << "\n"; std::cout << "Expected " << typeid(b1).name() << "\n"; } =============================================================== As you can see, it doesn't matter which order the policies are specified in, nor whether they are specified at all. Would this utility be useful to anyone else? Is it worth my while writing up some proper documentation and submitting it for review? If so, which library would it go into? Spencer Collyer -- 12:47pm up 48 days 20:28, 21 users, load average: 0.09, 0.06, 0.13 Registered Linux User #232457 | LFS ID 11703

8 24

[feature freeze] range issue
by Thorsten Ottosen 18 Feb '06

18 Feb '06

Thomas, Do you have anything to add to the discussion on committing the new version of boost.range? -Thorsten

6 14

[Assign] list_of comma operator removed?
by Jon Willesen 18 Feb '06

18 Feb '06

I recently attempted to upgrade from boost 1.32.0 to boost 1.33.1 got received some compiler errors from boost.assign. My most common usage of boost::assign looks like this: vector<string> data = (list_of<string>(), "foo", "bar", "baz"); I like this better than the alternative syntax (elements delimeted by parentheses) because I can type it more quickly and it more closely resembles array initialization syntax, which makes it more likely that my coworkers, who aren't as familiar with boost, will understand what's going on. But it appears my compiler errors were caused by the removal of the comma operator in the class the list_of function returns. It appears this was intentional since the unit tests were changed, but the current documentation for list_of still indicates the comma operator is legal syntax, and operator+= still uses the comma syntax, so I'm a little confused. I remember there was some discussion on this list earlier about the comma operator and whether it is ever ok to overload it, but I couldn't find anything about actually removing it from any aspect of boost.assign in the mailing list, the documentation, or the version history. Maybe I haven't looked deeply enough yet? Was the comma operator intentionally removed from list_of? If so, I would like to understand why so I can be properly dissuaded from reintroducing it for my own use. Thanks, -- Jon Willesen

2 10

Re: [boost] [serialization] exception-safety of container-serialization
by bwood 18 Feb '06

18 Feb '06

Joaquín M López Muñoz wrote: >I would NOT go for the strong guarantee for the following two reasons: >1. Given the basic guarantee, all-or-nothing semantics can >be implemented externally, and as efficiently as you'd do it >internally. >2. It might be of interest to keep a partially recovered object. >For instance, think of the situation in which a container is being >marshalled thru a socket and you lose internet conectivity. I started to reply to this and then wondered if I understood what you meant. Were you talking about the container as the "partially recovered object" or an object that will be stored by the container? The subsequent discussion I guess points to the latter. I think the first case is interesting. If a program sends 100 objects and another receives 99 of them no problem, it would probably be helpful to get that information back to the sender so the whole thing isn't repeated. Does Boost:: serialization support this? Brian

1 0

[concept check] Working on vc7.1?
by David Abrahams 18 Feb '06

18 Feb '06

Both concept_check_fail_expected and concept_check_class_fail_expected are compiling without errors for me. That makes me concerned that the library doesn't work at all on vc7.1. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Boost regression notification (2006-02-18 [HEAD])
by Douglas Gregor 18 Feb '06

18 Feb '06

Boost Regression test failures Report time: 2006-02-18T13:44:58Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 702 failures in 26 libraries random (1) concept_check (23) functional/hash (3) iostreams (2) graph (4) signals (32) program_options (7) rational (3) test (4) parameter (31) math (3) python (2) wave (3) integer (1) serialization (400) optional (10) spirit (36) pool (1) date_time (5) thread (1) config (1) multi_index (24) ptr_container (43) typeof (21) filesystem (34) assign (7) |random| random_test: intel-9.0-linux |concept_check| stl_concept_covering: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 qcc-3.3.5-cpp qcc-3.3.5-gpp tru64cxx71-006 vc-7_1 vc-7_1 |functional/hash| hash_friend_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux hash_global_namespace_test: borland-5_6_4 |iostreams| mapped_file_test: qcc-3.3.5-cpp qcc-3.3.5-gpp |graph| bundled_properties: qcc-3.3.5-cpp qcc-3.3.5-gpp graphviz_test: vc-7_1 vc-7_1 |signals| dead_slot_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin mingw-3_4_2 qcc-3.3.5-cpp qcc-3.3.5-gpp vc-7_1 vc-7_1 trackable_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin mingw-3_4_2 qcc-3.3.5-cpp qcc-3.3.5-gpp vc-7_1 vc-7_1 |program_options| cmdline_test_dll: cw-9_4 options_description_test_dll: cw-9_4 parsers_test_dll: cw-9_4 positional_options_test_dll: cw-9_4 unicode_test_dll: cw-9_4 variable_map_test_dll: cw-9_4 winmain_dll: cw-9_4 |rational| rational_test: borland-5_6_4 gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |test| test_fp_comparisons: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tools_test: gcc-4_0-darwin mingw-3_4_2 |parameter| basics: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux duplicates: borland-5_6_4 earwicker: 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 macros: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mpl: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux ntp: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux preprocessor: 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 singular: borland-5_6_4 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: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |math| complex_test: borland-5_6_4 hypot_test: borland-5_6_4 log1p_expm1_test: borland-5_6_4 |python| numpy: gcc-4_0-darwin slice: gcc-4_0-darwin |wave| testwave: cw-9_5-darwin testwave_dll: cw-9_4 cw-9_5-darwin |integer| integer_traits_test: qcc-3.3.5-gpp |serialization| test_array_binary_archive_dll: cw-9_4 test_array_text_archive_dll: cw-9_4 test_array_text_warchive_dll: cw-9_4 test_array_xml_archive_dll: cw-9_4 test_array_xml_warchive_dll: cw-9_4 test_binary_binary_archive_dll: cw-9_4 test_binary_text_archive_dll: cw-9_4 test_binary_text_warchive_dll: cw-9_4 test_binary_xml_archive_dll: cw-9_4 test_binary_xml_warchive_dll: cw-9_4 test_class_info_load_binary_archive_dll: cw-9_4 test_class_info_load_text_archive_dll: cw-9_4 test_class_info_load_text_warchive_dll: cw-9_4 test_class_info_load_xml_archive_dll: cw-9_4 test_class_info_load_xml_warchive_dll: cw-9_4 test_class_info_save_binary_archive_dll: cw-9_4 test_class_info_save_text_archive_dll: cw-9_4 test_class_info_save_text_warchive_dll: cw-9_4 test_class_info_save_xml_archive_dll: cw-9_4 test_class_info_save_xml_warchive_dll: cw-9_4 test_codecvt_null: qcc-3.3.5-gpp test_contained_class_binary_archive_dll: cw-9_4 test_contained_class_text_archive_dll: cw-9_4 test_contained_class_text_warchive_dll: cw-9_4 test_contained_class_xml_archive_dll: cw-9_4 test_contained_class_xml_warchive_dll: cw-9_4 test_cyclic_ptrs_binary_archive_dll: cw-9_4 test_cyclic_ptrs_text_archive_dll: cw-9_4 test_cyclic_ptrs_text_warchive_dll: cw-9_4 test_cyclic_ptrs_xml_archive_dll: cw-9_4 test_cyclic_ptrs_xml_warchive_dll: cw-9_4 test_delete_pointer_binary_archive_dll: cw-9_4 test_delete_pointer_text_archive_dll: cw-9_4 test_delete_pointer_text_warchive_dll: cw-9_4 test_delete_pointer_xml_archive_dll: cw-9_4 test_delete_pointer_xml_warchive_dll: cw-9_4 test_demo_auto_ptr_dll: cw-9_4 test_demo_fast_archive_dll: cw-9_4 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 test_demo_pimpl_dll: cw-9_4 test_demo_polymorphic_dll: cw-9_4 test_demo_portable_archive_dll: cw-9_4 test_demo_xml: intel-win32-8_1 test_deque_binary_archive_dll: cw-9_4 test_deque_text_archive_dll: cw-9_4 test_deque_text_warchive_dll: cw-9_4 test_deque_xml_archive_dll: cw-9_4 test_deque_xml_warchive_dll: cw-9_4 test_derived_binary_archive_dll: cw-9_4 test_derived_class_binary_archive_dll: cw-9_4 test_derived_class_ptr_binary_archive_dll: cw-9_4 test_derived_class_ptr_text_archive_dll: cw-9_4 test_derived_class_ptr_text_warchive_dll: cw-9_4 test_derived_class_ptr_xml_archive_dll: cw-9_4 test_derived_class_ptr_xml_warchive_dll: cw-9_4 test_derived_class_text_archive_dll: cw-9_4 test_derived_class_text_warchive_dll: cw-9_4 test_derived_class_xml_archive_dll: cw-9_4 test_derived_class_xml_warchive_dll: cw-9_4 test_derived_text_archive_dll: cw-9_4 test_derived_text_warchive_dll: cw-9_4 test_derived_xml_archive_dll: cw-9_4 test_derived_xml_warchive_dll: cw-9_4 test_diamond_binary_archive_dll: cw-9_4 test_diamond_text_archive_dll: cw-9_4 test_diamond_text_warchive_dll: cw-9_4 test_diamond_xml_archive_dll: cw-9_4 intel-win32-8_1 test_diamond_xml_warchive_dll: cw-9_4 test_list_binary_archive_dll: cw-9_4 test_list_ptrs_binary_archive_dll: cw-9_4 test_list_ptrs_text_archive_dll: cw-9_4 test_list_ptrs_text_warchive_dll: cw-9_4 test_list_ptrs_xml_archive_dll: cw-9_4 test_list_ptrs_xml_warchive_dll: cw-9_4 test_list_text_archive_dll: cw-9_4 test_list_text_warchive_dll: cw-9_4 test_list_xml_archive_dll: cw-9_4 test_list_xml_warchive_dll: cw-9_4 test_map_binary_archive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_map_binary_archive_dll: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_map_text_archive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_map_text_archive_dll: borland-5_6_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_map_text_warchive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux test_map_text_warchive_dll: borland-5_6_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux test_map_xml_archive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_map_xml_archive_dll: borland-5_6_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_map_xml_warchive: borland-5_6_4 cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux test_map_xml_warchive_dll: borland-5_6_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux test_multiple_ptrs_binary_archive_dll: cw-9_4 test_multiple_ptrs_text_archive_dll: cw-9_4 test_multiple_ptrs_text_warchive_dll: cw-9_4 test_multiple_ptrs_xml_archive_dll: cw-9_4 test_multiple_ptrs_xml_warchive_dll: cw-9_4 test_non_default_ctor_binary_archive_dll: cw-9_4 test_non_default_ctor_text_archive_dll: cw-9_4 test_non_default_ctor_text_warchive_dll: cw-9_4 test_non_default_ctor_xml_archive_dll: cw-9_4 test_non_default_ctor_xml_warchive_dll: cw-9_4 test_non_intrusive_binary_archive_dll: cw-9_4 test_non_intrusive_text_archive_dll: cw-9_4 test_non_intrusive_text_warchive_dll: cw-9_4 test_non_intrusive_xml_archive_dll: cw-9_4 test_non_intrusive_xml_warchive_dll: cw-9_4 test_null_ptr_binary_archive_dll: cw-9_4 test_null_ptr_text_archive_dll: cw-9_4 test_null_ptr_text_warchive_dll: cw-9_4 test_null_ptr_xml_archive_dll: cw-9_4 test_null_ptr_xml_warchive_dll: cw-9_4 test_nvp_binary_archive_dll: cw-9_4 test_nvp_text_archive_dll: cw-9_4 test_nvp_text_warchive_dll: cw-9_4 test_nvp_xml_archive_dll: cw-9_4 test_nvp_xml_warchive_dll: cw-9_4 test_object_binary_archive_dll: cw-9_4 test_object_text_archive_dll: cw-9_4 test_object_text_warchive_dll: cw-9_4 test_object_xml_archive_dll: cw-9_4 test_object_xml_warchive_dll: cw-9_4 test_optional_binary_archive_dll: cw-9_4 test_optional_text_archive_dll: cw-9_4 test_optional_text_warchive_dll: cw-9_4 test_optional_xml_archive_dll: cw-9_4 test_optional_xml_warchive_dll: cw-9_4 test_polymorphic_binary_archive_dll: cw-9_4 test_polymorphic_text_archive_dll: cw-9_4 test_polymorphic_text_warchive_dll: cw-9_4 test_polymorphic_xml_archive_dll: cw-9_4 test_polymorphic_xml_warchive_dll: cw-9_4 test_primitive_binary_archive_dll: cw-9_4 test_primitive_text_archive_dll: cw-9_4 test_primitive_text_warchive_dll: cw-9_4 test_primitive_xml_archive_dll: cw-9_4 test_primitive_xml_warchive_dll: cw-9_4 test_private_ctor_dll: cw-9_4 test_recursion_binary_archive_dll: cw-9_4 test_recursion_text_archive_dll: cw-9_4 test_recursion_text_warchive_dll: cw-9_4 test_recursion_xml_archive_dll: cw-9_4 test_recursion_xml_warchive_dll: cw-9_4 test_reset_object_address_dll: cw-9_4 test_set_binary_archive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_set_binary_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_set_text_archive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_set_text_archive_dll: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_set_text_warchive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux test_set_text_warchive_dll: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux test_set_xml_archive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_set_xml_archive_dll: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-gpp test_set_xml_warchive: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux test_set_xml_warchive_dll: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux test_simple_class_binary_archive_dll: cw-9_4 test_simple_class_ptr_binary_archive_dll: cw-9_4 test_simple_class_ptr_text_archive_dll: cw-9_4 test_simple_class_ptr_text_warchive_dll: cw-9_4 test_simple_class_ptr_xml_archive_dll: cw-9_4 test_simple_class_ptr_xml_warchive_dll: cw-9_4 test_simple_class_text_archive_dll: cw-9_4 test_simple_class_text_warchive_dll: cw-9_4 test_simple_class_xml_archive_dll: cw-9_4 test_simple_class_xml_warchive_dll: cw-9_4 test_split_binary_archive_dll: cw-9_4 test_split_text_archive_dll: cw-9_4 test_split_text_warchive_dll: cw-9_4 test_split_xml_archive_dll: cw-9_4 test_split_xml_warchive_dll: cw-9_4 test_tracking_binary_archive_dll: cw-9_4 test_tracking_text_archive_dll: cw-9_4 test_tracking_text_warchive_dll: cw-9_4 test_tracking_xml_archive_dll: cw-9_4 test_tracking_xml_warchive_dll: cw-9_4 test_utf8_codecvt: qcc-3.3.5-gpp test_variant_binary_archive_dll: cw-9_4 test_variant_text_archive_dll: cw-9_4 test_variant_text_warchive_dll: cw-9_4 test_variant_xml_archive_dll: cw-9_4 test_variant_xml_warchive_dll: cw-9_4 test_vector_binary_archive_dll: cw-9_4 test_vector_text_archive_dll: cw-9_4 test_vector_text_warchive_dll: cw-9_4 test_vector_xml_archive_dll: cw-9_4 test_vector_xml_warchive_dll: cw-9_4 test_void_cast_dll: cw-9_4 |optional| optional_test_io: cw-9_4 gcc-2.95.3-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.5-linux gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux intel-win32-8_1 tru64cxx71-006 |spirit| scanner_value_type_tests: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 qcc-3.3.5-cpp tru64cxx71-006 vc-7_1 vc-7_1 scanner_value_type_tests_debug: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 qcc-3.3.5-cpp tru64cxx71-006 vc-7_1 vc-7_1 |pool| test_pool_alloc: qcc-3.3.5-cpp |date_time| testgreg_serialize_dll: cw-9_4 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 |thread| test_mutex_lib: tru64cxx71-006 |config| math_info: borland-5_6_4 |multi_index| test_basic: tru64cxx71-006 test_capacity: tru64cxx71-006 test_comparison: tru64cxx71-006 test_composite_key: tru64cxx71-006 test_conv_iterators: tru64cxx71-006 test_copy_assignment: tru64cxx71-006 test_hash_ops: tru64cxx71-006 test_iterators: tru64cxx71-006 test_list_ops: tru64cxx71-006 test_modifiers: tru64cxx71-006 test_mpl_ops: tru64cxx71-006 test_observers: tru64cxx71-006 test_projection: tru64cxx71-006 test_range: tru64cxx71-006 test_rearrange: tru64cxx71-006 test_safe_mode: cw-9_4 cw-9_5-darwin tru64cxx71-006 test_set_ops: tru64cxx71-006 test_special_list_ops: vc-7_1 test_special_set_ops: tru64cxx71-006 test_update: cw-9_4 cw-9_5-darwin tru64cxx71-006 |ptr_container| incomplete_type_test: cw-9_4 cw-9_5-darwin indirect_fun: cw-9_4 cw-9_5-darwin iterator_test: cw-9_4 cw-9_5-darwin no_exceptions: cw-9_4 cw-9_5-darwin ptr_array: cw-9_4 cw-9_5-darwin ptr_deque: cw-9_4 cw-9_5-darwin ptr_list: cw-9_4 cw-9_5-darwin ptr_map: cw-9_4 cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin qcc-3.3.5-cpp qcc-3.3.5-gpp vc-7_1 vc-7_1 ptr_set: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.5-linux gcc-4.0.2-linux intel-win32-8_1 tru64cxx71-006 ptr_vector: cw-9_4 cw-9_5-darwin serialization: cw-9_4 cw-9_5-darwin gcc-4.0.2-linux tru64cxx71-006 tree_test: cw-9_4 cw-9_5-darwin tut1: cw-9_4 cw-9_5-darwin view_example: cw-9_4 cw-9_5-darwin |typeof| function_ptr_from_tpl_emulation: vc-7_1 vc-7_1 function_ptr_from_tpl_native: vc-7_1 vc-7_1 lvalue_emulation: gcc-4.0.2-linux lvalue_native: gcc-4.0.2-linux type_native: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux intel-9.0-linux qcc-3.3.5-cpp qcc-3.3.5-gpp vc-7_1 vc-7_1 |filesystem| convenience_test: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux fstream_test: gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux large_file_support_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mbcopy: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux mbpath: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux operations_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 operations_test_dll: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux path_test: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux path_test_dll: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux simple_ls: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux wide_test: borland-5_6_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux tru64cxx71-006 |assign| multi_index_container: tru64cxx71-006 ptr_list_inserter: cw-9_4 cw-9_5-darwin ptr_list_of: cw-9_4 cw-9_5-darwin ptr_map_inserter: cw-9_4 cw-9_5-darwin

1 0