[Boost-users] boost.statechart - a data driven state machine

[d...@kostiadis.com]

Hello all,

I'm using the statechart library to create a generic state machine that I can
reuse in a number of projects.

I'd like this state machine to be completely data driven because it will
massively simplify testing and experimenting with different behaviours (i.e.
I won't have to re-compile and produce new executables to try out a simple
change).

Instead of hard-coding all the states, events, transitions, etc., I would like
to read all those in from a config file (text, csv, xml, whatever).

I'm pretty sure I can't be the first person to want this.
Is there an implementation of this out there somewhere?
Are there any docs/links/etc. that will point me to the right direction?

Thank you in advance,
k.

_______________________________________________
Boost-users mailing list
Boost...@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users

[Andreas Huber]

[snip]

> I'd like this state machine to be completely data driven because it will

> massively simplify testing and experimenting with different behaviours (ie.

> I won't have to re-compile and produce new executables to try out a simple
change).
>
> Instead of hard-coding all the states, events, transitions, etc., I would like
> to read all those in from a config file (text, csv, xml, whatever).

Boost.Statechart deliberately does not support dynamic configurability. The rationale can be found here:

<http://www.boost.org/doc/libs/1_38_0/libs/statechart/doc/rationale.html#DynamicConfigurability>

Regards,

--
Andreas Huber

When replying by private email, please remove the words spam and trap
from the address shown in the header.