- Boost-users - lists.preview.boost.org

Boost.Unordered throws 64-bit portability warnings
by Lindley M French 31 May '09

31 May '09

I've noticed on Visual Studio 2005 that I get a slew of warnings from Boost/unordered/detail/hash_table_impl.hpp when I build with "Detect 64-bit portability issues" turned on. In particular at the moment I'm seeing the following warning: boost/unordered/detail/hash_table_impl.hpp(1569) : warning C4267: 'argument' : conversion from 'size_t' to 'unsigned int', possible loss of data And the same on lines 1328, 1569, 1541, 1799, and 1763. I doubt this poses a real problem, but with hash tables you never know. I'd prefer not to see warnings when I build. Can this be fixed, and can regression testing using this build setting be added to the mix in general?

3 5

stlport string vs. std string causing link errors - how to workaround?
by Chris Kruger 31 May '09

31 May '09

Hello everybody, I'm a relatively new user of boost and I have a problem. I believe I know what is causing the problem but I don't yet have a solution and I am looking for suggestions. I'm currently porting a product to Mac OSX. It makes use of both stlport and boost. I have got the software compiling happily enough but I have a couple of link errors that have stumped me for a bit. I believe the link problems are caused by the fact that boost was compiled using the stdlib included with gcc and the code in the product is using stlport. The boost methods causing problems both have stl strings in their arguments. The exact link errors I get is: 1. "boost::filesystem::detail::dir_itr_first(void*&, void*&, stlpmtx_std::basic_string<char, stlpmtx_std::char_traits<char>, stlpmtx_std::allocator<char> > const&, stlpmtx_std::basic_string<char, stlpmtx_std::char_traits<char>, stlpmtx_std::allocator<char> >&, boost::filesystem::file_status&, boost::filesystem::file_status&)" 2. "boost::filesystem::detail::status_api(stlpmtx_std::basic_string<char, stlpmtx_std::char_traits<char>, stlpmtx_std::allocator<char> > const&, boost::system::error_code&)" As you can see the linker is looking for methods that are using stlpmtx_std::basic_string ... i.e. the stlport string The library libboost_filesystem-xgcc40-1_36.dylib as expected contains these basic methods (confirmed by "nm libboost_filesystem-xgcc40-1_36.dylib") but no doubt with std::string I'm using boost 1_36 if that makes any difference and am quite happy to test any assumptions if you don't trust mine. TIA Chris K. http://www.coresoftware.net.au http://www.krugerheavyindustries.com

2 1

Bug Sprint Report for Saturday, May 30th
by Marshall Clow 31 May '09

31 May '09

The boost bug sprint started Friday, May 29th, and runs through Sunday June 7th. We're off to a great start! Status <https://svn.boost.org/trac/boost/report/1> 7:00 AM PDT 5/29: 797 open tickets. 7:45 AM PDT 5/30: 772 open tickets. 7:15 AM PDT 5/31: 763 open tickets. Activity: 5/29: 6 new tickets, 77 modifications, 25 tickets closed 5/30: 2 new tickets, 42 modifications, 17 tickets closed [ Numbers may not add up because I am counting via two different methods, using data that is time-stamped in two different time zones. Also, tickets can be closed and reopened. ] What can you do? See <https://svn.boost.org/trac/boost/wiki/BugSprintJune2009> for details. I've added four new reports to the trac: Open ticket count by owner: <https://svn.boost.org/trac/boost/report/18> Open ticket count by component: <https://svn.boost.org/trac/boost/report/19> Open ticket count by ticket type: <https://svn.boost.org/trac/boost/report/20> Open ticket count by milestone: <https://svn.boost.org/trac/boost/report/21> --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou(a)u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost(a)objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco(a)osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) 9) Steven Watanabe <watanabesj(a)gmail.com> (bug fixes, como) 10) vicente.botet" <vicente.botet(a)wanadoo.fr> 11) Stjepan Rajko <stjepan.rajko(a)gmail.com> (fusion) 12) Daniel Wallin (parameter, ...) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Re: [Boost-users] Boost Serialization + Forward compatibility [was Re: boost::serialization and PHP websites]
by Brian Wood 31 May '09

31 May '09

