RegexSplit (Stringlist function) - Revision history

Alex at 22:16, 21 January 2022

2022-01-21T22:16:03Z

← Older revision		Revision as of 22:16, 21 January 2022
Line 32:		Line 32:

	<tr><th><var>Options</var></th>		<tr><th><var>Options</var></th>
	<td>This is an optional, [[Notation conventions for methods#Named parameters\|name required]], parameter supplying 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 is an optional, [[Notation conventions for methods#Named parameters\|name required]], parameter supplying 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></tr>
	~~<table class="noVar">~~
	~~<tr><th>I</th>~~
	~~<td>Do case-insensitive matching between <var class="term">string</var> and <var class="term">regex</var>.</td></tr>~~

	~~<tr><th>S</th>~~
	~~<td>Dot-All mode: a period (<code>.</code>) can match any character, including carriage return and linefeed.</td></tr>~~

	~~<tr><th>M</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.</td></tr>~~
	~~</table>~~</td></tr>

	<tr><th><var>Status</var></th>		<tr><th><var>Status</var></th>
Line 281:		Line 271:
	==See also==		==See also==
	{{Template:Stringlist:RegexSplit footer}}		{{Template:Stringlist:RegexSplit footer}}

			[[Category:Regular expression processing]]

JAL: link repair

2016-05-11T22:41:09Z

link repair

← Older revision		Revision as of 22:41, 11 May 2016
Line 97:		Line 97:
	<li><var>RegexSplit</var> is available in <var class="product">[[Sirius Mods\|Sirius Mods]]</var> Version 7.0 and later.		<li><var>RegexSplit</var> is available in <var class="product">[[Sirius Mods\|Sirius Mods]]</var> Version 7.0 and later.

	<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>The <var>Stringlist</var> class <var>RegexSplit</var> function performs the same processing as the <var>[[Intrinsic classes\|intrinsic]]</var> <var>String</var> class <var>[[RegexSplit (String function)\|RegexSplit]]</var> function. The only differences are:		<li>The <var>Stringlist</var> class <var>RegexSplit</var> function performs the same processing as the <var>[[Intrinsic classes\|intrinsic]]</var> <var>String</var> class <var>[[RegexSplit (String function)\|RegexSplit]]</var> function. The only differences are:

JAL at 22:45, 14 November 2012

2012-11-14T22:45:56Z

← Older revision		Revision as of 22:45, 14 November 2012
Line 34:		Line 34:
	<td>This is an optional, [[Notation conventions for methods#Named parameters\|name required]], parameter supplying 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 is an optional, [[Notation conventions for methods#Named parameters\|name required]], parameter supplying 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~~">		<table class="noVar">
	<tr><th~~><var~~>I~~</var>~~</th>		<tr><th>I</th>
	<td>Do case-insensitive matching between <var class="term">string</var> and <var class="term">regex</var>.</td></tr>		<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>		<tr><th>S</th>
	<td>Dot-All mode: a period (<code>.</code>) can match any character, including carriage return and linefeed.</td></tr>		<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>		<tr><th>M</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.</td></tr>		<td>Multi-line mode: let anchor characters match end-of-line indicators <b><i>wherever</i></b> the indicator appears in the input string.</td></tr>
	</table></td></tr>		</table></td></tr>
Line 48:		Line 48:
	<td>The <var>Status</var> argument (name required) is optional; if specified, it is set to an integer code. These values are possible:		<td>The <var>Status</var> argument (name required) is optional; if specified, it is set to an integer code. These values are possible:

	<table ~~class="list"~~>		<table>
	<tr><th>n</th>		<tr><th>n</th>
	<td>A successful match was obtained. The (positive) number of items that are added to the method <var>Stringlist</var> <var class="term">sl</var>.</td></tr>		<td>A successful match was obtained. The (positive) number of items that are added to the method <var>Stringlist</var> <var class="term">sl</var>.</td></tr>
Line 66:		Line 66:
	<tr><th><var>Add</var></th>		<tr><th><var>Add</var></th>
	<td>The <var>Add</var> argument (name required) is one of the following <var>RegexSplitOutputOptions</var> <var>enumeration</var> values, which specify what substrings of the input string <var class="term">inString</var> to store in the method <var>Stringlist</var> <var class="term">sl</var>:		<td>The <var>Add</var> argument (name required) is one of the following <var>RegexSplitOutputOptions</var> <var>enumeration</var> values, which specify what substrings of the input string <var class="term">inString</var> to store in the method <var>Stringlist</var> <var class="term">sl</var>:
	~~<table class="list">~~

	<tr><th~~><var~~>Unmatched~~</var>~~</th>		<table class="noVar">
			<tr><th>Unmatched</th>
	<td>Store only each unmatched substring and any empty substrings due to adjacent separators (consecutive matching substrings). For example, if the value of <var class="term">regex</var> is <code>#</code>, and <var class="term">inString</var> is <code>C###D</code>, the <code>UnMatched</code> option adds four <var>Stringlist</var> items: <code>C</code>, two empty items, then <code>D</code>. Unmatched is the default.</td></tr>		<td>Store only each unmatched substring and any empty substrings due to adjacent separators (consecutive matching substrings). For example, if the value of <var class="term">regex</var> is <code>#</code>, and <var class="term">inString</var> is <code>C###D</code>, the <code>UnMatched</code> option adds four <var>Stringlist</var> items: <code>C</code>, two empty items, then <code>D</code>. Unmatched is the default.</td></tr>

	<tr><th~~><var~~>Matched~~</var>~~</th>		<tr><th>Matched</th>
	<td>Store each matched substring only. Include those characters matched by capturing or non-capturing groups.</td></tr>		<td>Store each matched substring only. Include those characters matched by capturing or non-capturing groups.</td></tr>

	<tr><th~~><var~~>MatchedAndUnmatched~~</var>~~</th>		<tr><th>MatchedAndUnmatched</th>
	<td>Store each matched and each unmatched substring in alternating <var>Stringlist</var> items. The first item contains the first unmatched substring, the second item contains the first matched substring, and so on, ending with the last matched substring and the last unmatched substring.</td></tr>		<td>Store each matched and each unmatched substring in alternating <var>Stringlist</var> items. The first item contains the first unmatched substring, the second item contains the first matched substring, and so on, ending with the last matched substring and the last unmatched substring.</td></tr>

	<tr><th~~><var~~>Captured~~</var>~~</th>		<tr><th>Captured</th>
	<td>Store only those substrings matched by capturing groups in <var class="term">regex</var> — as if <var>[[RegexCapture (Stringlist function)\|RegexCapture]]</var> were applied repeatedly.</td></tr>		<td>Store only those substrings matched by capturing groups in <var class="term">regex</var> — as if <var>[[RegexCapture (Stringlist function)\|RegexCapture]]</var> were applied repeatedly.</td></tr>

	<tr><th~~><var~~>CapturedAndUnmatched~~</var>~~</th>		<tr><th>CapturedAndUnmatched</th>
	<td>Store in alternating <var>Stringlist</var> items a) those substrings matched by capturing groups in <var class="term">regex</var>, and b) each unmatched substring.		<td>Store in alternating <var>Stringlist</var> items a) those substrings matched by capturing groups in <var class="term">regex</var>, and b) each unmatched substring.
	<p>		<p>

Dme at 05:13, 11 November 2012

2012-11-11T05:13:53Z

← Older revision		Revision as of 05:13, 11 November 2012
Line 203:		Line 203:
	<li><div id="anchor_2"></div>This example shows the utility of the <code>Add=Matched</code> option.		<li><div id="anchor_2"></div>This example shows the utility of the <code>Add=Matched</code> option.

	<p class="code"> ...		<p class="code">...
	%str = ' Barry Mildred Jack Faust '		%str = ' Barry Mildred Jack Faust '
	%sl:RegexSplit(%str, ' +')		%sl:RegexSplit(%str, ' +')

JAL at 21:01, 31 October 2012

2012-10-31T21:01:00Z

Show changes

JALWiccan: 1 revision

2012-10-31T20:25:45Z

1 revision

← Older revision	Revision as of 20:25, 31 October 2012
(No difference)

JAL at 20:25, 31 October 2012

2012-10-31T20:25:44Z

← Older revision		Revision as of 20:25, 31 October 2012
Line 10:		Line 10:
	</ul>		</ul>

	Within a regex, 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 (<tt>?</tt>). <var>RegexSplit</var> uses the rules of regular expression matching (information about which is provided in [[Regex_processing#Regex_rules\|"Regex processing rules"]]). <var>RegexSplit</var> accepts two required and three optional arguments, and it returns a numeric value. It is also a callable method. Specifying an invalid argument results in request cancellation.		Within a regex, 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 (<tt>?</tt>). <var>RegexSplit</var> uses the rules of regular expression matching (information about which is provided in [[Regex_processing#Regex_rules\|"Regex processing rules"]]). <var>RegexSplit</var> accepts two required and three optional arguments, and it returns a numeric value. It is also a [[Notation conventions for methods#Callable functions\|callable]] method. Specifying an invalid argument results in request cancellation.

	==Syntax==		==Syntax==

JAL at 20:25, 31 October 2012

2012-10-31T20:25:35Z

← Older revision		Revision as of 20:25, 31 October 2012
Line 57:		Line 57:
	<td>Store each matched and each unmatched substring in alternating <var>Stringlist</var> items. The first item contains the first unmatched substring, the second item contains the first matched substring, and so on, ending with the last matched substring and the last unmatched substring.</td></tr>		<td>Store each matched and each unmatched substring in alternating <var>Stringlist</var> items. The first item contains the first unmatched substring, the second item contains the first matched substring, and so on, ending with the last matched substring and the last unmatched substring.</td></tr>
	<tr><th><var>Captured</var></th>		<tr><th><var>Captured</var></th>
	<td>Store only those substrings matched by capturing groups in <var class="term">regex</var> — as if <var>[[RegexCapture (Stringlist function)\|RegexCapture]]</var> were applied repeatedly.</td></tr>		<td>Store only those substrings matched by capturing groups in <var class="term">regex</var> ??? as if <var>[[RegexCapture (Stringlist function)\|RegexCapture]]</var> were applied repeatedly.</td></tr>
	<tr><th><var>CapturedAndUnmatched</var></th>		<tr><th><var>CapturedAndUnmatched</var></th>
	<td>Store in alternating <var>Stringlist</var> items a) those substrings matched by capturing groups in <var class="term">regex</var>, and b) each unmatched substring.		<td>Store in alternating <var>Stringlist</var> items a) those substrings matched by capturing groups in <var class="term">regex</var>, and b) each unmatched substring.

