RegexReplaceCorresponding (Stringlist function) - Revision history

Alex at 00:02, 11 January 2022

2022-01-11T00:02:24Z

← Older revision		Revision as of 00:02, 11 January 2022
Line 1:		Line 1:
	{{Template:Stringlist:RegexReplaceCorresponding subtitle}}		{{Template:Stringlist:RegexReplaceCorresponding subtitle}}

			<p class="warn"><b>This method is deprecated and should not be used.</b></p>

	This method searches a given string for matches to one of multiple regular expressions contained in a list, and it replaces found matches with or according to a string contained in a list that corresponds to the regex list.		This method searches a given string for matches to one of multiple regular expressions contained in a list, and it replaces found matches with or according to a string contained in a list that corresponds to the regex list.

JAL: link repair

2016-05-11T22:42:19Z

link repair

← Older revision		Revision as of 22:42, 11 May 2016
Line 91:		Line 91:
	<li>All errors in <var>RegexReplaceCorresponding</var>, including invalid argument(s) result in request cancellation.		<li>All errors in <var>RegexReplaceCorresponding</var>, including invalid argument(s) result in request cancellation.

	<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>Items in <var class="term">sl</var> must <b><i>not</i></b> exceed 6124 bytes. However, the <var class="term">inString</var> value and items in <var class="term">replacementList</var> may exceed 6124 bytes.<li>For information about additional methods and $functions that support regular expressions, see [[Regex_processing~~\|"Regex Processing"~~]].		<li>Items in <var class="term">sl</var> must <b><i>not</i></b> exceed 6124 bytes. However, the <var class="term">inString</var> value and items in <var class="term">replacementList</var> may exceed 6124 bytes.<li>For information about additional methods and $functions that support regular expressions, see [[Regex_processing]].
	</ul>		</ul>

JAL: /* Usage notes */

2013-10-21T19:21:23Z

Usage notes

← Older revision		Revision as of 19:21, 21 October 2013
Line 94:		Line 94:

	<li>Items in <var class="term">sl</var> must <b><i>not</i></b> exceed 6124 bytes. However, the <var class="term">inString</var> value and items in <var class="term">replacementList</var> may exceed 6124 bytes.<li>For information about additional methods and $functions that support regular expressions, see [[Regex_processing\|"Regex Processing"]].		<li>Items in <var class="term">sl</var> must <b><i>not</i></b> exceed 6124 bytes. However, the <var class="term">inString</var> value and items in <var class="term">replacementList</var> may exceed 6124 bytes.<li>For information about additional methods and $functions that support regular expressions, see [[Regex_processing\|"Regex Processing"]].
	~~<li><var>RegexReplaceCorresponding</var> is available as of <var class="product">[[Sirius Mods\|Sirius Mods]]</var> Version 6.9.~~</ul>		</ul>

	==Examples==		==Examples==

Dme at 05:12, 11 November 2012

2012-11-11T05:12:48Z

← Older revision		Revision as of 05:12, 11 November 2012
Line 98:		Line 98:
	==Examples==		==Examples==
	In the following code fragment, the second item in regex list <code>%regList</code> is the first to match the input string <code>inStr</code>. The subexpression in that item performs no special capturing function — the parentheses are for grouping only. Since <code>%opt='g'</code> is specified, three replacements are made (using the corresponding, second, item in <code>%repList</code>):		In the following code fragment, the second item in regex list <code>%regList</code> is the first to match the input string <code>inStr</code>. The subexpression in that item performs no special capturing function — the parentheses are for grouping only. Since <code>%opt='g'</code> is specified, three replacements are made (using the corresponding, second, item in <code>%repList</code>):
	<p class="code"> ...		<p class="code">...
	%regList = new		%regList = new
	text to %regList		text to %regList

JAL: /* Syntax terms */

2012-11-06T17:55:14Z

Syntax terms

← Older revision		Revision as of 17:55, 6 November 2012
Line 24:		Line 24:
	<tr><th>replacementList</th>		<tr><th>replacementList</th>
	<td><p>A <var>Stringlist</var>, each of whose items is a potential replacement string for the substring of <var class="term">inString</var> that is matched by the corresponding item of <var class="term">sl</var>.</p>		<td><p>A <var>Stringlist</var>, each of whose items is a potential replacement string for the substring of <var class="term">inString</var> that is matched by the corresponding item of <var class="term">sl</var>.</p>
	<p>Except when the <code>A</code> option is specified (as described below for the <var>Options</var> argument), you can include <code>$0</code> markers in <var class="term">replacementList</var> items as placeholders for the substring of <var class="term">inString</var> that the item matches.</p>		<p>
	<p><code>xxx$0</code> is an example of a valid replacement string, and <code>xxx</code> concatenated with the portion of <var class="term">inString</var> that gets matched (by the corresponding <var class="term">sl</var> item) constitute the replacement string.</p>		Except when the <code>A</code> option is specified (as described below for the <var>Options</var> argument), you can include <code>$0</code> markers in <var class="term">replacementList</var> items as placeholders for the substring of <var class="term">inString</var> that the item matches.</p>
	<p>Any character after the dollar sign other than a zero is an error. Multiple zeroes (as many as 9) are permitted; a digit following such a string of zeroes must be escaped.</p>		<p>
	<p>You can also use the format <code>$m0</code>, where <i>m</i> is one of the following modifiers:</p>		<code>xxx$0</code> is an example of a valid replacement string, and <code>xxx</code> concatenated with the portion of <var class="term">inString</var> that gets matched (by the corresponding <var class="term">sl</var> item) constitute the replacement string.</p>
			<p>
			Any character after the dollar sign other than a zero is an error. Multiple zeroes (as many as 9) are permitted; a digit following such a string of zeroes must be escaped.</p>
			<p>
			You can also use the format <code>$m0</code>, where <i>m</i> is one of the following modifiers:</p>
	<table class="syntaxNested">		<table class="syntaxNested">
	<tr><th><var>U</var> or <var>u</var></th>		<tr><th><var>U</var> or <var>u</var></th>
