- Boost - lists.boost.org

asio forcing the use of handlers?
by Roland Schwarz 11 Sep '07

11 Sep '07

I am just about to find out how I could make use of the asio library, and am wondering if async io also can be done without using handler functions. I recognize that it is possible to use it in a blocked manner as follows: assuming we have an open socket: sock read(sock, buf); ... use the buffer contents ... Now I am wondering if I could also accomplish something like: cp = async_read(sock, buf); ... do something useful ... cp.wait(); .. use the buffer contents ... Thank you, Roland aka speedsnail

2 4

Release procedure. Where do we go?
by Roland Schwarz 11 Sep '07

11 Sep '07

Hopefully I am not seen as trying to add fuel to the fire, but I am wondering if anyone tried to perform an analysis of what exactly did not work with the (previous) release procedure. I have seen David Abrahams trying to analyze the current tools, but I have not seen an analysis of the procedure and why it fails. (But I might have missed it in the long thread.) So I dare to ask the question again: What is wrong on 1) working on trunk, the bleeding edge 2) branching out for release when the trunk is release-stable 2.1) feature freeze and stabilizing, merging relevant parts to trunk 3) releasing from release candidate branch, i.e. tagging the branch 3.1) bugfixing on branch, merging to trunk, tagging the branch Is it this procedure that is broken, or is it the tools that are insufficient to support this procedure? In this scenario there is also always a release-ready branch insofar as a branch, once released still is release-ready (e.g. for fixing). And there is nothing that can potentially destabilize a branch that has already been forked out. There is also no requirement that a release branch ever dies. Bug fixes still can go there after it has been tagged. I also see nothing wrong with multiple release candidate branches at the same time. A release branch simply is another name for a certain set of features that are covered. No resources to test everything? Only a reported failure indicates something being wrong, that needs to be fixed. So I think it only fair to ask the reporter to help with testing by providing access to her environment and spend the necessary processor cycles to fix the problem. (Of course we would need the tools that would allow us this kind of on demand remote testing.) (This kind of support is also where developers could earn money if they like.) A potential user just browses through the testing pages and selects the most up to date release that covers the required features. (With the option for bug-fixing if something does not work for his environment.) Of course in this scenario the release manager would have less work to do :-D . Just watching out when a agreed feature set is in the trunk, and branch when there. (Of course developers always try to hold trunk as stable as possible ;-) ) Another potential benefit of this model is that developers already are used to it. So my bottom point is to generalize the current model to what I have said above and concentrate to get better tools that support this. AFAIK this is also the model other big monolithic projects are using. Departing from it would require modularization of the boost library, which at the current state does not look like an easy task to me. A small example: I was trying to single out the asio lib, and discovered that it had quite some implicit (undocumented) dependencies on other header-only/prebuilt libs. Only when I tried to use auto_link on an msvc platform with BOOST_LIB_DIAGNOSTIC turned on I eventually figured out that I also had to provide boost_system boost_date_time and boost_regex to the linker while compiling with gcc. So the recipe I once heard on this list: just take the relevant files and copy to your directory if you don't need all of boost, is hoping at best. Roland aka speedsnail

5 8

Re: [boost] How to download Functional module of Fusion 2 ???
by dan marsden 11 Sep '07

11 Sep '07

Joel de Guzman wrote: >dan marsden wrote: >> Fusion is not in Boost 1.34.x as it was reviewed too late for that release. >> It will in incorporated in 1.35. As it's not yet officially in a boost release >> that may explain the difficulty finding it you had above. Hopefully we'll get more >> user friendly after that. > >Spirit has its own release cycle. Perhaps we ought to release Fusion 2.0 >in spirit.sf.net. I think that would be a good idea. 1.35 could be a while yet, and we'd benefit from user feedback in the meantime. I've got a few documentation mods I should do first, can we wait a week or so until I've tidied those up? Cheers Dan ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/

2 1

a question about message_queue
by nuaafantasy nuaafantasy 11 Sep '07

11 Sep '07

