- Boost-users - lists.boost.org

Re: [Boost-users] [boost-users][multi-index] passing modifier by reference/pointer?
by JOAQUIN M. LOPEZ MUÑOZ 24 Jul '08

24 Jul '08

________________________________________ De: boost-users-bounces(a)lists.boost.org [boost-users-bounces(a)lists.boost.org] En nombre de Igor R [boost.lists(a)gmail.com] Enviado el: miércoles, 23 de julio de 2008 19:53 Para: boost-users(a)lists.boost.org Asunto: [Boost-users] [boost-users][multi-index] passing modifier byreference/pointer? > > Hello, > > Is there a simple way to pass a modifier by reference/pointer in the > following expression: > > my_multi_index_container.modify(somePos, modifier); > > "modifier" is a functor that has some internal state, so I wouldn't > like it to be copied. > Is it possible to do this without an explicit creation of a binder > that binds operator() and &modifier (or so)? The following should do: modifier_type modifier(...); ... my_multi_index_container.modify<modifier_type&>(somePos, modifier); HTH, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

templating usage of state<>
by Tony Turner 24 Jul '08

24 Jul '08

Greetings; PROBLEM: I have a need to call a 'post_event' from the ctor of a templated state that belongs to a templated machine. BEST SHOT AT SOLUTION SO FAR: ( items #1,#2 & #3 below work fine... item #4, my goal, fails) Request for specific assistance is in item #5 below. Thank you for your time and effort, I know you are very busy and appreciate the help. Regards, Tony Turner acturner01(a)comcast.net //************************************************************************ (1) I started with the following non-templated version, which works just fine: ... namespace sc = boost::statechart; namespace mpl = boost::mpl; ... // fwd decl struct Start; struct Inst : public sc::state_machine< Inst, Start > {}; struct Start : public sc::state< Start, Inst > { Start(my_context ctx ) : my_base( ctx ) {// do some stuff ...} }; // 'main' routine is.... BOOST_AUTO_TEST_CASE(testMyMachine) { Inst myMachine; myMachine.initiate(); } //************************************************************************ (2) I then templated the machine, with no problems, which is half way to my solution: // fwd decl struct NDIREV_17 {}; struct Start; template< typename I > struct Inst : public sc::state_machine< Inst, Start > {}; struct Start : public sc::state< Start, Inst1<NDIREV_17> > { Start(my_context ctx ) : my_base( ctx ) {} }; // 'main' routine is.... BOOST_AUTO_TEST_CASE(testMyMachine) { Inst<NDIREV_17> myMachine; myMachine.initiate(); } //************************************************************************ (3) I then templated the simple_state<> version, which works just fine. struct NDIREV_17 {}; template< typename I > struct Start; template< typename I > struct Inst : public sc::state_machine< Inst, Start > {}; template< typename I > struct Start : public sc::simple_state< Start, Inst > { }; // same 'main' //************************************************************************ (4) finally, I templated the state<> version, , which has problems. [NOTE: I've referenced line # 3773 below, to sync with output] struct NDIREV_17 {}; template< typename I > struct Start; template< typename I > struct Inst : public sc::state_machine< Inst, Start > {};[ line# 3773 ] template< typename I > struct Start : public sc::state< Start, Inst > { Start(my_context ctx ) : my_base( ctx ) {} }; // same 'main' //************************************************************************ (5) ATTEMPTS TO FIX: a) look @ code in state.hpp ( shown below ) and attempt to replace "my_context" & "my_base" with direct substitutions of "simple_state" and this->set_context.... no luck. REQUEST FOR HELP: Could someone who has successfully templated both the machine<> and the state<> classes possibly give me a hint as to what I might be able to do to fix this bug? Thank you for your time and effort; Tony Turner acturner01(a)comcast.net //************************************************************************ (6) state.hpp fragment // here is 'state<> fragment from state.hpp template< class MostDerived, class Context, class InnerInitial = mpl::list<>, history_mode historyMode = has_no_history > class state : public simple_state< MostDerived, Context, InnerInitial, historyMode > { typedef simple_state< MostDerived, Context, InnerInitial, historyMode > base_type; protected: ////////////////////////////////////////////////////////////////////////// struct my_context { my_context( typename base_type::context_ptr_type pContext ) : pContext_( pContext ) { } typename base_type::context_ptr_type pContext_; }; typedef state my_base; state( my_context ctx ) { this->set_context( ctx.pContext_ ); } ~state() {} ------------------------------------------------------------ ------------------------------------------------------------ Resulting Error msg: Device.hpp:3774: error: expected `)' before 'ctx' In file included from src/bin/UnitTestDevice.cpp:25: Device.hpp:3774: error: expected `)' before 'ctx' /usr/include/boost/statechart/state.hpp: In static member function 'static typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::inner_context_ptr_type boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::shallow_construct(const typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::context_ptr_type&, typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]': /usr/include/boost/statechart/state.hpp:79: instantiated from 'static void boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::deep_construct(const typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::context_ptr_type&, typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]' /usr/include/boost/statechart/state.hpp:70: instantiated from 'static void boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::initial_deep_construct(typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]' /usr/include/boost/statechart/state_machine.hpp:701: instantiated from 'void boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initial_construct() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' /usr/include/boost/statechart/state_machine.hpp:716: instantiated from 'boost::statechart::result boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initial_construct_function::operator()() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' /usr/include/boost/statechart/null_exception_translator.hpp:33: instantiated from 'boost::statechart::result boost::statechart::null_exception_translator::operator()(Action, ExceptionEventHandler) [with Action = boost::statechart::state_machine<MNavAnts::Inst1<MNavAnts::NDIREV_99>, MNavAnts::Start1<MNavAnts::NDIREV_99>, std::allocator<void>, boost::statechart::null_exception_translator>::initial_construct_function, ExceptionEventHandler = boost::statechart::state_machine<MNavAnts::Inst1<MNavAnts::NDIREV_99>, MNavAnts::Start1<MNavAnts::NDIREV_99>, std::allocator<void>, boost::statechart::null_exception_translator>::exception_event_handler]' /usr/include/boost/statechart/state_machine.hpp:253: instantiated from 'void boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initiate() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' src/bin/UnitTestDevice.cpp:870: instantiated from here /usr/include/boost/statechart/state.hpp:89: error: no matching function for call to 'MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1( boost::statechart::state<MNavAnts::Start1<MNavAnts::NDIREV_99>, MNavAnts::Inst1<MNavAnts::NDIREV_99>, boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, has_no_history>::my_context)' Device.hpp:3773: note: candidates are: MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1() Device.hpp:3773: note: MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1(const MNavAnts::Start1<MNavAnts::NDIREV_99>&) /usr/include/boost/statechart/state.hpp: In static member function 'static typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::inner_context_ptr_type boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::shallow_construct(const typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::context_ptr_type&, typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]': /usr/include/boost/statechart/state.hpp:79: instantiated from 'static void boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::deep_construct(const typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::context_ptr_type&, typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]' /usr/include/boost/statechart/state.hpp:70: instantiated from 'static void boost::statechart::state<MostDerived, Context, InnerInitial, historyMode>::initial_deep_construct(typename boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::outermost_context_base_type&) [with MostDerived = MNavAnts::Start1<MNavAnts::NDIREV_99>, Context = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InnerInitial = boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::statechart::history_mode historyMode = has_no_history]' /usr/include/boost/statechart/state_machine.hpp:701: instantiated from 'void boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initial_construct() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' /usr/include/boost/statechart/state_machine.hpp:716: instantiated from 'boost::statechart::result boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initial_construct_function::operator()() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' /usr/include/boost/statechart/null_exception_translator.hpp:33: instantiated from 'boost::statechart::result boost::statechart::null_exception_translator::operator()(Action, ExceptionEventHandler) [with Action = boost::statechart::state_machine<MNavAnts::Inst1<MNavAnts::NDIREV_99>, MNavAnts::Start1<MNavAnts::NDIREV_99>, std::allocator<void>, boost::statechart::null_exception_translator>::initial_construct_function, ExceptionEventHandler = boost::statechart::state_machine<MNavAnts::Inst1<MNavAnts::NDIREV_99>, MNavAnts::Start1<MNavAnts::NDIREV_99>, std::allocator<void>, boost::statechart::null_exception_translator>::exception_event_handler]' /usr/include/boost/statechart/state_machine.hpp:253: instantiated from 'void boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::initiate() [with MostDerived = MNavAnts::Inst1<MNavAnts::NDIREV_99>, InitialState = MNavAnts::Start1<MNavAnts::NDIREV_99>, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator]' src/bin/UnitTestDevice.cpp:870: instantiated from here /usr/include/boost/statechart/state.hpp:89: error: no matching function for call to 'MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1( boost::statechart::state<MNavAnts::Start1<MNavAnts::NDIREV_99>, MNavAnts::Inst1<MNavAnts::NDIREV_99>, boost::mpl::list<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, has_no_history>::my_context)' Device.hpp:3773: note: candidates are: MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1() Device.hpp:3773: note: MNavAnts::Start1<MNavAnts::NDIREV_99>::Start1(const MNavAnts::Start1<MNavAnts::NDIREV_99>&)

4 6

boost mutex 1.35.0 vs 1.34.0
by Vial, Florent 24 Jul '08

24 Jul '08

hi all, i was running happily with boost 1.34.0 under Win32, using boost::program_options, boost_filesystem, and boost::thread. i decided to update to 1.35.0. I had to fix some broken code (e.g. boost::filesystem::filesystem_error does not have a member system_error() anymore) which was ok. Tell me if I am wrong, but now if i want to use a tiny boost::mutex (#include <boost/thread/mutex.hpp>), not only have I to define WIN32_LEAN_AND_MEAN before the include to avoid cryptic error messages due to the inclusion of winsock.h though i am using winsock2.h, but also I must now link to boost_thread AND to boost_system ? is this right ? thank you for any useful insights, florent Arnold & Richter Cine Technik GmbH & Co. Betriebs KG Sitz: Munchen - Registergericht: Amtsgericht Munchen - Handelsregisternummer: HRA 57918 Personlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH Sitz: Munchen - Registergericht: Amtsgericht Munchen - Handelsregisternummer: HRB 54477 Geschaftsfuhrer: Prof. Dr. Dejan Ilic; Franz Kraus; Jens Schafer

2 1

Phoenix in 1.35.0
by Robert Jones 23 Jul '08

23 Jul '08

My understanding of the state of play with Phoenix is that the lovely Phoenix 2.0 is part of the not-yet-released Boost 1.36.0, and that the current release of Boost, 1.35.0 hosts Phoenix 1.2. Phoenix 2.0 has lovely documentation at http://spirit.sourceforge.net/dl_docs/phoenix-2/libs/spirit/phoenix/doc/htm… but the corresponding documentation for V1.2, at http://www.boost.org/doc/libs/1_35_0/libs/spirit/phoenix/index.html is buried inside the Spirit docs, and is not nearly as good as the v2.0 documentation. In particular the v1.2 docs are very quiet about specific include file paths, which have also changed significantly for v2.0. Is there anything I've missed in all this? ----------- Also looking through the documentation of Boost libraries in general, the quality varies widely. Am I correct in believing this is due to whether the various library authors have found time to write quality documentation? Regards, Rob. -- ACCU - Professionalism in programming - http://www.accu.org

2 1

[boost-users][multi-index] passing modifier by reference/pointer?
by Igor R 23 Jul '08

23 Jul '08

Hello, Is there a simple way to pass a modifier by reference/pointer in the following expression: my_multi_index_container.modify(somePos, modifier); "modifier" is a functor that has some internal state, so I wouldn't like it to be copied. Is it possible to do this without an explicit creation of a binder that binds operator() and &modifier (or so)? Thanks.

2 1

variant warnings?
by hfye-wila＠spamex.com 23 Jul '08

23 Jul '08

Does Boost.Variant require certain warnings to be disabled? The following program generates a warning for me with VC9: COMPILER INPUT: #include <boost/variant.hpp> #include <iostream> struct vis : public boost::static_visitor<> { void operator()( int & ) const { std::cout << "int" << std::endl; } void operator()( std::string & ) const { std::cout << "string" << std::endl; } }; int main( int, char * ) { boost::variant< int, std::string > v; boost::apply_visitor( vis(), v ); return 0; } COMPILER OUTPUT: 1>Compiling... 1>variant_basic.cpp 1>J:\work\ext\boost_ext\boost/variant/variant.hpp(894) : warning C4512: 'boost::detail::variant::invoke_visitor<Visitor>' : assignment operator could not be generated 1> with 1> [ 1> Visitor=const vis 1> ] 1> J:\work\ext\boost_ext\boost/variant/variant.hpp(1771) : see reference to class template instantiation 'boost::detail::variant::invoke_visitor<Visitor>' being compiled 1> with 1> [ 1> Visitor=const vis 1> ] 1> J:\work\ext\boost_ext\boost/variant/detail/apply_visitor_unary.hpp(72) : see reference to function template instantiation 'void boost::variant<T0_,T1>::apply_visitor<const Visitor>(Visitor &)' being compiled 1> with 1> [ 1> T0_=int, 1> T1=std::string, 1> Visitor=vis 1> ] 1> ..\indep\variant_basic.cpp(11) : see reference to function template instantiation 'void boost::apply_visitor<vis,boost::variant<T0_,T1>>(const Visitor &,Visitable &)' being compiled 1> with 1> [ 1> T0_=int, 1> T1=std::string, 1> Visitor=vis, 1> Visitable=boost::variant<int,std::string> 1> ]

2 5

[Test] Glue for Visual Studio automated unit testing
by Stephen Nuchia 23 Jul '08

23 Jul '08

Visual Studio 2008, in the pricier editions, has rich support for automated unit testing - of "managed" code units. Not much help with 4 million lines of native code! I've set up unit test projects within my overall solution. These build executables from source (using boost-test's default main() ) and run them using custom build step scripts. It's simple and it works but it does not tie into the test automation infrastructure. Test failures show up as build failures, and there's no direct support for things like test coverage analysis. It turns out, however, that if what you want to test has a COM or .NET interface, you can write a C# (or managed C++) test driver, reference the interface exported by the native code, and test away. But that doesn't help you unit test traditional libraries. What I'd like to do is to develop a .NET-visible wrapper for a boost-test unit test driver. This would allow us to author the actual tests in native C++ using boost-test, build and run the test suite as before if desired. We could, for instance, execute the test driver under the debugger to investigate a failure. But we could also drive the tests from a Visual Studio Test project. The simple thing to do would be to make each native test driver (with its entire suite of tests) one Studio-level test. It might be possible to expose the internal boost-test suite structure to the wrapper so the individual tests show up in the database; I'm not sure this is desirable and it would be more work. My main purpose in posting this note is to see if anybody out there is interested in working with me on this. Secondarily, I'd appreciate any advice from those more familiar with the guts of boost-test. What is the best place to hook in and what features does the exported interface (object model) need to expose? Because this effort targets special features found only in high-end versions of visual studio, it will not be of much interest to the majority of the readers of this list. I suggest folks send me email directly unless you think everyone needs to see it. -swn

3 2

Boost test support for "Abstract Test Pattern"
by Bruce Trask 23 Jul '08

23 Jul '08

Hi, Does the boost test framework provide facilities out of the box for the Abstract Test Pattern? http://c2.com/cgi/wiki?AbstractTest Thanks in advance. Regards, Bruce

3 3

Boost.Date_Time - How to measure time elapsed?
by Jean-Sebastien Stoezel 23 Jul '08

23 Jul '08

Hello, I've been struggling with how to use the Date_Time library to measure time elapsed (like to measure how long code takes to execute). Could somebody provide me with an example? Resolution should be around msec. I could not find any in the reference that particularly addresses this. Thanks! Jean

2 2

Re: [Boost-users] Boost.Date_Time - How to measure time elapsed?
by Igor R 23 Jul '08

23 Jul '08

// untested!! namespace pt = boost::posix_time; pt::ptime now1 = pt::microsec_clock::universal_time(); ///....do something here... pt::ptime now2 = pt::microsec_clock::universal_time(); pt::time_duration dur = now2 - now1; you can get then dur.total_milliseconds(); > I've been struggling with how to use the Date_Time library to measure > time elapsed (like to measure how long code takes to execute). > > Could somebody provide me with an example? Resolution should be around > msec. I could not find any in the reference that particularly > addresses this. >

1 0