Re: [rFSM] only check guard if the transition is triggered by an event (#2)
Markus Klotzbuecher <[email protected]> Fri, 24 Jan 2014 10:55:57 +0100
| Newsgroups | gmane.science.robotics.orocos.devel |
|---|---|
| Message-ID | <20140124095557.GA21384@PMA-10-048> |
Hi Ruben,
Sorry for the late reply, I never check this channel, better send these
things to orocos-dev...
On Mo, Okt 21, 2013 at 12:53:33 -0700, Ruben Smits wrote:
>With this pull request guards will only be checked if the transition is
>triggered by an event in case a transition has both events and guards.
What is your motivation for this change, performance optimization? The
issue is the following: the events table is just a "convencience thing"
to cater the most common use case. However, the guard function is the
"real-thing". In the long run, I want to get rid of the 'events' table
and replace it with an event model, that then gets transformed into
guards. So in the end there will be only guards and nothing else. A
second issue is your patch would break the "await" extension, which
translates a special event "await('e1', 'e2')" into a guard condition
which only returns true after both e1 and w2 are received.
Best regards
Markus
--
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev