Databases
StackOverflow2013
Postsdbo
PObig vs. nested statemachines
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PObig vs. nested statemachines
    primarykey
    data
    text
    <p>I have a statemachine in a real-time system with very few (3) states.</p> <pre><code>typedef enum { STATE1, STATE2, STATE3 } state_t; </code></pre> <p>However, the transitions between those states need considerable time and have their own subdivisions. So I have two choices, either I extend the main statemachine such that all the intermediate states are represented:</p> <pre><code>typedef enum { STATE1, STATE1_PREPARE_TRANSITION_TO_STATE2, STATE1_DO_TRANSITION_TO_STATE2, STATE1_PREPARE_TRANSITION_TO_STATE3, STATE1_DO_TRANSITION_TO_STATE3, STATE2, ... } state_t; </code></pre> <p>or I create a nested statemachine for the relevant main states:</p> <pre><code>typedef enum { STATE1_NOT_ACTIVE, STATE1_NORMAL, STATE1_PREPARE_TRANSITION_TO_STATE2, STATE1_DO_TRANSITION_TO_STATE2, STATE1_PREPARE_TRANSITION_TO_STATE3, STATE1_DO_TRANSITION_TO_STATE3 } sub_state1_t; ... </code></pre> <p>Both possibilities have their advantages and drawbacks. The big statemachine gets messy and complicated very easily. However, having all the states consistent in the second case isn't trivial either and many functions would need information about both the global state and the substates.</p> <p>I'd like to avoid complicated code which has to handle several parallel states, like:</p> <pre><code>if ((global_state == STATE1) &amp;&amp; (sub_state_1 == STATE1_DO_TRANSITION_TO_STATE2)) { ... if (transition_xy_done(...)) { global_state = STATE2; sub_state_1 = STATE1_NOT_ACTIVE; sub_state_2 = STATE2_NORMAL; } } </code></pre> <p>What is the general best approach for such a problem: many small and nested statemachines (with many invalid combinations), one big statemachine or anything else?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USgroovingandi
    1. USgroovingandi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PObig vs. nested statemachines
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PObig vs. nested statemachines
      1. USuser77115
      1. VTFavorite
    1. COHave you considered using a some state machine generator?
      singulars
      1. PObig vs. nested statemachines
      1. USHasturkun
    2. COIs there any generator tool that can decide whether one big or several nested state machines are better?
      singulars
      1. PObig vs. nested statemachines
      1. USgroovingandi
    3. COProbably not, but a generator might make it easier to design/maintain a large state machine.
      singulars
      1. PObig vs. nested statemachines
      1. USHasturkun
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload