- Boost - lists.boost.org

asio formal review
by val salamakha 13 Dec '05

13 Dec '05

Hi everybody, I agree with my colleague - asio is ACE without hurt and really the best C++ network libraries. It has been written in modern C++ and has clear interface to BSD sockets. Documentation is foggy a little because of doxygen, but it is not a problem. I have each release of asio almost from the start of development and see significant improvement. Well done Chris, thanks to the contributors as well. I vote yes, asio must be a part of the boost. Valery Salamakha --------------------------------- Yahoo! Shopping Find Great Deals on Holiday Gifts at Yahoo! Shopping

1 0

Re: [boost] asio formal review begins
by Oliver.Kowalke＠infineon.com 13 Dec '05

13 Dec '05

Hello Christopher, >Hi Oliver, >Multicast support is there - see the example in libs/asio/multicast and >the boost::asio::ipv4::multicast namespace. Sorry - I was searching in the 0.20 version (as I could see 0.3.6 contains multicast). >> SIGPIPE is blocked by the ctor of basic_demuxer - I think it >> would be better to block SIGPIPE only in the functions reading >> from the socket and after that reset to the original signal >> handler. >But that would mean that the SIGPIPE is still delivered to the >application, wouldn't it? That's not very nice since the default >behaviour for SIGPIPE is to terminate the application. I chose to >ignore SIGPIPE globally since most people writing portable applications >would never want to know about it. If you do feel the need to handle >SIGPIPE yourself, just specialise boost::asio::detail::signal_init so >that it isn't ignored. I don't agree. Only if write/sendto is called on a closed socket SIGPIPE should be blocked by your library. In all other cases the user defined signal handler for SIGPIPE should be called. In your solution the user can only ignore SIGPIPE globally (even if the signal is generated from other sources than sockets) or install its own signal handler - and so be forced to distinguish between SIGPIPE from socket and other sources (problem - multiple sockets; which socket has generated the signal?). >> EINTR is not handled in the reading/writing functions? >The blocking functions will return error::interrupted in this case. Wouldn't it be better to call read/write again if EINTR is returned? >> Is it correct, that asio doesn't use AIO System Interfaces from >> the OS (like aiocb, aio_read, aio_write, aio_suspend, ...)? >However these function don't support sockets on Linux yet (AFAIK, it >may just be that they don't support sockets efficiently) Support for kernel AIO has been included in the 2.6 Linux kernel. AIO read and write on sockets doesn't return an explicit error, but quietly defaults to synchronous or rather non-AIO behavior. See http://lse.sourceforge.net/io/aio.html >and for solaris I'm planning to support /dev/poll first. /dev/poll is also supported by Linux. So long, Oliver

3 4

Re: [boost] Problem with building boost_1_33_1 using VC-7_1 - solved.
by Andrew Maclean 13 Dec '05

13 Dec '05

I found the problem. What I had done was to declare BOOST environment variables and these conflicted with the bjam processing of the files. Maybe a note should be added to the user instructions for building Boost in Windows along the line: "If you have any environment variables such as BOOST_INCLUDE, BOOST_LIB, BOOST_ROOT, BOOST_VERSION. Delete or rename them before running bjam." Thanks Andrew -----Original Message----- From: Andrew Maclean [mailto:a.maclean@cas.edu.au] Sent: Tuesday, 6 December 2005 14:47 To: boost-users(a)lists.boost.org Subject: Problem with building boost_1_33_1 using VC-7_1 The command I am running is: ..\bjam "-sTOOLS=vc-7_1" There is a vast amount of output but the key bit looks to be this: Jamfile:278: in load-jamfiles *** argument error * rule stage ( name : sources + : requirements * : local-build * ) * called with: ( : C:\boost\boost_1_33_1\boost\compatibility\cpp_c_headers\cassert ... <Lots and lots of files are listed> ... C:\boost\boost_1_33_1\boost\wave\util\unput_queue_iterator.hpp : <locate>C:\Boost <tree-subdirs>C:\boost\boost_1_33_1 <target>all : <suppress>true ) * missing argument name C:\boost\boost_1_33_1\tools/build/v1\boost-base.jam:2330:see definition of rule 'stage' being called C:\boost\boost_1_33_1\tools\build\v1\bootstrap.jam:21: in boost-build C:\boost\boost_1_33_1\boost-build.jam:16: in module scope The command works fine in boost_1_33_0. I suspect (but may be wrong) that "/" instrad of "\" may be causing the problem. Andrew ___________________________________________ Andrew J. P. Maclean Centre for Autonomous Systems The Rose Street Building J04 The University of Sydney 2006 NSW AUSTRALIA Ph: +61 2 9351 3283 Fax: +61 2 9351 7474 URL: http://www.cas.edu.au/ ___________________________________________

1 0

[asio] asio formal review
by Dave Moore 13 Dec '05

13 Dec '05

I vote to accept asio into Boost. I have previously experimented with earlier releases in the asio 1.3.x series. Using asio, I have built proof-of-concept applications that compile on Linux and Win32 handling udp multicast traffic at peak rates in excess of 100Mbit/s with low CPU utilization and no packet loss, even when compared with an existing hand-coded production implementation. Asio represents a serious effort at cross-platform networking by someone who clearly understands the problem domain. I have been representing it to my colleagues as "ACE without the cruft." I think that asio is a terrific framework that can (and will) be extended by many contributors. The SSL support and iostreams examples are strong evidence asio's extensibility. As a follower of the Boost mailing list for the past 5 years, I think I can say with confidence that asio surpasses any of the earlier false starts at a Boost networking library effort. What follows are nits, none of which are showstoppers for my support of accepting asio into Boost: For the deadline_time, I am unsure as to whether functions like "expires_from_now" benefit from their default coupling to boost::datetime. Most timer operations in high performance I/O tend to be relative, which is easily expressed without a clock binding… It does help that asio only depends upon the headers of datetime. Documentation: The annotated examples and the tutorial are the strength of the documentation, and are enough for people familiar with the problem domain to get their footing. The Doxygen docs are a bit hard to navigate. I would prefer hand-written documentation of the common public classes and concepts like buffer, deadline_timer, datagram_socket, etc. Doxygen docs are useful for completeness, but is seems to me like many of the classes in Boost::asio are of interest only to those looking to extend the framework. The documentation could be split into sections for users looking for basic async sockets, and users wanting to write their own services or demuxers. Installation of the Boost preview package: There weren't obvious instructions on how to overlay the asio boost evaluation package into an existing boost source tree. It seems like the installation/compilation docs apply to the standalone asio distribution, not the Boost evaluation package. I chose to unpack the asio Boost proposal package into my Boost 1.33.1source tree. The build instructions in the documentation didn't work for that case. Rather, I had to go around to the individual examples in libs\asio\example and run bjam from there. David Moore

3 4

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