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

[task][fiber] question about memory leaks
by Dorogan' Konstantin 11 Nov '10

11 Nov '10

Sorry for my "good" english. :) I'am try to use boost.task 0.4.2 in my project. I found some leaks in the files handle.hpp and task.hpp related use_count member initialization. So boost::intrusive_ptr can't release allocated resources. After fixing promblem of the use_count initialization, i ran my unit tests again, but some leaks still living. I discovered that the problem is in the boost.fiber (v 0.5.1). If i try to run compiled unit tests of the boost.fiber manually, the garbage collector of the boost.test shows the leaks. In hopes of finding the place of data leaks, I perform these tests under Rational Purify, but Puify reports that no leaks were detected. Is the garbage collector of the boost.test lies, or the leaks is real!? Tested environment: Windows 7 x64, Windows XP boost 1.42.0 boost.context 0.2.0 boost.task 0.4.2 boost.fiber 0.5.1

1 0

[1.45] Release v trunk, as of r66483
by Jim Bell 11 Nov '10

11 Nov '10

Here's a list of all differences between release and trunk, as of r66483 (this morning). I won't slam the mailing list with its contents, so it's here instead: http://jc-bell.com/files/release-v-trunk-r66483.csv Organized by Folder (2nd column), and it might have a stray false positive or negative since I apply a patch to test. FYI.

5 10

Re: [boost] [msm] Event deferring causes stack overflow
by Christophe Henry 10 Nov '10

10 Nov '10

<snip> >It is not that nice for 2 reasons: > >1. It makes state machine behavior description more splinted in our case to several files ( not a big deal). >2. I have created our own defer functor which logs the event deferral with our logging framework >is there a way do similar function in a state like the no_transition for deferred events where I can implement some generic logging ?. Hi Richard, No, it's not nice. Luckily, last night brought fresh ideas and I implemented a fix. It has to run all regression tests to be 100% sure but it looks good so you can give it a try. For your logging functor, you have to provide a typedef inside the functor definition (like Defer is now doing in functor_row.hpp): typedef int deferring_action; This activates the normal deferred handling and the stack overflow is gone. The fix can be downloaded from the trunk (revision 66490). Unfortunately, it is too late to make it into the 1.45 so be careful if you switch to the new boost release :( I also didn't have time to actualize the doc yet. HTH, Christophe

1 0

[boost.log] Using stream manipulators to influence record formatting per sink
by Jamie Allsop 10 Nov '10

10 Nov '10

