Lines Matching refs:lexical
157 * Rpcalc Lexer:: The lexical analyzer.
173 * Ltcalc Lexer:: The lexical analyzer.
1260 @cindex lexical analyzer, purpose
1277 The tokens come from a function called the @dfn{lexical analyzer} that
1279 parser calls the lexical analyzer each time it wants a new token. It
1281 may reflect this). Typically the lexical analyzer makes the tokens by
1288 additional functions. One is the lexical analyzer. Another is an
1298 functions such as the lexical analyzer function @code{yylex}, the
1334 Write a lexical analyzer to process input and pass tokens to the parser.
1335 The lexical analyzer may be written by hand in C (@pxref{Lexical, ,The
1390 You need to declare the lexical analyzer @code{yylex} and the error
1450 * Rpcalc Lexer:: The lexical analyzer.
1597 grammatical error is seen or the lexical analyzer says there are no more
1690 @cindex writing a lexical analyzer
1691 @cindex lexical analyzer, writing
1693 The lexical analyzer's job is low-level parsing: converting characters
1695 tokens by calling the lexical analyzer. @xref{Lexical, ,The Lexical
1698 Only a simple lexical analyzer is needed for the RPN
1700 lexical analyzer skips blanks and tabs, then reads in numbers as
1705 The return value of the lexical analyzer function is a numeric code which
1710 character literal in the lexical analyzer to express the number. If the
1724 Here is the code for the lexical analyzer:
1728 /* The lexical analyzer returns a double floating point
2046 most of the work needed to use locations will be done in the lexical
2052 * Ltcalc Lexer:: The lexical analyzer.
2162 tracking. The next step is to rewrite the lexical analyzer, and make it
2223 Basically, the lexical analyzer performs the same processing as before:
2262 only single-character literals. The lexical analyzer @code{yylex} passes
3251 Declarations}). If you don't do that, the lexical analyzer has to
5007 calling convention is used for the lexical analyzer function
5633 lexical analyzer function.
5636 lexical analyzer function.
6061 @cindex lexical analyzer
6063 The @dfn{lexical analyzer} function, @code{yylex}, recognizes tokens from
6066 call it. The function is sometimes referred to as a lexical scanner.
7776 file I/O, the lexical analysis performed by the scanner, and the user's
8080 once again commence. The next symbol returned by the lexical scanner is
8185 There is some similarity between this technique and a lexical tie-in
8186 (described next), in that information which alters the lexical analysis is
8189 program. A true lexical tie-in has a special-purpose flag controlled by
8194 @cindex lexical tie-in
8196 One way to handle context-dependency is the @dfn{lexical tie-in}: a flag
8295 being aborted or not. So if you are using a lexical tie-in, you had better
11906 User-supplied lexical analyzer function, called with no arguments to get
12180 the syntax structure of a set of tokens passed to it from a lexical
12238 the lexical analyzer. @xref{Symbols}.