Dear All: My project use messge_queue to communicate between two processes. When I used the processes as normal process,it runs well. but It seems that the client process can't access the message queue if I set the server process as a windows services. can you help me about this? is this a problem about privilege? but message_queue do not have a option to set privileges. looking forward to your help!

1 0

[property_tree] - segmentation fault from spirit xml parser -> threading issue
by Oliver.Kowalke＠qimonda.com 11 Sep '07

11 Sep '07

Hello, I got an segmentation fault if I create mutliple threads and each thread class a free function f() which creates an ptree from a xml stream. Because each thread calls f() it should create its own ptree xml parser - but why does the seg fault happen? Regards, Oliver Code: #include <iostream> #include <cstdlib> #include <string> #include <sstream> #include <boost/bind.hpp> #include <boost/property_tree/ptree.hpp> #include <boost/property_tree/xml_parser.hpp> #include <boost/shared_ptr.hpp> #include <boost/thread.hpp> #include <boost/thread/barrier.hpp> namespace ptr = boost::property_tree; void f() { try { std::string value = "<?xml version=\"1.0\" encoding=\"utf-8\"?>\ <fibonnaci>\ <in>\ <number>10</number>\ <delay>1</delay>\ </in>\ </fibonnaci>"; std::stringstream as_xml( value); // printf("in data == %s\n", as_xml.str().c_str() ); ptr::ptree p; ptr::read_xml( as_xml, p); } catch ( std::exception const& e) { std::cerr << e.what() << std::endl; } catch ( ... ) { std::cerr << "unhandled" << std::endl; } } struct X { boost::barrier & b_; X( boost::barrier & b) : b_( b) {} void operator()() { b_.wait(); f(); } }; int main(int argc, char *argv[]) { try { boost::barrier b( 10); boost::thread_group tg; X x( b); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.create_thread( boost::bind( & X::operator(), x) ); tg.join_all(); } catch ( std::exception const& e) { std::cerr << e.what() << std::endl; } catch ( ... ) { std::cerr << "unhandled" << std::endl; } } DGB: Program terminated with signal 11, Segmentation fault. #0 0x0804e9dc in std::mem_fun1_t<int, boost::spirit::impl::grammar_helper_base<boost::spirit::grammar<boost::p roperty_tree::xml_parser::xml_grammar<boost::property_tree::basic_ptree< boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >, boost::spirit::grammar<boost::property_tree::xml_parser::xml_grammar<boo st::property_tree::basic_ptree<boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> >*>::operator() (this=0xb554300c, __p=0x809aad8, __x=0xb5543134) at /opt/gcc-4.0.3/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0. 3/bits/stl_function.h:664 664 { return (__p->*_M_f)(__x); } (gdb) bt #0 0x0804e9dc in std::mem_fun1_t<int, boost::spirit::impl::grammar_helper_base<boost::spirit::grammar<boost::p roperty_tree::xml_parser::xml_grammar<boost::property_tree::basic_ptree< boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >, boost::spirit::grammar<boost::property_tree::xml_parser::xml_grammar<boo st::property_tree::basic_ptree<boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> >*>::operator() (this=0xb554300c, __p=0x809aad8, __x=0xb5543134) at /opt/gcc-4.0.3/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0. 3/bits/stl_function.h:664 #1 0x0804ea2a in std::binder2nd<std::mem_fun1_t<int, boost::spirit::impl::grammar_helper_base<boost::spirit::grammar<boost::p roperty_tree::xml_parser::xml_grammar<boost::property_tree::basic_ptree< boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >, boost::spirit::grammar<boost::property_tree::xml_parser::xml_grammar<boo st::property_tree::basic_ptree<boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> >*> >::operator() (this=0xb554300c, __x=@0x809bc80) at /opt/gcc-4.0.3/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0. 3/bits/stl_function.h:446 #2 0x0804f57a in std::for_each<std::reverse_iterator<__gnu_cxx::__normal_iterator<boost:: spirit::impl::grammar_helper_base<boost::spirit::grammar<boost::property _tree::xml_parser::xml_grammar<boost::property_tree::basic_ptree<boost:: property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >**, std::vector<boost::spirit::impl::grammar_helper_base<boost::spirit::gram mar<boost::property_tree::xml_parser::xml_grammar<boost::property_tree:: basic_ptree<boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >*, std::allocator<boost::spirit::impl::grammar_helper_base<boost::spirit::g rammar<boost::property_tree::xml_parser::xml_grammar<boost::property_tre e::basic_ptree<boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >*> > > >, std::binder2nd<std::mem_fun1_t<int, boost::spirit::impl::grammar_helper_base<boost::spirit::grammar<boost::p roperty_tree::xml_parser::xml_grammar<boost::property_tree::basic_ptree< boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >, boost::spirit::grammar<boost::property_tree::xml_parser::xml_grammar<boo st::property_tree::basic_ptree<boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> >*> > > (__first=@0xb5543088, __last=@0xb5543084, __f= {<std::unary_function<boost::spirit::impl::grammar_helper_base<boost::sp irit::grammar<boost::property_tree::xml_parser::xml_grammar<boost::prope rty_tree::basic_ptree<boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >*,int>> = {<No data fields>}, op = {<std::binary_function<boost::spirit::impl::grammar_helper_base<boost::s pirit::grammar<boost::property_tree::xml_parser::xml_grammar<boost::prop erty_tree::basic_ptree<boost::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > >*,boost::spirit::grammar<boost::property_tree::xml_parser::xml_grammar< boost::property_tree::basic_ptree<boost::property_tree::ptree_traits<cha r> > >, boost::spirit::parser_context<boost::spirit::nil_t> >*,int>> = {<No data fields>}, _M_f = {__pfn = 0x1, __delta = 0}}, value = 0xb5543134}) at /opt/gcc-4.0.3/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0. 3/bits/stl_algo.h:158 #3 0x0804f68f in boost::spirit::impl::grammar_destruct<boost::spirit::grammar<boost::prop erty_tree::xml_parser::xml_grammar<boost::property_tree::basic_ptree<boo st::property_tree::ptree_traits<char> > >, boost::spirit::parser_context<boost::spirit::nil_t> > > ( self=0xb5543134) at /opt/boost/include/boost-1_34/boost/spirit/core/non_terminal/impl/gramma r.ipp:307 #4 0x080613de in ~grammar (this=0xb5543134) at /opt/boost/include/boost-1_34/boost/spirit/core/non_terminal/grammar.hpp :50 #5 0x0806148b in ~xml_grammar (this=0xb5543134) at /opt/boost/include/boost-1_34/boost/property_tree/detail/xml_parser_read _spirit.hpp:132 #6 0x0806cc59 in boost::property_tree::xml_parser::read_xml_internal<boost::property_tree ::basic_ptree<boost::property_tree::ptree_traits<char> > > (stream=@0xb5543274, pt=@0xb5543330, flags=0, filename=@0xb5543240) at /opt/boost/include/boost-1_34/boost/property_tree/detail/xml_parser_read _spirit.hpp:724 #7 0x0806cd9e in boost::property_tree::xml_parser::read_xml<boost::property_tree::basic_p tree<boost::property_tree::ptree_traits<char> > > (stream=@0xb5543274, pt=@0xb5543330, flags=0) at /opt/boost/include/boost-1_34/boost/property_tree/xml_parser.hpp:38 #8 0x0804ae6e in f () at /home/kowalke/Projects/test_ptree/src/test_ptree.cpp:29 #9 0x0806cde8 in X::operator() (this=0xb5543448) at /home/kowalke/Projects/test_ptree/src/test_ptree.cpp:48 #10 0x0804f79e in boost::_mfi::mf0<void, X>::operator() (this=0xb5543440, t=@0xb5543448) at /opt/boost/include/boost-1_34/boost/bind/mem_fn_template.hpp:68 #11 0x0805179e in boost::_bi::list1<boost::_bi::value<X> >::operator()<boost::_mfi::mf0<void, X>, boost::_bi::list0> (this=0xb5543448, f=@0xb5543440, a=@0xb55433b6) at /opt/boost/include/boost-1_34/boost/bind.hpp:231 #12 0x080517e1 in boost::_bi::bind_t<void, boost::_mfi::mf0<void, X>, boost::_bi::list1<boost::_bi::value<X> > >::operator() ( this=0xb5543440) at /opt/boost/include/boost-1_34/boost/bind/bind_template.hpp:20 #13 0x080517fb in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<v oid, boost::_mfi::mf0<void, X>, boost::_bi::list1<boost::_bi::value<X> > >, void>::invoke (function_obj_ptr=@0xb5543440) at /opt/boost/include/boost-1_34/boost/function/function_template.hpp:155 #14 0xb7fad10c in boost::function0<void, std::allocator<boost::function_base> >::operator() () from /opt/boost/lib/libboost_thread-gcc40-mt-1_34.so.1.34.0 #15 0xb7fad061 in boost::thread_group::create_thread () from /opt/boost/lib/libboost_thread-gcc40-mt-1_34.so.1.34.0 #16 0xb7d4f240 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #17 0xb7e313de in clone () from /lib/tls/i686/cmov/libc.so.6

