Am 02.09.2012 um 16:20 schrieb Justin Cormack:
FSMs are something that have a lot of personal style choices, and Lua
is pretty flexible so any of them will work.
First, I would define the guards as functions, not strings. Then at
least you get to get syntax checking on them before runtime. So you
will want to name all the states (eg counters) so you can refer to
them in these.
Personally I like to define everything in an fsm as a function, so
each state is a function. Because Lua has proper tail recursion you
can just call the next state (in _javascript_ you have to use a
trampoline). Labels are fine too, but I find you can reuse state logic
by using parameterized functions and other things like that. Also I
like functions...
Thanks for your hints - can you give me an example?
