FASimulator should accept a DFA as constructor parameter and that can't be
changed once after the FASimulator has been constructed. It should also
provide basic functionality to "use" the underlying DFA.
DFA class simply represents a finite state machine. It doesn't deal with
how the machine is executed. And this is just what a FASimulator does. It
keeps a current state variable, which is used to track the current state.
It can accept a serious of inputs and returns the state of the underlying
DFA after that serious of inputs.
DFA is usually refered as FASimulator. But in our case, we differentiate
them as that DFA is just the underlying data structure used to present that
finite state machine, while it doesn't provide the "behaviour" of that
state machine.
Original issue reported on code.google.com by lemontree.cool on 23 Aug 2008 at 1:49
Original issue reported on code.google.com by
lemontree.cool
on 23 Aug 2008 at 1:49