1 0

Trac open bugs - by assignee
by Marshall Clow 10 Sep '07

10 Sep '07

[ 201 open bugs today, 204 on Friday ] If you are maintaining a library, and have not logged into the trac system at <http://svn.boost.org/trac/boost/>, please do so ASAP. Until you do that, no tickets can be assigned to you, and will remain under "None". Instructions on working with tickets can be found at: <http://svn.boost.org/trac/boost/wiki/TicketWorkflow> and a mapping of user names to "real names" can be found at: <http://svn.boost.org/trac/boost/report/16> Bug summary 16 doug_gregor 15 grafik 14 ramey 13 dgregor 12 az_sw_dude 10 rogeeff 10 None 9 djowel 8 dave 7 turkanis 7 jsiek 6 nesotto 6 agurtovoy 5 anthonyw 4 witt 4 vladimir_prus 4 shammah 4 samuel_krempp 4 pdimov 4 johnmaddock 4 <Blank> 3 jbandela 3 igaztanaga 3 fcacciola 3 danielw 3 bemandawes 2 urzuga 2 nasonov 2 jmaurer 2 hubert_holin 2 hkaiser 2 ebf 1 t_schwinger 1 speedsnail 1 samuel_k 1 pavol_droba 1 mistevens 1 dlwalker 1 aaron_windsor <Blank> 1033 iostreams::restrict doesn't work on an iostreams::file_source <Blank> 1070 [iostreams]boost\iostreams\copy.hpp line80 copy_impl <Blank> 823 Seekable file_descriptor_source /sink? <Blank> 824 BOOST_IOSTREAMS_HAS_LSEEK64 on Mac OS X None 1068 Mersenne twister disables streaming for Visual C++ None 1094 Finding the correct library to link (feature request for pkg-config support)h None 1184 property_tree assignment (operator) bug None 1187 bcp copy not needed files None 1222 lambda::ret<T> should declare result_type. None 1230 mbstate uninitialized None 1234 unbounded_array copy constructor does not compile with intel v 9.1 None 1237 Resizing symmetric matrices None 960 [random] lognormal_distribution problem None 991 [pool] aaron_windsor 778 top-level configure is broken agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 588 mpl::remove compile error with gcc 4.1.0 agurtovoy 640 documentation mistake anthonyw 1154 tss destruction segfaults in conjunction with dlopen/dlclose anthonyw 1168 [thread] tss crashes randomly anthonyw 1226 macro TEXT() in GetProcAddress() anthonyw 876 xtime documentation incomplete anthonyw 881 errors when build with Apache stdcxx az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1147 date_time library contains global #define ERROR az_sw_dude 1160 warning: month_format shadows a member of this az_sw_dude 1162 warning: ticks shadows a member of this az_sw_dude 287 wrong usage of ios_base::narrow az_sw_dude 316 date_time type conversion warning az_sw_dude 604 from_ftime incorrectly processes FILETIME filled with zeros az_sw_dude 642 operator<< for gregorian::date_duration not found az_sw_dude 889 Insane Dependencies az_sw_dude 890 date_time library supports only the current dst rule bemandawes 559 linker error mingw 3.4.5 bemandawes 752 directory_iterator doesn't work with catch bemandawes 897 exists() throws exeption on existing but locked file on wind danielw 1044 Argument pack inaccessable in a functions return type danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored dave 1010 linking boost.python on freebsd dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1085 Python rules for compiling in Mac OS X dave 1096 Tutorial needs updating for BBv2 dave 1179 [boost.python] can not export a union in VC2005sp1 dave 1181 [boost.python] can modify enum value dave 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python dgregor 1002 [iostreams] close_impl<closable_tag> does not comply with spec dgregor 1003 [iostreams] copy-paste error in typedefs for wchar multichar_filters dgregor 1011 amd64: #error Boost.Numeric.Interval: Please specify rounding control mechanism. dgregor 1139 [iostreams] Regex filter segfaults when zero matches found dgregor 1140 boost::iostreams linked_streambuf bug dgregor 1149 Minor doc error in basic_null_device dgregor 1164 Floyd Warshall broken with unsigned edge weights dgregor 1185 iostreams::direct_streambuf<T_Tr>::is_open always returns false if output iterator is not null dgregor 1192 [boostbook] problem when two files have the same name dgregor 1199 configure doesn't work with path containing whitespaces (MacOS X) dgregor 1218 Boostbook error when generating documentation for a member typedef with a description dgregor 1232 mapped_file_source::is_open() is broken under windows dgregor 556 Bundled graph properties djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1235 Admonitions produce invalid nested <para> in DocBook XML djowel 241 Miss " = ParserT()" djowel 314 spirit insert_key_actor.hpp djowel 664 crash in boost::spirit::parse dlwalker 613 boost/crc.hpp uses non-standard conforming syntax doug_gregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph doug_gregor 1067 Function needs to use pass-by-reference internally doug_gregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 doug_gregor 375 LEDA graph adaptors do not handle hidden nodes properly doug_gregor 402 random_vertex/random_edge are unnecessarily inefficient doug_gregor 403 Document copy_component doug_gregor 447 reverse_graph and constness of property maps doug_gregor 708 Dijkstra no_init version should not require VertexListGraph doug_gregor 732 Johnson All-Pairs needs better "no path" information doug_gregor 733 Numbered headers don't work with "preferred" syntax doug_gregor 735 Fruchterman-Reingold grid performance can be improved doug_gregor 736 Const correctness violation doug_gregor 738 Memory leaks with signal::connect? doug_gregor 829 Implicit graph not implement doug_gregor 852 Problem with Boost and GCC 4.1 doug_gregor 891 Bunch of compilation error reported while using function.hpp ebf 965 [doc] boost::variant tutorial - final example uses v1_v2 should be seq1_seq2 ebf 993 Variant should use least common multiple of alignments_ rather than maximum fcacciola 1217 value_initialized leaves data uninitialized_ when using MSVC fcacciola 617 Numeric Conversion Documentation minor bug fcacciola 818 No zero-argument in_place() grafik 1023 inspect grafik 1041 Cygwin requires PATH setting. grafik 1062 Cygwin install stage fails with combination of patches grafik 1128 boost-buil rule does not overrule BOOST_BUILD_PATH grafik 1135 bjam crashes grafik 1146 KAI Referenced in compiler status acknowledgements grafik 1233 Boost website still refers to CVS grafik 431 boost jam problem with parallel builds grafik 546 boost.build needs fixes for HP/UX grafik 616 Boost Jam_ and non english directorys grafik 721 Generated files "@()" don't work in regular expressions. grafik 896 <native-wchar_t>off does not work when build with vc-8.0 grafik 959 linking fails when Boost is compiled with STLport 5.1.* on Linux (names mismatch) grafik 977 bjam crashes when compiled with gcc 4.2 grafik 986 Problem building Python modules on boost 1.34.0 hkaiser 1077 Spirit integer parser does not always detect integer overflow hkaiser 1079 boost-1.34.0 fails to compile. concept checks not satisfied. hubert_holin 162 Cannot compile octonion_test.cpp because of bug in sinc.hpp hubert_holin 647 octonion documentation bug igaztanaga 1080 boost::interprocess win32 global file mapping issue igaztanaga 1210 interprocess::barrier hangs during second use under linux (boost 1.33.1) igaztanaga 1231 interprocess_condition (emulated) hangs after notify_all(). jbandela 283 Compiler error for tokenizer on Solaris jbandela 501 token_iterator::at_end() result is inversed jbandela 665 bug in char_separator jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 jmaurer 819 uniform_int<> with type's maximum availaible range error johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1083 boost_regex 1.34.0 uses ICU library without linking to it johnmaddock 1130 GCC -wundef warnings johnmaddock 1148 boost_1_34_1 regex library compile failure on aix with xlv jsiek 416 Spelling of Edmonds-Karp-Algorithm jsiek 575 Calling subgraph::global_to_local on a root graph jsiek 636 strange compiling problem for transitive_closure jsiek 813 concept_check.hpp unused variable warning jsiek 815 remove_edge core dumps on self-circle jsiek 875 No iterator based constructor for adjacency_matrix jsiek 900 graphml reader namespace handling is broken mistevens 688 ublas: bug in mapped_vector_of_mapped_vector nasonov 1220 lexical_cast requires RTTI nasonov 754 boost::any - typeid comparison across shared boundaries nesotto 1145 Small bugs in Boost.Range documentation nesotto 471 boost.range and "const char[]". nesotto 518 [Boost.Range]boost::const_begin calls non-qualified 'begin' nesotto 723 local_time_facet error in VS2005 Win2003 nesotto 730 The ptr_map iterator cannot be dereference to value type nesotto 807 boost::assignment documentation: mathematical "typo" pavol_droba 1152 rle_example fails pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* pdimov 1108 shared_ptr does not compile under g++ with -fno-rtti pdimov 1243 ODR violation by boost::detail::lightweight_mutex pdimov 997 error in boost::bind doc ramey 1036 assert failure in oserializer.hpp:418 ramey 1038 "<" and ">" should be excaped in xml_oarchive ramey 1086 Serialization of weak_ptr produces invalid XML ramey 1089 missing boost::serialization::make_nvp in pointer container library ramey 1121 xml_archive_exception is missing seperate header file_ and documentation mismatch ramey 1137 Virtual destructor is missing ramey 1141 Dangerious operator<< for wostream ramey 1142 boost/serialization/optional doesn't include necessary header ramey 1223 boost::serialization chokes on correcly formatted empty XML element ramey 757 xml serialization fails when using namespace ramey 878 error C2039: 'mbstate_t' : is not a member of 'std' ramey 961 boost::basic_binary_oprimitive not instantiated correctly ramey 968 xml_grammar - incorrect define char ramey 969 basic_binary_iprimitive::load_binary bug rogeeff 1030 execution_monitor.ipp #warning directive breaks compilation on MSVC 8.0 rogeeff 1032 typo in Boost.Test documentation rogeeff 1050 BOOST_CHECK_CLOSE_FRACTION documentation missing rogeeff 1060 no example sources in online docs for Boost::Test rogeeff 1212 Template fixtures rogeeff 607 Log level names wrong in documentation rogeeff 842 typo in auto_unit_test.hpp Revision 1.17 rogeeff 893 grammatical error in error message rogeeff 956 Doc error in test examples. rogeeff 962 Missing links in Test library documentation samuel_k 585 64 bit compile warning/error for boost::format samuel_krempp 1195 patch: boost/format/parsing.hpp does not compile if BOOST_NO_LOCALE_ISDIGIT is defined samuel_krempp 1196 Patch: when BOOST_NO_STD_LOCALE is not defined_ boost/format/internals.hpp fails to compile. samuel_krempp 704 format zero length string msvc-8 samuel_krempp 859 boost::format ignores a user defined locale shammah 284 pool::purge_memory() does not reset next_size shammah 290 perfomance: memory cleanup for pool takes too long shammah 386 boost::pool_allocator breaks with vector of vectors shammah 88 ct_gcd_lcm.hpp compilation error speedsnail 1138 Problems with TSS and static thread library t_schwinger 1100 Building boost.function_types fails cvs rev-1.1_ no chdir command in bash turkanis 525 problem with boost::iostreams when compiled with Visual C++ turkanis 699 Changing size of memory-mapped file on Windows turkanis 786 bug in iostreams/copy.hpp line 81 turkanis 791 iostreams::tee_filter is for output only turkanis 817 Performance problem in iostreams turkanis 822 Incorrect usage of bad_write()_ bad_seek() etc. turkanis 856 iostreams file_descriptor::write fails under Win32 urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode urzuga 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile vladimir_prus 1165 more quoting problems vladimir_prus 1228 bug in toolset gcc + HP/UX PA-RSIC vladimir_prus 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments witt 1046 Boost.Python quickstart instructions mention nonexistent target witt 834 Homepage regression links witt 957 The "Getting Started" page does not mention the stdlib option witt 973 zip_iterator has value_type == reference -- -- Marshall Marshall Clow Qualcomm, Inc. <mailto:mclow@qualcomm.com> The famous British scientist, Lord Kelvin, said: "When you measure what you are speaking about and express it in numbers, you know something about it, but when you cannot (or do not) measure it, when you cannot (or do not) express it in numbers, then your knowledge is of a meagre and unsatisfactory kind."

