- Boost - lists.boost.org

asio formal review
by dirk 13 Dec '05

13 Dec '05

I vote YES! It's the best C++ network library available today (ACE without the 'hurt' - I must agree there :-) ) Not only it just works, but it is also very extensible: - multicast was added in march/april (thanks Chris!) - ssl was added (and donated back) in august/september (thanks Indrek!) Both additions went very wel. I've used ASIO in 2 production running projects this year: multicast & finance and a voip app where ASIO handles (secure) Jabber and a high volume proxy-server. The examples are good: copy them and you're off. Documenation is a little cryptic - but maybe that's doxygen for you :) I don't know if this is the formal review expected, no network lib comes close - I feel it fits very well into Boost. Dirk

1 0

ptr_container issue/question regarding polymorphic types
by Michael Goldshteyn 12 Dec '05

12 Dec '05

It is my understanding that ptr_containers allow and support pointers to polymorphic types. But, the following does not appear to be possible: class Animal { }; class Cow: public Animal { }; ptr_vector<Cow> cows; ptr_vector<Animal> animals; ... // Add in some cows to the cows container ... // Transfer all cows to the animal container // Error: transfer() is not a class member function template // it expects the "from" container to be of the same types of pointers animals.transfer(animals.end(),cows.begin(),cows.end(),cows); Thanks, Mike

2 1

boost md5 implementation?
by Nigel Stewart 12 Dec '05

12 Dec '05

Greetings boost-land, We've been looking around for an implementation of the MD5 (http://en.wikipedia.org/wiki/MD5) hash algorithm and came across a boost-oriented implementation by Stanislav Baranov: http://www.garret.ru/~baranov/boost_md5/lib/md5/md5.html Does anyone know if this was ever formally reviewed for inclusion in boost, or if there are other proposals or plans for message digest algorithms as part of boost? Thanks in advance, Nigel Stewart

9 11

[Boost-bugs] [ boost-Bugs-1378907 ] g++ v3.2.3 inker error for read_graphviz ih boost v1.33.1
by SourceForge.net 12 Dec '05

12 Dec '05

Bugs item #1378907, was opened at 2005-12-12 10:07 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=1378907&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: g++ v3.2.3 inker error for read_graphviz ih boost v1.33.1 Initial Comment: There's a link error when trying to compile the graphviz.cpp example file. Submitters email address is "marioaranha(a)yahoo.com". Details below: cd .../boost_1_33_1/libs/graph/example g++ -I../../.. graphviz.cpp -L../../../libs/graph/src -lbgl-viz /tmp/ccu7dj8Y.o(.gnu.linkonce.t._ZN5boost13read_graphvizINS_14adjacency_listINS_4vecSES2_NS_11undirectedSENS_8propertyINS_13vertex_name_tESsNS_11no_propertyEEENS4_INS_13edge_weight_tEdS6_EES6_NS_5listSEEEEEbRSiRT_RNS_18dynamic_propertiesERKSs+0x6e): In function `bool boost::read_graphviz<boost::adjacency_list<boost::vecS, boost::vecS, boost::undirectedS, boost::property<boost::vertex_name_t, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::no_property>, boost::property<boost::edge_weight_t, double, boost::no_property>, boost::no_property, boost::listS> >(std::basic_istream<char, std::char_traints<char> >&, boost::adjacency_list<boost::vecS, boost::vecS, boost::undirectedS, boost::property<boost::vertex_name_t, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::no_property>, boost::property<boost::edge_weight_t, double, boost::no_property>, boost::no_property, boost::listS>&, boost::dynamic_properties&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)': : undefined reference to `boost::detail::graph::read_graphviz(std::basic_istream<char, std::char_traints<char> >&, boost::detail::graph::mutate_graph&)' collect2: ld returned 1 exit status ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1378907&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

Re: [boost] [asio] my review
by Martin Bonner 12 Dec '05

12 Dec '05

----Original Message---- From: Giovanni P. Deretta [mailto:gpderetta@gmail.com] Sent: 12 December 2005 16:00 To: boost(a)lists.boost.org Subject: Re: [boost] [asio] my review >> I'm against introduzing exceptions. But I agree it may be possible to >> work a little more in the error handling. But, IMO, it should be like >> adding helper classes for this, but not throwing exceptions. >> > > I think too that the current asio error handling interface is fine, > and it is not worth changing it a this time. Has anybody got a "non-ignorable return" class that they could add to boost? (A class that encapsulates a return value whose destructor asserts/aborts if the return code has not been examined or deliberatedly ignored by the calling code.) It would be a natural for this sort of application, and would be a generally useful utility class. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 2

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

12 Dec '05