So I've been using the previously reviewed log library by Andrey Semashev with some degree of success. One thing however has caused me a great deal of trouble and I'm sure with a couple of changes would become a lot easier. Basically I have an application that outputs tabular data in the logs. I have objects that know how to stream themselves either as an ascii table or as an html table. I have a custom defined manipulator that can be set for a stream that the objects can check the value of, and stream themselves either as text or html as appropriate. In using the log library I face two major challenges. The first is how can I set the manipulator to the desired value so that the log record will be aware of the manipulator while building its message? It is not possible to do this by calling set_formatter() on the sink since the this receives *an already composed* record.message() string. My work-around for this is a lot more complex than I'd like it to be and I'll detail it here in the hope that it provides some insight to Andrey so that he might be able to offer a nicer alternative more in-keeping with his library. So starting at the beginning I have objects that implement streaming something like this: ---- template< class CharT, class Traits> friend std::basic_ostream< CharT, Traits>& operator<<( std::basic_ostream<CharT, Traits>& Ostream, const my_class& Value ) { if( log::output_format::value_in( Ostream ) == log::output_format::text ) { write_text( Ostream, Value ); } else if( log::output_format::value_in( Ostream ) == log::output_format::html ) { write_html( Ostream, Value ); } return Ostream; } ---- where 'value_in()' simply retrieves the value from the stream. Now during logging a temporary stream object is created that must have this manipulator applied. What I'd like to do is be able to specify if I want this manipulator applied on a per-sink basis. In much the same way as I can define a specific formatter for a sink, or a specific filtering rule for a sink. Currently there is no way to do that (at least not without a *lot* of effort) so I'll address this later. Instead I'll consider how we can deal with this be setting this desire globally by using a global attribute. We could write something like this: ---- log::output_format::type OutputFormat = log::output_format::html; std::pair< boost::log::core::attribute_set_type::iterator, bool > OutputFormatAttribute = boost::log::core::get()->add_global_attribute ( "OutputFormat", boost::make_shared< boost::log::attributes::constant<log::output_format::type> >( OutputFormat ) ); ---- Later we can extract this value to decide if we need the manipulator applied to the stream that is used to compose the log record message. We can use a helper object that is aware of all the manipulators that are to be applied and have it the log record stream based on attributes that represent them. For example, given a class called 'manipulators' we can define this insertion operator as: ---- template< class CharT, class TraitsT > inline std::basic_ostream<CharT,TraitsT>& operator<< ( std::basic_ostream<CharT,TraitsT>& Ostream, const manipulators& Manipulators ) { Manipulators.apply( Ostream ); return Ostream; } ---- where apply could be implemented (in our case) as this: --- template< class CharT, class TraitsT > void apply( std::basic_ostream<CharT,TraitsT>& Ostream ) const { boost::log::basic_record<CharT> Record( RecordHandle_ ); apply_output_format( Ostream, Record ); } private: ---- template< class CharT, class TraitsT > void apply_output_format( std::basic_ostream<CharT,TraitsT>& Ostream, const boost::log::basic_record<CharT>& Record ) const { log::output_format::type OutputFormat = log::output_format::text; boost::log::extract<log::output_format::type> ( "OutputFormat", Record.attribute_values(), boost::lambda::var( OutputFormat ) = boost::lambda::_1 ); if( OutputFormat == log::output_format::text ) { Ostream << log::set_output_format( log::output_format::text ); } else if( OutputFormat == log::output_format::html ) { Ostream << log::set_output_format( log::output_format::html ); } } ---- This then requires that the insertion operator is called as part of the streaming for any log record. In order to achieve this I need to write my own logging macros that do essentially what the severity logging macros do already but with the addition of streaming a 'manipulator' object at the same time so that the manipulators I want added can be applied to the stream that is constructed during that process. Here is the key macro that I need to write which gets substituted in a chanin of macros: ---- #define MY_LOG_STREAM_WITH_PARAMS_INTERNAL(logger, rec_var, params_seq)\ for (::boost::log::record_handle rec_var = (logger).open_record((BOOST_PP_SEQ_ENUM(params_seq))).handle(); !!rec_var; rec_var.reset())\ ::boost::log::aux::make_pump_stream((logger), rec_var).stream() << log::manipulators(rec_var) ---- The important part is this: ---- log::manipulators(rec_var) ---- The stream object is created and immediately passed an instance log::manipulators passing the RecordHandle to the constructor. Finally then I can have manipulators passed down to the stream that is used to create the log record message, and in my case allow the logged objects to either stream themselves as text or as html. A downside of this is that this only works with global attributes. So either all log sinks would one format or the other. Given that it is generally desirable to treat different sinks differently (and often the reason they exist) it would be much nice if there was the concept of sink-level attributes. These could be added to the record's attribute set along with the source and global attributes. Currently there is no way (it seems) to associate any state with a sink or make any decision during logging that relates to a sink. We can set a custom formatter that applies to the log message created but that has no effect on the record message itself. (Decorators only seem to be for post-processing of the record message). We can also set a custom filter to determine whether a log record gets logged by a given sink. It seems odd then that we have no way to to be able to say (for example) that a given sink will have an attribute that indicates that all messages through that sink should be in a certain format (for those objects that support the formatting). From looking at the code this does not appear to be a major issue so hopefully it could be supported. It would also be highly desirable to be able to specify manipulators directly that could then be applied to the record message stream itself. Supporting this at the global and sink level should be possible. If we had sink-level attributes the technique I described could be used to simulate this, even though it is somewhat kludgey. Most directed to Andrey, but I'd welcome comments and suggestions from others familiar with the log library. Jamie

2 3

[icl] The Interval Container Library (ICL) moved to the Boost trunk
by Joachim Faulhaber 10 Nov '10

10 Nov '10

Dear All, thank you again for you welcoming comments on the latest version of the now renamed Interval Container Library ICL (formerly Interval Template Library ITL). And thanks to Hartmut for your "invitation" to move the library to the Boost trunk. This might be a small step for Boost but it's a big step for me ;-) I am not sure what has to be done now, so my test suite will be executed in the daily tests that is summarized in the trunk summary on the Boost web-site. I have added my lib into the list in status/Jamfile.v2. I am also wondering how I get information about and deal with errors from those tests on platforms that I can not run on my machine. I didn't find anything about those topics on the Wiki so far. Maybe someone can provide some guidance :) Thanks, Joachim

1 0

[boost.log] set_open_handler() and set_close_handler() for text_multifile_backend?
by Jamie Allsop 10 Nov '10

10 Nov '10

I think it makes a lot of sense for these methods to be available for the text_multifile_backend as they are for the text_file_backend. My use case is that I am logging data out in html format and being able to log data out as individual html files for browsing through later on. Being able to have an html header and footer added as files are opened and closed makes a lot of sense for this backend. Jamie

