November 2010 - Boost - lists.preview.boost.org

[1.45.0] Permission to merge trunk to release for Boost.Optional
by Fernando Cacciola 13 Nov '10

13 Nov '10

Hi, As reported by Eric Niebler, the release brunch did not had the swap member that existed in the trunk for a long time. I just merged it locally and run the tests on the release branch. Can I commit the changes? P.S: The test suite changed as well due to the different swap. P.S.2: I've also been reported on a couple of minor documentation issues, so I've fixed this on both the trunk and the release branch. P.S.3: Going over all the differences I've found a trivial change in the testsuite for value_initialized: The trunk version uses the lightweight "minimal" test tools instead of the full test tools. I've merged this one as well. Can I commit these changes to the release branch? --- Fernando Cacciola SciSoft Consulting, Founder http://www.scisoft-consulting.com

6 9

[FunctionTypes] Removing the ClassTransform when invoking parameter_types
by Edward Diener 12 Nov '10

12 Nov '10

When invoking boost::function_types::parameter_types with a member function pointer as the first template parameter, what do I susbstitute as the second template parameter so that no transform is done ?

2 1

[exception] [1.44] you own a showstopper
by Eric Niebler 12 Nov '10

12 Nov '10

Emil, The following bug in exception is marked as a Showstopper for the 1.44 release. What are your plans for it? If you're planning on fixing it, can you do so soon? If you feel it is not a showstopper, can you set its priority appropriately? https://svn.boost.org/trac/boost/ticket/4768 Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com

3 6

Type traits extension & Bitfield reviews
by Joel Falcou 12 Nov '10

12 Nov '10

I've just seen these libraries hanging out in the review queue for quite some time now. Considering their potential usefulness adn my personnal interest, I consider stepping up as a review manager for these. What's the formal sequence to follow to apply for such a task ?

7 10

[inspect] added new check for C-style assert macro (was: [property_tree][showstopper][1.45] missing include in string_path.hpp)
by Eric Niebler 12 Nov '10

12 Nov '10

On 11/11/2010 3:49 PM, Sebastian Redl wrote: > On 11.11.2010, at 21:38, Eric Niebler wrote: >> If BOOST_ASSERT is *always* to be preferred over C's assert macro, >> then we should probably add that to the inspection report, right? > > That would probably a good idea. I just modified the inspect tool to check for the presence of C-style assert in Boost code. Everybody should be using BOOST_ASSERT. (Right?) Here's the result of running the new check over Boost trunk: http://pastebin.com/NttTw3BJ Beman, the inspection report looks like it was last run in June. What's up? http://boost.cowic.de/rc/inspect-trunk.html -- Eric Niebler BoostPro Computing http://www.boostpro.com

4 11

[1.45][filesystem/io] Streaming operator
by Chard 12 Nov '10

12 Nov '10

The filesystem path streaming operator (>>) has a bug in 1.44, documented here: https://svn.boost.org/trac/boost/ticket/4716 A patch has been provided, and has been implemented on the trunk, detailed here: http://lists.boost.org/boost-commit/2010/08/27576.php Any chance of this being merged to the release branch for 1.45? [.../boost/io/detail/quoted_manip.hpp] --

1 0

Re: [boost] [Boost-users] What's so cool about Boost.MPI?
by Matthias Troyer 12 Nov '10

12 Nov '10

On 5 Nov 2010, at 20:04, Riccardo Murri wrote: > On Fri, Nov 5, 2010 at 3:51 PM, Peter Foelsche <foelsche(a)sbcglobal.net> wrote: >> Can somebody explain to me, what is so great about mpi or boost/mpi? > > Daunting task, but I'll give it a try :-) > > MPI is a library interface[1] to ease some common communication > patterns in scientific/HPC software. In particular, MPI provides > library functions for: > > 1. Reliable delivery of messages between two concurrent processes; > there are functions for both synchronous and asynchronous > communication. > > 2. Collective communication of the running processes: e.g., one > process broadcasting a message to all others; all processes > broadcasting to all; scattering a large array to all running > processes, etc. > > 3. "Remote shared memory": a process can expose a memory buffer that > all others can directly read/write. > > 4. Parallel I/O, where many processes access (possibly interleaved) > portions of a file independently. > > Despite being non-trivial features to implement on top of a standard > TCP socket interface, MPI implementations are mostly into performance: > they can usually take advantage of special hardware (e.g., Infiniband > or Myrinet interconnects) and use the native protocols (instead of > TCP/IP) to provide faster communication speed. > > A "message" in usual socket programming is just a flat array of bytes. > A "message" in MPI is a (potentially non-contiguous portion) of a C or > FORTRAN data structure; MPI can handle C structures and > multi-dimensional C-style arrays, and multi-dimensional arrays of C > structures (containing multi-dimensional arrays, etc.). However, > since MPI is implemented as a library, you have to tdescribe to MPI > the in-memory layout of the data structures you want to send as a > message; thus "duplicating" work that is done by the compiler. You > can imagine that this quickly gets tedious and unwieldy once you start > having non-trivial data structures, possibly with members of unknown > length (e.g., a list). > > This is where Boost.MPI comes to the rescue: if you can provide > Boost.Serialization support for your classes, you can send them as MPI > messages with no extra effort: no need for lengthy calls to > MPI_Type_create_struct() etc. And it does this with minimal or even > no overhead! (Plus you also get a nice C++ interface to MPI > functionality, whereas the MPI C calls are quite low-level.) > > > .. [1] MPI proper is a specification; there are several > implementations of the spec (e.g., OpenMPI, MPICH, MVAPICH, plus > many vendor/proprietary one), but they are all compatible at the > source level. > > Best regards, > Riccardo Nice summary! Matthias

