Here is sample code which attempts to replicate the diagram, but just for the A state (the B state is not included, which would be trivial to do): ------------------------------------------------------------------------------------------------------------------------------------ #include <iostream> #include <thread> #include #include #include #include namespace msm = boost::msm; namespace msmf = boost::msm::front; namespace mpl = boost::mpl; // Events struct timeout {}; struct outer_:msmf::state_machine_def { struct inner_:msmf::state_machine_def { template void on_entry(Event const&, Fsm&) { std::cout << "[state machine entry] inner" << std::endl; } struct A:msmf::state<> { template void on_entry(Event const&, Fsm& f) { std::cout << "[state entry] A" << std::endl; stop_threads_ = false; thread_ = new std::thread(&A::func,this); } template void on_exit(Event const&, Fsm&) { stop_threads_ = true; thread_->join(); // wait for threads to finish delete thread_; std::cout << "[state exit] A" << std::endl; } void func() { while (!stop_threads_) { usleep(1000000); std::cout << "Hello" << std::endl; // QUESTION: how to call process_event(timeout()) here? } } public: std::thread* thread_; bool stop_threads_; }; struct Action { template void operator()(Event const&, Fsm&, SourceState&, TargetState&) { std::cout << "Trying again..." << std::endl; } }; typedef A initial_state; struct transition_table:mpl::vector< msmf::Row > {}; }; typedef msm::back::state_machine inner; typedef inner initial_state; }; typedef msm::back::state_machine outer; void waiting_thread() { while(true) { usleep(2000000); } } int main() { outer sm; sm.start(); std::thread wait(waiting_thread); wait.join(); } ------------------------------------------------------------------------------------------------------------------------------------ Please see the comment `// QUESTION: how to call process_event(timeout()) here?`. How can I call process_event from inside the func() function in Boost MSM? Thank you, Danylo. On Tue, Mar 21, 2017 at 2:26 PM, degski via Boost wrote:

On 21 March 2017 at 14:35, Danylo Malyuta via Boost

...

wrote:

...

Thanks for your input. I'm going to use std::thread for the parallel functionality, I think. How stable/complete is Asynchronous? Can I rely on it, or would I still have a moderate chance of running into bugs?

I still think you're over-engineering the thing, use std:thread and std::chrono. A simple loop will do what you desribed as your requirement, while limiting your dependencies... simpler generally means faster and easier to debug. Obviously this state, AB-state as I called it, can be part of a bigger picture, with (a) state machine(s).

degski

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/ mailman/listinfo.cgi/boost