[boost-users][StateChart] deferring events
Hello,
I noticed that if I declare an event as deferred in a "parent" state
(unintentionally), and define the reaction in some "indirect" inner
state, then this reaction has no chance to be called.
Is this the correct behavior or a bug?
Example (pseudo-code):
struct Parent : simple_state<..., Inner1>
{
defer Ev1; //of course, this is unnecessary; but if this an error?
if I leave this line, then when we come to Inner1_3, the Ev1 is *not*
processed; if I remove this line, everything is ok!
};
struct Inner1
{
defer Ev1;
transit
Hi Igor
I noticed that if I declare an event as deferred in a "parent" state (unintentionally), and define the reaction in some "indirect" inner state, then this reaction has no chance to be called. Is this the correct behavior or a bug? [snip pseudo code]
This looks like a bug, could you please post a repro? Thanks & Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.
Hi Andreas,
I couldn't reproduce it on some trivial FSMs, so I'll try and extract
the "minimal reproducing" piece out of my code, but it will take some
time.
Thank you,
Igor'.
2008/8/6, Andreas Huber
Hi Igor
I noticed that if I declare an event as deferred in a "parent" state (unintentionally), and define the reaction in some "indirect" inner state, then this reaction has no chance to be called. Is this the correct behavior or a bug? [snip pseudo code]
This looks like a bug, could you please post a repro?
Thanks & Regards,
-- Andreas Huber
When replying by private email, please remove the words spam and trap from the address shown in the header.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
I couldn't reproduce it on some trivial FSMs, so I'll try and extract the "minimal reproducing" piece out of my code, but it will take some time.
If it's easier for you, you can also send a more than minimal (but compileable) repro by private email, the bug should be fairly easy to reproduce even if the FSM is huge. Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.
participants (2)
-
Andreas Huber -
Igor R