- •Introduction
- •Who This Book Is For
- •What This Book Covers
- •How This Book Is Structured
- •What You Need to Use This Book
- •Conventions
- •Source Code
- •Errata
- •p2p.wrox.com
- •What Are Regular Expressions?
- •What Can Regular Expressions Be Used For?
- •Finding Doubled Words
- •Checking Input from Web Forms
- •Changing Date Formats
- •Finding Incorrect Case
- •Adding Links to URLs
- •Regular Expressions You Already Use
- •Search and Replace in Word Processors
- •Directory Listings
- •Online Searching
- •Why Regular Expressions Seem Intimidating
- •Compact, Cryptic Syntax
- •Whitespace Can Significantly Alter the Meaning
- •No Standards Body
- •Differences between Implementations
- •Characters Change Meaning in Different Contexts
- •Regular Expressions Can Be Case Sensitive
- •Case-Sensitive and Case-Insensitive Matching
- •Case and Metacharacters
- •Continual Evolution in Techniques Supported
- •Multiple Solutions for a Single Problem
- •What You Want to Do with a Regular Expression
- •Replacing Text in Quantity
- •Regular Expression Tools
- •findstr
- •Microsoft Word
- •StarOffice Writer/OpenOffice.org Writer
- •Komodo Rx Package
- •PowerGrep
- •Microsoft Excel
- •JavaScript and JScript
- •VBScript
- •Visual Basic.NET
- •Java
- •Perl
- •MySQL
- •SQL Server 2000
- •W3C XML Schema
- •An Analytical Approach to Using Regular Expressions
- •Express and Document What You Want to Do in English
- •Consider the Regular Expression Options Available
- •Consider Sensitivity and Specificity
- •Create Appropriate Regular Expressions
- •Document All but Simple Regular Expressions
- •Document What You Expect the Regular Expression to Do
- •Document What You Want to Match
- •Test the Results of a Regular Expression
- •Matching Single Characters
- •Matching Sequences of Characters That Each Occur Once
- •Introducing Metacharacters
- •Matching Sequences of Different Characters
- •Matching Optional Characters
- •Matching Multiple Optional Characters
- •Other Cardinality Operators
- •The * Quantifier
- •The + Quantifier
- •The Curly-Brace Syntax
- •The {n} Syntax
- •The {n,m} Syntax
- •Exercises
- •Regular Expression Metacharacters
- •Thinking about Characters and Positions
- •The Period (.) Metacharacter
- •Matching Variably Structured Part Numbers
- •Matching a Literal Period
- •The \w Metacharacter
- •The \W Metacharacter
- •Digits and Nondigits
- •The \d Metacharacter
- •Canadian Postal Code Example
- •The \D Metacharacter
- •Alternatives to \d and \D
- •The \s Metacharacter
- •Handling Optional Whitespace
- •The \S Metacharacter
- •The \t Metacharacter
- •The \n Metacharacter
- •Escaped Characters
- •Finding the Backslash
- •Modifiers
- •Global Search
- •Case-Insensitive Search
- •Exercises
- •Introduction to Character Classes
- •Choice between Two Characters
- •Using Quantifiers with Character Classes
- •Using the \b Metacharacter in Character Classes
- •Selecting Literal Square Brackets
- •Using Ranges in Character Classes
- •Alphabetic Ranges
- •Use [A-z] With Care
- •Digit Ranges in Character Classes
- •Hexadecimal Numbers
- •IP Addresses
- •Reverse Ranges in Character Classes
- •A Potential Range Trap
- •Finding HTML Heading Elements
- •Metacharacter Meaning within Character Classes
- •The ^ metacharacter
- •How to Use the - Metacharacter
- •Negated Character Classes
- •Combining Positive and Negative Character Classes
- •POSIX Character Classes
- •The [:alnum:] Character Class
- •Exercises
- •String, Line, and Word Boundaries
- •The ^ Metacharacter
- •The ^ Metacharacter and Multiline Mode
- •The $ Metacharacter
- •The $ Metacharacter in Multiline Mode
- •Using the ^ and $ Metacharacters Together
- •Matching Blank Lines
- •Working with Dollar Amounts
- •Revisiting the IP Address Example
- •What Is a Word?
- •Identifying Word Boundaries
- •The \< Syntax
- •The \>Syntax
- •The \b Syntax
- •The \B Metacharacter
- •Less-Common Word-Boundary Metacharacters
- •Exercises
- •Grouping Using Parentheses
- •Parentheses and Quantifiers
- •Matching Literal Parentheses
- •U.S. Telephone Number Example
- •Alternation
- •Choosing among Multiple Options
- •Unexpected Alternation Behavior
- •Capturing Parentheses
- •Numbering of Captured Groups
- •Numbering When Using Nested Parentheses
- •Named Groups
- •Non-Capturing Parentheses
- •Back References
- •Exercises
- •Why You Need Lookahead and Lookbehind
- •The (? metacharacters
- •Lookahead
- •Positive Lookahead
- •Negative Lookahead
- •Positive Lookahead Examples
- •Positive Lookahead in the Same Document
- •Inserting an Apostrophe
- •Lookbehind
- •Positive Lookbehind
- •Negative Lookbehind
- •How to Match Positions
- •Adding Commas to Large Numbers
- •Exercises
- •What Are Sensitivity and Specificity?
- •Extreme Sensitivity, Awful Specificity
- •Email Addresses Example
- •Replacing Hyphens Example
- •The Sensitivity/Specificity Trade-Off
- •Sensitivity, Specificity, and Positional Characters
- •Sensitivity, Specificity, and Modes
- •Sensitivity, Specificity, and Lookahead and Lookbehind
- •How Much Should the Regular Expressions Do?
- •Abbreviations
- •Characters from Other Languages
- •Names
- •Sensitivity and How to Achieve It
- •Specificity and How to Maximize It
- •Exercises
- •Documenting Regular Expressions
- •Document the Problem Definition
- •Add Comments to Your Code
- •Making Use of Extended Mode
- •Know Your Data
- •Abbreviations
- •Proper Names
- •Incorrect Spelling
- •Creating Test Cases
- •Debugging Regular Expressions
- •Treacherous Whitespace
- •Backslashes Causing Problems
- •Considering Other Causes
- •The User Interface
- •Metacharacters Available
- •Quantifiers
- •The @ Quantifier
- •The {n,m} Syntax
- •Modes
- •Character Classes
- •Back References
- •Lookahead and Lookbehind
- •Lazy Matching versus Greedy Matching
- •Examples
- •Character Class Examples, Including Ranges
- •Whole Word Searches
- •Search-and-Replace Examples
- •Changing Name Structure Using Back References
- •Manipulating Dates
- •The Star Training Company Example
- •Regular Expressions in Visual Basic for Applications
- •Exercises
- •The User Interface
- •Metacharacters Available
- •Quantifiers
- •Modes
- •Character Classes
- •Alternation
- •Back References
- •Lookahead and Lookbehind
- •Search Example
- •Search-and-Replace Example
- •Online Chats
- •POSIX Character Classes
- •Matching Numeric Digits
- •Exercises
- •Introducing findstr
- •Finding Literal Text
- •Quantifiers
- •Character Classes
- •Command-Line Switch Examples
- •The /v Switch
- •The /a Switch
- •Single File Examples
- •Simple Character Class Example
- •Find Protocols Example
- •Multiple File Example
- •A Filelist Example
- •Exercises
- •The PowerGREP Interface
- •A Simple Find Example
- •The Replace Tab
- •The File Finder Tab
- •Syntax Coloring
- •Other Tabs
- •Numeric Digits and Alphabetic Characters
- •Quantifiers
- •Back References
- •Alternation
- •Line Position Metacharacters
- •Word-Boundary Metacharacters
- •Lookahead and Lookbehind
- •Longer Examples
- •Finding HTML Horizontal Rule Elements
- •Matching Time Example
- •Exercises
- •The Excel Find Interface
- •Escaping Wildcard Characters
- •Using Wildcards in Data Forms
- •Using Wildcards in Filters
- •Exercises
- •Using LIKE with Regular Expressions
- •The % Metacharacter
- •The _ Metacharacter
- •Character Classes
- •Negated Character Classes
- •Using Full-Text Search
- •Using The CONTAINS Predicate
- •Document Filters on Image Columns
- •Exercises
- •Using the _ and % Metacharacters
- •Testing Matching of Literals: _ and % Metacharacters
- •Using Positional Metacharacters
- •Using Character Classes
- •Quantifiers
- •Social Security Number Example
- •Exercises
- •The Interface to Metacharacters in Microsoft Access
- •Creating a Hard-Wired Query
- •Creating a Parameter Query
- •Using the ? Metacharacter
- •Using the * Metacharacter
- •Using the # Metacharacter
- •Using the # Character with Date/Time Data
- •Using Character Classes in Access
- •Exercises
- •The RegExp Object
- •Attributes of the RegExp Object
- •The Other Properties of the RegExp Object
- •The test() Method of the RegExp Object
- •The exec() Method of the RegExp Object
- •The String Object
- •Metacharacters in JavaScript and JScript
- •SSN Validation Example
- •Exercises
- •The RegExp Object and How to Use It
- •Quantifiers
- •Positional Metacharacters
- •Character Classes
- •Word Boundaries
- •Lookahead
- •Grouping and Nongrouping Parentheses
- •Exercises
- •The System.Text.RegularExpressions namespace
- •A Simple Visual Basic .NET Example
- •The Classes of System.Text.RegularExpressions
- •The Regex Object
- •Using the Match Object and Matches Collection
- •Using the Match.Success Property and Match.NextMatch Method
- •The GroupCollection and Group Classes
- •The CaptureCollection and Capture Class
- •The RegexOptions Enumeration
- •Case-Insensitive Matching: The IgnoreCase Option
- •Multiline Matching: The Effect on the ^ and $ Metacharacters
- •Right to Left Matching: The RightToLeft Option
- •Lookahead and Lookbehind
- •Exercises
- •An Introductory Example
- •The Classes of System.Text.RegularExpressions
- •The Regex Class
- •The Options Property of the Regex Class
- •Regex Class Methods
- •The CompileToAssembly() Method
- •The GetGroupNames() Method
- •The GetGroupNumbers() Method
- •GroupNumberFromName() and GroupNameFromNumber() Methods
- •The IsMatch() Method
- •The Match() Method
- •The Matches() Method
- •The Replace() Method
- •The Split() Method
- •Using the Static Methods of the Regex Class
- •The IsMatch() Method as a Static
- •The Match() Method as a Static
- •The Matches() Method as a Static
- •The Replace() Method as a Static
- •The Split() Method as a Static
- •The Match and Matches Classes
- •The Match Class
- •The GroupCollection and Group Classes
- •The RegexOptions Class
- •The IgnorePatternWhitespace Option
- •Metacharacters Supported in Visual C# .NET
- •Using Named Groups
- •Using Back References
- •Exercise
- •The ereg() Set of Functions
- •The ereg() Function
- •The ereg() Function with Three Arguments
- •The eregi() Function
- •The ereg_replace() Function
- •The eregi_replace() Function
- •The split() Function
- •The spliti() Function
- •The sql_regcase() Function
- •Perl Compatible Regular Expressions
- •Pattern Delimiters in PCRE
- •Escaping Pattern Delimiters
- •Matching Modifiers in PCRE
- •Using the preg_match() Function
- •Using the preg_match_all() Function
- •Using the preg_grep() Function
- •Using the preg_quote() Function
- •Using the preg_replace() Function
- •Using the preg_replace_callback() Function
- •Using the preg_split() Function
- •Supported Metacharacters with ereg()
- •Using POSIX Character Classes with PHP
- •Supported Metacharacters with PCRE
- •Positional Metacharacters
- •Character Classes in PHP
- •Documenting PHP Regular Expressions
- •Exercises
- •W3C XML Schema Basics
- •Tools for Using W3C XML Schema
- •Comparing XML Schema and DTDs
- •How Constraints Are Expressed in W3C XML Schema
- •W3C XML Schema Datatypes
- •Derivation by Restriction
- •Unicode and W3C XML Schema
- •Unicode Overview
- •Using Unicode Character Classes
- •Matching Decimal Numbers
- •Mixing Unicode Character Classes with Other Metacharacters
- •Unicode Character Blocks
- •Using Unicode Character Blocks
- •Metacharacters Supported in W3C XML Schema
- •Positional Metacharacters
- •Matching Numeric Digits
- •Alternation
- •Using the \w and \s Metacharacters
- •Escaping Metacharacters
- •Exercises
- •Introduction to the java.util.regex Package
- •Obtaining and Installing Java
- •The Pattern Class
- •Using the matches() Method Statically
- •Two Simple Java Examples
- •The Properties (Fields) of the Pattern Class
- •The CASE_INSENSITIVE Flag
- •Using the COMMENTS Flag
- •The DOTALL Flag
- •The MULTILINE Flag
- •The UNICODE_CASE Flag
- •The UNIX_LINES Flag
- •The Methods of the Pattern Class
- •The compile() Method
- •The flags() Method
- •The matcher() Method
- •The matches() Method
- •The pattern() Method
- •The split() Method
- •The Matcher Class
- •The appendReplacement() Method
- •The appendTail() Method
- •The end() Method
- •The find() Method
- •The group() Method
- •The groupCount() Method
- •The lookingAt() Method
- •The matches() Method
- •The pattern() Method
- •The replaceAll() Method
- •The replaceFirst() Method
- •The reset() Method
- •The start() Method
- •The PatternSyntaxException Class
- •Using the \d Metacharacter
- •Character Classes
- •The POSIX Character Classes in the java.util.regex Package
- •Unicode Character Classes and Character Blocks
- •Using Escaped Characters
- •Using Methods of the String Class
- •Using the matches() Method
- •Using the replaceFirst() Method
- •Using the replaceAll() Method
- •Using the split() Method
- •Exercises
- •Obtaining and Installing Perl
- •Creating a Simple Perl Program
- •Basics of Perl Regular Expression Usage
- •Using the m// Operator
- •Using Other Regular Expression Delimiters
- •Matching Using Variable Substitution
- •Using the s/// Operator
- •Using s/// with the Global Modifier
- •Using s/// with the Default Variable
- •Using the split Operator
- •Using Quantifiers in Perl
- •Using Positional Metacharacters
- •Captured Groups in Perl
- •Using Back References in Perl
- •Using Alternation
- •Using Character Classes in Perl
- •Using Lookahead
- •Using Lookbehind
- •Escaping Metacharacters
- •A Simple Perl Regex Tester
- •Exercises
- •Index
Visual Basic .NET and Regular Expressions
If you want to specify multiple options, you must separate the options with the word Or. So to specify case-insensitive matching that matches from right to left, you could use code such as the following:
myMatchCollection = Regex.Matches(inputString, myPattern, _
RegexOptions.IgnoreCase Or RegexOptions.RightToLeft)
Multiline Matching: The Effect on the ^ and $ Metacharacters
The ^ metacharacter normally matches the position before the first character at the beginning of a string, and the $ metacharacter normally matches the position after the last character at the end of a string.
When multiline matching is used, the ^ metacharacter matches the position before the first character at the beginning of each line, and the $ metacharacter matches the position after the last character on each line.
Inline Documentation Using the IgnorePatternWhitespace
Option
The IgnorePatternWhitespace option allows inline comments to be created that spell out the meaning of each part of the regular expression pattern.
Normally, when a regular expression pattern is matched, any whitespace in the pattern is significant. For example, a space character in the pattern is interpreted as a character to be matched. As a result of setting the IgnorePatternWhitespace option, all whitespace contained in the pattern is ignored, including space characters and newline characters. This allows a single pattern to be laid out to aid readability, to allow comments to be added, and to aid in maintenance of the regular expression pattern. To match a whitespace character, you can use the \s metacharacter.
In Visual Basic .NET, the syntax for adding inline comments is a little cumbersome. If you wanted to use the myRegex variable to match an alphabetic character followed by a numeric digit, you might typically write the following:
Dim myRegex = New Regex(“[A-Z]\d”)
However, to use the IgnorePatternWhitespace option to specify the same regular expression pattern and include comments inline, you must write something like the following:
Dim myRegex = New Regex( |
_ |
||
“[A-Z] (?# |
A character |
class to match an uppercase alphabetic character)” & _ |
|
“\d |
(?# |
followed by |
a numeric digit)”, & _ |
RegexOptions.IgnorePatternWhitespace)
The inline comments are preceded by the character sequence (?# and followed by a ) character. The Visual Basic .NET concatenation character, &, is used between the components of the pattern, and the line-continuation character (the underscore) is used to indicate that a statement is being continued on the following line.
505
Chapter 21
Try It Out |
Using the IgnorePatternWhitespace Option |
This example matches a U.S. Social Security number. The code contained in Module1.vb in the
IgnorePatternWhitespaceDemo project is shown here:
Imports |
System.Text.RegularExpressions |
|
||
Module Module1 |
|
|
|
|
Dim myRegex = _ |
|
|
||
New Regex _ |
|
|
|
|
|
(“^ |
(?# |
match the position before |
the first character)” & _ |
|
“\d{3} (?# |
Three numeric digits, followed by)” & _ |
||
|
“- |
(?# |
a literal hyphen)” & _ |
|
|
“\d{2} (?# |
then two numeric digits)” |
& _ |
|
|
“- |
(?# |
then a literal hyphen)” & |
_ |
|
“\d{4} (?# |
then two numeric digits)” |
& _ |
|
|
“$ |
(?# |
match the position after the last character)”, _ |
RegexOptions.IgnorePatternWhitespace) Sub Main()
Console.WriteLine(“Enter a string on the following line:”) Dim inputString = Console.ReadLine()
Dim myMatch = myRegex.Match(inputString) If myMatch.ToString.Length Then
Console.WriteLine(“The match, ‘“ & myMatch.Value & “‘ was found.”)
Else
Console.WriteLine(“There was no match”) End If
Console.WriteLine(“Press Return to close this application.”) Console.ReadLine()
End Sub
End Module
1.Create a new console application project in Visual Studio 2003. Name the project
IgnorePatternWhitespaceDemo.
2.Edit the code in the code window so that it matches the code in the preceding Module1.vb file. Save the code, and press F5 to run it.
3.At the command line, enter the test string 123-12-1234. Press Return, and inspect the results, as shown in Figure 21-11. Notice that there is a successful match.
Figure 21-11
4.In Visual Studio 2005, press F5 to run the code again.
5.At the command line, enter the test string A123-12-1234. Press Return, and inspect the results, as shown in Figure 21-12.
506
Visual Basic .NET and Regular Expressions
Figure 21-12
How It Works
The pattern to be matched, if written on a single line, is as follows:
^\d{3}-\d{2}-\d{4}
You may recognize this as a simple pattern that will match a valid U.S. Social Security number (SSN).
In this example, the pattern is written with inline comments when the myRegex variable is dimensioned. As you can see, it is much more complex to write the pattern in this way, but the inline comments make it easier for you or another developer to work out precisely what the pattern was intended to do.
The Visual Basic .NET syntax of (?# ... ) for inline comments is less clean than the simple # construct in Visual C# .NET, for example. I find that the Visual Basic .NET syntax tends to get in the way of readability of the comments. Lining up the left parentheses on each line helps maximize readability in Visual Basic .NET:
New Regex _ |
|
|
|
(“^ |
(?# |
match the position before |
the first character)” & _ |
“\d{3} (?# |
Three numeric digits, followed by)” & _ |
||
“- |
(?# |
a literal hyphen)” & _ |
|
“\d{2} (?# |
then two numeric digits)” |
& _ |
|
“- |
(?# |
then a literal hyphen)” & |
_ |
“\d{4} (?# |
then two numeric digits)” |
& _ |
|
“$ |
(?# |
match the position after the last character)”, _ |
|
RegexOptions.IgnorePatternWhitespace) |
|
||
|
|
|
|
The pattern is equivalent to ^\d{3}-\d{2}-\d{4}$ and so matches an SSN. Therefore, when the test string is 123-12-1234, there is a match, as indicated in Figure 21-11. This is under control of the If statement in the following code. When the Length property is not 0, a match has been found, so the myMatch variable’s Value property contains the matching sequence of characters:
If myMatch.ToString.Length Then
Console.WriteLine(“The match, ‘“ & myMatch.Value & “‘ was found.”)
When the Length property of myMatch.ToString is 0, no match has been found, and a message indicating that is output in the Else clause:
Else
Console.WriteLine(“There was no match”)
End If
Right to Left Matching: The RightToLeft Option
When using English, the normal progression of characters along a line is from left to right. In some other languages, the progression of characters is from right to left. To support use of regular expressions in such languages, the .NET Framework provides the functionality to conduct matching from right to
left. Unfortunately, my experience and that of others is that when using the RightToLeft option, the
matching behavior is not fully reliable.
507
Chapter 21
The Metacharacters Suppor ted in Visual Basic .NET
Visual Basic .NET has perhaps a more complete and extensive regular expressions implementation than any of the tools you have seen in earlier chapters of this book.
Much of the regular expression support in Visual Basic .NET can reasonably be termed standard. However, as with many Microsoft technologies, the standard syntax and techniques have been extended or modified in places.
The following table summarizes the metacharacters supported in Visual Basic .NET.
Metacharacter |
Description |
|
|
\d |
Matches a numeric digit. |
\D |
Matches any character except a numeric digit. |
\w |
Equivalent to the character class [A-Za-z0-9_]. |
\W |
Equivalent to the character class [^A-Za-z0-9_]. |
\b |
Matches the position at the beginning of a sequence of \w characters |
|
or at the end of a sequence of \w characters. Colloquially, \b is |
|
referred to as a word-boundary metacharacter. |
\B |
Matches a position that is not a \b position. |
\t |
Matches a tab character. |
\n |
Matches a newline character. |
\040 |
Matches an ASCII character, expressed in Octal notation. The |
|
metacharacter \040 matches a space character. |
\x020 |
Matches an ASCII character, expressed in hexadecimal notation. The |
|
metacharacter \x020 matches a space character. |
\u0020 |
Matches a Unicode character, expressed in hexadecimal notation |
|
with exactly four numeric digits. The metacharacter \u0020 matches |
|
a space character. |
[...] |
Matches any character specified in the character class. |
[^...] |
Matches any character but the characters specified in the character |
|
class. |
\s |
Matches a whitespace character. |
\S |
Matches any character that is not a whitespace character. |
^ |
Depending on whether the MultiLine option is set, it matches the |
|
position before the first character in a line or the position before the |
|
first character in a string. |
|
|
508
|
|
Visual Basic .NET and Regular Expressions |
|
|
|
|
Metacharacter |
Description |
|
|
|
|
$ |
Depending on whether the MultiLine option is set, it matches the |
|
|
position after the last character in a line or the position after the last |
|
|
character in a string. |
|
$number |
Substitutes the character sequence matched by the last occurrence of |
|
|
group number number. |
|
${name} |
Substitutes the character sequence matched by the last occurrence of |
|
|
the group named name. |
|
\A |
Matches the position before the first character in a string. Its behavior |
|
|
is not affected by the setting of the MultiLine option. |
|
\Z |
Matches the position after the last character in a string. Its behavior is |
|
|
not affected by the setting of the MultiLine option. |
|
\G |
Specifies that matches must be consecutive, without any intervening |
|
|
nonmatching characters. |
|
? |
A quantifier. Matches when there is zero or one occurrence of the pre- |
|
|
ceding character or group. |
|
* |
A quantifier. Matches when there are zero or more occurrences of the |
|
|
preceding character or group. |
|
+ |
A quantifier. Matches when there are one or more occurrences of the |
|
|
preceding character or group. |
|
{n} |
A quantifier. Matches when there are exactly n occurrences of the |
|
|
preceding character or group. |
|
{n,m} |
A quantifier. Matches when there are at least n occurrences and a |
|
|
maximum of m occurrences of the preceding character or group. |
|
(substring) |
Captures the contained substring. |
|
(?<name>substring) |
Captures the contained substring and assigns it a name. |
|
(?:substring) |
A non-capturing group. |
|
(?=...) |
A positive lookahead. |
|
(?!...) |
A negative lookahead. |
|
(?<=...) |
A positive lookbehind. |
|
(?<!...) |
A negative lookbehind. |
|
\N (where N is a number) |
A back reference to a numbered group. |
|
\k<name> |
A back reference that references a named back reference (same mean- |
|
|
ing as the following). |
|
\k’name’ |
A back reference that references a named back reference (same mean- |
|
|
ing as the preceding). |
|
! |
Alternation. |
|
(?imnsx-imnsx) |
An alternate technique to specify RegexOptions settings inline. |
|
|
|
509