JALWiccan: 1 revision

2012-10-30T22:02:48Z

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 57:		Line 57:
	<td>Store each matched and each unmatched substring in alternating <var>Stringlist</var> items. The first item contains the first unmatched substring, the second item contains the first matched substring, and so on, ending with the last matched substring and the last unmatched substring.</td></tr>		<td>Store each matched and each unmatched substring in alternating <var>Stringlist</var> items. The first item contains the first unmatched substring, the second item contains the first matched substring, and so on, ending with the last matched substring and the last unmatched substring.</td></tr>
	<tr><th><var>Captured</var></th>		<tr><th><var>Captured</var></th>
	<td>Store only those substrings matched by capturing groups in <var class="term">regex</var> -- as if <var>[[RegexCapture (Stringlist function)\|RegexCapture]]</var> were applied repeatedly.</td></tr>		<td>Store only those substrings matched by capturing groups in <var class="term">regex</var> — as if <var>[[RegexCapture (Stringlist function)\|RegexCapture]]</var> were applied repeatedly.</td></tr>
	<tr><th><var>CapturedAndUnmatched</var></th>		<tr><th><var>CapturedAndUnmatched</var></th>
	<td>Store in alternating <var>Stringlist</var> items a) those substrings matched by capturing groups in <var class="term">regex</var>, and b) each unmatched substring.		<td>Store in alternating <var>Stringlist</var> items a) those substrings matched by capturing groups in <var class="term">regex</var>, and b) each unmatched substring.

← Older revision		Revision as of 22:41, 11 May 2016
Line 97:		Line 97:
	<li><var>RegexSplit</var> is available in <var class="product">[[Sirius Mods\|Sirius Mods]]</var> Version 7.0 and later.		<li><var>RegexSplit</var> is available in <var class="product">[[Sirius Mods\|Sirius Mods]]</var> Version 7.0 and later.

	<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>The <var>Stringlist</var> class <var>RegexSplit</var> function performs the same processing as the <var>[[Intrinsic classes\|intrinsic]]</var> <var>String</var> class <var>[[RegexSplit (String function)\|RegexSplit]]</var> function. The only differences are:		<li>The <var>Stringlist</var> class <var>RegexSplit</var> function performs the same processing as the <var>[[Intrinsic classes\|intrinsic]]</var> <var>String</var> class <var>[[RegexSplit (String function)\|RegexSplit]]</var> function. The only differences are: