Practical Regular Expression Examples
You'll learn: How to construct real-world regular expressions for common programming tasks like identifiers, numbers, and email addresses.
Why This Matters
Now that you know regex syntax—unions, concatenation, character classes, Kleene star, and precedence—it's time to see how these operators combine to match practical patterns you'll encounter in compilers, validators, and text processors.
Common Token Patterns
Identifiers
Programming identifiers typically start with a letter or underscore, followed by letters, digits, or underscores:
[a-zA-Z_][a-zA-Z0-9_]*
The first character class handles the start requirement; the second (with Kleene star) allows zero or more valid continuation characters.
Numeric Literals
An unsigned integer is one or more digits:
[0-9]+
For optional sign and decimals:
(+|-)?[0-9]+(.[0-9]+)?
The first group is optional sign, mandatory digits, then an optional decimal part (dot plus more digits).
Email Patterns (Simplified)
A basic email validator might look like:
[a-zA-Z0-9._]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}
Local part (before @), at symbol, domain name, dot, and top-level domain of at least two letters. (Real email validation is much more complex!)
Whitespace
Matching spaces, tabs, or newlines:
( |\t|\n)+
This uses union to match any whitespace character, one or more times.
Building Intuition
Think of regex construction like assembling Lego blocks: character classes are your basic pieces, operators (star, plus, union) connect them, and parentheses group sub-patterns into reusable chunks.
Key Takeaway: Regular expressions solve practical tokenization problems by combining character classes, repetition operators, and alternation to precisely describe text patterns like identifiers, numbers, and structured formats.