|.NET Regular Expressions In Depth|
|Written by Mike James|
|Thursday, 16 July 2020|
Page 5 of 5
So far we have created regular expressions with the idea that we can use them to test that a string meets a specification or to extract a substring.
These are the two conventional uses of regular expressions. However you can also use them to perform some very complicated string editing and rearrangements.
The whole key to this idea is that notion that you can use the captures as part of the specified replacement string. The only slight problem is that the substitution strings use a slightly different syntax to a regular expression.
The Replace method:
simply takes every match of the associated regular expression and performs the substitution specified. Notice that it performs the substitution on every match and the result returned is the entire string with the substitutions made.
There are other versions of the Replace method but they all work in more or less the same way.
For example, if we define the regular expression:
and apply the following replacement:
then the ISBN suffix will be replaced by ISBN-13. Notice that an ISBN-13 suffix will also be replaced by ISBN-13 so making all ISBN strings consistent. Also notice that if there are multiple ISBNs within the string they will all be matched and replaced. There are versions of the method that allow you to restrict the number of matches that are replaced.
This is easy enough to follow and works well as long as you have defined your regular expression precisely enough. More sophisticated is the use of capture groups within the substitution string.
You can use:
to refer to capture group n or:
to refer to a capture group by name. There are a range of other substitution strings but these are fairly obvious in use.
As an example of how this all works consider the problem of converting a US format date to a UK format date. First we need a regular expression to match the mm/dd/yyyy format:
This isn’t a particularly sophisticated regular expression but we have allowed one or two digits for the month and day numbers but insisted on four for the year number. You can write a more interesting and flexible regular expression for use with real data. Notice that we have three named capture groups corresponding to month, day and year.
To create a European style date all we have to do assemble the capture groups in the correct order in a substitution string:
This substitutes the day, month and year capture groups in place of the entire matched string, i.e. the original date.
Regular expressions are addictive in a way that can ultimately be unproductive.
It isn’t worth spending days crafting a single regular expression that matches all variations on a string when building one or two simpler alternatives and using a wider range of string operations would do the same job as well if not as neatly.
Resist the temptation to write regular expressions that you only just understand and always make sure you test them with strings that go well outside of the range of inputs that you consider correct – greedy matching and backtracking often result in the acceptance of a wider range of strings that was originally intended.
If you take care, however, regular expressions are a very powerful way of processing and transforming text without the need to move to a complete syntax analysis package.
TIf you would like to suggest a topic for our Core C# section or if you have any comments contact our C# editor Mike James.
or email your comment to: firstname.lastname@example.org
|Last Updated ( Thursday, 16 July 2020 )|