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

threads and async questions and asnwers
by Victor Yankee 03 Jun '15

03 Jun '15

Hello List, I have a thread with a class and its method that raises a "question" signal and needs to wait with a timeout for an "answer" signal. There are several worker threads, some of which may be connected to the question signal. The answer signal will be raised by a worker thread only if it knows the answer; it is possible that no worker thread knows the answer so no answer signal will be raised (hence need for timeout). The question thread cannot know which worker thread to ask. What is a good way to achieve this using boost 1.58 and/or C++11? I am using g++ 4.9 on 64bit ubuntu 14.04. Thanks, Vic

4 4

[Test]
by Merrill Cornish 02 Jun '15

02 Jun '15

I'm get a SIGEGV segmentation fault /only/ when trying to register a test manually. Everything works just fine if I use auto registration. All compiles and links in both cases are without error. I know almost nothing about using gdb, but I was able to see the segment violation message shown below. I'm running Boost 1.58.0; Windows 7.1 64-bit; MinGW 4.9.2 64-bit; Eclipse Luna; CDT 8.6.0 In my TestMain.cpp #define BOOST_TEST_ALTERNATIVE_INIT_API #define BOOST_TEST_NO_MAIN #include "boost/test/unit_test.hpp" extern void Operand_Default_Constructor_Test(); bool init_unit_test() { framework::master_test_suite().p_name.value = "DiGSE Master Test"; framework::master_test_suite().add(BOOST_TEST_CASE(&Operand_Default_Constructor_Test)); return true; } int main(int argc, char* argv[]) { return boost::unit_test::unit_test_main(&init_unit_test, argc, argv); } It compiles and links without error. However, executing it gives this SIGEGV fault: Program received signal SIGSEGV, Segmentation fault. 0x000000006b405a12 in boost::unit_test::framework::get (id=1, t=boost::unit_test::tut_suite) at ./boost/test/impl/framework.ipp:388 388 if( (res->p_type & t) == 0 ) The failing snippet is part of a test that would throw internal_error(), but the if test itself seems to fail. if( (res->p_type & t) == 0 ) throw internal_error( "Invalid test unit type" ); If the Operand_Default_Constructor_Test test is changed from void Operand_Default_Constructor_Test() to BOOST_AUTO_TEST_CASE(Operand_Default_Constructor_Test) and the contents of init_unit_test() are removed, it works just fine with automatic registration. And the automatic registration is certainly the easiest way; but I was holding out hope for being able to specify test ordering. Merrill Cornish

2 2

boost::posix_time::time_period and boost::serialization
by Lakin Wecker 01 Jun '15

01 Jun '15