2 4

[optional] swap not a member of boost::optional
by Eric Niebler 10 Nov '10

10 Nov '10

It seems like boost::optional has a swap member function on trunk but not on release, and it's been this way for a few releases already. Can we get this inconsistency resolved? I've been bitten by it a few times already when merging things to the release branch. -- Eric Niebler BoostPro Computing http://www.boostpro.com

1 1

[graph] Kudos!
by K. Noel Belcourt 10 Nov '10

10 Nov '10

Hi, Just wanted to say nice job to Jeremiah Willcock!! Found this killer graph on page 5: http://www.sandia.gov/LabNews/ln11-05-10/labnews11-05-10.pdf I probably cut the citation off (it reads: Graph courtesy of Jeremiah Willcock, Indiana University). Guessing this was generated with pBGL? -- Noel

1 0

[fusion] rev. 66411 breaks VC 8.0
by Ralf W. Grosse-Kunstleve 10 Nov '10

10 Nov '10

minimal.cpp: #include <boost/fusion/sequence/comparison/less_equal.hpp> cl /c /EHsc /I..\hot\boost minimal.cpp Gives the error below. It works with rev. 66410 but not 66411 (and still not with current 66472): % svn log -v -c66411 ------------------------------------------------------------------------ r66411 | cschmidt | 2010-11-06 05:21:18 -0700 (Sat, 06 Nov 2010) | 1 line Changed paths: M /trunk/boost/fusion/container/deque/deque.hpp A /trunk/boost/fusion/container/deque/detail/is_sequence_impl.hpp M /trunk/boost/fusion/container/vector/detail/vector_n.hpp M /trunk/boost/fusion/sequence/comparison/detail/enable_comparison.hpp M /trunk/boost/fusion/support/detail/is_mpl_sequence.hpp M /trunk/boost/fusion/support/is_sequence.hpp M /trunk/boost/fusion/support/sequence_base.hpp Fusion: removed fusion::sequence_root; Fixes #2335 ------------------------------------------------------------------------ ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2039: 'is_native_fusion_sequence' : is not a member of 'boost::fusion::detail' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2065: 'is_native_fusion_sequence' : undeclared identifier ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2974: 'boost::disable_if' : invalid template argument for 'Cond', type expected ..\hot\boost\boost/utility/enable_if.hpp(59) : see declaration of 'boost ::disable_if' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2988: unrecognizable template declaration/definition ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2059: syntax error : ',' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(48) : error C2039: 'type' : is not a member of '`global namespace'' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(55) : error C2039: 'is_native_fusion_sequence' : is not a member of 'boost::fusion::detail' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(55) : error C2974: 'boost::disable_if' : invalid template argument for 'Cond', type expected ..\hot\boost\boost/utility/enable_if.hpp(59) : see declaration of 'boost ::disable_if' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(56) : error C2039: 'type' : is not a member of '`global namespace'' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(57) : error C2143: syntax error : missing ';' before '{' ..\hot\boost\boost/fusion/sequence/comparison/less_equal.hpp(57) : error C2447: '{' : missing function header (old-style formal list?)

2 2

Showstopper ticket #4736 not in trunk or release
by Jim Bell 10 Nov '10

10 Nov '10

The patch for showstopper ticket # 4736 isn't in either the trunk or release branches as of this morning (r66453). Did it get missed?

3 7

MinGW's last thread/tss problem: fixable?
by Jim Bell 10 Nov '10

10 Nov '10

Thread is still failing test_tss_lib, now with this... ../libs/thread/test/test_tss.cpp(181): error in "test_tss": Support of automatic tss cleanup for native threading API not available If I understand this correctly, the tss cleanup will never be called for a thread created via the native API. There's no global function that can force a clean-up because nothing can force the underlying thread mechanism to return the thread-specific value for a thread that's already exited. I see some subtle magic in libs/thread/src/win32/tss_pe.cpp, some even for __MINGW32_... Is this for static libs? Any chance we can make that work for MinGW's gcc-4.3.3 and gcc-4.4.0? Also, I think the docs need a "Note" section describing this issue, say thread_local_storage.html, inside the section "Cleanup at thread exit".

2 1

Re: [boost] [Review] Formal Review of Proposed Boost.Chrono LibraryStarts TOMORROW
by Aaron Graham 10 Nov '10

10 Nov '10

