RegexMatch (String function) - Revision history

Alex: /* See also */

2022-01-21T17:05:01Z

Alex: /* Syntax terms */

2022-01-21T16:59:45Z

Syntax terms

← Older revision		Revision as of 16:59, 21 January 2022
Line 18:		Line 18:

	<tr><th><var>Options</var></th>		<tr><th><var>Options</var></th>
	<td>This is an optional, but [[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, but [[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>		</td></tr>

Alex at 16:52, 21 January 2022

2022-01-21T16:52:28Z

@@ Line 19: / Line 19: @@
 <tr><th><var>Options</var></th>
 <td>This is an optional, but [[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">
+</td></tr>
 <tr><th><var>CaptureList</var></th>
@@ Line 141: / Line 128: @@
 {{Template:String:RegexMatch footer}}

JAL: link repair

2016-05-11T22:49:45Z

link repair

← Older revision		Revision as of 22:49, 11 May 2016
Line 47:		Line 47:
	==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>For information about additional methods that support regular expressions, see [[Regex processing]].		<li>For information about additional methods that support regular expressions, see [[Regex processing]].

JAL: minor cleanup

2016-05-11T19:20:52Z

minor cleanup

← Older revision		Revision as of 19:20, 11 May 2016
Line 47:		Line 47:
	==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#User_Language_programming_considerations\|User Language programming considerations]].

	<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>RegexMatch</var> is something of a misnomer. It does not determine if a string matches a regular expression, it determines if a string <b><i>contains</i></b> a substring that matches a regular expression. <var>RegexMatch</var> behaves more like a matching method if the regular expression is "anchored" (begins with a caret (<tt>^</tt>) and ends with a dollar sign (<tt>$</tt>)), or if the <var>C</var> option indicates XML Schema mode.		<li><var>RegexMatch</var> is something of a misnomer. It does not determine if a string matches a regular expression, it determines if a string <b><i>contains</i></b> a substring that matches a regular expression. <var>RegexMatch</var> behaves more like a matching method if the regular expression is "anchored" (begins with a caret (<tt>^</tt>) and ends with a dollar sign (<tt>$</tt>)), or if the <var>C</var> option indicates XML Schema mode.
			</ul>
	~~<li><var>RegexMatch</var> is available as of <var class="product">[[Sirius Mods\|Sirius Mods]]</var> Version 7.2.~~</ul>

	==Examples==		==Examples==
Line 102:		Line 101:
	This is the same as <code>%regex = '[^aeiou]'</code>; the circumflex, or "caret," (<tt>^</tt>) has the meaning of "negation" at the start of a character class. The EBCDIC code that <var>RegexMatch</var> uses for the circumflex is X'5F', as used by codepage 1047. Using the hex code point as above ensures that your regex will work whether the program was entered with codepage 1047 or 0037.		This is the same as <code>%regex = '[^aeiou]'</code>; the circumflex, or "caret," (<tt>^</tt>) has the meaning of "negation" at the start of a character class. The EBCDIC code that <var>RegexMatch</var> uses for the circumflex is X'5F', as used by codepage 1047. Using the hex code point as above ensures that your regex will work whether the program was entered with codepage 1047 or 0037.

	<li>The right hand side of that statement (<code>'[' '5F':HexToString 'aeiou]'</code>) uses the [[Implicit concatenation\|implicit concatenation]] feature ~~introduced in version 7.9 of the <var class="product">Sirius Mods</var>~~.		<li>The right hand side of that statement (<code>'[' '5F':HexToString 'aeiou]'</code>) uses the [[Implicit concatenation\|implicit concatenation]] feature.

	<li>This use of <var>RegexMatch</var> is like the standard <var class="product">~~User Language~~</var> <var>$Verify</var> function, although it indicates not just whether all characters in the given string are in the regex, but also the position (plus one) of the first character that is not in the regex.		<li>This use of <var>RegexMatch</var> is like the standard <var class="product">SOUL</var> <var>$Verify</var> function, although it indicates not just whether all characters in the given string are in the regex, but also the position (plus one) of the first character that is not in the regex.
	</ul>		</ul>

JAL: /* Finding the first position that is not one of several characters */ switch 2 lines in request

2016-05-11T18:10:26Z

Finding the first position that is not one of several characters: switch 2 lines in request

← Older revision		Revision as of 18:10, 11 May 2016
Line 84:		Line 84:
	A programming task similar to that in the preceding example is finding the position of the first character that is not one of a set of characters. This task, which is not as amenable to processing with the <var>StringTokenizer</var> as the task in the preceding example, is readily accomplished with <var>RegexMatch</var>. Here is an example:		A programming task similar to that in the preceding example is finding the position of the first character that is not one of a set of characters. This task, which is not as amenable to processing with the <var>StringTokenizer</var> as the task in the preceding example, is readily accomplished with <var>RegexMatch</var>. Here is an example:
	<p class="code">%regex = '[' '5F':HexToString 'aeiou]'; * Scan for any non-vowel		<p class="code">%regex = '[' '5F':HexToString 'aeiou]'; * Scan for any non-vowel
			%str = 'albatross'
	%i = %str:regexMatch(%regex)		%i = %str:regexMatch(%regex)
	~~%str = 'albatross'~~
	if %i then		if %i then
	printText Before non-vowel: {%str:Left(%i - 2)}		printText Before non-vowel: {%str:Left(%i - 2)}

JAL: /* Syntax terms */

2012-11-05T17:36:08Z

Syntax terms

← Older revision		Revision as of 17:36, 5 November 2012
Line 34:		Line 34:
	</table></td></tr>		</table></td></tr>

	<tr><th><var>CaptureList</var></th><td></td></tr>		<tr><th><var>CaptureList</var></th>
			<td>This argument is available for Sirius development testing purposes only. Not an ordinary user parameter.</td></tr>
	</table>		</table>

JAL at 22:05, 2 November 2012

2012-11-02T22:05:38Z

Show changes

JAL2 at 21:53, 7 August 2012

2012-08-07T21:53:54Z

← Older revision		Revision as of 21:53, 7 August 2012
Line 21:		Line 21:
	<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><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>		<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>M</var> mode is ignored if <var>C</var> (XML Schema) mode is specified.</td></tr>
	<tr><th><var>C</var></th>		<tr><th><var>C</var></th>
	<td>Do the match according to <var>[[Regex_processing#XML_Schema_mode\|"XML Schema regex rules"]]</var>. Each <var class="term">regex</var> is implicitly anchored at the beginning and end, and no characters serve as anchors.</td></tr>		<td>Do the match according to <var>[[Regex_processing#XML_Schema_mode\|"XML Schema regex rules"]]</var>. Each <var class="term">regex</var> is implicitly anchored at the beginning and end, and no characters serve as anchors.</td></tr>

JAL2: /* Using a few other regex features */

2011-07-20T15:13:16Z

Using a few other regex features

← Older revision		Revision as of 15:13, 20 July 2011
Line 88:		Line 88:
	</ul>		</ul>

	===Using ~~a few~~ other regex features===		===Using some other regex features===
	The following example tests whether the regex <code>\bc?[5-8]</code> matches <code>ab6</code> (it does, and note that it matches "in the middle" of the string).		The following example tests whether the regex <code>\bc?[5-8]</code> matches <code>ab6</code> (it does, and note that it matches "in the middle" of the string).
	<p class="code">begin		<p class="code">begin

← Older revision		Revision as of 17:05, 21 January 2022
Line 129:		Line 129:
	{{Template:String:RegexMatch footer}}		{{Template:String:RegexMatch footer}}

	[[Category:Regular ~~Expression Processing~~]]		[[Category:Regular expression processing]]