5 8

[1.45.0] Beta 1 available from SourceForge
by Beman Dawes 11 Nov '10

11 Nov '10

Boost release1.45.0 beta 1 is now available from SourceForge. For those who downloaded release candidate 1, note that beta 1 was build from a slightly later release candidate. See http://sourceforge.net/projects/boost/files/ This release contains numerous enhancements and bug fixes for existing libraries. For details of what's in the release, see http://beta.boost.org/users/news/version_1_45_0. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. There are still a few serious bugs outstanding, and we will be working on clearing those before the final release. Thanks, -- The Boost Release Team

7 9

Re: [boost] [serialization][thread] possible regressions?
by Eric Niebler 11 Nov '10

11 Nov '10

On 11/11/2010 1:41 PM, Robert Ramey wrote: > Anthony Williams wrote: >> Eric Niebler <eric(a)boostpro.com> writes: >> >>> I don't know whether this is a serialization issue or a thread issue. >>> Robert, Anthony, can you two weigh in? >> >> Looks like a serialization problem to me. > > I would agree - but its hard to reproduce from here. I don't see this as > quick fix - it would require some time and help from the person who can > actually reproduce it. Thanks, Robert. This is now https://svn.boost.org/trac/boost/ticket/4842 Ruediger, anything you can do to help Robert with this one would be much appreciated. -- Eric Niebler BoostPro Computing http://www.boostpro.com

1 0

Problem with boost deserialization.
by Esteban RG 11 Nov '10

11 Nov '10

Hi, I need serialization in a project of mine. I have reduced my options to boost and ProtocolBuffer, but in order to be able to decide which one to use, I am trying to build a timing test for serialization and deserialization. Let me explain a little about my setup: a) Platform: - windows 7, 64bit version - visual studio 2008 express edition x32 b) Additional library: - ACE library for High resolution timer. The code (an explanations) that I have used to implement the comparison is at follows: I build a class with four different lists of boost/serialization/list like documentation states: std::list<unsigned int> &lint_; std::list<ACE_INT64> &llong_; std::list<float> &lfloat_; std::list<std::string> &lstring_; The test is increasing the size of every list simultaneously. Then it gets serializated and deserializated and finally I get the time results for this process. However there is one issue: Serialization always works, but deserialization fails during execution time whenever the lists are bigger than 10 elements, throws a exception "input stream error" into boost/serialization/throw_exception.hpp as seen with the debugger in the variable/const std::exception const &e (boost library) Visual studio shows this message: Unhandled exception at 0x765cb727 in prTestBoostSerialization2.exe: Microsoft C++ exception: boost::archive::archive_exception at memory location 0x003fc564.. my class definition is: #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <boost/serialization/string.hpp> #include <boost/serialization/list.hpp> //#include <boost/serialization/version.hpp> //#include <boost/serialization/split_member.hpp> #include <iostream> #include <list> #include <string> class BoostSerializationClass { public: // Not required because al member are public // friend class boost::serialization::access; BoostSerializationClass(std::list<unsigned int> &lint , std::list<float> &lfloat , std::list<ACE_INT64> &llong , std::list<std::string> &lstring) : lint_(lint), lfloat_(lfloat), llong_(llong), lstring_(lstring) { //std::cout << std::endl << " max size " << lint_.max_size(); //std::cout << std::endl << " " << llong_.max_size(); //std::cout << std::endl << " " << lfloat_.max_size(); //std::cout << std::endl << " " << lstring_.max_size(); } std::list<unsigned int> &lint_; std::list<ACE_INT64> &llong_; std::list<float> &lfloat_; std::list<std::string> &lstring_; }; namespace boost { namespace serialization { template<class Archive> void serialize(Archive &ar, BoostSerializationClass &c , const unsigned int version){ ar & c.lint_; ar & c.llong_; ar & c.lfloat_; ar & c.lstring_; } } } ----------------------- And main function is: #include <iostream> #include <fstream> //#include <cstdlib> #include <ace/OS.h> #include <ace/Time_Value.h> #include <ace/High_Res_Timer.h> // high resolution timer // include for BOOST #include "../prTestProtocolBuffers/BoostSerializationClass.h" #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> //#include <list> <- dont include this use boost/serialization/list #include <boost/serialization/list.hpp> void gen_random_string(std::string &s, const int len); int ACE_TMAIN(int argc, ACE_TCHAR* argv[]){ //int lengthList = 5; //int lengthList = 10; int lengthList = 15; //int lengthList = 50; // int lengthList = 100; // int lengthList = 1000; std::list<unsigned int> listInteger,listInteger2; std::list<float> listFloat,listFloat2; std::list<ACE_INT64> listLongs,listLongs2; std::list<std::string> listString,listString2; int rint = 0; float rfloat = 0.f; ACE_INT64 rint64 = 0; std::string rstring = ""; std::cout << std::endl << "Begin random generate message. Please be patient."; // Generate random fields for messages for (int i=0 ; i<lengthList ; i++){ listInteger.push_back( rand() ); listFloat.push_back( (float)rand()/(float)RAND_MAX ); listLongs.push_back( rand()*rand()*rand() ); gen_random_string(rstring, lengthList); listString.push_back( rstring ); } // BOOST SERIALIZATION ACE_High_Res_Timer hrTimerBoost; // Load fields into BoostSerializableClass BoostSerializationClass boostSerializationClass( listInteger, listFloat, listLongs, listString); std::ofstream obfile("boost-file.bin"); boost::archive::binary_oarchive oba(obfile); //ACE_Time_Value btvStart = ACE_OS::gettimeofday(); hrTimerBoost.start(); oba & boostSerializationClass; // boost serialization; obfile.close(); hrTimerBoost.stop(); ACE_hrtime_t usecsBoost; hrTimerBoost.elapsed_microseconds(usecsBoost); //ACE_Time_Value btvEnd = ACE_OS::gettimeofday(); //ACE_Time_Value tvIncBoost( btvEnd.sec() - btvStart.sec() , btvEnd.msec() - btvStart.msec() ); std::cout << std:: endl << " ===== BOOST SERIALIZATION =====" ; //std::cout << std::endl << tvIncBoost.sec() << " seconds " << tvIncBoost.msec() << " mseconds" << std::endl ; std::cout << std::endl << usecsBoost << " micro seconds " << std::endl ; // BOOST DESERIALIZACION BoostSerializationClass boostSerializationClass2( listInteger2, listFloat2, listLongs2, listString2); std::ifstream ibfile("boost-file.bin"); boost::archive::binary_iarchive iba(ibfile); //btvStart = ACE_OS::gettimeofday(); hrTimerBoost.reset(); hrTimerBoost.start(); iba & boostSerializationClass2; ibfile.close(); hrTimerBoost.stop(); hrTimerBoost.elapsed_microseconds(usecsBoost); //btvEnd = ACE_OS::gettimeofday(); //tvIncBoost = ACE_Time_Value( btvEnd.sec() - btvStart.sec() , btvEnd.msec() - btvStart.msec() ); std::cout << std:: endl << " ===== BOOST DE-SERIALIZATION =====" ; //std::cout << std::endl << tvIncBoost.sec() << " seconds " << tvIncBoost.msec() << " mseconds" << std::endl ; std::cout << std::endl << usecsBoost << " micro seconds " << std::endl ; ACE_OS::system("pause"); return 0; } //////////////////////////////////////////////////////////////////////////////////////////////////////////// void gen_random_string(std::string &s, const int len) { static const char alphanum[] = "0123456789" "ABCDEFGHIJKLMNOPQRSTUVWXYZ" "abcdefghijklmnopqrstuvwxyz"; s.clear(); for (int i = 0; i < len ; ++i) { s.push_back(rand() % (sizeof(alphanum) - 1) ); } } Can anyone of you help me with this? Any help would be truly appreciated. Thanks in advance.

4 4