Microsoft & .NETVisual C#Understanding Basic Regular Expressions Patterns

Understanding Basic Regular Expressions Patterns

When I began writing about the .NET implementation of regular expressions, I intended to focus solely on the .NET classes and not on regular expressions themselves. To that end, I started with a couple of very basic tasks that can be formed with regular expressions: splitting strings with the Regex::Split method and using the Match and MatchCollection methods to enumerate found literals or patterns.

Many readers wrote in explaining that they are new to regular expressions, and they want at least an article or two that explain some basic patterns–instead of having all the examples search for literals or unexplained patterns. Therefore, this article presents some very basic regular expression patterns to get people who are new to this area off and running.

Searching for Letters and Words

The first thing to note is that regular expression patterns consist of metacharacters, which are simply characters that represent other characters and tell the regular expressions parser how to scan the input string and what to search for.

The following sections illustrate some basic patterns that utilize some of the more commonly used metacharacters. The end of the article presents a table that you can use as a metacharacter quick-reference when creating your own patterns.

Here’s a basic string that all the example patterns in this article use:

John and Harry are members of the Borbon club.

Now, suppose you want to locate all the proper nouns in this sentence. Logically, you would know that you need to locate every capitalized word. In terms of a regular expression pattern, that would look like the following:

[A-Z][a-z]+[ ]*

If you’re new to regular expressions, this definitely will look a bit strange at first. The following breakdown explains each of the pattern’s components:

[A-Z]

The A-Z indicates that you’re looking for any letter within the range of a capital A to a capital Z. The square brackets simply group this like the parenthesis in a numeric equation to remove ambiguity.
[a-z]+

Once again, a range of characters is being searched for, this time the lower case letters a-z. However, the plus sign (+) after the right bracket indicates that the parser will search for one match to the criteria specified in the brackets. In other words, the parser is being instructed to look for one or more lowercase letters.
[ ]*

This part of the pattern indicates that a space will be located, but the asterisk after the right bracket indicates that the parser will match on zero or any number of spaces. This allows for the pattern to properly handle the end of a string or multiple spaces between words.

So there you have it. The following pattern simply states “Find a capital letter, followed by one or more lowercase letters, followed by any number of spaces.”

[A-Z][a-z]+[ ]*

Using this pattern results in the following list of matches:

John
Harry
Borbon

However, the pattern has two problems. First, it will not catch capitalized abbreviations or acronyms, as it stipulates that only one capital letter will be matched, followed by lowercase letters. Therefore, the current pattern used on the following input value will not yield the match for IBM:

John and Harry are members of the Borbon club at IBM

To fix this problem, you need to modify the pattern as follows where I’ve bolded change:

[A-Z][A-Z|a-z]+[ ]*

What I’ve inserted into this pattern is the A-Z range and the vertical bar separator (|), which acts as an “or” operator. Therefore, the pattern now states: “Find a single capital letter followed by one or more upper and lower case letters followed by any number of spaces”. The pattern will now yield the following:

John
Harry
Borbon
IBM

The second problem that the pattern has is it doesn’t handle singular pronouns correctly. This is the easiest problem to solve. All you need to do is replace the plus sign in the pattern with an asterisk, so that the parser knows that there may not be a sequence of letters following the capital letter. Using an input value of: “John, Harry and I are members of the Borbon club at IBM.”, the pattern would be as follows:

[A-Z][A-Z|a-z]*[ ]*

It would yield:


John
Harry
I
Borbon
IBM

As promised, the following table contains the most commonly used metacharacters.

 
Table 1: Commonly used regular expressions metacharacters

Expression Description
. Matches any character except n
[characters] Matches a single character in the list
[^characters] Matches a single character not in the list
[charX-charY] Matches a single character in the specified range
w Matches a word character, same as [a-zA-Z_0-9]
W Matches a non-word character
s Matches a whitespace character; same as [nrtf]
S Matches a non-whitespace character
d Matches a decimal digit; same as [0-9]
D Matches a nondigit character
^ Match the beginning of a line
$ Match the end of a line
b On a word boundary
B Not on a word boundary
* Zero or more matches
+ One or more matches
? Zero or one match
{n} Exactly n matches
{n,} At least n matches
{n,m} At least n but no more than m matches
( ) Capture matched substring
(?) Capture matched substring into group name
| Logical OR

Simply combine these metacharacters with what you learned in the previous articles on string splitting and using the Match and MatchCollection classes and you’ll be surprised at how easily you can search for many basic patterns.

More Advanced Uses of Regular Expressions

At this point, you have the basic knowledge required to form regular expressions and use them in your Managed C++ code. While what you’ve learned thus far will work for a lot of common parsing needs, regular expressions allow you to do so much more than search for simple character patterns. For example, you can:

  • Search for email addresses where the number of valid formats leads to very complex patterns
  • Search and replace specific patterns
  • Extract specific information, such as searching for phone numbers and then extracting only the area code

In order to move into these more advanced areas of regular expressions use, you’ll need to know about groups and captures. Therefore, future articles will cover these areas and examine some of the tasks mentioned in this article.

Download the Code

To download the code for the demo application, click here.

About the Author

Tom Archer owns his own training company, Archer Consulting Group, which specializes in educating and mentoring .NET programmers and providing project management consulting. If you would like to find out how the Archer Consulting Group can help you reduce development costs, get your software to market faster, and increase product revenue, contact Tom through his Web site.

Get the Free Newsletter!
Subscribe to Developer Insider for top news, trends & analysis
This email address is invalid.
Get the Free Newsletter!
Subscribe to Developer Insider for top news, trends & analysis
This email address is invalid.

Latest Posts

Related Stories