When state gets out of hand, I know of three options: 1. Put a constraint solver over it so that the programmer describes rulesets instead of state "paths". Re

When state gets out of hand, I know of three options: 1. Put a constraint solver over it so that the programmer describes rulesets instead of state "paths". Regex rules like the Kleene star's backtracking are a simple example of such. 2. Put a compiler over it so that boilerplate "if" statements are generated from a smaller description. E.g. FSM compilers are one way of doing this. Years ago I read of an implementation of TCP/IP (which I can no longer find) built from a custom parser that read the actual text of the RFC spec and generated output source code. 3. Enumerate everything in an enormous decision table so that the spec is tighter.