1 0

[serialization][trunk] please bring us archive helpers back
by Joaquín Mª López Muñoz 10 Sep '07

10 Sep '07

Hello, Boost.Serialization 1.33-1.34 introduces the notion or "helpers" to the Archive interface by means of the member functions: void lookup_helper( const extended_type_info* const eti, shared_ptr<void>& sph); void insert_helper( const extended_type_info* const eti, shared_ptr<void>& sph); which allow the user to make an archive instance store arbitrary helper objects associated to any given type. This helper interface is used to implement serialization of boost::shared_ptr in a non-intrusive way, which was impossible for former versions of Boost.Serialization. This is a wonderful addition to the library because not only solves the old problem with serializating shared_ptr but also serves as a general utility for implementing complicated serialization schemes, notably those in which internal resources are serialized which cannot be directly manipulated from the class public interface. I have used archive helpers to good effect in implementing an otherwise unfeasible serialization algorithm for a library I'm writing, but when I moved from Boost 1.34 to the SVN trunk I discovered to my dismay that this (admittedly undocumented) feature has been removed in favor of an ad-hoc extension of the Archive interface (internally based on something resembling the former helper code) to specifically allow serialization of boost::shared_ptr. IMHO this is a step back because it singles out shared_ptr as a type receiving special attention (vg. what will happen with std::tr1::shared_ptr, will the interface be augmented again to cope with this?) and primarily because it deprives us developers from a very very powerful tool. Could the helper interface please please be brought back to Boost.Serialization? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 10