Robert Ramey writes: > Sohail Somani wrote: >> I also notice you have not mentioned anything about the 70 billion >> dollar bailout for the serialization library and spreading the >> wealth. I assume the cheque's in the mail. > I purposely overlooked that comment. It seemed to be an > attempt at some sort of criticism. I was pointing out how quickly things changed in the automobile industry. I don't think anyone would argue that the computer industry is less volatile than the automobile industry. I'm also dismayed by the government's investment of billions of dollars in General Motors. (I'm not sure if the amount is closer to 50 billion or 70 billion.) > It's absolutely amazing to > me how much I've been criticised (many times personally) > for making this library. I'm not sure if you are referring to me there. I have at times pointed out what I consider to be weaknesses of the serialization library. I don't think I've criticised you personally. Regards, Brian Wood Ebenezer Enterprises www.webEbenezer.net

3 2

boost::thread Compile error with Sun Studio 12
by Roman Morokutti 30 May '09

30 May '09

Hi, When I compile the example on the boost::thread documentation (the source is wrapped by a main function): #include <stdlib.h> #include <boost/thread.hpp> /* * */ int main(int argc, char** argv) { boost::system_time const timeout = boost::get_system_time() + boost::posix_time::milliseconds(500); extern bool done; extern boost::mutex m; extern boost::condition_variable cond; boost::unique_lock<boost::mutex> lk(m); while (!done) { if (!cond.timed_wait(lk, timeout)) { throw "timed out"; } } boost:: return (EXIT_SUCCESS); } I get the error CC -library=stlport4 -mt -c -g -I/opt/boost/boost_1_39_0 -o build/Debug/SunStudio-Solaris-x86/thread.o thread.cpp "/opt/boost/boost_1_39_0/boost/thread/detail/thread.hpp", line 344: Error: boost::thread::thread(boost::thread&) is not accessible from boost::move(boost::detail::thread_move_t<boost::thread>). 1 Error(s) detected. So could anyone tell me how to bypass this error, or should the library be updated? -Roman

3 11

[random] Bias in boost::random generators?
by Tiago de Paula Peixoto 30 May '09

30 May '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm experiencing a bug with the boost::random library. Apparently, most generators, together with uniform_int<>, produce heavily biased sequences. I'm sending attached a small test program which generates several random walks on a lattice, starting from the center, and counts how many times a site has been visited. It uses both the boost::random generators, and the tr1::random generators from GCC 4.3, and writes the separate counts in the files "bcount" and "tcount", respectively. A plot of the output with boost::random can be seen here: http://dl.getdropbox.com/u/280654/boost_random.png There is an obvious tendency towards the (0,0) corner of the lattice... With tr1::random, everything looks normal: http://dl.getdropbox.com/u/280654/tr1_random.png Not to mention I used the same generator (mt19937) with the same seed value in both cases, which should have given the exact same sequence! I obtain similar results with other generators, except with minstd_rand, where the sequences from both libraries are the same. This lead me to conclude that the problem is with the generators themselves, not with uniform_int<>. More info on my end: platform: x86_64 intel, GNU/Linux GCC: 4.3.3 Boost: 1.37 Best regards, Tiago -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoXu/8ACgkQBNxGHvNv411+4QCfSfgo1Mu1lROQhwPnGxtEoq51 C1MAn1GJi0BYVtyExFmfdsxvtpKOM/fk =CsWe -----END PGP SIGNATURE-----

3 6

Bug Sprint Report for Friday, May 29th
by Marshall Clow 30 May '09

30 May '09

The boost bug sprint started Friday, May 29th, and runs through Sunday June 7th. We're off to a great start! Status <https://svn.boost.org/trac/boost/report/1> 7:00 AM PDT 5/29: 797 open tickets. 7:45 AM PDT 5/30: 772 open tickets. Activity: 5/29: 6 new tickets, 77 modifications, 25 tickets closed [ Numbers may not add up because I am counting via two different methods, using data that is time-stamped in two different time zones ] What can you do? See <https://svn.boost.org/trac/boost/wiki/BugSprintJune2009> for details. I've added three new reports to the trac: Open ticket count by owner: <https://svn.boost.org/trac/boost/report/18> Open ticket count by component: <https://svn.boost.org/trac/boost/report/19> Open ticket count by ticket type: <https://svn.boost.org/trac/boost/report/20> Open ticket count by milestone: <https://svn.boost.org/trac/boost/report/21> The following bugs appear to have been fixed, but the tickets were never closed. I would appreciate it if the library maintainers could verify this and close the tickets. https://svn.boost.org/trac/boost/ticket/145 Iterator https://svn.boost.org/trac/boost/ticket/287 date_time The following tickets are feature requests that are unlikely ever to be implemented. Should they be closed? https://svn.boost.org/trac/boost/ticket/558 database https://svn.boost.org/trac/boost/ticket/100 concept_check https://svn.boost.org/trac/boost/ticket/182 concept_check --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou(a)u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost(a)objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco(a)osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) 9) Steven Watanabe <watanabesj(a)gmail.com> (bug fixes, como) 10) vicente.botet" <vicente.botet(a)wanadoo.fr> 11) Stjepan Rajko <stjepan.rajko(a)gmail.com> (fusion) 12) Daniel Wallin (parameter, ...) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

[MPI / Serialization] unable to register user-defined class for serialization through base class pointer
by Ariel Ouziel 30 May '09

30 May '09

Hello, I've just started to try using Boost.MPI, but I'm facing problems with user-defined class serialization. Maybe I'm just missing something. Basically, I have a pure virtual class "task" with the method execute and I want to send classes that implement this interface through MPI. For this to work, I have to register derived class for serialization. Unfortunately, this causes compilation error under MSVC9.0. Here is my code : #include <iostream> #include <exception> #include <boost/mpi.hpp> #include <boost/serialization/string.hpp> #include <boost/serialization/export.hpp> class task { public: virtual void execute() = 0; }; class dtask : public task { public: dtask() {} dtask(std::string text) : text(text) {} virtual void execute() { std::cout << text << std::endl; } private: std::string text; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & text; } }; BOOST_CLASS_EXPORT(dtask) int main(int argc, char* argv[]) { boost::mpi::environment env(argc, argv); boost::mpi::communicator world; try { if (world.rank() == 0) { task * t = new dtask("Blah"); world.send(1, 0, t); } else if (world.rank() == 1) { task * t; world.recv(0, 0, t); t->execute(); } } catch (std::exception &e) { std::cout << "Error : " << e.what() << std::endl; } return 0; } And the compilation error : 1>Compiling... 1>data_testbed.cpp 1>d:\grooviz\libs\boost_1_38\boost\mpi\datatype.hpp(184) : error C2664: 'boost::mpl::assertion_failed' : cannot convert parameter 1 from 'boost::mpl::failed ************boost::mpi::is_mpi_datatype<T>::* ***********' to 'boost::mpl::assert<false>::type' 1> with 1> [ 1> T=std::basic_string<char,std::char_traits<char>,std::allocator<char>> 1> ] 1> No constructor could take the source type, or constructor overload resolution was ambiguous 1> d:\grooviz\libs\boost_1_38\boost\mpi\detail\mpi_datatype_primitive.hpp(96) : see reference to function template instantiation 'MPI_Datatype boost::mpi::get_mpi_datatype<T>(const T &)' being compiled 1> with 1> [ 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(95) : see reference to function template instantiation 'void boost::mpi::detail::mpi_datatype_primitive::save<T>(const T &)' being compiled 1> with 1> [ 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(212) : see reference to function template instantiation 'void boost::archive::save_access::save_primitive<Archive,T>(Archive &,const T &)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(211) : while compiling class template member function 'void boost::archive::detail::save_non_pointer_type<Archive,T>::save_primitive::invoke(Archive &,const T &)' 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(294) : see reference to class template instantiation 'boost::archive::detail::save_non_pointer_type<Archive,T>::save_primitive' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(282) : while compiling class template member function 'void boost::archive::detail::save_non_pointer_type<Archive,T>::invoke(Archive &,const T &)' 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(506) : see reference to class template instantiation 'boost::archive::detail::save_non_pointer_type<Archive,T>' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\mpi\detail\ignore_skeleton_oarchive.hpp(46) : see reference to function template instantiation 'void boost::archive::save<Archive,T>(Archive &,const T &)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\interface_oarchive.hpp(64) : see reference to function template instantiation 'void boost::mpi::detail::ignore_skeleton_oarchive<Archive>::save_override<const T>(const T &,int)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\interface_oarchive.hpp(72) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_oarchive<Archive>::operator <<<const T>(T &)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\sandbox\test\data_testbed\data_testbed.cpp(30) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_oarchive<Archive>::operator &<std::string>(T &)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::content_oarchive, 1> T=std::string 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\access.hpp(109) : see reference to function template instantiation 'void dtask::serialize<Archive>(Archive &,const unsigned int)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive> 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\serialization.hpp(74) : see reference to function template instantiation 'void boost::serialization::access::serialize<Archive,T>(Archive &,T &,const unsigned int)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> T=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\serialization.hpp(133) : see reference to function template instantiation 'void boost::serialization::serialize<Archive,T>(Archive &,T &,const unsigned int)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> T=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(148) : see reference to function template instantiation 'void boost::serialization::serialize_adl<Archive,T>(Archive &,T &,const unsigned int)' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> T=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(140) : while compiling class template member function 'void boost::archive::detail::oserializer<Archive,T>::save_object_data(boost::archive::detail::basic_oarchive &,const void *) const' 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> T=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(170) : see reference to class template instantiation 'boost::archive::detail::oserializer<Archive,T>' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> T=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\oserializer.hpp(167) : while compiling class template member function 'const boost::archive::detail::basic_oserializer &boost::archive::detail::pointer_oserializer<Archive,T>::get_basic_serializer(void) const' 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> T=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\export.hpp(75) : see reference to class template instantiation 'boost::archive::detail::pointer_oserializer<Archive,T>' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> T=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\export.hpp(72) : while compiling class template member function 'const boost::archive::detail::basic_pointer_oserializer &boost::archive::detail::export_impl<Archive,Serializable>::enable_save(boost::mpl::true_)' 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> Serializable=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\export.hpp(106) : see reference to class template instantiation 'boost::archive::detail::export_impl<Archive,Serializable>' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> Serializable=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\export.hpp(105) : while compiling class template member function 'void boost::archive::detail::ptr_serialization_support<Archive,Serializable>::instantiate(void)' 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> Serializable=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\archive\detail\register_archive.hpp(27) : see reference to class template instantiation 'boost::archive::detail::ptr_serialization_support<Archive,Serializable>' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> Serializable=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\export.hpp(128) : see reference to class template instantiation 'boost::archive::detail::_ptr_serialization_support<Archive,Serializable>' being compiled 1> with 1> [ 1> Archive=boost::mpi::detail::ignore_skeleton_oarchive<boost::mpi::detail::content_oarchive>, 1> Serializable=dtask 1> ] 1> d:\grooviz\libs\boost_1_38\boost\serialization\export.hpp(124) : while compiling class template member function 'const boost::archive::detail::guid_initializer<T> &boost::archive::detail::guid_initializer<T>::export_guid(const char *,boost::mpl::false_)' 1> with 1> [ 1> T=dtask 1> ] 1> d:\grooviz\sandbox\test\data_testbed\data_testbed.cpp(36) : see reference to class template instantiation 'boost::archive::detail::guid_initializer<T>' being compiled 1> with 1> [ 1> T=dtask 1> ] Note that if I remove the BOOST_CLASS_EXPORT(dtask), the program compiles fine but I get "unregistered class" exception at runtime. Note also that if I use dtask pointer instead of task with send and recv, the program runs fine. Additionaly, if I use primitive type like "int" instead of std::string in my derived class, the compilation goes fine with the export statement. It seems to me that at some point the compiler tries to get the MPI datatype of std::string even if it shouldn't since it's not a primitive type. What am I missing here ? Thank you in advance, Ariel Ouziel

2 1

Boost.Thread: static lib vs dll - what's the current recommendation?
by Dave Burnard 29 May '09

29 May '09

In a large project, we're currently building the thread library as a dll. We're bringing in a new subcomponent that is also building the thread library as a dll. Various issues ensue - we need to eliminate one of them. One solution is to have the subcomponent use a static version of the thread library, or we can try to make the two dlls "identical" so we only need one copy. Regarding the static linkage option, I have read in various places that dll linkage was recommended for the thread library because of thread local storage issues. Those emails were a couple of years old so I am wondering if that has been resolved in the mean time. We're currently using v37 if that matters. Dave Burnard please CC me off-list as I am not a regular boost-users reader.

1 0

make_argpack(vec_kwd, make_vector(arg[0], ..., arg[n-1]))
by er 29 May '09

29 May '09

Hi All, Any suggestion for this? typedef typename mpl::transform<range_c<0,n>,meta::kwd >::type vec_kwd_t; arg_list< tagged_argument<tag<0>,A<0> >, ... arg_list< tagged_argument<tag<n-1>,A<n-1> >, empty_arg_list > > make_argpack(vec_kwd,make_vector(arg[0],...,arg[n-1])){ // Step 1: get a vector of tagged_argument vec_tagged_arg_t vec_tagged_arg = fusion::transform( kwds, args, binary_f() ); //OK // Step 2: // recursively construct args_list_t from vec_tagged_arg using // arg_list(TaggedArg arg, Next const& tail) // : Next(tail) // // , arg(arg) // // {} // // A little tedious. Before I go ahead : is this the proper way? // A better solution altogether? } Thanks.

2 4

[Graph] how best to submit patch?
by Tim Keitt 29 May '09

29 May '09

I would like to submit a patch for the Graph library. (This is the iterator splitting issue I raised some time ago.) So what is the procedure? 1) check out source from sourceforge SVN (done) 2) make changes 3) run tests??? (what is the best way to ensure the behavior has not changed?) 4) generate the patch (use svn diff?) 5) submit somewhere I just want to be sure I'm pulling the correct tree and there is some means to run regressions on my changes. Thanks. THK -- Timothy H. Keitt Associate Professor Section of Integrative Biology University of Texas at Austin http://www.keittlab.org/

3 3

Boost.iostreams to stream stderr/stdout from forked shell command?
by Andrej van der Zee 29 May '09

29 May '09

Hi, I was wondering if it is possible with boost iostreams to stream stderr/stdout of a forked shell program to the parent process, and use it as an iostream. I could not find anything like this in the documentation or examples. Does anybody has some working code that does just this? Thank you, Andrej

2 1

The Boost Bug Sprint is here!
by Marshall Clow 29 May '09

29 May '09

The boost bug sprint starts today Friday, May 29th, and runs through Sunday June 7th. Status 5/29: 812 open tickets. The goal is to address a large number of open bugs/patches/feature requests in the Trac system at <http://svn.boost.org/trac/report/1>. There are currently 812 open tickets; we'd like to knock that number down _a lot_. What can you do? 1) You can fix bugs. * If you are a library maintainer, you can commit your fixes. ;-) * If you are not a library maintainer, you can fix a problem on your local machine (and test it!!), and then attach your fix as a patch to the Trac ticket for the library maintainer to commit. If you do this, please provide a test case that exercises the problem; i.e, one that fails w/o your patch, and succeeds afterwards. 2) You can characterize bugs. * You can attempt to replicate the bug on your system(s), and attach information that you discover to the Trac ticket. This will make it easier for other people to solve the problem, even if you cannot. * You can write test cases demonstrating the problem, and attach them to the Trac ticket. * You can determine if the bug still exists; sometimes they get fixed, and the ticket never gets closed. In this case, try to identify a checkin that addresses the bug; it's always suspicious when bugs go away "by accident." 3) You can test patches. * Some of the tickets in the Trac system contain patches - some are quite old. You can install these patches on your system, and determine if they (a) build, and (b) work. If you do this, please provide detail. Don't just say "works for me" - say "I installed this over revision XXX on system YYY with compiler ZZZ. The patch installed and compiled successfully, and passed all the tests." * You can write test cases for the patches, and attach them to the ticket. 4) You can help implement new features. * There are a whole set of "feature requests" in the Trac system. If you have an idea about one of these, you can add comments to the Trac system. You can attempt to implement these new features, and attach the patch to the ticket. (Don't forget the test cases!!). Every day during the bug sprint, I'll post the # of tickets modified/closed/opened on the previous day, as well as the total number of open tickets. If you aren't sure where to start, you can verify existing patches. Here are a list of patches that have been open at least six months. [ Note: The URL for ticket number XXXX is https://svn.boost.org/trac/boost/ticket/XXXX ] Bug # Library Description 2603 smart_ptr patch for owner_before and owner_less support with shared_ptr/weak_ptr 2581 mpi MPI tutorial sample has missing includes 2509 string_algo case conversion (to_upper) fails in Codegear C++Builder 5.9.3 2484 bimap Const-overload needed for bimap associative_container_adaptor::count() 2482 concept_check msvc-9.0 unreferenced formal parameter warning when using boost::breadth_first_visit 2454 fusion Fusion - MSVC level 1 warnings 2452 fusion Fusion vector warning 4512 supression would be nice, 2390 test "[patch] fix gcc-4.3 ""unused"" warning in floating_point_comparison" 2370 lexical_cast [lexical_cast] Patch to reduce warnings for CodeGear (Borland) 2351 spirit Minor BOOST_SPIRIT_RULE fixes (rule_parser.hpp) 2312 smart_ptr intrusive_ptr::operator= should have by-value argument 2304 spirit Patch to fix warnings in spirit 2297 mpl Workaround for GCC bug 2290 serialization Patch for GCC-4.0.1 compatibility (and better compile time). 2271 serialization Cannot load version 1.35.0 xml archives that contain vectors of primitive types 2208 Python Pyste can use ElementTree from Python 2.5 2149 date_time Updated Daylight Savings Time for Australia/Perth 2142 Python Patch for boost.python - return_pointee_value, 2114 none Patch for export symbols from shared library 2064 tokenizer Interval notation is wrong in tokenizer documentation 2053 threads porting boost to avr32 linux platform 1947 iterator traversal access decoupling 1861 date_time time_duration type can not be correctly written or read of the period spans 24 hours of more (vc9 and probably others). 1850 thread request for unlock_guard (and/or unique_unlock) to compliment lock_guard/unique_lock 1811 Building Boost Help packaging by supporting DESTDIR 1791 lexical_cast fix warning on MSVC warning level 4 1702 random serialization for Mersenne twister 1681 filesystem patch for NTFS symbolic links 1541 parameter [parameter] Patch for missing includes 1535 function [result_of] remove unneeded headers 1534 build Add support for winsdk 6.1.6000 to Boost.Build.v2 1533 iterator boost/function.hpp unneeded in transform_iterator.hpp 1529 fusion Missing include statement 1521 bimap Missing #include statements 1519 iterator lvalue-ness resurrection in transform_iterator 1437 random "normal_distribution.hpp, improvements to distribution and possibly speed" 1418 serialization polymorphic archive performance improvement 1377 GIL Add ability to save RGBA image as TIFF with associated-alpha (premultiplied) transparency channel. 1341 asio unused argument and another g++ warning 1338 numeric g++ warnings and incomplete header inclusions 1271 Python unused parameter warning in release build 1116 build disable some warnings in msvc build 1066 Python Patch to make Boost.Python compile on SunCC 1049 mpl Getting mpl/has_xxx.hpp to compile on AIX 1020 iterator Boost.Iterator proposal to add is_constant_iterator 903 Python inconsistent usage of function pointer typedefs 868 thread [thread] thread_specific_ptr::element_type ? 864 lambda [lambda][utility] Make lambda support result<> 863 [parameter] fix operator|| for lazy binding 861 parameter Detect nested template members with has_template_xxx,mpl 857 Python add shared_ptr< const T> support 827 date_time Unused variable in format date parser, 802 thread [thread] MSVS: Allow use of thread headers with /Za 761 mpl [mpl] evc4 port 717 Python Add operator for __repr__ similar to __str__ 637 mpl Adjusts mpl::pair concept to be compatible with STL pairs --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou(a)u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost(a)objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco(a)osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) 9) Steven Watanabe <watanabesj(a)gmail.com> (bug fixes, como) 10) vicente.botet" <vicente.botet(a)wanadoo.fr> 11) Stjepan Rajko <stjepan.rajko(a)gmail.com> (fusion) 12) Daniel Wallin (parameter, ...) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 1

[BGL] Dynamic property map containing pointers to custom object
by Leonardo Ciman 29 May '09

29 May '09

Hi, i tried to build a property map using the associative_property_map and putting a poiter to a pure virtual class as value type but i had some error i can't understand. I also tried with a normal class pointer and i had the same problem. /usr/include/boost/dynamic_property_map.hpp:202: error: no match for ‘operator<<’ in' out << boost::get ... I'm new to boost and c++, it's likely that i've done some stupid errors. I hope somebody can help me. That's a test that reproduce the problem: f#include <boost/graph/adjacency_list.hpp> #include <boost/dynamic_property_map.hpp> #include <boost/property_map.hpp> #include <map> #include <iostream> typedef boost::adjacency_list<boost::vecS,boost::vecS,boost::undirectedS>Graph; typedef boost::graph_traits<Graph>::vertex_descriptor vertex_descriptor; class Interface { virtual void test()=0; }; class Implement : Interface { void test(){std::cout << "ok" <<std::endl;} }; int main() { std::map<vertex_descriptor,Interface&>* testmap = new std::map<vertex_descriptor, Interface&>; boost::associative_property_map<std::map<vertex_descriptor,Interface&> > test_map(*testmap); boost::dynamic_properties dp; dp.property("test", test_map); //that's the line that cause the problem Implement i; put("test", dp, 0, i); }

