Lines Matching full:lexical
156 * Lexer: Rpcalc Lexer. The lexical analyzer.
172 * Lexer: Ltcalc Lexer. The lexical analyzer.
231 * Lexical:: You must supply a function @code{yylex}
238 The Lexical Analyzer Function @code{yylex}
271 * Lexical Tie-ins:: Token parsing can depend on the syntactic context.
272 * Tie-in Recovery:: Lexical tie-ins have implications for how
1204 @cindex lexical analyzer, purpose
1219 The tokens come from a function called the @dfn{lexical analyzer} that
1221 parser calls the lexical analyzer each time it wants a new token. It
1223 may reflect this). Typically the lexical analyzer makes the tokens by
1225 @xref{Lexical, ,The Lexical Analyzer Function @code{yylex}}.
1230 the lexical analyzer. Another is an error-reporting function which the
1239 such as the lexical analyzer function @code{yylex}, the error reporting
1275 Write a lexical analyzer to process input and pass tokens to the parser.
1276 The lexical analyzer may be written by hand in C (@pxref{Lexical, ,The
1277 Lexical Analyzer Function @code{yylex}}). It could also be produced
1331 You need to declare the lexical analyzer @code{yylex} and the error
1391 * Lexer: Rpcalc Lexer. The lexical analyzer.
1530 grammatical error is seen or the lexical analyzer says there are no more
1619 @subsection The @code{rpcalc} Lexical Analyzer
1620 @cindex writing a lexical analyzer
1621 @cindex lexical analyzer, writing
1623 The lexical analyzer's job is low-level parsing: converting characters
1625 tokens by calling the lexical analyzer. @xref{Lexical, ,The Lexical
1628 Only a simple lexical analyzer is needed for the @acronym{RPN}
1630 lexical analyzer skips blanks and tabs, then reads in numbers as
1635 The return value of the lexical analyzer function is a numeric code which
1640 character literal in the lexical analyzer to express the number. If the
1654 Here is the code for the lexical analyzer:
1658 /* The lexical analyzer returns a double floating point
1959 most of the work needed to use locations will be done in the lexical
1965 * Lexer: Ltcalc Lexer. The lexical analyzer.
2067 @subsection The @code{ltcalc} Lexical Analyzer.
2070 tracking. The next step is to rewrite the lexical analyzer, and make it
2129 Basically, the lexical analyzer performs the same processing as before:
2168 only single-character literals. The lexical analyzer @code{yylex} passes
2785 Declarations}). If you don't do that, the lexical analyzer has to
4094 calling convention is used for the lexical analyzer function
4369 * Lexical:: You must supply a function @code{yylex}
4452 @node Lexical
4453 @section The Lexical Analyzer Function @code{yylex}
4455 @cindex lexical analyzer
4457 The @dfn{lexical analyzer} function, @code{yylex}, recognizes tokens from
4460 call it. The function is sometimes referred to as a lexical scanner.
6002 once again commence. The next symbol returned by the lexical scanner is
6023 * Lexical Tie-ins:: Token parsing can depend on the syntactic context.
6024 * Tie-in Recovery:: Lexical tie-ins have implications for how
6103 There is some similarity between this technique and a lexical tie-in
6104 (described next), in that information which alters the lexical analysis is
6107 program. A true lexical tie-in has a special-purpose flag controlled by
6110 @node Lexical Tie-ins
6111 @section Lexical Tie-ins
6112 @cindex lexical tie-in
6114 One way to handle context-dependency is the @dfn{lexical tie-in}: a flag
6166 @section Lexical Tie-ins and Error Recovery
6168 Lexical tie-ins make strict demands on any error recovery rules you have.
6215 being aborted or not. So if you are using a lexical tie-in, you had better
8410 User-supplied lexical analyzer function, called with no arguments to get
8411 the next token. @xref{Lexical, ,The Lexical Analyzer Function
8574 @item Lexical analyzer (scanner)
8576 @xref{Lexical, ,The Lexical Analyzer Function @code{yylex}}.
8578 @item Lexical tie-in
8580 tokens are parsed. @xref{Lexical Tie-ins}.
8605 the syntax structure of a set of tokens passed to it from a lexical
8663 the lexical analyzer. @xref{Symbols}.
