What is a Lexer ? known also as Tokenizer or Scanner - Lexical Analysis

About

Lexer are also known as:

• Lexical analyzer
• Lexical Tokenizer
• Lexical Scanner

Example

Consider the following expression:

sum = 3 + 2;

A lexer will tokenized it in the following symbol table:

Definition

A lexer defines how the contents of a file is broken into tokens.

A lexer reads an input character or byte stream (i.e. characters, binary data, etc.), divides it into tokens using:

• patterns (rules) specified in a grammar file or in the code.
• and generates a token stream as output.

This process of transforming an input text into discrete components called tokens is known as:

• lexical analysis,
• lexing
• tokenizing
• or simply scanning.

A Lexer is a stateful stream generator (ie the position in the source file is saved). Every time it is advanced, it returns the next token in the Source. Normally, the final Token emitted by the lexer is a EOF and it will repeatedly return the same EOF token whenever called.

Lexical analysis is the first step of a compiler. In the second step, the tokens can then then processed by a parser.

Lexers are generally quite simple and does nothing with the tokens. Most of the complexity is deferred to the following steps:

• parsing
• or semantic analysis ¹⁾ (seeing if there is a problem, a possible optimization, …)

For example, a typical lexical analyzer recognizes parentheses as tokens, but does nothing to ensure that each “(” is matched with a “)”. This syntax analysis is left to the parser.

Steps

Tokenizing is generally done in a single pass.

1. Reads in a input stream of characters from a scanner
2. Groups the characters into meaningful sequences called lexemes that adheres to the grammar. Tokens are frequently in the rule defined by regular expressions.
3. Categorize each lexeme (sequence of characters) into tokens (symbols of the vocabulary of the language). If the lexer finds an invalid token, it will report an error.

Why not using simply a regular expression (Lexer vs Regexp)

Why not using simply a regular expression

• lack of recursion: You cannot have a regular expression inside another one, therefore you can't define any tree. Some regular expression engine allows recursion but this is the exception not the norm and the expressiveness is limited.
• no lexical mode: The lexical mode (or context) is important when you want your parsing rules to be applied conditionally. The most obvious being for instance a html pre where you don't want any parsing inside.

^{2) 3)}