1 0

ublas: tridiagonal with diagonal=upper+lower
by Hicham Mouline 29 May '09

29 May '09

Hello, Is there a special name for tridiagonal matrices that have the property: a(i,i) = a(i, i-1) + a(i, i+1) where the first index is the row, and the 2nd is the column. Do these matrices have special properties? Regards,

1 0

[Date Time] Howto get current time zone
by Bo Karlsson 29 May '09

29 May '09

Hello! Does anyone know how I can get the current time zone (configured in the OS) using the date time library? I need this to convert a UTC time value to the users local time zone. Thanks! /Bo

1 0

make_shared and custom deleter
by Dominique Devienne 28 May '09

28 May '09

I was thinking of using the new make_shared, but I'm already using a custom deleter (shared instances have private destructora and declare the custom deleter as a friend, and new instances are returned wrapped in shared_ptr, thus no explicit new or delete should be possible). Looking at make_shared, I can't see a way to use both at the same time. Am I out of luck? Thanks, --DD

2 2

Re: [Boost-users] Integral type with no upper limit?
by Robert Dailey 28 May '09

28 May '09

On Thu, May 28, 2009 at 7:59 AM, Barend Gehrels <Barend.Gehrels(a)geodan.nl>wrote: > Hi Robert, Francesco, > > I sent (to the other (developers) list) this: If the boost library did decide to implement and add its own limitless integer type, Couldn't this be added to part of the Boost.Math library?