Re: [boost] How to download Functional module of Fusion 2 ???
by dan marsden 10 Sep '07

10 Sep '07

>In particular I'm looking for >#include <boost/fusion/functional/invocation/invoke_procedure.hpp> You'll need to download the latest stuff from the boost svn trunk to get the functional library, and other enhancements to Fusion added since the review. <snip lots of problems finding the latest code> >Not exactly what you would call "user friendly".... Fusion is not in Boost 1.34.x as it was reviewed too late for that release. It will in incorporated in 1.35. As it's not yet officially in a boost release that may explain the difficulty finding it you had above. Hopefully we'll get more user friendly after that. Cheers Dan ___________________________________________________________ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html

3 3

Release Team?
by Rene Rivera 09 Sep '07

09 Sep '07

Just catching up after a week vacation... I had a quick conversation on IRC with Volodya where he mentioned a rather appealing idea which happened to coincide with a similar idea I was having. He mentioned the idea of a "release team" to hammer out the specifics of the new release procedures. Now what I was thinking of... For a while now I've been considering volunteering to manage a release. But I came to some obvious observations, and others pointed out similar thoughts: * Being a release manager is a lot of work because of the size and scope of Boost. * There's a lot of learning involved for each new manager. In the form of learning the process and tools to get the release completed. * It seems we are expecting the manager to both manage releases, and to advance the development of the release procedures. This is not new to this release cycle. AFAICT most release managers have "fine tuned" the release process as part of their work. * If we are going to expect another Boost release, with something more than just patches, in the near future we have to start a release cycle now. * As a body of volunteers, no one person has enough "free time" to devote to managing a release. Particularly if that same person is also dealing with development of a Boost component. For 1.35 the release manager is going to face not just fine tuning the process, but overhauling it. The repository changed, the process is changing, and the tools are changing. Additionally, from my POV, the discussions about the new release process don't seem to be progressing at a quick enough pace. This made me realize it would be unrealistic for me to devote the need time that being a release manager would require. So the simple idea is to have a "Release Team" instead of a "Release Manager" to distribute the work and hopefully smooth out the attention a release gets. The dynamic would be: * A release team is composed of three people. Yes, it's an arbitrary number, hence it only feels right because of the expected amount of work 1.35 is likely to be. For later releases two people might be enough. * The goal is for the team to have a good spread in understanding of the release process. And hence we should prefer picking, when possible, people with knowledge of the management, building, and testing aspects of the process. * The members of the team are free to decide how they split up the work. But we should encourage working on all aspects to advance the spread of the release process know-how. * A member signs on for two consecutive releases, in a staggered order. The obvious exception being the first few releases where one or more would only do one release. This reduces the ramping up time a single release manager would go through, hence keeping the releases going smoothly. Does this sounds like an idea worth pursuing, i.e. running with for this release? Seeing as we really need to get moving on some process decisions if we want to see a release for 2008/01! -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

