When implementing a state machine using Boost.Statechart, I ran into a problem related to trying to access the external context simple_statefrom my constructor. The comment in simple_state.hpptells me:
simple_state
simple_state.hpp
// This assert fails when an attempt is made to access an outer // context from a constructor of a state that is *not* a subtype of // state<>. To correct this, derive from state<> instead of // simple_state<>.
Besides being able to access the external context from my constructor, what differences or consequences exist when used state<>instead of simple_state<>as a base class for my states?
state<>
simple_state<>
, state < > , simple_state < > . . , < > .
, , , - , , , ( ), < > from simple_state < > .
Source: https://habr.com/ru/post/1782113/More articles:JHAT не может анализировать дамп памяти - javaPassing Mercurial (Hg) branch to GitHub - gitHow to read a file from a website using objective-c & xcode - objective-cПочему мое использование контекста(). Method() нарушает утверждение statechart? - boostJava - confuse one rule for each file - javareview / history of resident memory usage - memory-managementRecommended web technologies for WPF developer? - c #Проблема в понимании некоторых аспектов "Онтологии пиццы" - protegeHow do you compare music data - javaRun the command "stty raw" in the same terminal? - javaAll Articles