Lines Matching full:state
10 # ICU Break Iterator Rule Parser State Table
12 # This state table is used when reading and parsing a set of RBBI rules
13 # The rule parser uses a state machine; the data in this file define the
14 # state transitions that occur for each input character.
24 # Here is the syntax of the state definitions in this file:
28 # input-char n next-state ^push-state action
29 # input-char n next-state ^push-state action
31 # | | | | |--- action to be performed by state machine
34 # | | | |--- Push this named state onto the state stack.
35 # | | | Later, when next state is specified as "pop",
36 # | | | the pushed state will become the current state.
38 # | | |--- Transition to this state if the current input character matches the input
40 # | | state to be popped from the state stack.
42 # | |--- When making the state transition specified on this line, advance to the next
46 # matches, peform the actions and go to the state specified on this line.
55 # start state, scan position is at the beginning of the rules file, or in between two rules.
235 # The state that branched to here must have pushed a return state
239 # The $ is consummed here rather than in the state that first detected it
265 # The action for this state invokes the UnicodeSet parser.
282 # follows the variable name. We get to this state when the variable name
293 # assign-end This state is entered when the end of the expression on the
295 # a pop; this state is pushed when the '=' in an assignment is found.
308 # errorDeath. This state is specified as the next state whenever a syntax error
309 # in the source rules is detected. Barring bugs, the state machine will never
311 # But, just in case, this state asks the state machine to exit.