7 8

[atomic_count] Discrepancy between gcc and solaris implementation
by Corrado Zoccolo 09 Sep '07

09 Sep '07

Hi boosters, when performance tuning a really tight loop in a simple program, I found that reading the value of an atomic count is unexpectedly slow on a gcc platform. I checked the code, and the implementation used, (I have a checkout of some month ago of boost HEAD, when there was still the cvs in place), is: operator long() const { return __exchange_and_add(&value_, 0); } I checked other implementations, and for example solaris has the much lighter: operator uint32_t() const { return static_cast<uint32_t const volatile &>( value_ ); } Is there a compelling reason to use the locked operation with gcc, or a simpler volatile access can serve the same purpose? A simple test program shows a large overhead for the locked operation. #include <boost/timer.hpp> #include <boost/detail/atomic_count.hpp> #include <iostream> namespace cz { using __gnu_cxx::__atomic_add; using __gnu_cxx::__exchange_and_add; class atomic_count { public: explicit atomic_count(long v) : value_(v) {} void operator++() { __atomic_add(&value_, 1); } long operator--() { return __exchange_and_add(&value_, -1) - 1; } operator long() const { return static_cast<_Atomic_word volatile const &>(value_); } private: atomic_count(atomic_count const &); atomic_count & operator=(atomic_count const &); mutable _Atomic_word value_; }; } int main(int argc, char **argv) { { boost::timer t; for(boost::detail::atomic_count i(0);i<10000000;++i); std::cout<<t.elapsed()<<std::endl; } { boost::timer t; for(cz::atomic_count i(0);i<10000000;++i); std::cout<<t.elapsed()<<std::endl; } } Compiled with g++ -O3, and run on a Linux box equipped with Pentium IV 2.8GHz (HT disabled), I obtain the following result: [corrado@et2 test]$ ./a.out 1.4 0.75 i.e. the "for" that uses the volatile access is almost twice as fast than the other one. Do you see any drawback in changing the access to the counter to a simple volatile access, at least when the platform is known to be an IA32? Corrado -- __________________________________________________________________________ dott. Corrado Zoccolo mailto:zoccolo@di.unipi.it PhD - Department of Computer Science - University of Pisa, Italy --------------------------------------------------------------------------

2 1