You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Boost SML, like other similar state machine libraries, seems to favor Mealy-style state machine over Moore. In Mealy representation, the action is defined at the edge rather than in the state itself. Is it intentional?
Also, I am aware that all Moore-style representation can be converted to Mealy-style manually. Such an algorithm is taught in computer science courses. Does Boost SML implement the conversion algorithm internally at -O3 compiler optimization level?
Aside: what I meant by Moore:
The text was updated successfully, but these errors were encountered:
Boost SML, like other similar state machine libraries, seems to favor Mealy-style state machine over Moore. In Mealy representation, the action is defined at the edge rather than in the state itself. Is it intentional?
Also, I am aware that all Moore-style representation can be converted to Mealy-style manually. Such an algorithm is taught in computer science courses. Does Boost SML implement the conversion algorithm internally at
-O3
compiler optimization level?Aside: what I meant by Moore:
The text was updated successfully, but these errors were encountered: