Lines Matching full:matched
53 * Matching:: How the input is matched
107 How The Input Is Matched
108 the rules for determining what has been matched
111 how to specify what to do when a pattern is matched
196 By default, any text not matched by a `flex' scanner is copied to
444 an R but only if it is followed by an S. The text matched by S is
447 executed. So the action only sees the text matched by R. This
577 How the input is matched
591 corresponding to the matched pattern is then executed (a more detailed
596 character in the input is considered matched and copied to the standard
650 action is empty, then when the pattern is matched the input token is
658 they will be matched by the default rule.)
700 rule which matched the input (or a prefix of the input). The rule
701 is chosen as described above in "How the Input is Matched", and
703 which matched as much text as the originally chosen rule but came
704 later in the `flex' input file, or one which matched less text.
749 First "mega-" is matched and echoed to the output. Then "kludge"
750 is matched, but the previous "mega-" is still hanging around at
804 `%array' instead (see How The Input Is Matched).
1466 is always executed prior to the matched rule's action. For example, it
1469 number of the matched rule (rules are numbered starting with 1).
1470 Suppose you want to profile how often each of your rules is matched.
1622 --accepting rule at line 53 ("the matched text")
1643 ignored, and tokens in the input will be matched regardless of
1644 case. The matched text given in `yytext' will have the preserved
1728 token has been matched if it absolutely must. It turns out that
2126 which is matched. With a bit of head-scratching one can see that this
2202 longer the tokens matched, the faster the scanner will run. This is
2235 to keep the matched text as long as possible. Note that *adding* rules
2318 section How the Input is Matched, dynamically resizing `yytext' to
2353 returns the text of the most recently matched token, the
2357 returns the length of the most recently matched token, the
2551 to read characters following whatever has been matched by a rule.
2631 token is matched, unless the scanner was built using `%array'.
2698 `warning, rule cannot be matched'
2699 indicates that the given rule cannot be matched because it follows
2701 example, in the following "foo" cannot be matched because it comes
2709 `warning, -s option given but default rule can be matched'
2727 wasn't matched by any of its rules. This error can also occur due
2731 your scanner uses `%array' and one of its rules matched a string
2800 Some trailing context patterns cannot be properly matched and
2805 draft states that the text matched by such patterns is undefined.)
2827 rescanning all the text matched so far by the current (generally huge)
2835 of table entries needed to determine what rule has been matched. The