Boost regression test failures ------------------------------ Report time: 2005-12-12T15:30:24Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 352 failures in 19 libraries: bind (1) concept_check (19) config (1) date_time (20) foreach (1) graph (5) io (1) mpl (1) multi_array (1) parameter (1) python (2) regex (15) serialization (21) smart_ptr (2) spirit (2) tr1 (181) typeof (31) wave (2) xpressive (45) |bind| bind_dm3_test: msvc |concept_check| stl_concept_covering: cw-9_4 cw-9_4 cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin gcc-4_0-darwin intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 |config| math_info: cw-9_5-darwin |date_time| testc_local_adjustor: msvc testclock: msvc testdst_rules: msvc testfiletime_functions: msvc testgreg_duration_operators: msvc testgreg_serialize_dll: cw-9_4 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 vc-7_1 testiterator: msvc testlocal_adjustor: msvc testmicrosec_time_clock: msvc testparse_time: msvc testtime: msvc testtime_formatters: msvc testtime_period: msvc testwcustom_time_zone: msvc testwposix_time_zone: msvc |foreach| rvalue_const: intel-win32-9_0 |graph| dominator_tree_test: intel-win32-9_0 graphviz_test: vc-7_1 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 |multi_array| index_bases: cw-9_4 |parameter| sfinae: msvc |python| pickle4: mingw-3_4_2 stl_iterator: msvc |regex| concept_check: 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 mingw-3_4_2 vc-7_1 vc-7_1 regex_regress: cw-9_4 intel-win32-8_1 vc-7_1 regex_regress_dll: cw-9_4 intel-win32-8_1 vc-7_1 |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-4_0-darwin test_class_info_load_text_archive: gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-4_0-darwin test_class_info_load_text_warchive: gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-4_0-darwin test_class_info_load_xml_archive: cw-9_5-darwin gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_demo_xml_load: intel-win32-8_1 test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |smart_ptr| pointer_to_other_test: msvc shared_ptr_alloc2_test: msvc |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos gcc-4_0-darwin std_run_complex_overloads: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos gcc-4_0-darwin std_run_random: cw-9_4 cw-9_5-darwin std_test_array: cw-9_4 cw-9_5-darwin std_test_bind: cw-9_4 cw-9_5-darwin gcc-4_0-darwin std_test_complex: cw-9_4 cw-9_5-darwin std_test_function: cw-9_4 cw-9_5-darwin std_test_hash: cw-9_4 cw-9_5-darwin std_test_mem_fn: cw-9_4 cw-9_5-darwin std_test_random: cw-9_4 cw-9_5-darwin std_test_regex: cw-9_4 cw-9_5-darwin std_test_result_of: cw-9_4 cw-9_5-darwin std_test_tr1_include: cw-9_4 cw-9_5-darwin std_test_tuple: cw-9_4 cw-9_5-darwin std_test_type_traits: cw-9_4 cw-9_5-darwin test_array: cw-9_4 test_bind: cw-9_4 cw-9_5-darwin gcc-4_0-darwin test_complex: cw-9_4 cw-9_5-darwin test_function: cw-9_4 cw-9_5-darwin test_hash: cw-9_4 cw-9_5-darwin test_mem_fn: cw-9_4 cw-9_5-darwin test_random: cw-9_4 cw-9_5-darwin test_reference_wrapper: cw-9_4 cw-9_5-darwin test_result_of: cw-9_4 cw-9_5-darwin test_shared_ptr: cw-9_4 cw-9_5-darwin test_tr1_include: cw-9_4 cw-9_5-darwin test_tuple: cw-9_4 cw-9_5-darwin tr1_add_const_test: cw-9_4 cw-9_5-darwin tr1_add_cv_test: cw-9_4 cw-9_5-darwin tr1_add_pointer_test: cw-9_4 cw-9_5-darwin tr1_add_reference_test: cw-9_4 cw-9_5-darwin tr1_add_volatile_test: cw-9_4 cw-9_5-darwin tr1_aligned_storage_test: cw-9_4 cw-9_5-darwin tr1_alignment_of_test: cw-9_4 cw-9_5-darwin tr1_extent_test: cw-9_4 cw-9_5-darwin tr1_has_nothrow_assign_test: cw-9_4 cw-9_5-darwin tr1_has_nothrow_constr_test: cw-9_4 cw-9_5-darwin tr1_has_nothrow_copy_test: cw-9_4 cw-9_5-darwin tr1_has_tr1_ref_wrap_fail: cw-9_4 cw-9_5-darwin tr1_has_tr1_shared_ptr_fail: cw-9_4 cw-9_5-darwin tr1_has_tr1_tuple_fail: cw-9_4 cw-9_5-darwin tr1_has_trivial_assign_test: cw-9_4 cw-9_5-darwin tr1_has_trivial_constr_test: cw-9_4 cw-9_5-darwin tr1_has_trivial_copy_test: cw-9_4 cw-9_5-darwin tr1_has_trivial_destructor_test: cw-9_4 cw-9_5-darwin tr1_has_virtual_destructor_test: cw-9_4 cw-9_5-darwin tr1_is_arithmetic_test: cw-9_4 cw-9_5-darwin tr1_is_array_test: cw-9_4 cw-9_5-darwin tr1_is_base_of_test: cw-9_4 cw-9_5-darwin tr1_is_class_test: cw-9_4 cw-9_5-darwin tr1_is_compound_test: cw-9_4 cw-9_5-darwin tr1_is_const_test: cw-9_4 cw-9_5-darwin tr1_is_convertible_test: cw-9_4 cw-9_5-darwin tr1_is_empty_test: cw-9_4 cw-9_5-darwin tr1_is_enum_test: cw-9_4 cw-9_5-darwin tr1_is_floating_point_test: cw-9_4 cw-9_5-darwin tr1_is_function_test: cw-9_4 cw-9_5-darwin tr1_is_fundamental_test: cw-9_4 cw-9_5-darwin tr1_is_integral_test: cw-9_4 cw-9_5-darwin tr1_is_member_func_test: cw-9_4 cw-9_5-darwin tr1_is_member_obj_test: cw-9_4 cw-9_5-darwin tr1_is_member_pointer_test: cw-9_4 cw-9_5-darwin tr1_is_object_test: cw-9_4 cw-9_5-darwin tr1_is_pod_test: cw-9_4 cw-9_5-darwin tr1_is_pointer_test: cw-9_4 cw-9_5-darwin tr1_is_polymorphic_test: cw-9_4 cw-9_5-darwin tr1_is_reference_test: cw-9_4 cw-9_5-darwin tr1_is_same_test: cw-9_4 cw-9_5-darwin tr1_is_scalar_test: cw-9_4 cw-9_5-darwin tr1_is_signed_test: cw-9_4 cw-9_5-darwin tr1_is_union_test: cw-9_4 cw-9_5-darwin tr1_is_unsigned_test: cw-9_4 cw-9_5-darwin tr1_is_void_test: cw-9_4 cw-9_5-darwin tr1_is_volatile_test: cw-9_4 cw-9_5-darwin tr1_rank_test: cw-9_4 cw-9_5-darwin tr1_remove_all_extents_test: cw-9_4 cw-9_5-darwin tr1_remove_const_test: cw-9_4 cw-9_5-darwin tr1_remove_cv_test: cw-9_4 cw-9_5-darwin tr1_remove_extent_test: cw-9_4 cw-9_5-darwin tr1_remove_pointer_test: cw-9_4 cw-9_5-darwin tr1_remove_reference_test: cw-9_4 cw-9_5-darwin tr1_remove_volatile_test: cw-9_4 cw-9_5-darwin tr1_tricky_abstract_type_test: cw-9_4 cw-9_5-darwin tr1_tricky_add_pointer_test: cw-9_4 cw-9_5-darwin tr1_tricky_function_type_test: cw-9_4 cw-9_5-darwin tr1_tricky_incomplete_type_test: cw-9_4 cw-9_5-darwin tr1_tricky_is_enum_test: cw-9_4 cw-9_5-darwin tr1_tricky_partial_spec_test: cw-9_4 cw-9_5-darwin |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_from_tpl_emulation: vc-7_1 vc-7_1 vc-7_1 function_ptr_from_tpl_native: vc-7_1 vc-7_1 vc-7_1 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc 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 cw-9_4 cw-9_5-darwin std_native: cw-9_4 cw-9_4 cw-9_5-darwin 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 msvc template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave_dll: cw-9_4 cw-9_5-darwin |xpressive| misc1: cw-9_4 cw-9_5-darwin test1: cw-9_4 cw-9_5-darwin test1u: cw-9_4 cw-9_5-darwin test2: cw-9_4 cw-9_5-darwin test2u: cw-9_4 cw-9_5-darwin test3: cw-9_4 cw-9_5-darwin test3u: cw-9_4 cw-9_5-darwin test4: cw-9_4 cw-9_5-darwin test4u: cw-9_4 cw-9_5-darwin test5: cw-9_4 cw-9_5-darwin test5u: cw-9_4 cw-9_5-darwin test6: cw-9_4 cw-9_5-darwin test6u: cw-9_4 cw-9_5-darwin test7: cw-9_4 cw-9_5-darwin test7u: cw-9_4 cw-9_5-darwin test8: cw-9_4 cw-9_5-darwin test8u: cw-9_4 cw-9_5-darwin test9: cw-9_4 cw-9_5-darwin test9u: cw-9_4 cw-9_5-darwin test_cycles: cw-9_4 cw-9_5-darwin test_dynamic: cw-9_4 cw-9_5-darwin test_non_char: cw-9_4 cw-9_5-darwin test_static: cw-9_4

