What kind of interface / API would you be interested in seeing? How would you want to use said module?
in reply to Are state machines just for parsing?
The reason I ask is that I've built state machines for several projects and they were different enough that I don't think I could've used a generic solution / framework. For example, I've used state machines to
- perform actions in a basic scripting language
- handle events that have been defined to fire when X occurs
- be the engine for a web application (both before I found CGI::Application and with it)
It's kinda like trying to build a module for the Schwartzian Transform or the Guttman-Rosler Transform (GRT). It's good to know the pattern, but making a generic version just complicates the matter. Or, put another way, we'd almost have to write another mini-language to have a state machine. And, we already have that with regexes.
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.