2 1

Re: [Boost-users] Integral type with no upper limit?
by Scott McMurray 28 May '09

28 May '09

2009/5/26 Marshall Clow <marshall(a)idio.com>: > At 1:00 AM +0200 5/27/09, Michiel Helvensteijn wrote: >> >> Perhaps Boost shouldn't reinvent the wheel? There's already an open-source >> arbitrary precision arithmetic library: http://gmplib.org/ > > Which says: > GMP is distributed under the GNU LGPL. This license makes the library > free to use, share, and improve, and allows you to pass on the result. The > license gives freedoms, but also sets firm restrictions on the use with > non-free programs. > > There are people using Boost for both free and non-free programs. > It's my understanding that we (Boost) want to continue to support all of > them. > Personally, I think Boost would be best served providing some sort of expression template wrapper into which different arbitrary-precision numbers could be plugged. That would mean far less work to get something usable, as it could use the GMP implementation initially. Then a BSL version of the implementation could be developed incrementally, while non-floss users could license some implementation to use with the Boost interface.

6 6

[Boost.serialization] unexpected bad_cast exception while deserializing some arbitrary instances (e.g.: ar & data) ...
by Francois Mauger 28 May '09

28 May '09

Hi serializers! Let me present my problem: I have a class, named 'io_factory', that enables to deserialize an arbitrary object from a text (or XML) archive using the following '__load_text' template method: -8<--------------------------------------------------------------------- class io_factory { ... template <typename Data> void __load_text (boost::archive::text_iarchive & ar_, Data & data_) { Data & b = data_; std::cerr << "DEVEL: io_factory::__load_text: archive class name='" << typeid (ar_).name () << "'" << std::endl; std::cerr << "DEVEL: io_factory::__load_text: class name='" << typeid (b).name () << "'" << std::endl; try { /* Here I may experience an unexpected exception * only in very special circumstances: */ ar_ >> b; std::cerr << "DEVEL: io_factory::__load_text: deserialization is ok." << std::endl; } catch (std::exception & x) { std::cerr << "DEVEL: io_factory::__load_text: EXCEPTION=" << x.what () << std::endl; } std::cerr << "DEVEL: io_factory::__load_text: done" << std::endl; } ... }; -8<--------------------------------------------------------------------- I wrote a shared library that makes use of this template code segment. Using a test program, as I try to deserialize an instance of some 'nemo3::ana_event' class from a Boost text archive file, it prints: -8<--------------------------------------------------------------------- DEVEL: io_factory::__load_text: archive class name='N5boost7archive13text_iarchi veE' DEVEL: io_factory::__load_text: class name='N5nemo39ana_eventE' <= ok 'nemo3::ana_event' DEVEL: io_factory::__load_text: deserialization is ok. <==== IT WORKS! DEVEL: io_factory::__load_text: done -8<--------------------------------------------------------------------- This is fine! My object is properly loaded from the file. My test program works as expected. Well, now, I also have a Python module that wraps some C++ code and the 'io_factory' class. I use Boost.Python to do that. When I run my Python program, importing this wrapper module, to deserialize the same Boost text archive file from the python shell; it prints: -8<--------------------------------------------------------------------- ... DEVEL: io_factory::__load_text: archive class name='N5boost7archive13text_iarchiveE' DEVEL: io_factory::__load_text: class name='N5nemo39ana_eventE' DEVEL: io_factory::__load_text: EXCEPTION=std::bad_cast <= OOOOPS! DEVEL: io_factory::__load_text: done ... -8<--------------------------------------------------------------------- As you can see, there is a nasty 'std::bad_cast' thrown exception from the "ar_ >> b;" statement. This code works perfectly in the first case, now something is broken and I cannot figure out what! I am really confused by this issue. I already used exactly the same approach within another library (also based on Boost.serialization and Boost.Python) and I never met any problem. More, I also have a smaller python script that uses the same wrapper module with the same input archive file and it works: I can read all the instances I stored in my archive file! If I use an XML archive, the problem is exactly the same: it works in the first case, not in the last one. I do not understand where this 'bad_cast' exception comes from. For me it as nothing to do with: - the format of the archive (I know the archive file is ok as the test program store/load is properly) - the wrapping within Python (I can make it run ok within a sample python script) I really need a hint that could help me to understand this issue. It seems this problem looks like a side-effect (?) anyway the deep reason is outside of the scope of my code and my knowledge. My config is: * OS: Ubuntu Linux 8.04 * Linux Kernel: $ uname -a Linux mauger-laptop 2.6.24-24-generic #1 SMP Wed Apr 15 15:54:25 UTC 2009 i686 GNU/Linux * Boost: $ boost-config --version 1_38_0 * gcc: $ g++ --version g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu3) * Python 2.5 I'd really appreciate your comments. I'm afraid I cannot send a small sample code that could reproduce this 'bug' in a simpler way as it comes only at a quite high level on top of 3 big shared libraries + Boost + Python. My attempt to isolate some critical code to see this side-effect within "Boost.serialization only" or "Boost.Python only" failed. More it confirms that the code works as expected (hum... or seems to work...). Thanks a lot for your help. regards frc -- François Mauger Département de Physique - Université de Caen Basse-Normandie courriel/e-mail: mauger(a)lpccaen.in2p3.fr tél./phone: 02 31 45 25 12 / (+33) 2 31 45 25 12 fax: 02 31 45 25 49 / (+33) 2 31 45 25 49 Adresse/address: Laboratoire de Physique Corpusculaire de Caen (UMR 6534) ENSICAEN 6, Boulevard du Marechal Juin 14050 CAEN Cedex FRANCE

4 5

[boost::serialization] string serialization
by Bob Walters 28 May '09

28 May '09

I've been trying to use boost::serialization to serialize non-standard strings. Specifically, std::basic_string with a non-standard allocator type, and in another case, boost::interprocess::basic_string. Looking at how std::string serialization was enabled in serialization/string.hpp, I thought I would try to broaden that approach by using a specialization of the implementation_level template as follows: namespace boost { namespace serialization { template <typename C, class T, class A> struct implementation_level< std::basic_string<C,T,A> > { typedef mpl::integral_c_tag tag; typedef mpl::int_< boost::serialization::primitive_type > type; BOOST_STATIC_CONSTANT( int, value = implementation_level::type::value ); }; } // namespace } // namespace I've tried also adding wraper traits (also in boost::serialization namespace): template<typename C, class T, class A> struct is_wrapper< std::basic_string<C,T,A> > : mpl::true_ {}; Serialization of these strings is compiling, and running. At first it looked like it worked, but not quite. Specifically: when the string in question is 16 bytes or less in size (including the \0), the string serializes fine. When longer than that, its value appears to be completely truncated. (I'm looking at the dump of a binary_oarchive.) This isn't the case for std::string, but I'm having a problem figuring out why. I realize this is an unconventional scenario, but any assistance on how to make the support for string serialization apply to more than just std::string is appreciated. (Perhaps this should be ticketed as a feature request?)

1 0

[ASIO] Deadlock during static destruction
by Dan Eaton 28 May '09

28 May '09

Hello, I'm using boost::asio on WinXP64, with boost 1.39. My app is deadlocking during destruction of a static object that has an io_service member variable. If I explicitly delete the static object, no deadlock occurs. The static object is actually a shared_pointer, which points to the object I mentioned above. So at exit, assuming I haven't explicitly deleted the object, once the reference count reaches zero, delete is called, and the process deadlocks. The offending piece of code appears to be in win_thread.hpp:143. void join() { ::WaitForSingleObject(exit_event_, INFINITE); ::CloseHandle(exit_event_); if (terminate_threads()) { ::TerminateThread(thread_, 0); } else { ::QueueUserAPC(apc_function, thread_, 0); ::WaitForSingleObject(thread_, INFINITE); } } It is blocked at ::WaitForSingleObject(exit_event_, INFINITE); (This is as a result of the destruction of the io_service member). In case it's significant, the io_service object is used to establish several socket connections (to and from remote hosts), some of which are through socket.connect, and others through socket.connect_async. Thanks! Danny

2 1

[thread] getting thread id number
by Hipatia 27 May '09

27 May '09

Hi! I'm trying to get the id number of a thread just to write it to the standard output. Since I'm not an expert in c++ programming, let me explain what I do (even if it's quite simple): a create an instance as follows, boost::thread::id thread_id= boost::this_thread::get_id(); By debugging my code with Visual Studio, I see that 'thread_id' has an 'unsigned int' object member called 'id', so I would like to display this value. Unfortunately, I cannot find in the boost documentation any function member of boost::thread::id class that returns its value. Thanks, Hipatia. -- View this message in context: http://www.nabble.com/-thread--getting-thread-id-number-tp23222717p23222717… Sent from the Boost - Users mailing list archive at Nabble.com.

5 6

[threads] calling unlock twice
by Ovanes Markarian 27 May '09

27 May '09

Hello *, I wrote a code which used a RAII idiom to lock multiple mutex instances in ctor and unlock them in dtor. This resulted in the class similar to: struct lock_many { lock_many(mutex& m1, mutex& m2, ...) : m1_(m1), ... { boost::lock(*m1_, *m2_, ...); } ~lock_many() { //some asserts here, which ensure that either all mutex pointers are NULL or unequl to each other if(m1_==NULL && m2_==NULL && ...) return; // all are NULL no unlock needed } private: mutex* m1_; mutex* m2_; };

3 3

[asio] socket_types.hpp defines _WIN32_WINNT under Windows Mobile
by Tom Aylesworth 27 May '09

27 May '09

The socket_types.hpp defines _WIN32_WINNT to 0x0501 if neither _WIN32_WINNT nor _WIN32_WINDOWS are defined. However, under Windows Mobile, _WIN32_WINNT should not be defined. It appears this is only being used to determine the value for max_iov_len: # if defined(_WIN32_WINNT) const int max_iov_len = 64; # else const int max_iov_len = 16; # endif So I think that the original test should also test for _WIN32_WCE, so that _WIN32_WINNT is not defined under Windows Mobile: # if !defined(_WIN32_WINNT) && !defined(_WIN32_WINDOWS) && !defined(_WIN32_WCE) Does anyone know what max_iov_len should be set to under Windows Mobile 5, or how I might be able to find out? I assume it's safer to leave it at the lower value (16) for now, but it would be nice to have it set correctly. Thanks, Thomas Aylesworth Senior Software Engineer RealityMobile http://www.realitymobile.com/ 703.636.7202 office 703.209.1081 mobile

1 0