RegexReplace (String function): Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
 
(9 intermediate revisions by 4 users not shown)
Line 13: Line 13:
<tr><th>%outString</th>
<tr><th>%outString</th>
<td>A string set to the value of method object <var class="term">string</var> with each matched substring replaced by the value of <var class="term">replacement</var>.  </td></tr>
<td>A string set to the value of method object <var class="term">string</var> with each matched substring replaced by the value of <var class="term">replacement</var>.  </td></tr>
<tr><th>string</th>
<tr><th>string</th>
<td>The method object string, within which matches for <var class="term">regex</var> are sought.</td>
<td>The method object string, within which matches for <var class="term">regex</var> are sought.</td>
<tr><th>regex</th>
<tr><th>regex</th>
<td>A string that is interpreted as a regular expression and that is applied to the method object <var class="term">string</var> to find the one or more substrings matched by <var class="term">regex</var> </td></tr>
<td>A string that is interpreted as a regular expression and that is applied to the method object <var class="term">string</var> to find the one or more substrings matched by <var class="term">regex</var> </td></tr>
<tr><th>replacement</th>
<tr><th>replacement</th>
<td>The string that replaces the substrings of <var class="term">string</var> that <var class="term">regex</var> matches.  Except when the <code>A</code> option is specified (as described below for the <var>Options</var> argument), you can include markers in the <var class="term">replacement</var> value to indicate where to insert corresponding captured strings &mdash; strings matched by capturing groups (parenthesized subexpressions) in <var class="term">regex</var>, if any.
<td>The string that replaces the substrings of <var class="term">string</var> that <var class="term">regex</var> matches.  Except when the <code>A</code> option is specified (as described below for the <var>Options</var> argument), you can include markers in the <var class="term">replacement</var> value to indicate where to insert corresponding captured strings &mdash; strings matched by capturing groups (parenthesized subexpressions) in <var class="term">regex</var>, if any.
<p>As in Perl, these markers are in the form <var class="term">$n</var>, where <i>n</i> is the number of the capture group, and 1 is the number of the first capture group. <i>n</i> must not be 0 or contain more than 9 digits.  If a capturing group makes no matches (is positional, for example), or if there was no <i>n</i>th capture group corresponding to the <var class="term">$n</var> marker in a replacement string, the (literal) value of <var class="term">$n</var> is used in the replacement string instead of the empty string.  <code>xxx$1</code> is an example of a valid replacement string, and <code>$0yyy</code> is an example of an invalid one.  Or you can use the format <var class="term">$mn</var>, where <i>m</i> is one of the following modifiers:
<p>
As in Perl, these markers are in the form <var class="term">$n</var>, where <i>n</i> is the number of the capture group, and 1 is the number of the first capture group. <i>n</i> must not be 0 or contain more than 9 digits.  If a capturing group makes no matches (is positional, for example), or if there was no <i>n</i>th capture group corresponding to the <var class="term">$n</var> marker in a replacement string, the (literal) value of <var class="term">$n</var> is used in the replacement string instead of the empty string.  <code>xxx$1</code> is an example of a valid replacement string, and <code>$0yyy</code> is an example of an invalid one.  Or you can use the format <var class="term">$mn</var>, where <i>m</i> is one of the following modifiers:
</p>
</p>
<table class="syntaxNested"><tr><th><var>U or u</var></th>
<table class="syntaxNested">
<tr><th><var>U</var> or <var class="camel">u</var></th>
<td>Specifies that the specified captured string should be uppercased when inserted.</td></tr>
<td>Specifies that the specified captured string should be uppercased when inserted.</td></tr>
<tr><th><var>L or l</var></th>
 
<tr><th><var>L</var> or <var class="camel">l</var></th>
<td>Indicates that the captured string should be lowercased when inserted.</td></tr>
<td>Indicates that the captured string should be lowercased when inserted.</td></tr>
</table>
</table>
Line 30: Line 36:


