Zend_Search_Lucene_FSMAbstract Finite State Machine
Take a look on Wikipedia state machine description: http://en.wikipedia.org/wiki/Finite_state_machine
Any type of Transducers (Moore machine or Mealy machine) also may be implemented by using this abstract FSM. process() methods invokes a specified actions which may construct FSM output. Actions may be also used to signal, that we have reached Accept State
Located in /Zend/Search/Lucene/FSM.php (line 43)
Zend_Search_Lucene_FSM
__construct
([array $states = array()], [array $inputAphabet = array()], [array $rules = array()])
void
addInputAction
(integer|string $state, $inputSymbol, Zend_Search_Lucene_FSMAction $action, integer|string $input)
void
addRule
(integer|string $sourceState, integer|string $input, integer|string $targetState, [Zend_Search_Lucene_FSMAction|null $inputAction = null])
void
addTransitionAction
(integer|string $sourceState, integer|string $targetState, Zend_Search_Lucene_FSMAction $action)
Constructor __construct (line 141)
Finite State machine constructor
$states is an array of integers or strings with a list of possible machine states constructor treats fist list element as a sturt state (assignes it to $_current state). It may be reassigned by setState() call. States list may be empty and can be extended later by addState() or addStates() calls.
$inputAphabet is the same as $states, but represents input alphabet it also may be extended later by addInputSymbols() or addInputSymbol() calls.
$rules parameter describes FSM transitions and has a structure: array( array(sourseState, input, targetState[, inputAction]), array(sourseState, input, targetState[, inputAction]), array(sourseState, input, targetState[, inputAction]), ... ) Rules also can be added later by addRules() and addRule() calls.
FSM actions are very flexible and may be defined by addEntryAction(), addExitAction(), addInputAction() and addTransitionAction() calls.
addEntryAction (line 287)
Add state entry action.
Several entry actions are allowed. Action execution order is defined by addEntryAction() calls
addExitAction (line 308)
Add state exit action.
Several exit actions are allowed. Action execution order is defined by addEntryAction() calls
addInputAction (line 330)
Add input action (defined by {state, input} pair).
Several input actions are allowed. Action execution order is defined by addInputAction() calls
addInputSymbol (line 217)
Add symbol to the input alphabet
addInputSymbols (line 205)
Add symbols to the input alphabet
addRule (line 251)
Add symbol to the input alphabet
addRules (line 235)
Add transition rules
array structure: array( array(sourseState, input, targetState[, inputAction]), array(sourseState, input, targetState[, inputAction]), array(sourseState, input, targetState[, inputAction]), ... )
addState (line 165)
Add state to the state machine
addStates (line 153)
Add states to the state machine
addTransitionAction (line 358)
Add transition action (defined by {state, input} pair).
Several transition actions are allowed. Action execution order is defined by addTransitionAction() calls
getState (line 195)
Get FSM state.
process (line 384)
Process an input
reset (line 424)
setState (line 181)
Set FSM state.
No any action is invoked
Documentation generated on Wed, 21 Feb 2007 11:49:35 -0800 by phpDocumentor 1.3.1