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

Re: [Boost-users] [statechart] Is it possible to have nested (sub)states in an asynchronous state machine?
by Gurcan Gulesir 09 Jun '11

09 Jun '11

Hi Andreas, I realized that some lines in my previously posted listings were wrapped by my e-mail client. Since this may cause compilation problems for you, I hereby attach the source code files for your convenience. Thanks & Regards, Gurcan

1 0

Re: [Boost-users] [statechart] Is it possible to have nested (sub)states in an asynchronous state machine?
by Igor R 09 Jun '11

09 Jun '11

> Upon your request, I wrote a small but complete program that demonstrates > the issue. This program consists of 5 source code files: > > 1) main.cpp > 2) StateMachine.hpp > 3) StateMachine.cpp > 4) SuperState.hpp > 5) SubState.hpp You've got a compiler error, not a linker one, right? If so, why do you need 2 translation units and 5 files to reproduce it? I belive, you can reproduce it in one single file, which we could just copy&paste into an empty file, and try to compile. It should go like this: // states definition... // machine definition... int main() { // machine instantiation }

1 0

Re: [Boost-users] [statechart] Is it possible to have nested (sub)states in an asynchronous state machine?
by Gurcan Gulesir 09 Jun '11

09 Jun '11

Hi Andreas, Many thanks for your help first of all! Upon your request, I wrote a small but complete program that demonstrates the issue. This program consists of 5 source code files: 1) main.cpp 2) StateMachine.hpp 3) StateMachine.cpp 4) SuperState.hpp 5) SubState.hpp The contents of these files are listed at the end of this e-mail. You should be able to compile these listings and then run the executable successfully. Depending on your compiler flags, you may receive one warning that says "/* within comment". This is intentional, so please ignore the warning. To reproduce my problem regarding the nesting of states, please modify the listings in three locations, as explained in the comments in SuperState.hpp and SubState.hpp, and then re-compile. You should receive multiple errors pointing to the Boost Statechart library. Looking forward to your feedback. Thanks & Regards, Gurcan ---------------------------------------- 1) main.cpp ---------------------------------------- #include <iostream> #include <boost/bind.hpp> #include <boost/function.hpp> #include <boost/thread/thread.hpp> #include <boost/statechart/asynchronous_state_machine.hpp> #include <boost/statechart/fifo_worker.hpp> #include "StateMachine.hpp" int main() { std::cout<<"\n\nPress any key and then <CR> to exit\n\n"<<std::endl; char key; boost::statechart::fifo_scheduler<> scheduler(true); boost::statechart::fifo_scheduler<>::processor_handle handle = scheduler.create_processor<StateMachine> (); scheduler.initiate_processor(handle); boost::thread aThread(boost::bind(&boost::statechart::fifo_scheduler<>::operator(),&schedu ler, 0)); std::cin >> key; scheduler.destroy_processor(handle); scheduler.terminate(); aThread.join(); return 0; } ---------------------------------------- 2) StateMachine.hpp ---------------------------------------- #ifndef StateMachine_hpp #define StateMachine_hpp #include <boost/statechart/asynchronous_state_machine.hpp> class StateMachine; class SuperState; namespace boost { namespace statechart { template<> inline void asynchronous_state_machine<StateMachine, SuperState>::initiate_impl() {} }} class StateMachine: public boost::statechart::asynchronous_state_machine<StateMachine, SuperState> { public: StateMachine(my_context ctx) : my_base(ctx) {} private: virtual void initiate_impl(); }; #endif ---------------------------------------- 3) StateMachine.cpp ---------------------------------------- #include <boost/statechart/state_machine.hpp> #include "StateMachine.hpp" #include "SuperState.hpp" void StateMachine::initiate_impl() { boost::statechart::state_machine<StateMachine, SuperState>::initiate(); } ---------------------------------------- 4) SuperState.hpp ---------------------------------------- #ifndef SuperState_hpp #define SuperState_hpp #include <iostream> #include <boost/statechart/simple_state.hpp> #include "StateMachine.hpp" #include "SubState.hpp" class StateMachine; class SubState; //MODIFICATION 1 of 3: UNCOMMENT THE FOLLOWING LINE //class SuperState: public boost::statechart::simple_state<SuperState, StateMachine, SubState> { //MODIFICATION 2 of 3: COMMENT OUT THE FOLLOWING LINE class SuperState: public boost::statechart::simple_state<SuperState, StateMachine> { public: SuperState(){ std::cout<<"Entered into SuperState."<<std::endl; } }; #endif ---------------------------------------- 5) SubState.hpp ---------------------------------------- //MODIFICATION 3 of 3: COMMENT OUT THE FOLLOWING LINE /* #ifndef SubState_hpp #define SubState_hpp #include <iostream> #include <boost/statechart/simple_state.hpp> #include "SuperState.hpp" class SuperState; class SubState: public boost::statechart::simple_state<SubState, SuperState> { public: SubState(){ std::cout<<"Enteres into SubState."<<std::endl; } }; #endif /**/

1 0

Using lamdba for vector of array initialization
by Alexander Khomyak 09 Jun '11

09 Jun '11

