/[pcre]/code/trunk/ChangeLog

Diff of /code/trunk/ChangeLog

Parent Directory | Revision Log | View Patch Patch

-revision 1378 by zherczeg,
Mon Oct 14 06:55:28 2013 UTC
+revision 1553 by ph10,
Tue Apr 28 11:36:24 2015 UTC
 Line 1
  ChangeLog for PCRE
  ------------------
- Version 8.34 xx-xxxx-201x
+ Version 8.37 28-April-2015
  --------------------------
+.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
+     for those parentheses to be closed with whatever has been captured so far.
+     However, it was failing to mark any other groups between the hightest
+     capture so far and the currrent group as "unset". Thus, the ovector for
+     those groups contained whatever was previously there. An example is the
+     pattern /(x)|((*ACCEPT))/ when matched against "abcd".
+.  If an assertion condition was quantified with a minimum of zero (an odd
+     thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
+.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
+     unrecognized modifier, a crash could occur.
+.  An attempt to do global matching in pcretest with a zero-length ovector
+     caused a crash.
+.  Fixed a memory leak during matching that could occur for a subpattern
+     subroutine call (recursive or otherwise) if the number of captured groups
+     that had to be saved was greater than ten.
+.  Catch a bad opcode during auto-possessification after compiling a bad UTF
+     string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
+     UTF with NO_UTF_CHECK is documented as having an undefined outcome.
+.  A UTF pattern containing a "not" match of a non-ASCII character and a
+     subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
+. When a pattern is compiled, it remembers the highest back reference so that
+    when matching, if the ovector is too small, extra memory can be obtained to
+    use instead. A conditional subpattern whose condition is a check on a
+    capture having happened, such as, for example in the pattern
+    /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
+    setting the highest backreference number. This mattered only if pcre_exec()
+    was called with an ovector that was too small to hold the capture, and there
+    was no other kind of back reference (a situation which is probably quite
+    rare). The effect of the bug was that the condition was always treated as
+    FALSE when the capture could not be consulted, leading to a incorrect
+    behaviour by pcre_exec(). This bug has been fixed.
+. A reference to a duplicated named group (either a back reference or a test
+    for being set in a conditional) that occurred in a part of the pattern where
+    PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
+    to be incorrectly calculated, leading to overwriting.
+. A mutually recursive set of back references such as (\2)(\1) caused a
+     segfault at study time (while trying to find the minimum matching length).
+     The infinite loop is now broken (with the minimum length unset, that is,
+     zero).
+. If an assertion that was used as a condition was quantified with a minimum
+     of zero, matching went wrong. In particular, if the whole group had
+     unlimited repetition and could match an empty string, a segfault was
+     likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
+     assertions to be quantified, but not if they are being used as conditions,
+     so the above pattern is faulted by Perl. PCRE has now been changed so that
+     it also rejects such patterns.
+. A possessive capturing group such as (a)*+ with a minimum repeat of zero
+     failed to allow the zero-repeat case if pcre2_exec() was called with an
+     ovector too small to capture the group.
+. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
+     Red Hat Product Security:
+     (a) A crash if /K and /F were both set with the option to save the compiled
+     pattern.
+     (b) Another crash if the option to print captured substrings in a callout
+     was combined with setting a null ovector, for example \O\C+ as a subject
+     string.
+. A pattern such as "((?2){0,1999}())?", which has a group containing a
+     forward reference repeated a large (but limited) number of times within a
+     repeated outer group that has a zero minimum quantifier, caused incorrect
+     code to be compiled, leading to the error "internal error:
+     previously-checked referenced subpattern not found" when an incorrect
+     memory address was read. This bug was reported as "heap overflow",
+     discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
+     CVE-2015-2325.
+. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
+     call within a group that also contained a recursive back reference caused
+     incorrect code to be compiled. This bug was reported as "heap overflow",
+     discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
+     number CVE-2015-2326.
+. Computing the size of the JIT read-only data in advance has been a source
+     of various issues, and new ones are still appear unfortunately. To fix
+     existing and future issues, size computation is eliminated from the code,
+     and replaced by on-demand memory allocation.
+. A pattern such as /(?i)[A-`]/, where characters in the other case are
+     adjacent to the end of the range, and the range contained characters with
+     more than one other case, caused incorrect behaviour when compiled in UTF
+     mode. In that example, the range a-j was left out of the class.
+. Fix JIT compilation of conditional blocks, which assertion
+     is converted to (*FAIL). E.g: /(?(?!))/.
+. The pattern /(?(?!)^)/ caused references to random memory. This bug was
+     discovered by the LLVM fuzzer.
+. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
+     when this assertion was used as a condition, for example (?(?!)a|b). In
+     pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
+     error about an unsupported item.
+. For some types of pattern, for example /Z*(|d*){216}/, the auto-
+     possessification code could take exponential time to complete. A recursion
+     depth limit of 1000 has been imposed to limit the resources used by this
+     optimization.
+. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
+     such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
+     because \S ensures they are all in the class. The code for doing this was
+     interacting badly with the code for computing the amount of space needed to
+     compile the pattern, leading to a buffer overflow. This bug was discovered
+     by the LLVM fuzzer.
+. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
+     other kinds of group caused stack overflow at compile time. This bug was
+     discovered by the LLVM fuzzer.
+. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
+     between a subroutine call and its quantifier was incorrectly compiled,
+     leading to buffer overflow or other errors. This bug was discovered by the
+     LLVM fuzzer.
+. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
+     assertion after (?(. The code was failing to check the character after
+     (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
+     was discovered by the LLVM fuzzer.
+. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
+     a fixed maximum following a group that contains a subroutine reference was
+     incorrectly compiled and could trigger buffer overflow. This bug was
+     discovered by the LLVM fuzzer.
+. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
+     caused a stack overflow instead of the diagnosis of a non-fixed length
+     lookbehind assertion. This bug was discovered by the LLVM fuzzer.
+. The use of \K in a positive lookbehind assertion in a non-anchored pattern
+     (e.g. /(?<=\Ka)/) could make pcregrep loop.
+. There was a similar problem to 36 in pcretest for global matches.
+. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
+     and a subsequent item in the pattern caused a non-match, backtracking over
+     the repeated \X did not stop, but carried on past the start of the subject,
+     causing reference to random memory and/or a segfault. There were also some
+     other cases where backtracking after \C could crash. This set of bugs was
+     discovered by the LLVM fuzzer.
+. The function for finding the minimum length of a matching string could take
+     a very long time if mutual recursion was present many times in a pattern,
+     for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
+     method has been implemented. This infelicity was discovered by the LLVM
+     fuzzer.
+. Static linking against the PCRE library using the pkg-config module was
+     failing on missing pthread symbols.
+ Version 8.36 26-September-2014
+ ------------------------------
+.  Got rid of some compiler warnings in the C++ modules that were shown up by
+     -Wmissing-field-initializers and -Wunused-parameter.
+.  The tests for quantifiers being too big (greater than 65535) were being
+     applied after reading the number, and stupidly assuming that integer
+     overflow would give a negative number. The tests are now applied as the
+     numbers are read.
+.  Tidy code in pcre_exec.c where two branches that used to be different are
+     now the same.
+.  The JIT compiler did not generate match limit checks for certain
+     bracketed expressions with quantifiers. This may lead to exponential
+     backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
+     issue should be resolved now.
+.  Fixed an issue, which occures when nested alternatives are optimized
+     with table jumps.
+.  Inserted two casts and changed some ints to size_t in the light of some
+     reported 64-bit compiler warnings (Bugzilla 1477).
+.  Fixed a bug concerned with zero-minimum possessive groups that could match
+     an empty string, which sometimes were behaving incorrectly in the
+     interpreter (though correctly in the JIT matcher). This pcretest input is
+     an example:
+       '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
+       NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
+     the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
+     JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
+     for an empty string was breaking the inner loop and carrying on at a lower
+     level, when possessive repeated groups should always return to a higher
+     level as they have no backtrack points in them. The empty string test now
+     occurs at the outer level.
+.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
+     ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
+.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
+     doesn't).
+. Change 8.34/15 introduced a bug that caused the amount of memory needed
+     to hold a pattern to be incorrectly computed (too small) when there were
+     named back references to duplicated names. This could cause "internal
+     error: code overflow" or "double free or corruption" or other memory
+     handling errors.
+. When named subpatterns had the same prefixes, back references could be
+     confused. For example, in this pattern:
+       /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
+     the reference to 'Name' was incorrectly treated as a reference to a
+     duplicate name.
+. A pattern such as /^s?c/mi8 where the optional character has more than
+     one "other case" was incorrectly compiled such that it would only try to
+     match starting at "c".
+. When a pattern starting with \s was studied, VT was not included in the
+     list of possible starting characters; this should have been part of the
+.34/18 patch.
+. If a character class started [\Qx]... where x is any character, the class
+     was incorrectly terminated at the ].
+. If a pattern that started with a caseless match for a character with more
+     than one "other case" was studied, PCRE did not set up the starting code
+     unit bit map for the list of possible characters. Now it does. This is an
+     optimization improvement, not a bug fix.
+. The Unicode data tables have been updated to Unicode 7.0.0.
+. Fixed a number of memory leaks in pcregrep.
+. Avoid a compiler warning (from some compilers) for a function call with
+     a cast that removes "const" from an lvalue by using an intermediate
+     variable (to which the compiler does not object).
+. Incorrect code was compiled if a group that contained an internal recursive
+     back reference was optional (had quantifier with a minimum of zero). This
+     example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
+     caused segmentation faults because of stack overflows at compile time.
+. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
+     group that is quantified with an indefinite repeat, caused a compile-time
+     loop which used up all the system stack and provoked a segmentation fault.
+     This was not the same bug as 19 above.
+. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
+     Patch by Mike Frysinger.
+ Version 8.35 04-April-2014
+ --------------------------
+.  A new flag is set, when property checks are present in an XCLASS.
+     When this flag is not set, PCRE can perform certain optimizations
+     such as studying these XCLASS-es.
+.  The auto-possessification of character sets were improved: a normal
+     and an extended character set can be compared now. Furthermore
+     the JIT compiler optimizes more character set checks.
+.  Got rid of some compiler warnings for potentially uninitialized variables
+     that show up only when compiled with -O2.
+.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
+     of a match later then the end of the match. The pcretest program was not
+     handling the case sensibly - it was outputting from the start to the next
+     binary zero. It now reports this situation in a message, and outputs the
+     text from the end to the start.
+.  Fast forward search is improved in JIT. Instead of the first three
+     characters, any three characters with fixed position can be searched.
+     Search order: first, last, middle.
+.  Improve character range checks in JIT. Characters are read by an inprecise
+     function now, which returns with an unknown value if the character code is
+     above a certain threshold (e.g: 256). The only limitation is that the value
+     must be bigger than the threshold as well. This function is useful when
+     the characters above the threshold are handled in the same way.
+.  The macros whose names start with RAWUCHAR are placeholders for a future
+     mode in which only the bottom 21 bits of 32-bit data items are used. To
+     make this more memorable for those maintaining the code, the names have
+     been changed to start with UCHAR21, and an extensive comment has been added
+     to their definition.
+.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
+     to the export list in Makefile.am (they were accidentally omitted from the
+.34 tarball).
+.  The informational output from pcretest used the phrase "starting byte set"
+     which is inappropriate for the 16-bit and 32-bit libraries. As the output
+     for "first char" and "need char" really means "non-UTF-char", I've changed
+     "byte" to "char", and slightly reworded the output. The documentation about
+     these values has also been (I hope) clarified.
+. Another JIT related optimization: use table jumps for selecting the correct
+     backtracking path, when more than four alternatives are present inside a
+     bracket.
+. Empty match is not possible, when the minimum length is greater than zero,
+     and there is no \K in the pattern. JIT should avoid empty match checks in
+     such cases.
+. In a caseless character class with UCP support, when a character with more
+     than one alternative case was not the first character of a range, not all
+     the alternative cases were added to the class. For example, s and \x{17f}
+     are both alternative cases for S: the class [RST] was handled correctly,
+     but [R-T] was not.
+. The configure.ac file always checked for pthread support when JIT was
+     enabled. This is not used in Windows, so I have put this test inside a
+     check for the presence of windows.h (which was already tested for).
+. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
+     The algorithm provides a way to skip certain starting offsets, and usually
+     faster than linear prefix searches.
+. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
+     as for 'fr_FR' and 'french'. For some reason, however, it then used the
+     Windows-specific input and output files, which have 'french' screwed in.
+     So this could never have worked. One of the problems with locales is that
+     they aren't always the same. I have now updated RunTest so that it checks
+     the output of the locale test (test 3) against three different output
+     files, and it allows the test to pass if any one of them matches. With luck
+     this should make the test pass on some versions of Solaris where it was
+     failing. Because of the uncertainty, the script did not used to stop if
+     test 3 failed; it now does. If further versions of a French locale ever
+     come to light, they can now easily be added.
+. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
+     there was a message during ./configure, but it did not stop. This now
+     provokes an error. The invalid example in README has been corrected.
+     If a value less than the minimum is given, the minimum value has always
+     been used, but now a warning is given.
+. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
+     was a bug in the test system, which is now fixed. Also, the list of various
+     configurations that are tested for each release did not have one with both
+/32 bits and --enable-bar-anycrlf. It now does.
+. pcretest was missing "-C bsr" for displaying the \R default setting.
+. Little endian PowerPC systems are supported now by the JIT compiler.
+. The fast forward newline mechanism could enter to an infinite loop on
+     certain invalid UTF-8 input. Although we don't support these cases
+     this issue can be fixed by a performance optimization.
+. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
+     not take account if existing stack usage. There is now a new global
+     variable called pcre_stack_guard that can be set to point to an external
+     function to check stack availability. It is called at the start of
+     processing every parenthesized group.
+. A typo in the code meant that in ungreedy mode the max/min qualifier
+     behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
+     not match "ab".
+. When UTF was disabled, the JIT program reported some incorrect compile
+     errors. These messages are silenced now.
+. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
+     compiler.
+. Change all the temporary files used in RunGrepTest to be different to those
+     used by RunTest so that the tests can be run simultaneously, for example by
+     "make -j check".
+ Version 8.34 15-December-2013
+ -----------------------------
 .  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
      executable memory. Patch inspired by Carsten Klein.
 .  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
      this macro is never tested and has no effect, because the work to support
      coverage involves only compiling and linking options and special targets in
      the Makefile. The comment in config.h implied that defining the macro would
      enable coverage support, which is totally false. There was also support for
      setting this macro in the CMake files (my fault, I just copied it from
      configure). SUPPORT_GCOV has now been removed.
 .  Make a small performance improvement in strlen16() and strlen32() in
      pcretest.
 .  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
      detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
      these cases). There was also one in pcretest.c.
 .  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
 .  In UTF mode, the code for checking whether a group could match an empty
      string (which is used for indefinitely repeated groups to allow for
-Line 31 
 Version 8.34 xx-xxxx-201x
+Line 416 
 Version 8.34 xx-xxxx-201x
      data item and had a minimum repetition of zero (for example, [^\x{100}]* in
      UTF-8 mode). The effect was undefined: the group might or might not be
      deemed as matching an empty string, or the program might have crashed.
 .  The code for checking whether a group could match an empty string was not
      recognizing that \h, \H, \v, \V, and \R must match a character.
 .  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
      an empty string. If it can, pcretest shows this in its information output.
 .  Fixed two related bugs that applied to Unicode extended grapheme clusters
      that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
      matched by pcre_exec() without using JIT:
      (a) If the rest of the pattern did not match after a maximal run of
          grapheme clusters, the code for backing up to try with fewer of them
          did not always back up over a full grapheme when characters that do not
          have the modifier quality were involved, e.g. Hangul syllables.
      (b) If the match point in a subject started with modifier character, and
          there was no match, the code could incorrectly back up beyond the match
          point, and potentially beyond the first character in the subject,
          leading to a segfault or an incorrect match result.
 . A conditional group with an assertion condition could lead to PCRE
      recording an incorrect first data item for a match if no other first data
      item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
      first data item, and therefore matched "ca" after "c" instead of at the
      start.
 . Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
      bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
 . The source of pcregrep now includes z/OS-specific code so that it can be
      compiled for z/OS as part of the special z/OS distribution.
 . Added the -T and -TM options to pcretest.
 . The code in pcre_compile.c for creating the table of named capturing groups
      has been refactored. Instead of creating the table dynamically during the
      actual compiling pass, the information is remembered during the pre-compile
      pass (on the stack unless there are more than 20 named groups, in which
      case malloc() is used) and the whole table is created before the actual
      compile happens. This has simplified the code (it is now nearly 150 lines
      shorter) and prepared the way for better handling of references to groups
      with duplicate names.
 . A back reference to a named subpattern when there is more than one of the
      same name now checks them in the order in which they appear in the pattern.
      The first one that is set is used for the reference. Previously only the
      first one was inspected. This change makes PCRE more compatible with Perl.
 . Unicode character properties were updated from Unicode 6.3.0.
 . The compile-time code for auto-possessification has been refactored, based
      on a patch by Zoltan Herczeg. It now happens after instead of during
      compilation. The code is cleaner, and more cases are handled. The option
-     PCRE_NO_AUTO_POSSESSIFY is added for testing purposes, and the -O and /O
+     PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
-     options in pcretest are provided to set it.
+     options in pcretest are provided to set it. It can also be set by
+     (*NO_AUTO_POSSESS) at the start of a pattern.
-. The character VT has been added to the set of characters that match \s and
-     are generally treated as white space, following this same change in Perl
+. The character VT has been added to the default ("C" locale) set of
-.18. There is now no difference between "Perl space" and "POSIX space".
+     characters that match \s and are generally treated as white space,
+     following this same change in Perl 5.18. There is now no difference between
-. The code for checking named groups as conditions, either for being set or
+     "Perl space" and "POSIX space". Whether VT is treated as white space in
+     other locales depends on the locale.
+. The code for checking named groups as conditions, either for being set or
      for being recursed, has been refactored (this is related to 14 and 15
      above). Processing unduplicated named groups should now be as fast at
      numerical groups, and processing duplicated groups should be faster than
      before.
 . Two patches to the CMake build system, by Alexander Barkov:
        (1) Replace the "source" command by "." in CMakeLists.txt because
            "source" is a bash-ism.
        (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
            without these the CMake build does not work on Solaris.
 . Perl has changed its handling of \8 and \9. If there is no previously
      encountered capturing group of those numbers, they are treated as the
      literal characters 8 and 9 instead of a binary zero followed by the
      literals. PCRE now does the same.
 . Following Perl, added \o{} to specify codepoints in octal, making it
      possible to specify values greater than 0777 and also making them
      unambiguous.
 . Perl now gives an error for missing closing braces after \x{... instead of
      treating the string as literal. PCRE now does the same.
 . RunTest used to grumble if an inappropriate test was selected explicitly,
      but just skip it when running all tests. This make it awkward to run ranges
      of tests when one of them was inappropriate. Now it just skips any
      inappropriate tests, as it always did when running all tests.
 . If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
      character types such as \d or \w, too many callouts were inserted, and the
      data that they returned was rubbish.
 . In UCP mode, \s was not matching two of the characters that Perl matches,
      namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
      were matched by \h. The code has now been refactored so that the lists of
      the horizontal and vertical whitespace characters used for \h and \v (which
      are defined only in one place) are now also used for \s.
 . Add JIT support for the 64 bit TileGX architecture.
      Patch by Jiong Wang (Tilera Corporation).
+. Possessive quantifiers for classes (both explicit and automatically
+     generated) now use special opcodes instead of wrapping in ONCE brackets.
+. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
+     (because it's meaningless), this was not happening when PCRE_CASELESS was
+     set. Not wrong, but inefficient.
+. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
+     properties for \w, \d, etc) is present in a test regex. Otherwise if the
+     test contains no characters greater than 255, Perl doesn't realise it
+     should be using Unicode semantics.
+. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
+     [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
+     does in Unicode mode.
+. Added the "forbid" facility to pcretest so that putting tests into the
+     wrong test files can sometimes be quickly detected.
+. There is now a limit (default 250) on the depth of nesting of parentheses.
+     This limit is imposed to control the amount of system stack used at compile
+     time. It can be changed at build time by --with-parens-nest-limit=xxx or
+     the equivalent in CMake.
+. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
+     errors. Perl warns for these when in warning mode, but PCRE has no facility
+     for giving warnings.
+. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
+     However, this was not working for (?!) because it is optimized to (*FAIL),
+     for which PCRE does not allow quantifiers. The optimization is now disabled
+     when a quantifier follows (?!). I can't see any use for this, but it makes
+     things uniform.
+. Perl no longer allows group names to start with digits, so I have made this
+     change also in PCRE. It simplifies the code a bit.
+. In extended mode, Perl ignores spaces before a + that indicates a
+     possessive quantifier. PCRE allowed a space before the quantifier, but not
+     before the possessive +. It now does.
+. The use of \K (reset reported match start) within a repeated possessive
+     group such as (a\Kb)*+ was not working.
+. Document that the same character tables must be used at compile time and
+     run time, and that the facility to pass tables to pcre_exec() and
+     pcre_dfa_exec() is for use only with saved/restored patterns.
+. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
+     features for Builds with MSVC:
+. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
+        builds). The .rc files can be used to set FileDescription and many other
+        attributes.
+. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
+        This allows higher-level build scripts which want .pdb files to avoid
+        hard-coding the exact files needed."
+. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
+     mean "start of word" and "end of word", respectively, as a transition aid.
+. A minimizing repeat of a class containing codepoints greater than 255 in
+     non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
+     compiled to use the heap for recursion.
+. Got rid of some compiler warnings for unused variables when UTF but not UCP
+     is configured.
  Version 8.33 28-May-2013
  ------------------------

 Legend:



Removed from v.1378
 


changed lines


 
Added in v.1553
 Legend:



Removed from v.1378
 


changed lines


 
Added in v.1553
-Removed from v.1378
+Added in v.1553

	ViewVC Help
Powered by ViewVC 1.1.5