See this gcc bugzilla entry for a discussion I've had about chrono support in the gcc implementation. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41861 Unfortunately, monotonic_clock support, even if it exists, is a transparent lie. It's not so much a problem with the chrono library as it is a problem with the thread library's use of chrono. A monotonic clock is used to provide somewhat accurate/reliable wait times even in the face of changing clocks, especially in the case of mutexes and condition variables. When condition::wait_until is called with a monotonic_clock time_point, that time_point is translated to a system_clock time_point. If the system_clock is changed (via NTP, adjtime, settimeofday, etc) between when convert_to<system_clock> is called and when the underlying posix call is made, the very reason for using monotonic_clock defenestrates and splatters all over the pavement. Depending on the magnitude of the clock change, wait_until could hang forever. In my opinion, all convert_to calls in the thread library should go to the monotonic_clock, if available. Not system_clock. I couldn't get the gcc people to understand this, so I won't be able to use <chrono> in the standard library sans modification. Maybe boost will get it right? Let me know if I'm missing a subtle point that moots my concerns. Other than that, I think the this library is great. I need it badly. I haven't looked over all the code yet, but what I've seen looks good.

3 2

mkl+boost problems
by Andrey Asadchev 10 Nov '10

10 Nov '10

Hello. mkl (intel blas) has "mkl_cblas.h" file which in turn includes " mkl_types.h" file which defines P4 macro variable: 70 /** CPU codes for int MKL_CPU_DETECT(void) **/ 71 #ifdef _IPF 72 #define ITP 0 73 #else 74 #ifdef _EM64T 75 #define NI 0 76 #define CT 1 77 #define MNI 2 78 #define PNR 3 79 #else 80 #define DEF 0 81 #define PIII 1 82 #define P4 2 83 #define P4P 3 84 #define P4M 4 85 #endif 86 #endif This P4 variable creates havoc of MPL templates which have P4 template parameters names. What to do?

9 10

Re: [boost] [msm] Event deferring causes stack overflow
by Christophe Henry 09 Nov '10

09 Nov '10

> Hi All > > We have found a serious problem in msm back end for event deferring. > I case there is a composite state and the outer state machine defers 2 > events when it is in the composite state, the 1st event deferred fine > in the deferred queue of the outer state machine. > Than the 2nd event is processed and this is deferred as well as a part > of this deferral msm back end dispatches the 1st event but it is still > deferred and saved again in the deferred queue but than msm processes > the deferred queue again as an action of the deferral of the 1st event > and dispatches the 2nd event again which is deferred and the cycle > repeats itself until the system runs out of call stack. Hi, No, it's not that serious, but still not nice. The problem is that the principle of the Defer functor is not working and I am wondering if I should keep it. To make short, Defer is an action, and for all front-ends, actions return void. This has the unintended effect of marking the transition results as "handled" instead of "deferred", which breaks my defensive measures. If you replace the transitions by the standard UML method of marking the state as deferring (through the deferred_events typedef), you have no more stack overflow. Now I understand that the Defer functor is cool and offering to remove it is guaranteed to cause disappointment, so I see 2 possibilities: - explaining its limitations in the doc - making a change to all front-ends for this special case to work around the fact that actions return void For the meantime, use the "normal" way and I will see if I find a workaround. Cheers, Christophe

2 1

[mpl] mpl::c_str fails for mpl::push_back
by vicente.botet 09 Nov '10

09 Nov '10

Hi, the following results in a compile error for msvc-10.0. It works for gcc-3.4, gcc-4.3, gcc-4.5. typedef mpl::vector_c<char, 'h','e','l','l','o',' ','w','o','r','l','d'> hello; typedef mpl::push_back<hello, mpl::char_<'!'> >::type hello2; BOOST_TEST((std::string(mpl::c_str<hello2>::value)== "hello world!")); // line 59 C:\cygwin\boost\v44\boost/mpl/string.hpp(592) : error C2039: 'value_type' : is not a member of 'boost::mpl::vector12<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>' with [ T0=boost::mpl::integral_c<char,104>, T1=boost::mpl::integral_c<char,101>, T2=boost::mpl::integral_c<char,108>, T3=boost::mpl::integral_c<char,108>, T4=boost::mpl::integral_c<char,111>, T5=boost::mpl::integral_c<char,32>, T6=boost::mpl::integral_c<char,119>, T7=boost::mpl::integral_c<char,111>, T8=boost::mpl::integral_c<char,114>, T9=boost::mpl::integral_c<char,108>, T10=boost::mpl::integral_c<char,100>, T11=boost::mpl::char_<33> ] io\match_pass.cpp(59) : see reference to class template instantiation 'boost::mpl::c_str<Sequence>' being compiled with [ Sequence=hello2 ] Is this a known bug? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

3 13