Hi. I have vector of boost array: typedef boost::array<char, 10> array10; typedef std::vector<array10> vector_of_array10; vector_of_array10 v; v.resize(10); Now I initialize it using for statement: for(vector_of_array10::iterator i = v.begin(); i != v.end(); ++i) (*i)[0] = '\0'; How can I do the same initialization using lambda expression and for_each? In advance thank you very much for the tip.

2 3

Re: [Boost-users] [statechart] Is it possible to have nested (sub)states in an asynchronous state machine?
by Andreas Huber 09 Jun '11

09 Jun '11

Hi [snip] > I started to > suspect that the statechart library does not support the > nesting of states > in an asynchronous state machine. Am I right or am I missing > something? Probably the latter: Asynchronous state machines should be able to deal with nested states just like synchronous ones. Please post a small but complete program that demonstrates the issue. Thanks & Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.

1 0

Regex no longer builds with toolset=sun
by Will Mason 08 Jun '11

08 Jun '11

Hello, The last version of Boost that successfully builds on Solaris x86 32-bit with the Sun compiler (toolset sun) was version 1.43. Are there any plans to fix this toolset going forward? Thank you, Will Mason

6 10

[statechart] Is it possible to have nested (sub)states in an asynchronous state machine?
by Gurcan Gulesir 08 Jun '11

08 Jun '11

Hi, I am trying to implement an asynchronous state machine whose states contain substates. Since my compilation errors seem to be related to the statechart library (instead of directly to the code I wrote myself), I started to suspect that the statechart library does not support the nesting of states in an asynchronous state machine. Am I right or am I missing something? Upon trying any combination of boost::statechart::state and boost::statechart::simple_state as the super class of the top-level states and sub states, the typical compilation errors I received are like the following: 'deep_construct' is not a member of 'boost::statechart::simple_state<MostDerived, Context, InnerInitial, historyMode>::deep_construct_inner_impl_non_empty::deep_construct_inner_impl (const boost::intrusive_ptr<T>&, typename Context::inner_context_type::outermost_context_base_type&) [with InnerList = boost::mpl::list<robot::RobotSM::SCOUTING, 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>, MostDerived = robot::RobotSM::CONNECTED_WITH_OPERATOR, Context = robot::RobotSM::RobotSM, InnerInitial = robot::RobotSM::SCOUTING, boost::statechart::history_mode historyMode = (boost::statechart::history_mode)0u]::current_inner' RobotBehavior line 894, external location: /usr/include/boost/statechart/simple_state.hpp C/C++ Problem 'class boost::statechart::simple_state<robot::RobotSM::SAFE_TO_MOVE, robot::RobotSM::CONNECTED_WITH_OPERATOR, 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)0u>' has no member named 'deferred_events' RobotBehavior line 360, external location: /usr/include/boost/statechart/simple_state.hpp C/C++ Problem 'class boost::statechart::state<robot::RobotSM::SAFE_TO_MOVE, robot::RobotSM::CONNECTED_WITH_OPERATOR, 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)0u>' has no member named 'set_context' RobotBehavior line 50, external location: /usr/include/boost/statechart/state.hpp C/C++ Problem If nested states are intentionally not supported in current Boost.Statechart, is there a fundamental reason for this restriction? Or is it just not yet implemented as a feature of asynchronous state machines? Many thanks for your response, in advance. Best regards, Gurcan

1 0

More Boostcon videos available
by Marshall Clow 08 Jun '11

08 Jun '11

Sumant (Mondau): http://blip.tv/boostcon/toward-native-xml-processing-using-multi-paradigm-d… Justin (Tuesday): http://blip.tv/boostcon/intel-s-c-software-transactional-memory-compiler-an… Robert Stewart (Tuesday): http://blip.tv/boostcon/spirit-qi-in-the-real-world-5254335 ( I'm not going to be able to keep up this pace, btw...... ) -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

1 0

[Thread] unresolved typeref token for 'boost.detail.win32._SECURITY_ATTRIBUTES' using /clr
by Daniele Barzotti 08 Jun '11

08 Jun '11

Hi, I try to build my C++ library with the /clr option to make it visible to managed world. I get a linker error: warning LNK4248: unresolved typeref token (01000027) for 'boost.detail.win32._SECURITY_ATTRIBUTES'; image may not run I found the ticket#2226 (https://svn.boost.org/trac/boost/ticket/2226) which say that 'Boost thread does not work with managed C++ when statically linked.' How can I solve this issue? I need to link it dynamically? Regards, Daniele.

1 0

BGL edge iteration questions
by David Doria 08 Jun '11

08 Jun '11

1) When is it appropriate to use adjacency_list directly vs using directed_graph and undirected_graph? 2) I am trying to iterate over the edges of a directed_graph: http://codepad.org/jO3rJLtF In the first method I tried: typedef boost::graph_traits < Graph >::out_edge_iterator out_edge_iterator; std::pair<out_edge_iterator, out_edge_iterator> outEdges = boost::out_edges(v1, g); , memory addresses seem to be output instead of vertex ids. In the second method: typedef boost::property_map<Graph, boost::vertex_index_t>::type IndexMap; IndexMap index = get(boost::vertex_index, g); , vertex ids are output, but I didn't specify if I wanted in edges or out edges? When using adjacency_list directly, I used to have to specify boost::bidirectionalS: typedef boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS> Graph; Is something like that required when using directed_graph? Thanks, David

2 2