Big state machines
Fri Apr 15 15:01:39 CEST 2005
Joel Reymont wrote:
> I'm implementing my poker logic as a gen_fsm behavior. I'm finding that
> my FSM is getting a bit unwieldy, though, what with all the tests I have
> to write for different state transitions, etc.
> I'm wondering if there's an idiomatic way of splitting big FSMs into
> smaller chunks. Should I move the processing code into different modules
> and leave just invocations in the FSM callback module?
The eXAT agent programming platform that I've written allows agent
behaviours to be programmed by means of hierarchical FSMs, also using
You may take a loot at
The version that can be downloaded is old, but please contact me for the
new release, if you are interested.
Eng. Corrado Santoro, Ph.D.
University of Catania - Engineering Faculty
Department of Computer Science and
Viale A. Doria, 6 - 95125 CATANIA (ITALY)
Tel: +39 095 7382144 Int. (5) 8035
+39 095 7382380
+39 095 7382365
+39 095 7382364
Fax: +39 095 7382397
Personal Home Page:
NUXI Home Page:
More information about the erlang-questions