Hi- while this might be fairly easy to do given the way seq does its
internal bookkeeping, seems to me it would muck up the relatively
clean
DFA state-machine model we have now. I've handled cases like you
describe
(e.g. an "ABORT" button that allows interrupting a long series of
states)
by adding extra intermediate states, as in:
state A
{
entry {
flag = OK;
}
when (<event>) {
if (trouble) flag = BUBU;
} state A_check
}
state A_check
{
when (flag == BUBU) { /* uh oh! */
} state A_abort
when () {
} state B /* next state */
}
The "out-of-order" transitions I mentioned referred to a future
debugging
environment, where it might be useful to interactively force a
transition
to an arbitrary state.