Line 36:		Line 40:
	</table>		</table>
	<p>		<p>
	The only characters you can escape in a replacement string are dollar sign (<code>$</code>), backslash (<code>\</code>), and the digits <code>0</code> through <code>9</code>. So only these escapes are respected:<code>\\</code>, <code>\$</code>, and <code>\0</code> through <code>\9</code>. No other escapes are allowed in a replacement string &~~amp;amp;amp;~~mdash; this includes "shorthand" escapes like <code>\d</code> &~~amp;amp;amp;~~mdash; and an "unaccompanied" backslash (<code>\</code>) is an error.</p>		The only characters you can escape in a replacement string are dollar sign (<code>$</code>), backslash (<code>\</code>), and the digits <code>0</code> through <code>9</code>. So only these escapes are respected:<code>\\</code>, <code>\$</code>, and <code>\0</code> through <code>\9</code>. No other escapes are allowed in a replacement string — this includes "shorthand" escapes like <code>\d</code> — and an "unaccompanied" backslash (<code>\</code>) is an error.</p>
	<p>For example, since the scan for the number that accompanies the meta-$ stops at the first nonnumeric, you use <code>1$0\0</code> to indicate that the first matched substring should go between the numbers <code>1</code> and <code>0</code> in the replacement string.</p></td></tr>		<p>
			For example, since the scan for the number that accompanies the meta-$ stops at the first nonnumeric, you use <code>1$0\0</code> to indicate that the first matched substring should go between the numbers <code>1</code> and <code>0</code> in the replacement string.</p></td></tr>

	<tr><th><var>Options</var></th>		<tr><th><var>Options</var></th>

JALWiccan: 1 revision

2012-11-06T17:46:14Z

1 revision

← Older revision	Revision as of 17:46, 6 November 2012
(No difference)

JAL at 17:46, 6 November 2012

2012-11-06T17:46:03Z

← Older revision		Revision as of 17:46, 6 November 2012
Line 36:		Line 36:
	</table>		</table>
	<p>		<p>
	The only characters you can escape in a replacement string are dollar sign (<code>$</code>), backslash (<code>\</code>), and the digits <code>0</code> through <code>9</code>. So only these escapes are respected:<code>\\</code>, <code>\$</code>, and <code>\0</code> through <code>\9</code>. No other escapes are allowed in a replacement string &~~amp;amp;amp;~~amp;amp;amp;mdash; this includes "shorthand" escapes like <code>\d</code> &~~amp;amp;amp;~~amp;amp;amp;mdash; and an "unaccompanied" backslash (<code>\</code>) is an error.</p>		The only characters you can escape in a replacement string are dollar sign (<code>$</code>), backslash (<code>\</code>), and the digits <code>0</code> through <code>9</code>. So only these escapes are respected:<code>\\</code>, <code>\$</code>, and <code>\0</code> through <code>\9</code>. No other escapes are allowed in a replacement string &amp;amp;mdash; this includes "shorthand" escapes like <code>\d</code> &amp;amp;mdash; and an "unaccompanied" backslash (<code>\</code>) is an error.</p>
	<p>For example, since the scan for the number that accompanies the meta-$ stops at the first nonnumeric, you use <code>1$0\0</code> to indicate that the first matched substring should go between the numbers <code>1</code> and <code>0</code> in the replacement string.</p></td></tr>		<p>For example, since the scan for the number that accompanies the meta-$ stops at the first nonnumeric, you use <code>1$0\0</code> to indicate that the first matched substring should go between the numbers <code>1</code> and <code>0</code> in the replacement string.</p></td></tr>

JAL at 20:06, 31 October 2012

2012-10-31T20:06:44Z

Show changes

JALWiccan: 1 revision

2012-10-30T22:02:47Z

1 revision

← Older revision	Revision as of 22:02, 30 October 2012
(No difference)

JALWiccan: 1 revision

2012-10-30T22:02:32Z

1 revision

← Older revision		Revision as of 22:02, 30 October 2012
Line 61:		Line 61:

	==Examples==		==Examples==
	<ol><li>In the following code fragment, the second item in regex list <code>%regList</code> is the first to match the input string <code>inStr</code>. The subexpression in that item performs no special capturing function -- the parentheses are for grouping only. Since <code>%opt='g'</code> is specified, three replacements are made (using the corresponding, second, item in <code>%repList</code>):		<ol><li>In the following code fragment, the second item in regex list <code>%regList</code> is the first to match the input string <code>inStr</code>. The subexpression in that item performs no special capturing function — the parentheses are for grouping only. Since <code>%opt='g'</code> is specified, three replacements are made (using the corresponding, second, item in <code>%repList</code>):
	<p class="code"> ...		<p class="code"> ...
	%regList = new		%regList = new