1 0

Important: RC_1_33_0 -> HEAD merge
by Doug Gregor 12 Dec '05

12 Dec '05

Now that 1.33.1 is out and the RC_1_33_0 branch is most likely closed for good, I've merged many of the changes from the RC_1_33_0 branch back to HEAD so that we don't lose all of the minor tweaks we made at the end. For many changes, the merge was so trivial that I've just committed the results. However, some libraries seemed to get quite out-of-sync. This happens when changes were made on both HEAD and RC_1_33_0, and CVS can't figure out how to merge those changes. These libraries are: Date-Time Iostreams Parameter Pointer containers Range Regex Serialization uBLAS The authors of these libraries should look at the merged results to determine what changes need to be made in HEAD. Otherwise, fixes that we have done for 1.33.1 will be forgotten and lost. To do so, have a clean checkout of CVS HEAD available and run something like this: cvs -z6 update -j Version_1_33_0 -j Version_1_33_1 boost/iostreams libs/iostreams (You may want to redirect the output of that command to a file; there's a lot of information in there) Look for "conflicts" in the output to see went wrong, then dig through conflicting files looking for sections between <<<<< and ==== (HEAD code) and ===== and >>>>> (RC_1_33_0 code). Once you've cleaned up everything, commit back to head and you'll be done. Doug

8 7

[BGL] auto index property maps in the boost vault
by Aaron Windsor 12 Dec '05

12 Dec '05

Hi all, I've put some files in the boost vault under algorithms/graph in a package I'm calling "auto index property maps." I developed these in response to a thread on boost-users a few months back (http://tinyurl.com/bezjr) and a steady stream of questions on this mailing list and boost-users about how to use/create vertex and edge index maps when they aren't provided for you. Vertex index maps are property maps that map the vertices of a graph bijectively into the range [0..num_vertices(g)). Edge index maps map edges bijectively into [0..num_edges(g)). Many BGL algorithms require a vertex or edge index map, and one can be supplied either in the form of an interior property or an external property map. Auto index property maps are external property maps that were created with ease of use in mind. In short, whenever a vertex index map is expected for the graph g, you can substitute the expression "make_auto_vertex_index(g)" and everything will work as expected. Similarly, if an edge index property map is expected, you can use the expression "make_auto_edge_index(g)" instead. It's my hope that the auto index property maps will provide a quick solution to those looking to get started with the BGL who aren't yet worried about delving into the details of working with internal properties, which seems to be a difficult issue for a lot of beginners. Auto index property maps can be used while prototyping and replaced later with interior properties if efficiency is an issue. Any feedback would be most appreciated. I've tested everything with gcc 3.4.4 on cygwin. Aaron

3 5

[Wave] Wrong phase for trigraphs? Generator interface?
by Daryle Walker 12 Dec '05

12 Dec '05

[Sorry if this has already been reported, fixed, and/or superceded.] Looking at <http://www.boost.org/libs/wave/doc/token_ids.html>, I see various kinds of tokens. There are tokens for the preprocessor that are seen by the lexer and don't make it to the preprocessing iterator level. The other sets of tokens do make it to that level, modulo any transformations. The trigraphs are put in the operator token list. However, trigraphs should not be there. They are processed before anything else, even before the preprocessor tokens. So there should be another level of lexer working here. As is, it doesn't seem that you could use the trigraph for "#", "??=", for preprocessor directives. ??=include <cstdio> // this should work On a related note, I thought maybe Wave should use a generator interface: template < typename Iterator, typename FileID > class phase1 { public: phase1( Iterator b, Iterator e, FileID id ); operator bool() const; // TRUE while not done cpp_p1_char_type operator ()(); }; template < typename Iterator, typename FileID > class phase2 { public: explicit phase2( phase1<Iterator, FileID> const &p ); operator bool() const; // TRUE while not done cpp_p2_line_string_type operator ()(); }; //... You generally can't rewind, of course. The cpp_p1_char_type would contain the expanded character's identity AND some indicator of its location (starting iterator, file ID, and line, row, and un-lined offset numbers). The cpp_p2_line_string_type would carry the locations for each character in its string. Then the tokens of later phases would know the location of their first characters. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

3 2

BOOST_HAS_NRVO not being set for VC++ 8.0
by Beman Dawes 12 Dec '05

12 Dec '05

According to http://msdn.microsoft.com/visualc/default.aspx?pull=/library/en-us/dnvs05/h…, VC++ 8.0 now support NRVO. Config info isn't reporting BOOST_HAS_NRVO as being set. Should this be changed? --Beman

5 6