I'm having some issues getting the following example to compile in g++4.9, or clang 3.6, using boost 1.58.0 I'm not quite experienced enough with boost or c++ to be certain, but it appears that the vector serialization is done in such a way that it doesn't pick up the load_construct_data for time_period from boost/date_time/posix_time/time_serialize.hpp Is the fix simply to do my own vector serialization a situation like this? Or is there another fix? Thank in advance, Lakin $ cat test.cpp #include <boost/date_time/posix_time/time_serialize.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/date_time/posix_time/posix_time_types.hpp> #include <boost/serialization/vector.hpp> #include <vector> #include <sstream> class test { public: friend class boost::serialization::access; std::vector<boost::posix_time::time_period> m_vec; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & m_vec; } }; int main(int argc, char *argv[]) { test a; std::ostringstream os; boost::archive::text_oarchive oa(os); oa << a; std::istringstream is(os.str()); boost::archive::text_iarchive ia(is); ia >> a; std::cout << os.str() << std::endl; return 0; } $ g++ -std=c++14 test.cpp -I deps/boost_1_58_0 In file included from /usr/include/c++/4.9/memory:64:0, from deps/boost_1_58_0/boost/config/no_tr1/memory.hpp:21, from deps/boost_1_58_0/boost/smart_ptr/shared_ptr.hpp:23, from deps/boost_1_58_0/boost/shared_ptr.hpp:17, from deps/boost_1_58_0/boost/date_time/gregorian/greg_month.hpp:14, from deps/boost_1_58_0/boost/date_time/gregorian/greg_ymd.hpp:16, from deps/boost_1_58_0/boost/date_time/gregorian/greg_calendar.hpp:16, from deps/boost_1_58_0/boost/date_time/gregorian/gregorian_types.hpp:19, from deps/boost_1_58_0/boost/date_time/posix_time/posix_time_config.hpp:18, from deps/boost_1_58_0/boost/date_time/posix_time/posix_time_system.hpp:13, from deps/boost_1_58_0/boost/date_time/posix_time/ptime.hpp:12, from deps/boost_1_58_0/boost/date_time/posix_time/posix_time.hpp:15, from deps/boost_1_58_0/boost/date_time/posix_time/time_serialize.hpp:12, from test.cpp:1: /usr/include/c++/4.9/bits/stl_construct.h: In instantiation of ‘void std::_Construct(_T1*, _Args&& ...) [with _T1 = boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>; _Args = {}]’: /usr/include/c++/4.9/bits/stl_uninitialized.h:516:43: required from ‘static void std::__uninitialized_default_n_1<_TrivialValueType>::__uninit_default_n(_ForwardIterator, _Size) [with _ForwardIterator = boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>*; _Size = long unsigned int; bool _TrivialValueType = false]’ /usr/include/c++/4.9/bits/stl_uninitialized.h:571:33: required from ‘void std::__uninitialized_default_n(_ForwardIterator, _Size) [with _ForwardIterator = boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>*; _Size = long unsigned int]’ /usr/include/c++/4.9/bits/stl_uninitialized.h:632:50: required from ‘void std::__uninitialized_default_n_a(_ForwardIterator, _Size, std::allocator<_Tp>&) [with _ForwardIterator = boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>*; _Size = long unsigned int; _Tp = boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>]’ /usr/include/c++/4.9/bits/vector.tcc:549:39: required from ‘void std::vector<_Tp, _Alloc>::_M_default_append(std::vector<_Tp, _Alloc>::size_type) [with _Tp = boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>; _Alloc = std::allocator<boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration> >; std::vector<_Tp, _Alloc>::size_type = long unsigned int]’ /usr/include/c++/4.9/bits/stl_vector.h:676:41: required from ‘void std::vector<_Tp, _Alloc>::resize(std::vector<_Tp, _Alloc>::size_type) [with _Tp = boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>; _Alloc = std::allocator<boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration> >; std::vector<_Tp, _Alloc>::size_type = long unsigned int]’ deps/boost_1_58_0/boost/serialization/vector.hpp:90:9: [ skipping 24 instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ] deps/boost_1_58_0/boost/archive/detail/iserializer.hpp:618:24: required from ‘void boost::archive::load(Archive&, T&) [with Archive = boost::archive::text_iarchive; T = test]’ deps/boost_1_58_0/boost/archive/detail/common_iarchive.hpp:66:40: required from ‘void boost::archive::detail::common_iarchive<Archive>::load_override(T&, int) [with T = test; Archive = boost::archive::text_iarchive]’ deps/boost_1_58_0/boost/archive/basic_text_iarchive.hpp:71:9: required from ‘void boost::archive::basic_text_iarchive<Archive>::load_override(T&, int) [with T = test; Archive = boost::archive::text_iarchive]’ deps/boost_1_58_0/boost/archive/text_iarchive.hpp:92:57: required from ‘void boost::archive::text_iarchive_impl<Archive>::load_override(T&, int) [with T = test; Archive = boost::archive::text_iarchive]’ deps/boost_1_58_0/boost/archive/detail/interface_iarchive.hpp:60:9: required from ‘Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = test; Archive = boost::archive::text_iarchive]’ test.cpp:36:11: required from here /usr/include/c++/4.9/bits/stl_construct.h:75:7: error: no matching function for call to ‘boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>::period()’ { ::new(static_cast<void*>(__p)) _T1(std::forward<_Args>(__args)...); } ^ /usr/include/c++/4.9/bits/stl_construct.h:75:7: note: candidates are: In file included from deps/boost_1_58_0/boost/date_time/gregorian/gregorian_types.hpp:18:0, from deps/boost_1_58_0/boost/date_time/posix_time/posix_time_config.hpp:18, from deps/boost_1_58_0/boost/date_time/posix_time/posix_time_system.hpp:13, from deps/boost_1_58_0/boost/date_time/posix_time/ptime.hpp:12, from deps/boost_1_58_0/boost/date_time/posix_time/posix_time.hpp:15, from deps/boost_1_58_0/boost/date_time/posix_time/time_serialize.hpp:12, from test.cpp:1: deps/boost_1_58_0/boost/date_time/period.hpp:101:3: note: boost::date_time::period<point_rep, duration_rep>::period(point_rep, duration_rep) [with point_rep = boost::posix_time::ptime; duration_rep = boost::posix_time::time_duration] period<point_rep,duration_rep>::period(point_rep first_point, duration_rep len) : ^ deps/boost_1_58_0/boost/date_time/period.hpp:101:3: note: candidate expects 2 arguments, 0 provided deps/boost_1_58_0/boost/date_time/period.hpp:90:3: note: boost::date_time::period<point_rep, duration_rep>::period(point_rep, point_rep) [with point_rep = boost::posix_time::ptime; duration_rep = boost::posix_time::time_duration] period<point_rep,duration_rep>::period(point_rep first_point, ^ deps/boost_1_58_0/boost/date_time/period.hpp:90:3: note: candidate expects 2 arguments, 0 provided deps/boost_1_58_0/boost/date_time/period.hpp:51:9: note: constexpr boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>::period(const boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>&) class period : private ^ deps/boost_1_58_0/boost/date_time/period.hpp:51:9: note: candidate expects 1 argument, 0 provided deps/boost_1_58_0/boost/date_time/period.hpp:51:9: note: constexpr boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>::period(boost::date_time::period<boost::posix_time::ptime, boost::posix_time::time_duration>&&) deps/boost_1_58_0/boost/date_time/period.hpp:51:9: note: candidate expects 1 argument, 0 provided

2 3

Re: [Boost-users] [MSM] Boost.MSM: statemachine to transition on templatized event-type
by Christophe Henry 01 Jun '15

01 Jun '15

Hi, > having tested Boost.MSM, I'm pretty happy with it. :) >It's interesting, in that it seems to handle all states in a static table. >No "new" operator etc. It's much faster without dynamic allocation. <snip> g_row<StateInitial, EventT, StateEven, &Machine_<EventT>::guardToEven>, >Unfortunately >gcc gives this error: >d.cpp:119:5: error: ‘g_row’ was not declared in this scope > g_row<StateInitial, EventT, StateEven, &Machine_<EventT>::guardToEven>, Short answer. Try: typename Machine_<EventT>::template g_row<StateFloat, EventT, StateFloat, &Machine_<EventT>::guardToFloat> Long answer: g_row is a type of state_machine_def and as your fsm is a template, it becomes a dependent type (=> typename) and a template one even (=> template). C++ is sometimes really annoying :( Longer answer. Give up this front-end, it's deprecated anyway. A better solution will be: #include <boost/msm/front/functor_row.hpp> using namespace boost::msm::front; struct GuardToOdd { template <class EVT,class FSM,class SourceState,class TargetState> bool operator()(EVT const& num,FSM& ,SourceState& ,TargetState& ) { const long long x = static_cast<long long>(num.getNum()); return ((x == num.getNum()) // is Integral type && ((x % 2) != 0)); } }; Row< StateFloat, EventT, StateOdd, none, GuardToOdd> HTH, Christophe

3 2

[Boost Test] BOOST_TEST_ALTERNATIVE_INIT_API
by Merrill Cornish 01 Jun '15

01 Jun '15

I am using Boost 1.58.0. After I downloaded it, I did a full default build with build_type=complete. So, Boost Test was built without any special command line arguments. The minimal tests I have so far work. I have defined BOOST_TEST_ALTERNATIVE_INIT_API <http://www.boost.org/doc/libs/1_57_0/libs/test/doc/html/utf/compilation.htm…> in my main program, so my initialization function (currently empty) is bool init_function(). However, I noticed something in the documentation that said if you do define BOOST_TEST_ALTERNATIVE_INIT_API <http://www.boost.org/doc/libs/1_57_0/libs/test/doc/html/utf/compilation.htm…> in your main(), you also have to define it when you build the library. But my test code seems to be working without the special build. Does 1.58.0, perhaps, not need the command line definition. Or, am I kidding myself that everything is all right, and the Roadrunner is going to drop an anvil on my head at a later date? Merrill Cornish

2 1

{Boost-Test] How to specify order test suites are run.
by Merrill Cornish 01 Jun '15

01 Jun '15

I'm running Boost 1_58_0 on Windows 7.1, 64-bit, with MinGW 4.9.2, 64-bit. I've just started writing tests for my project and have one test suite working. I'm using BOOST_AUTO_TEST_CASE and BOOST_AUTO_TEST_SUITE. There will be many more test suites to come. They are not LOGICALLY dependent on each other, but if some fail, the other tests will be a waste of time. Therefore, I would like to be able to specify the order in which they are run. Is there a way to do that, or does choosing BOOST_AUTO_TEST_SUITE take it all out of my hands? Merrill Cornish

3 4

[Interprocess] Can I use google sparsehash?
by Malko 31 May '15

31 May '15

Hi, I thought I would find this question already answered on the internet or in previous posts in the mailing list, but my research is fruitless. Hence, since I am not proficient in the way of allocators, I will ask directly: is it possible to use google sparsehash with Boost.Interprocess? According to the info I found sparsehash can be faster than boost::unordered_map, and I could really use the additional speed. Thanks for the help! -- View this message in context: http://boost.2283326.n4.nabble.com/Interprocess-Can-I-use-google-sparsehash… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

How to fetch boost libraries and their dependencies from github via CMake
by Gonzalo BG 30 May '15

30 May '15

Dear all, I have a CMake project that requires some header-only boost libraries: - container, dynamic_bitset, math, units I would like CMake to always fetch automatically the latest version of these libraries and their dependencies from github as an external project. AFAIK FindBoost doesn't do this, is there maybe a different cmake script that does? Best regards, Gonzalo

5 6

[MSM] Boost.MSM: statemachine to transition on templatized event-type
by nice sw123 29 May '15

29 May '15

Hi there, having tested Boost.MSM, I'm pretty happy with it. It's interesting, in that it seems to handle all states in a static table. No "new" operator etc. Since there is no "new" and all is static, I cannot use the runtime, to specialize my transitions. So instead, I have to use templates! Unfortunately I'm not a template master, and the compiler is giving me an error. Here's what I'm trying: template <typename EventT> struct Machine_ : public msm::front::state_machine_def<Machine_<EventT> > { // ... struct transition_table : mpl::vector< g_row<StateInitial, EventT, StateEven, &Machine_<EventT>::guardToEven>, g_row<StateInitial, EventT, StateOdd, &Machine_<EventT>::guardToOdd>, g_row<StateInitial, EventT, StateFloat, &Machine_<EventT>::guardToFloat>, g_row<StateEven, EventT, StateEven, &Machine_<EventT>::guardToEven>, g_row<StateEven, EventT, StateOdd, &Machine_<EventT>::guardToOdd>, g_row<StateEven, EventT, StateFloat, &Machine_<EventT>::guardToFloat>, g_row<StateOdd, EventT, StateEven, &Machine_<EventT>::guardToEven>, g_row<StateOdd, EventT, StateOdd, &Machine_<EventT>::guardToOdd>, g_row<StateOdd, EventT, StateFloat, &Machine_<EventT>::guardToFloat>, g_row<StateFloat, EventT, StateEven, &Machine_<EventT>::guardToEven>, g_row<StateFloat, EventT, StateOdd, &Machine_<EventT>::guardToOdd>, g_row<StateFloat, EventT, StateFloat, &Machine_<EventT>::guardToFloat> >{}; // ... } Unfortunately gcc gives this error: d.cpp:119:5: error: ‘g_row’ was not declared in this scope g_row<StateInitial, EventT, StateEven, &Machine_<EventT>::guardToEven>, etc. Can somebody help in this regard? Thanks. nicesw123 In case you're interested. Here's the code of the complete example that I'm trying to get working: #include <iostream> #include <boost/msm/front/state_machine_def.hpp> #include <boost/msm/back/state_machine.hpp> namespace msm = boost::msm; namespace mpl = boost::mpl; // events struct EventNumber1 { // int number! EventNumber1(int num_) : num{num_} {} int getNum() const { return num; } private: int num; }; struct EventNumber2 { // double number! EventNumber2(double num_) : num{num_} {} double getNum() const { return num; } private: double num; }; typedef EventNumber2 MyEvent; // using doubles // StateBase -- a base (parent) state struct StateBase : public msm::front::state<> { StateBase(const std::string& stateName = "") : stateName{stateName} {} template <typename Event, typename FSM> void on_entry(const Event&, FSM&) { std::cout << "Entering " << stateName << std::endl; } template <typename Event, typename FSM> void on_exit(const Event&, FSM&) { std::cout << "Leaving " << stateName << std::endl; } private: std::string stateName; }; #if 0 // not used (just an idea) template <typename T> struct StateMachineFront_Base : public msm::front::state_machine_def<StateMachineFront_Base<T>> { StateMachineFront_Base(const std::string& stateMachineName = "") : stateMachineName{stateMachineName} {} template <typename Event, typename FSM> void on_entry(const Event&, FSM&) { std::cout << "Entering " << stateMachineName << std::endl; } template <typename Event, typename FSM> void on_exit(const Event&, FSM&) { std::cout << "Leaving " << stateMachineName << std::endl; } private: std::string stateMachineName; }; #endif template <typename EventT> struct Machine_ : public msm::front::state_machine_def<Machine_<EventT> > { Machine_(const std::string& stateMachineName = "Machine_") : stateMachineName{stateMachineName} {} template <typename Event, typename FSM> void on_entry(const Event&, FSM&) { std::cout << "Entering " << stateMachineName << std::endl; } template <typename Event, typename FSM> void on_exit(const Event&, FSM&) { std::cout << "Leaving " << stateMachineName << std::endl; } // states struct StateInitial : public StateBase { StateInitial(const std::string name = "StateInitial") : StateBase{name} {} }; struct StateEven : public StateBase { StateEven(const std::string name = "StateEven") : StateBase{name} {} }; struct StateOdd : public StateBase { StateOdd(const std::string name = "StateOdd") : StateBase{name} {} }; struct StateFloat : public StateBase { StateFloat(const std::string name = "StateFloat") : StateBase{name} {} }; // guards bool guardToEven(const EventT& num) { const long long x = static_cast<long long>(num.getNum()); return ((x == num.getNum()) // is Integral type && ((x % 2) == 0)); } bool guardToOdd(const EventT& num) { const long long x = static_cast<long long>(num.getNum()); return ((x == num.getNum()) // is Integral type && ((x % 2) != 0)); } bool guardToFloat(const EventT& num) { const long long x = static_cast<long long>(num.getNum()); return (x != num.getNum()); // is Floating type } typedef StateInitial initial_state; struct transition_table : mpl::vector< g_row<StateInitial, EventT, StateEven, &Machine_<EventT>::guardToEven>, g_row<StateInitial, EventT, StateOdd, &Machine_<EventT>::guardToOdd>, g_row<StateInitial, EventT, StateFloat, &Machine_<EventT>::guardToFloat>, g_row<StateEven, EventT, StateEven, &Machine_<EventT>::guardToEven>, g_row<StateEven, EventT, StateOdd, &Machine_<EventT>::guardToOdd>, g_row<StateEven, EventT, StateFloat, &Machine_<EventT>::guardToFloat>, g_row<StateOdd, EventT, StateEven, &Machine_<EventT>::guardToEven>, g_row<StateOdd, EventT, StateOdd, &Machine_<EventT>::guardToOdd>, g_row<StateOdd, EventT, StateFloat, &Machine_<EventT>::guardToFloat>, g_row<StateFloat, EventT, StateEven, &Machine_<EventT>::guardToEven>, g_row<StateFloat, EventT, StateOdd, &Machine_<EventT>::guardToOdd>, g_row<StateFloat, EventT, StateFloat, &Machine_<EventT>::guardToFloat> >{}; private: std::string stateMachineName; }; typedef msm::back::state_machine<Machine_<MyEvent>> Machine; template <typename T> void postEvents(Machine& machine) { for (T i; std::cin >> i; ) { machine.process_event(MyEvent{i}); } } int main() { Machine machine; machine.start(); postEvents<double>(machine); machine.stop(); return 0; }

2 4

Fwd: [Boost-announce] [boost] [metaparse] Review period starts May 25th and ends June 7th
by Christophe Henry 28 May '15

28 May '15

I had sent this message only to the Developer mailing list. Please let me correct this mistake now. ------------------------------------------------------------------------------------------------------------------------- Dear all, The review of the Metaparse library starts next Monday, May 25th and ends June 7th. Metaparse was written by Abel Sinkovics. Metaparse is a parser generator library for template metaprograms. The purpose of this library is to support the creation of parsers that parse at compile time. This library is intended to be used for embedded domain specific language creation for C++ and can help libraries provide a better interface. It is similar to Boost.Spirit, however while parsers built with Spirit parse at run-time, parsers built with Metaparse parse at compile-time. It makes it possible for library authors to provide an interface that follows the common notation of the problem domain of the library. (eg. SQL queries, grammars, etc written in their common notation instead of similar-looking C++ expressions). For example there is a (yet incomplete) interface for Boost.Spirit that makes it possible to write MPLLIBS_REGEX("^[abcd][3-8]\\.foo$") instead of bos >> set[as_xpr('a')|'b'|'c'|'d'] >> range('3','8') >> '.' >> 'f' >> 'o' >> 'o' >> eos and make the parser built with Metaparse generate the latter expression from the former one. (It can be found here: https://github.com/istvans/mpllibs/tree/master/libs/xlxpressive) Since the library is based on template metaprogramming, the DSLs can be used for type validation as well. This is demonstrated by the type-safe printf implementation ( http://abel.web.elte.hu/mpllibs/safe_printf/index.html) It type-checks the arguments of a printf call based on the format string and has zero runtime overhead compared to unchecked printf. Parsers can be constructed in a declarative manner and (even though this is template metaprogramming based) remain readable. The implementation reflects the grammar it parses (with additional elements for semantic actions). Even though the library requires the parser author to write template metaprograms, the development of parsers is well supported by tools like Metashell and MDB. An important aspect of parsers (built with this library or another one) is error reporting for invalid input. The library offers tools for the parser authors to be able to provide useful error messages in case of parsing errors. Here is an example error report by a parser built with Metaparse (the parser can be found in the Getting Started guide of the library): ..... x__________________PARSING_FAILED__________________x<1, 5, unpaired<1, 1, literal_expected<')'>>> .... It is an error report letting the developer know that a closing paren is missing at line 1, column 5 and the unclosed opening paren is in line 1, column 1. Metaparse can be downloaded from Github: https://github.com/sabel83/mpllibs/tree/master/mpllibs/metaparse And a very complete tutorial: http://abel.web.elte.hu/mpllibs/metaparse/getting_started.html The tutorial also offers the nice feature of a link to metashell for quick-starting trying out the library: http://abel.web.elte.hu/shell/metashell.html Boost.Msm v3 also implements a new compile-time strings based front-end called eUML2 to demonstrate the power of the library and the conciseness and expressiveness it allows. Please have a look at the documentation: https://htmlpreview.github.io/?https://raw.githubusercontent.com/boostorg/m… Everybody on this list is invited to participate in this formal review. I hope to see your review of Metaparse, including your vote on acceptance, and I welcome your participation in the ensuing discussions on the Boost developers' mailing list. Please always include in your review a vote as to whether the library should be accepted into Boost. Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? - With what compiler? - Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Regards, Christophe Review Manager

1 0