Talk:Event-driven finite-state machine

Removed text

I removed the following from the article, as it appears to be unencyclopeadic, and/or confusing or strange:

The author of StateCHARTS uses the term event driven finite state machine to describe machines where any incoming input has to be consumed immediately, i.e. the FSM has to perform a transition or input action otherwise the input disappears.

In contrast to the StateCHART virtual finite state machine (VFSM) technology, the application of event driven FSM in complex systems leads to the state explosion problem, as each truly required state path must be repeated for all possible input values. Event driven FSM can be implemented with a state transition table as is often done for parser applications.

A significant reduction in complexity can be achieved by utilizing hierarchy a la hierarchical state machines (HSMs). The use of hierarchy eliminates the "state explosion" problem by allowing a single transition from multiple related states, through state nesting. A more rigorous definition of hierarchical state machines that includes an example can be found at http://www.quantum-leaps.com/resources/glossary.htm#HSM.

Possibly cite http://www.programmersheaven.com/2/Design-State-Machine-Engine (an example of someone speaking about event-driven state machines as an informal idiom)

Please don't re-insert without review. linas 21:40, 29 May 2007 (UTC)