Regular expressions
In computing, a regular expression is a string that is used to describe or match a set of strings, according to certain syntax rules. A regular expression is simply a string that describes a pattern.
String =~ m/regex/; #matches 0 or 1
There are two types, text-directed or regex-directed engine. You can do the test by applying the regex regex|regex not to the string regex not. If the resulting match is only regex, the engine is regex-directed. If the result is regex not, then it is text-directed. The reason behind this is that the regex-directed engine is "eager". Perl and PHP are regex-directed engines, they will always match at the earliest possible point in the string. See How Regexes Work for details.
Regular expressions generally involve two stages in parsing, the first stage involves variable substitution, in the second sage the pattern and string are sent to the RE engine.
Regular expression engies are token engines where a token is an assertion or an atom. An assertion tests some property of the string, zero width assertions such as \b are termed assertions whereas assertions with nonzero-width are atoms, such as any W:ASCII or W:binary character. Internally the token engine matches from left to right a string to a regular expression pattern consuming the string whether the match is satisfied or not.
- When a regexp can match a string in several different ways, we can use the principles above to predict which way the regexp will match
- Principle 0: Taken as a whole, any regexp will be matched at the earliest possible position in the string.
- Principle 1: In an alternation a|b|c... , the leftmost alternative that allows a match for the whole regexp will be the one used.
- Principle 2: The maximal matching quantifiers ?, * , + and {n,m} will in general match as much of the string as possible while still allowing the whole regexp to match.
- Principle 3: If there are two or more elements in a regexp, the leftmost greedy quantifier, if any, will match as much of the string as possible while still allowing the whole regexp to match. The next leftmost greedy quantifier, if any, will try to match as much of the string remaining available to it as possible, while still allowing the whole regexp to match. And so on, until all the regexp elements are satisfied.
An example
<perl>
"Hello World" =~ m/World/; # matches
</perl> What is this perl statement all about? "Hello World" is a simple double quoted string. World is the regular expression and the // enclosing m/World/ tells perl to search a string for a match. The operator =~ associates the string with the regexp match and produces a true value if the regexp matched, or false if the regexp did not match. In our case, World matches the second word in "Hello World" , so the expression is true.
Wikipedia provides a useful overview of regular expressions and their history.
Perl one liners
If you type; <perl> perl --help </perl> on the command line, perl will provide details on its usage and command line switches. The switches we are interested in are
-d[:debugger] run program under debugger
-e program one line of program (several -e's allowed, omit programfile)
-n assume 'while (<>) { ... }' loop around program
Using -e switch
<perl>
- Unix/Linux
perl -e 'print "It matches\n" if "Hello World" =~ /World/;'
- Windows
perl -e "print \"It matches\n\" if "Hello World" =~ /World/;" </perl>
- See string literals for details on differences between single and double quotes.
Using -de switch
To initiate the debugger for a one line program type; <perl> perl -de 42
- Returns an interactive shell within the perl debugger
DB<1>
</perl> Now type 'h' to obtain for help commands used within the debugger. Commands useful for one liners in the debugger are;
'x' to eval an expression in list context, and print the result. 'q' to quit
See also
Tutorials
Reference books
Engines
- Perl compatible regular expressions (PCRE)
- TRE Regular expression engine in C
- DEELX Regular expression engine in C++/DEELX
