Iain K. Hanson wrote:
I'd love to see a DSL ( Domain Specific Language ) for state charts that generated Alexsey style FSMs with states able to be defined in seperate compilation units. This would solve the scaleabilty problems.
If you're talking about this http://boost-consulting.com/boost/libs/mpl/example/fsm/player2.cpp then there is nothing to put in separate TUs because states are numbers. Probably, you mixed states up with transitions. This is more a problem of proposed Boost.FSM then yours. In my opition, too many things are put in state definition and too much a user has to remember: 1 curiously recurring template pattern 2 forward declaration of events 3 state context 4 transitions and other reactions 5 other advanced features (only for advanced user) I think some of them should be defined somewhere else. -- Alexander Nasonov