<tr><th><var>Options</var></th>
<tr><th><var>Options</var></th>
<td>This optional, [[Notation conventions for methods#Named parameters|name required]], parameter is a string of single-letter options, which may be specified in uppercase or lowercase, in any combination, and blank separated or not, as you prefer. For more information about these options, see [[Regex_processing#Common_regex_options|"Common regex options"]]:
<td>This optional, [[Notation conventions for methods#Named parameters|name required]], parameter is a string of single-letter options, which may be specified in uppercase or lowercase, in any combination, and blank separated or not, as you prefer. For more information about these options, see [[Regex_processing#Common_regex_options|Common regex options]].
<table class="syntaxNested">
</td></tr>
<tr><th><var>I</var></th>
<td>Do case-insensitive matching between <var class="term">string</var> and <var class="term">regex</var>.</td></tr>
 
<tr><th><var>S</var></th>
<td>Dot-All mode: a period (<code>.</code>) can match any character, including carriage return and linefeed.</td></tr>
 
<tr><th><var>M</var></th>
<td>Multi-line mode: let anchor characters match end-of-line indicators <b><i>wherever</i></b> the indicator appears in the input string.  <var class="term">M</var> mode is ignored if <var class="term">C</var> (XML Schema) mode is specified.</td></tr>
 
<tr><th><var>C</var></th>
<td>Do the match according to [[Regex_processing#XML_Schema_mode|"XML Schema regex rules"]]. Each <var class="term">regex</var> is implicitly anchored at the beginning and end, and no characters serve as anchors.</td></tr>
 
<tr><th><var>G</var></th>
<td>Replace every occurrence of the match, not just (as in non-<var class="term">G</var> mode) the first matched substring only. </td></tr>
 
<tr><th><var>A</var></th>
<td>Copy the <var class="term">replacement</var> string as is.  Do not recognize escapes; interpret a <code>$n</code> combination as a literal and <b><i>not</i></b> as a special marker; and so on.</td></tr>
</table></td></tr>
</table>
</table>
==Exceptions==
<var>RegexReplace</var> can throw the following exceptions:
<dl>
<dt><var>[[InvalidRegex_class|InvalidRegex]]</var>
<dd>If the <var class="term">regex</var> parameter does not contain a valid regular expression. The exception object indicates the position of the character in the <var class="term">regex</var> parameter where it was determined that the regular expression is invalid, and a description of the nature of the error.
</dl>


==Usage notes==
==Usage notes==
<ul>
<ul>
<li>It is strongly recommended that you protect your environment from regular expression processing demands on PDL and STBL space by setting, say, <code>UTABLE LPDLST 3000</code> and <code>UTABLE LSTBL 9000</code>. See [[Regex_processing#User_Language_programming_considerations|"User Language programming considerations"]].
<li>It is strongly recommended that you protect your environment from regular expression processing demands on PDL and STBL space by setting, say, <code>UTABLE LPDLST 3000</code> and <code>UTABLE LSTBL 9000</code>. See [[Regex processing#SOUL programming considerations|SOUL programming considerations]].


<li>Within a regular expression, characters enclosed by a pair of unescaped parentheses form a "subexpression." A subexpression is a capturing group if the opening parenthesis is <b><i>not</i></b> followed by a question mark (<tt>?</tt>). A capturing group that is nested within a non-capturing subexpression is still a capturing group.
<li>Within a regular expression, characters enclosed by a pair of unescaped parentheses form a "subexpression." A subexpression is a capturing group if the opening parenthesis is <b><i>not</i></b> followed by a question mark (<tt>?</tt>). A capturing group that is nested within a non-capturing subexpression is still a capturing group.
Line 67: Line 48:
<li>In Perl, <var class="term">$n</var> markers (<code>$1</code>, for example) enclosed in single quotes are treated as literals instead of as "that which was captured by the first capturing parentheses." <var>RegexReplace</var> uses the <code>A</code> option of the <var>Options</var> argument for this purpose.
<li>In Perl, <var class="term">$n</var> markers (<code>$1</code>, for example) enclosed in single quotes are treated as literals instead of as "that which was captured by the first capturing parentheses." <var>RegexReplace</var> uses the <code>A</code> option of the <var>Options</var> argument for this purpose.


<li>Matching of <var class="term">regex</var> may "succeed" but yet  match no characters. For example, a quantifier like <code>?</code> is allowed by definition to match no characters, though it tries to match one. <var>RegexReplace</var> honors such a zero-length match by substituting the specified replacement string at the current position. If the global option is in effect, the <var class="term">regex</var> is then applied again one position to the right in the input string, and again, until the end of the string. The regex <code>9?</code> globally applied to the string <code>abc</code> with a comma-comma (<code>,,</code>) replacement string results in this output string: <code>,,a,,b,,c,,</code>.
<li>Matching of <var class="term">regex</var> may "succeed" but yet  match no characters. For example, a quantifier like <code>?</code> is allowed by definition to match no characters, though it tries to match one. <var>RegexReplace</var> honors such a zero-length match by substituting the specified replacement string at the current position. If the global option is in effect, the <var class="term">regex</var> is then applied again one position to the right in the input string, and again, until the end of the string. The regex <code>9?</code> globally applied to the string <code>abc</code> with a comma-comma (<tt>,,</tt>) replacement string results in this output string: <code>,,a,,b,,c,,</code>.


<li>For information about additional methods that support regular expressions, see [[Regex_processing|"Regex Processing"]].
<li>For information about additional methods that support regular expressions, see [[Regex processing]].
 
<li><var>RegexReplace</var> is available as of <var class="product">Sirius Mods</var> Version 7.2.
</ul>
</ul>


==Examples==
==Examples==
<ol><li>In the following example, the regex <code>(5.)</code> is applied repeatedly (global option) to the string <code>5A5B5C5D5E</code> to replace the uppercase letters with their lowercase counterparts. The <code>$L1</code> <var class="term">replacement</var> value makes the replacement string equal to whatever is matched by the capturing group, <code>(5.)</code>, in the <var class="term">regex</var> (the <code>L</code> causes the lowercase versions of the captured letters to be used).
<ol>
<li>In the following example, the regex <code>(5.)</code> is applied repeatedly (global option) to the string <code>5A5B5C5D5E</code> to replace the uppercase letters with their lowercase counterparts. The <code>$L1</code> <var class="term">replacement</var> value makes the replacement string equal to whatever is matched by the capturing group, <code>(5.)</code>, in the <var class="term">regex</var> (the <code>L</code> causes the lowercase versions of the captured letters to be used).
<p class="code">begin
<p class="code">begin
   %regex longstring
   %regex longstring
Line 87: Line 67:
   %replacement='$L1'
   %replacement='$L1'
   %opt='g'
   %opt='g'
   %outStr = %inStr:Regexreplace(%regex, %replacement, options=%opt)
   %outStr = %inStr:regexReplace(%regex, %replacement, options=%opt)
   [[PrintText statement|printText]] OutputString: '{%outStr}'
   [[PrintText statement|printText]] OutputString: '{%outStr}'
end
end
Line 95: Line 75:
</p>
</p>
The non-capturing regex <code>5.</code> matches and replaces the same substrings as the capturing group <code>(5.)</code>, but <code>(5.)</code> is used above to take advantage of the self-referring marker for the replacement string, <code>$L1</code>, which is valid only for capturing groups.
The non-capturing regex <code>5.</code> matches and replaces the same substrings as the capturing group <code>(5.)</code>, but <code>(5.)</code> is used above to take advantage of the self-referring marker for the replacement string, <code>$L1</code>, which is valid only for capturing groups.
<li>Say you want to supply end tags to items of of the form <code><img foo="bar"></code>, converting them to <code><img foo="bar"></img></code>. You decide to use the following regex to capture <code>img</code> tags that have attributes:
 
<div id="greedy"></div>
<li>Say you want to supply end tags to items of the form <code><img foo="bar"></code>, converting them to <code><img foo="bar"></img></code>. You decide to use the following regex to capture <code>img</code> tags that have attributes:
<p class="code">(<img .*>)</p>
<p class="code">(<img .*>)</p>
And you use the following replacement string to replace the captured string with the captured string plus an appended <code></img></code>:
And you use the following replacement string to replace the captured string with the captured string plus an appended <code></img></code>:
Line 102: Line 84:
<p class="code"><body><img src="foo" width="24"></body></img></p>
<p class="code"><body><img src="foo" width="24"></body></img></p>
One remedy for this situation is to use the following <var class="term">regex</var>, which employs a negated character class to match non-closing-bracket characters:
One remedy for this situation is to use the following <var class="term">regex</var>, which employs a negated character class to match non-closing-bracket characters:
<p class="code">(<img [&circ;>]*>)</p>
<p class="code">(<img [&#94;>]*>)</p>
This <var class="term">regex</var> does not extend beyond the first closing angle bracket in the target input string, and the resulting output string is:
This <var class="term">regex</var> does not extend beyond the first closing angle bracket in the target input string, and the resulting output string is:
<p class="output"><body><img src="foo" width="24"></img></body></p></ol>
<p class="output"><body><img src="foo" width="24"></img></body></p></ol>
Line 108: Line 90:
==See also==
==See also==
{{Template:String:RegexReplace footer}}
{{Template:String:RegexReplace footer}}
[[Category:Regular expression processing]]

Latest revision as of 01:43, 26 March 2022

Replace regex match(es) (String class)


The RegexReplace intrinsic function searches a given string for matches of a regular expression, and replaces matches with, or according to, a specified replacement string. The function stops after the first match and replace, or it can continue searching and replacing until no more matches are found.

Matches are obtained according to the rules of regular expression matching.

Syntax

%outString = string:RegexReplace( regex, replacement, [Options= string]) Throws InvalidRegex

Syntax terms

%outString A string set to the value of method object string with each matched substring replaced by the value of replacement.
string The method object string, within which matches for regex are sought.
regex A string that is interpreted as a regular expression and that is applied to the method object string to find the one or more substrings matched by regex
replacement The string that replaces the substrings of string that regex matches. Except when the A option is specified (as described below for the Options argument), you can include markers in the replacement value to indicate where to insert corresponding captured strings — strings matched by capturing groups (parenthesized subexpressions) in regex, if any.

As in Perl, these markers are in the form $n, where n is the number of the capture group, and 1 is the number of the first capture group. n must not be 0 or contain more than 9 digits. If a capturing group makes no matches (is positional, for example), or if there was no nth capture group corresponding to the $n marker in a replacement string, the (literal) value of $n is used in the replacement string instead of the empty string. xxx$1 is an example of a valid replacement string, and $0yyy is an example of an invalid one. Or you can use the format $mn, where m is one of the following modifiers:

U or u Specifies that the specified captured string should be uppercased when inserted.
L or l Indicates that the captured string should be lowercased when inserted.

The only characters you can escape in a replacement string are dollar sign ($), backslash (\), and the digits 0 through 9. So only these escapes are respected: \\, \$, and \0 through \9. No other escapes are allowed in a replacement string — this includes "shorthand" escapes like \d — and an "unaccompanied" backslash (\) is an error. For example, since the scan for the number that accompanies the meta-$ stops at the first non-numeric, you use 1$1\2 to indicate that the first captured string should go between the numbers 1 and 2 in the replacement string.

An invalid replacement string results in request cancellation.

Options This optional, name required, parameter is a string of single-letter options, which may be specified in uppercase or lowercase, in any combination, and blank separated or not, as you prefer. For more information about these options, see Common regex options.

Usage notes

  • It is strongly recommended that you protect your environment from regular expression processing demands on PDL and STBL space by setting, say, UTABLE LPDLST 3000 and UTABLE LSTBL 9000. See SOUL programming considerations.
  • Within a regular expression, characters enclosed by a pair of unescaped parentheses form a "subexpression." A subexpression is a capturing group if the opening parenthesis is not followed by a question mark (?). A capturing group that is nested within a non-capturing subexpression is still a capturing group.
  • In Perl, $n markers ($1, for example) enclosed in single quotes are treated as literals instead of as "that which was captured by the first capturing parentheses." RegexReplace uses the A option of the Options argument for this purpose.
  • Matching of regex may "succeed" but yet match no characters. For example, a quantifier like ? is allowed by definition to match no characters, though it tries to match one. RegexReplace honors such a zero-length match by substituting the specified replacement string at the current position. If the global option is in effect, the regex is then applied again one position to the right in the input string, and again, until the end of the string. The regex 9? globally applied to the string abc with a comma-comma (,,) replacement string results in this output string: ,,a,,b,,c,,.
  • For information about additional methods that support regular expressions, see Regex processing.

Examples

  1. In the following example, the regex (5.) is applied repeatedly (global option) to the string 5A5B5C5D5E to replace the uppercase letters with their lowercase counterparts. The $L1 replacement value makes the replacement string equal to whatever is matched by the capturing group, (5.), in the regex (the L causes the lowercase versions of the captured letters to be used).

    begin %regex longstring %inStr longstring %replacement longstring %outStr longstring %opt string len 10 %inStr='5A5B5C5D5E' %regex='(5.)' %replacement='$L1' %opt='g' %outStr = %inStr:regexReplace(%regex, %replacement, options=%opt) printText OutputString: '{%outStr}' end

    The example result is:

    OutputString: '5a5b5c5d5eBold text'

    The non-capturing regex 5. matches and replaces the same substrings as the capturing group (5.), but (5.) is used above to take advantage of the self-referring marker for the replacement string, $L1, which is valid only for capturing groups.

  2. Say you want to supply end tags to items of the form <img foo="bar">, converting them to <img foo="bar"></img>. You decide to use the following regex to capture img tags that have attributes:

    (<img .*>)

    And you use the following replacement string to replace the captured string with the captured string plus an appended </img>:

    $1</img>

    However, if the regex above is applied to the string <body><img src="foo" width="24"></body>, the end tag </img> is not inserted after the first closing angle bracket (>) after 24 as you want. Instead, the matched string greedily extends to the second closing angle bracket, and the tag </img> is positioned at the end:

    <body><img src="foo" width="24"></body></img>

    One remedy for this situation is to use the following regex, which employs a negated character class to match non-closing-bracket characters:

    (<img [^>]*>)

    This regex does not extend beyond the first closing angle bracket in the target input string, and the resulting output string is:

    <body><img src="foo" width="24"></img></body>

See also