search for: pcre2pattern

...e documented result on at least one >> system (which is "123456789", because "{,5}" is documented to not be >> a quantifier, so it should only match the literal string "{,5}"). This is a change in documented behavior in PCRE. PCRE2 10.43 (share/man/man3/pcre2pattern.3) says: "If the first number is omitted, the lower limit is taken as zero; in this case the upper limit must be present. X{,4} is interpreted as X{0,4}. In earlier versions such a sequence was not interpreted as a quantifier. Other regular expression engines may behave either way."...

Thanks Tomas. Do note that my original post also mentioned a bug or doc error in the PCRE docs for this regexp: > - perl = TRUE does *not* give the documented result on at least one > system (which is "123456789", because "{,5}" is documented to not be a > quantifier, so it should only match the literal string "{,5}"). Duncan On 2024-08-01 6:49 a.m.,

...rted to Unicode prior to matching. Best, B [1]: https://github.com/r-devel/r-svn/blob/a8a3c4d6902525e4222e0bbf5b512f36e2ceac3d/src/main/grep.c#L1385 [2]: https://github.com/r-devel/r-svn/blob/a8a3c4d6902525e4222e0bbf5b512f36e2ceac3d/src/main/grep.c#L1378 [3]: https://pcre.org/current/doc/html/pcre2pattern.html > > Duncan Murdoch >> >> Best, >> >> B. >> >> >>> >>> >>> However, this thread on SO:? https://stackoverflow.com/q/76749529 gives >>> some indication that this is not true for `perl = TRUE`.? Specifically: >>...