--- In [email protected], "Sheri" <sheri...@...> wrote:
> The problem with "literal" option should have shown up in
> regexPluginTest 43c, but the intending replacement string and option
> were not defined prior to or applied to the test. The literal option
> is supposed to bypass all evaluation and substitution applied to the
> replacement string.
Is what follows a replacement regexPluginTest 43c?
> Examples:
>
> win.debug(?"Expected: \x22This subject had quotations.\x22")
> win.debug("Actual:", regex.pcrereplace(?X"X, ;;+
> ?X"This subject has quotations."X, ?"\x22", "literal"))
> ;The quotations should be literally replaced by backslash x 2 2.
> win.debug("")
> local notefolder = pprofolder++?"notes"
> win.debug("Expected: Notes folder: "++pprofolder++?"Notes")
> win.debug("Actual: ",regex.pcrereplace(?": \K", ?"Notes folder: ", ;;+
> notefolder, "literal"))
> here are the newer defines in pcre.h
newish Compile-Time options: add new option keywords as follows,
unless you prefer others:
PCRE_JAVASCRIPT_COMPAT javascript
PCRE_BSR_ANYCRLF r_matches_crlf
PCRE_BSR_UNICODE r_matches_all
newish Exec-Time options: add new option keywords as follows, unless
you prefer others:
PCRE_BSR_ANYCRLF r_matchescrlf
PCRE_BSR_UNICODE r_matchesall
newish property of the pcre library: : add new keyword for
getPcreProperty unless you prefer another:
PCRE_CONFIG_BSR r_matches
