{"id":269,"date":"2007-10-08T00:00:00","date_gmt":"2007-10-08T00:00:00","guid":{"rendered":"http:\/\/www.strongd.net\/?p=269"},"modified":"2007-10-08T00:00:00","modified_gmt":"2007-10-08T00:00:00","slug":"Perl Regular Expression Tutorial","status":"publish","type":"post","link":"https:\/\/www.strongd.net\/?p=269","title":{"rendered":"Perl Regular Expression Tutorial"},"content":{"rendered":"

Perl Regular Expression Tutorial<\/STRONG><\/FONT><\/DIV>
\n
 <\/DIV>
\n

\n

\n<\/DIV>
\n
<\/DIV>
\n

Contents<\/H2>
\n

    \n
  1. Overview<\/A>
    \n
  2. Simple Regular Expressions<\/A>
    \n
  3. Metacharacters<\/A>
    \n
  4. Forbidden Characters<\/A>
    \n
  5. Things To Remember<\/A> <\/LI><\/OL>
    \n


    \n


    \n

    \n<\/DIV>
    \n


    \n

    Overview<\/H2>
    \n
    A regular expression is a string of characters which tells the searcher which string (or strings) you are looking for. The following explains the format of regular expressions in detail. If you are familiar with Perl, you already know the syntax. If you are familiar with Unix, you should know that there are subtle differences between Perl’s regular expressions and Unix’ regular expressions. <\/DIV>
    \n

    Simple Regular Expressions<\/H3>
    \n
    In its simplest form, a regular expression is just a word or phrase to search for. For example, <\/DIV>
      gauss<\/PRE>
    \n
    would match any subject with the string “gauss” in it, or which mentioned the word “gauss” in the subject line. Thus, subjects with “gauss”, “gaussian” or “degauss” would all be matched, as would a subject containing the phrases “de-gauss the monitor” or “gaussian elimination.” Here are some more examples: <\/DIV>
      carbon<\/PRE>
    \n

    \n
    Finds any subject with the string “carbon” in its name, or which mentions carbon (or carbonization or hydrocarbons or carbon-based life forms) in the subject line. <\/DD><\/DL>
      hydro<\/PRE>
    \n

    \n
    Finds any subject with the string “hydro” in its name or contents. Subjects with “hydro”, “hydrogen” or “hydrodynamics” are found, as well as subjects containing the words “hydroplane” or “hydroelectric”. <\/DD><\/DL>
      oxy<\/PRE>
    \n

    \n
    Finds any subject with the string “oxy” in the subject line. This could be used to find subjects on oxygen, boxy houses or oxymorons. <\/DD><\/DL>
      top ten<\/PRE>
    \n

    \n
    Note that spaces may be part of the regular expression. The above expression could be used to find top ten lists. (Note that they would also find articles on how to stop tension.) <\/DD><\/DL>
    \n

    \n
    Metacharacters<\/H3>
    \n
    Some characters have a special meaning to the searcher. These characters are called metacharacters<\/EM>. Although they may seem confusing at first, they add a great deal of flexibility and convenience to the searcher. <\/DIV>
    \n
    The period<\/EM> (.<\/STRONG>) is a commonly used metacharacter. It matches exactly one character, regardless of what the character is. For example, the regular expression: 
      2,.-Dimethylbutane<\/PRE>
    \n
    will match “2,2-Dimethylbutane” and “2,3-Dimethylbutane”. Note that the period matches exactly one<\/EM> character– it will not match a string of characters, nor will it match the null string. Thus, “2,200-Dimethylbutane” and “2,-Dimenthylbutane” will not<\/EM> be matched by the above regular expression. <\/DIV>
    \n
    But what if you wanted to search for a string containing a period? For example, suppose we wished to search for references to pi. The following regular expression would not<\/EM> work: 
      3.14     (THIS IS WRONG!)<\/STRONG><\/PRE>
    \n
    This would indeed match “3.14”, but it would also match “3514”, “3f14”, or even “3+14”. In short, any string of the form “3×14”, where x is any character, would be matched by the regular expression above. <\/DIV>
    \n
    To get around this, we introduce a second metacharacter, the backslash<\/EM> (\\<\/STRONG>). The backslash can be used to indicate that the character immediately to its right is to be taken literally. Thus, to search for the string “3.14”, we would use: 
      3\\.14    (This will<\/EM> work.)<\/PRE>
    \n
    This is called “quoting”. We would say that the period in the regular expression above has been quoted. In general, whenever the backslash is placed before a metacharacter, the searcher treats the metacharacter literally rather than invoking its special meaning. <\/DIV>
    \n
    (Unfortunately, the backslash is used for other things besides quoting metacharacters. Many “normal” characters take on special meanings when preceded by a backslash. The rule of thumb is, quoting a metacharacter turns it into a normal character, and quoting a normal character may<\/EM> turn it into a metacharacter.)
    \n
    Let’s look at some more common metacharacters. We consider first the question mark<\/EM> (?<\/STRONG>). The question mark indicates that the character immediately preceding it either zero times or one time. Thus 
      m?ethane<\/PRE>
    \n
    would match either “ethane” or “methane”. Similarly, <\/DIV>
      comm?a<\/PRE>
    \n
    would match either “coma” or “comma”. <\/DIV>
    \n
    Another metacharacter is the star<\/EM> (*<\/STRONG>). This indicates that the character immediately to its left may be repeated any number of times, including zero. Thus 
      ab*c<\/PRE>
    \n
    would match “ac”, “abc”, “abbc”, “abbbc”, “abbbbbbbbc”, and any string that starts with an “a”, is followed by a sequence of “b”‘s, and ends with a “c”. <\/DIV>
    \n
    The plus<\/EM> (+<\/STRONG>) metacharacter indicates that the character immediately preceding it may be repeated one or more times. It is just like the star metacharacter, except it doesn’t match the null string. Thus 
      ab+c<\/PRE>
    \n
    would not<\/EM> match “ac”, but it would<\/EM> match “abc”, “abbc”, “abbbc”, “abbbbbbbbc” and so on. <\/DIV>
    \n
    Metacharacters may be combined. A common combination includes the period and star metacharacters, with the star immediately following the period. This is used to match an arbitrary string of any length, including the null string. For example: 
      cyclo.*ane<\/PRE>
    \n
    would match “cyclodecane”, “cyclohexane” and even “cyclones drive me insane.” Any string that starts with “cyclo”, is followed by an arbitrary string, and ends with “ane” will be matched. Note that the null string will be matched by the period-star pair; thus, “cycloane” would be matche by the above expression. <\/DIV>
    \n
    If you wanted to search for articles on cyclodecane and cyclohexane, but didn’t want to match articles about how cyclones drive one insane, you could string together three periods, as follows: 
      cyclo…ane<\/PRE>
    \n
    This would match “cyclodecane” and “cyclohexane”, but would not match “cyclones drive me insane.” Only strings eleven characters long which start with “cyclo” and end with “ane” will be matched. (Note that “cyclopentane” would not be matched, however, since cyclopentane has twelve characters, not eleven.) <\/DIV>
    \n
    Here are some more examples. These involve the backslash. Note that the placement of backslash is important. 
      a\\.*z<\/PRE>
    \n

    \n
    Matches any string starting with “a”, followed by a series of periods (including the “series” of length zero), and terminated by “z”. Thus, “az”, “a.z”, “a..z”, “a…z” and so forth are all matched.<\/DD><\/DL>
      a.\\*z<\/PRE>
    \n

    \n
    (Note that the backslash and period are reversed in this regular expression.)
    \n
    Matches any string starting with an “a”, followed by one arbitrary character, and terminated with “*z”. Thus, “ag*z”, “a5*z” and “a@*z” are all matched. Only strings of length four, where the first character is “a”, the third “*”, and the fourth “z”, are matched.<\/P><\/DD><\/DL>
      a\\++z<\/PRE>
    \n

    \n
    Matches any string starting with “a”, followed by a series of plus signs, and terminated by “z”. There must be at least one plus sign between the “a” and the “z”. Thus, “az” is not<\/EM> matched, but “a+z”, “a++z”, “a+++z”, etc. will be matched.<\/DD><\/DL>
      a\\+\\+z<\/PRE>
    \n

    \n
    Matches only the string “a++z”.<\/DD><\/DL>
      a+\\+z<\/PRE>
    \n

    \n
    Matches any string starting with a series of “a”‘s, followed by a single plus sign and ending with a “z”. There must be at least one “a” at the start of the string. Thus “a+z”, “aa+z”, “aaa+z” and so on will match, but “+z” will not.<\/DD><\/DL>
      a.?e<\/PRE>
    \n

    \n
    Matches “ace”, “ale”, “axe” and any other three-character string beginning with “a” and ending with “e”; will also match “ae”.<\/DD><\/DL>
      a\\.?e<\/PRE>
    \n

    \n
    Matches “ae” and “a.e”. No other string is matched.<\/DD><\/DL>
      a.\\?e<\/PRE>
    \n

    \n
    Matches any four-character string starting with “a” and ending with “?e”. Thus, “ad?e”, “a1?e” and “a%?e” will all be matched.<\/DD><\/DL>
      a\\.\\?e<\/PRE>
    \n

    \n
    Matches only “a.?e” and nothing else.<\/DD><\/DL>
    \n
    Earlier it was mentioned that the backslash can turn ordinary characters into metacharacters, as well as the other way around. One such use of this is the digit<\/EM> metacharacter, which is invoked by following a backslash with a lower-case “d”, like this: “\\d<\/STRONG>“. The “d” must be lower case<\/EM>, for reasons explained later. The digit metacharacter matches exactly one digit; that is, exactly one occurence of “0”, “1”, “2”, “3”, “4”, “5”, “6”, “7”, “8” or “9”. For example, the regular expression: <\/DIV>
      2,\\d-Dimethylbutane<\/PRE>
    \n
    would match “2,2-Dimethylbutane”, “2,3-Dimethylbutane” and so forth. Similarly, <\/DIV>
      1\\.\\d\\d\\d\\d\\d<\/PRE>
    \n
    would match any six-digit floating-point number from 1.00000 to 1.99999 inclusive. We could combine the digit metacharacter with other metacharacters; for instance, <\/DIV>
      a\\d+z<\/PRE>
    \n
    matches any string starting with “a”, followed by a string of numbers, followed by a “z”. (Note that the plus is used, and thus “az” is not matched.) <\/DIV>
    \n
    The letter “d” in the string “\\d<\/STRONG>” must be lower-case. This is because there is another metacharacter, the non-digit<\/EM> metacharacter, which uses the uppercase “D”. The non-digit metacharacter looks like “\\D<\/STRONG>” and matches any character except<\/EM> a digit. Thus, 
      a\\Dz<\/PRE>
    \n
    would match “abz”, “aTz” or “a%z”, but would not<\/EM> match “a2z”, “a5z” or “a9z”. Similarly, <\/DIV>
      \\D+<\/PRE>
    \n
    Matches any non-null string which contains no<\/EM> numeric characters. <\/DIV>
    \n
    Notice that in changing the “d” from lower-case to upper-case, we have reversed the meaning of the digit metacharacter. This holds true for most other metacharacters of the format backslash-letter.
    \n
    There are three other metacharacters in the backslash-letter format. The first is the word<\/EM> metacharacter, which matches exactly one letter, one number, or the underscore character (_<\/CODE>). It is written as “\\w<\/STRONG>“. It’s opposite, “\\W<\/STRONG>“, matches any one character except<\/EM> a letter, a number or the underscore. Thus, 
      a\\wz<\/PRE>
    \n
    would match “abz”, “aTz”, “a5z”, “a_z”, or any three-character string starting with “a”, ending with “z”, and whose second character was either a letter (upper- or lower-case), a number, or the underscore. Similarly, <\/DIV>
      a\\Wz<\/PRE>
    \n
    would not<\/EM> match “abz”, “aTz”, “a5z”, or “a_z”. It would<\/EM> match “a%z”, “a{z”, “a?z” or any three-character string starting with “a” and ending with “z” and whose second character was not a letter, number, or underscore. (This means the second character must either be a symbol or a whitespace character.) <\/DIV>
    \n
    The whitespace<\/EM> metacharacter matches exactly one character of whitespace. (Whitespace is defined as spaces, tabs, newlines, or any character which would not use ink if printed on a printer.) The whitespace metacharacter looks like this: “\\s<\/STRONG>“. It’s opposite, which matches any character that is not<\/EM> whitespace, looks like this: “\\S<\/STRONG>“. Thus, 
      a\\sz<\/PRE>
    \n
    would match any three-character string starting with “a” and ending with “z” and whose second character was a space, tab, or newline. Likewise, <\/DIV>
      a\\Sz<\/PRE>
    \n
    would match any three-character string starting with “a” and ending with “z” whose second character was not<\/EM> a space, tab or newline. (Thus, the second character could be a letter, number or symbol.) <\/DIV>
    \n
    <\/P>
    \n
    The word boundary<\/EM> metacharacter matches the boundaries of words; that is, it matches whitespace, punctuation and the very beginning and end of the text. It looks like “\\b<\/STRONG>“. It’s opposite searches for a character that is not<\/EM> a word boundary. Thus: <\/DIV>
      \\bcomput<\/PRE>
    \n
    will match “computer” or “computing”, but not “supercomputer” since there is no spaces or punctuation between “super” and “computer”. Similarly, <\/DIV>
      \\Bcomput<\/PRE>
    \n
    will not<\/EM> match “computer” or “computing”, unless it is part of a bigger word such as “supercomputer” or “recomputing”. <\/DIV>
    \n
    Note that the underscore (_<\/CODE>) is considered a “word” character. Thus, 
      super\\bcomputer<\/PRE>
    \n
    will not<\/EM> match “super_computer”. <\/DIV>
    \n
    There is one other metacharacter starting with a backslash, the octal<\/EM> metacharacter. The octal metacharacter looks like this: “\\nnn<\/STRONG>“, where “n” is a number from zero to seven. This is used for specifying control characters that have no typed equivalent. For example, 
      \\007<\/PRE>
    \n
    would find all subjects with an embedded ASCII “bell” character. (The bell is specified by an ASCII value of 7.) You will rarely need to use the octal metacharacter. <\/DIV>
    \n
    There are three other metacharacters that may be of use. The first is the braces<\/EM> metacharacter. This metacharacter follows a normal character and contains two number separated by a comma (,<\/STRONG>) and surrounded by braces ({}<\/STRONG>). It is like the star metacharacter, except the length of the string it matches must be within the minimum and maximum length specified by the two numbers in braces. Thus, 
      ab{3,5}c<\/PRE>
    \n
    will match “abbbc”, “abbbbc” or “abbbbbc”. No other string is matched. Likewise, <\/DIV>
      .{3,5}pentane<\/PRE>
    \n
    will match “cyclopentane”, “isopentane” or “neopentane”, but not “n-pentane”, since “n-” is only two characters long. <\/DIV>
    \n
    The alternative metacharacter is represented by a vertical bar (|<\/STRONG>). It indicates an either\/or behavior by separating two or more possible choices. For example: 
      isopentane|cyclopentane<\/PRE>
    \n
    will match any subject containing the strings “isopentane” or “cyclopentane” or both. However, It will not match “pentane” or “n-pentane” or “neopentane.” The last metacharacter is the brackets<\/EM> metacharacter. The bracket metacharacter matches one occurence of any character inside the brackets ([]<\/STRONG>). For example, <\/DIV>
      \\s[cmt]an\\s<\/PRE>
    \n
    will match “can”, “man” and “tan”, but not “ban”, “fan” or “pan”. Similarly, <\/DIV>
      2,[23]-dimethylbutane<\/PRE>
    \n
    will match “2,2-dimethylbutane” or “2,3-dimethylbutane”, but not “2,4-dimethylbutane”, “2,23-dimethylbutane” or “2,-dimethybutane”. Ranges of characters can be used by using the dash (–<\/STRONG>) within the brackets. For example, <\/DIV>
      a[a-d]z<\/PRE>
    \n
    will match “aaz”, “abz”, “acz” or “adz”, and nothing else. Likewise, <\/DIV>
      textfile0[3-5]<\/PRE>
    \n
    will match “textfile03”, “textfile04”, or “textfile05” and nothing else. <\/DIV>
    \n
    If you wish to include a dash within brackets as one of the characters to match, instead of to denote a range, put the dash immediately before the right bracket. Thus: 
      a[1234-]z<\/PRE>
    \n
    and <\/DIV>
      a[1-4-]z<\/PRE>
    \n
    both do the same thing. They both match “a1z”, “a2z”, “a3z”, “a4z” or “a-z”, and nothing else. <\/DIV>
    \n
    The bracket metacharacter can also be inverted by placing a caret (^<\/STRONG>) immediately after the left bracket. Thus, 
      textfile0[^02468]<\/PRE>
    \n
    matches any ten-character string starting with “textfile0” and ending with anything except an even number. Inversion and ranges can be combined, so that <\/DIV>
      \\W[^f-h]ood\\W<\/PRE>
    \n
    matches any four letter wording ending in “ood” except<\/EM> for “food”, “good” or “hood”. (Thus “mood” and “wood” would both be matched.) <\/DIV>
    \n
    Note that within brackets, ordinary quoting rules do not apply and other metacharacters are not available. The only characters that can be quoted in brackets are “[<\/CODE>“, “]<\/CODE>“, and “\\<\/CODE>“. Thus, 
      [\\[\\\\\\]]abc<\/PRE>
    \n
    matches any four letter string ending with “abc” and starting with “[<\/CODE>“, “]<\/CODE>“, or “\\<\/CODE>“. <\/DIV>
    \n
    Forbidden Characters<\/H3>
    \n
    Because of the way the searcher works, the following metacharacters should not<\/EM> be used, even though they are valid Perl metacharacters. They are: <\/DIV>
    \n

    \n
    ^<\/STRONG> (allowed within brackets)
    \n
    $<\/STRONG> (allowed within brackets)
    \n
    \\n<\/STRONG>
    \n
    \\r<\/STRONG>
    \n
    \\t<\/STRONG>
    \n
    \\f<\/STRONG>
    \n
    \\b<\/STRONG>
    \n
    ( )<\/STRONG> (allowed within brackets. Note that if you wish to search for parentheses within text outside of brackets, you should quote the parentheses.)
    \n
    \\1<\/STRONG>, \\2<\/STRONG> … \\9<\/STRONG>
    \n
    \\B<\/STRONG>
    \n
    :<\/STRONG>
    \n
    !<\/STRONG> <\/DD><\/DL>
    \n
    Things To Remember<\/H3>
    \n
    Here are some other things you should know about regular expressions. <\/DIV>
    \n

      \n
    1. The archive search software searches only subject lines, and all articles within the same thread will also be displayed.
      \n
      <\/P>
      \n
    2. Regular expressions should be a last resort. Because they are complex, it can be more work mastering a search than just sifting through a long list of matches (unless you’re already familiar with regular expressions).
      \n
      <\/P>
      \n
    3. We limit the number of articles which can be shown to 200 or less. This is to minimize load on our system.
      \n
      <\/P>
      \n
    4. The search is case insensitive; thus 
        mopac<\/PRE>and 
        Mopac<\/PRE>and 
        MOPAC<\/PRE>all search for the same set of strings. Each will match “mopac”, “MOPAC”, “Mopac”, “mopaC”, “MoPaC”, “mOpAc” and so forth. Thus you need not worry about capitalization. (Note, however, that metacharacter must still have the proper case. This is especially important for metacharacters whose case determines whether their meaning is reversed or not.)
      \n
      <\/P>
      \n
    5. Outside of the brackets metacharacter, you must quote parentheses, brackets and braces to get the searcher to take them literally. <\/LI><\/OL><\/A><\/p>\n","protected":false},"excerpt":{"rendered":"
      Perl Regular Expression Tutorial   Contents Overview Simple Regular Expressions Metacharacters Forbidden Characters Things To Remember Overview A regular expression is a string of characters which tells the searcher which string (or strings) you are looking for. The following explains the format of regular expressions in detail. If you are familiar with Perl, you already … Continue reading Perl Regular Expression Tutorial<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-269","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts\/269","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=269"}],"version-history":[{"count":0,"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts\/269\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=269"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=269"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=269"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}