From 6dc01f74431a40dac698417d2947f0d8ddbd8c8c Mon Sep 17 00:00:00 2001 From: Karen Arutyunov Date: Mon, 28 Oct 2024 12:52:11 +0200 Subject: Make $regex.*search() functions not to match empty substrings in non empty strings --- doc/testscript.cli | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'doc/testscript.cli') diff --git a/doc/testscript.cli b/doc/testscript.cli index 18dac41..7f7522d 100644 --- a/doc/testscript.cli +++ b/doc/testscript.cli @@ -2372,8 +2372,8 @@ continuations. \h#syntax-regex|Output Regex| Instead of literal text the expected result in output here-strings and -here-documents can be specified as ECMAScript regular expressions (more -specifically, ECMA-262-based C++11 regular expressions). To signal the use of +here-documents can be specified as ECMAScript regular expressions, more +precisely, ECMA-262-based C++11 regular expressions. To signal the use of regular expressions the redirect must end with the \c{~} modifier, for example: @@ -3082,7 +3082,9 @@ illegal. Note that this builtin implementation deviates substantially from POSIX \c{sed} (as described next). Most significantly, the regular expression flavor -is ECMAScript (more specifically, ECMA-262-based C++11 regular expressions). +is ECMAScript, more precisely, ECMA-262-based C++11 regular expressions. Note +that the \c{match_not_null} flag is in effect unless the line being matched +is empty. \dl| -- cgit v1.1