From deee8d934595c4b856361955aaf4dd26995d203a Mon Sep 17 00:00:00 2001 From: ph10 Date: Sat, 17 Oct 2015 13:50:56 +0000 Subject: Implement --never-backslash-C git-svn-id: svn://vcs.exim.org/pcre2/code/trunk@386 6239d852-aaf2-0410-a92c-79f79f948069 --- README | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'README') diff --git a/README b/README index 955d45a..49eaaf6 100644 --- a/README +++ b/README @@ -219,6 +219,13 @@ library. They are also documented in the pcre2build man page. to be the end of a line (see above). However, the caller of PCRE2 can restrict \R to match only CR, LF, or CRLF. You can make this the default by adding --enable-bsr-anycrlf to the "configure" command (bsr = "backslash R"). + +. In a pattern, the escape sequence \C matches a single code unit, even in a + UTF mode. This can be dangerous because it breaks up multi-code-unit + characters. You can build PCRE2 with the use of \C permanently locked out by + adding --enable-never-backslash-C (note the upper case C) to the "configure" + command. When \C is allowed by the library, individual applications can lock + it out by calling pcre2_compile() with the PCRE2_NEVER_BACKSLASH_C option. . PCRE2 has a counter that limits the depth of nesting of parentheses in a pattern. This limits the amount of system stack that a pattern uses when it @@ -833,4 +840,4 @@ The distribution should contain the files listed below. Philip Hazel Email local part: ph10 Email domain: cam.ac.uk -Last updated: 16 July 2015 +Last updated: 16 October 2015 -- cgit v1.2.1