7 Apr
2008
7 Apr
'08
1:56 p.m.
But introducing an outermost context (say Active ) which all substates have in common and moving state_machine transit functions there should be the right approach, shouldn't be?
Right. Keep in mind though, that state_machine<> declares other functions you might want to hide too: <http://www.boost.org/doc/libs/1_35_0/libs/statechart/doc/reference.html#Clas... mplatestate_machine>, e.g. state_begin(), state_end(), etc. That's why you often don't expose state_machine<> subclasses directly but wrap them in another object. Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.