http://www.stateworks.net/2008/07/getting-started/ StateWORKS blog about software engineering using virtual finite state machines Wed, 15 Sep 2010 17:51:43 +0200 http://wordpress.org/?v=2.8.4 hourly 1 http://www.stateworks.net/2008/07/getting-started/comment-page-1/#comment-7 John M Mon, 07 Jul 2008 13:22:23 +0000 http://stateworksnet.cmarc.net/2008/07/getting-started/#comment-7 Thanks Ferdinand! A further general question arising from Q3 (counter being reset in State A entry action) : Do entry actions of intermediate states get executed? I would think not. I can't tell from my test because (per your direct email) State A became effectively an intermediate state (at least until the executor stopped the loop) - yes? A. No, entry actions of all intermediate states are executed. If they have any effect on some control value (for instance the ResetCounter) this effect will come into being when the executor leaves the execution loop. Executor takes the virtual input and processes it until there is nothing more to do. When it returns to the point “wait for event” it takes the actualized virtual input and continues. It explains the behavior of your state machine. Thanks Ferdinand! A further general question arising from Q3 (counter being reset in State A entry action) : Do entry actions of intermediate states get executed? I would think not. I can’t tell from my test because (per your direct email) State A became effectively an intermediate state (at least until the executor stopped the loop) – yes?
A. No, entry actions of all intermediate states are executed. If they have any effect on some control value (for instance the ResetCounter) this effect will come into being when the executor leaves the execution loop. Executor takes the virtual input and processes it until there is nothing more to do. When it returns to the point “wait for event” it takes the actualized virtual input and continues. It explains the behavior of your state machine.

]]>