version 1.1.1.2, 2012/02/21 23:50:25
|
version 1.1.1.3, 2012/10/09 09:19:17
|
Line 1
|
Line 1
|
ChangeLog for PCRE |
ChangeLog for PCRE |
------------------ |
------------------ |
|
|
|
Version 8.31 06-July-2012 |
|
------------------------- |
|
|
|
1. Fixing a wrong JIT test case and some compiler warnings. |
|
|
|
2. Removed a bashism from the RunTest script. |
|
|
|
3. Add a cast to pcre_exec.c to fix the warning "unary minus operator applied |
|
to unsigned type, result still unsigned" that was given by an MS compiler |
|
on encountering the code "-sizeof(xxx)". |
|
|
|
4. Partial matching support is added to the JIT compiler. |
|
|
|
5. Fixed several bugs concerned with partial matching of items that consist |
|
of more than one character: |
|
|
|
(a) /^(..)\1/ did not partially match "aba" because checking references was |
|
done on an "all or nothing" basis. This also applied to repeated |
|
references. |
|
|
|
(b) \R did not give a hard partial match if \r was found at the end of the |
|
subject. |
|
|
|
(c) \X did not give a hard partial match after matching one or more |
|
characters at the end of the subject. |
|
|
|
(d) When newline was set to CRLF, a pattern such as /a$/ did not recognize |
|
a partial match for the string "\r". |
|
|
|
(e) When newline was set to CRLF, the metacharacter "." did not recognize |
|
a partial match for a CR character at the end of the subject string. |
|
|
|
6. If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when |
|
running pcretest, the text "(JIT)" added to the output whenever JIT is |
|
actually used to run the match. |
|
|
|
7. Individual JIT compile options can be set in pcretest by following -s+[+] |
|
or /S+[+] with a digit between 1 and 7. |
|
|
|
8. OP_NOT now supports any UTF character not just single-byte ones. |
|
|
|
9. (*MARK) control verb is now supported by the JIT compiler. |
|
|
|
10. The command "./RunTest list" lists the available tests without actually |
|
running any of them. (Because I keep forgetting what they all are.) |
|
|
|
11. Add PCRE_INFO_MAXLOOKBEHIND. |
|
|
|
12. Applied a (slightly modified) user-supplied patch that improves performance |
|
when the heap is used for recursion (compiled with --disable-stack-for- |
|
recursion). Instead of malloc and free for each heap frame each time a |
|
logical recursion happens, frames are retained on a chain and re-used where |
|
possible. This sometimes gives as much as 30% improvement. |
|
|
|
13. As documented, (*COMMIT) is now confined to within a recursive subpattern |
|
call. |
|
|
|
14. As documented, (*COMMIT) is now confined to within a positive assertion. |
|
|
|
15. It is now possible to link pcretest with libedit as an alternative to |
|
libreadline. |
|
|
|
16. (*COMMIT) control verb is now supported by the JIT compiler. |
|
|
|
17. The Unicode data tables have been updated to Unicode 6.1.0. |
|
|
|
18. Added --file-list option to pcregrep. |
|
|
|
19. Added binary file support to pcregrep, including the -a, --binary-files, |
|
-I, and --text options. |
|
|
|
20. The madvise function is renamed for posix_madvise for QNX compatibility |
|
reasons. Fixed by Giuseppe D'Angelo. |
|
|
|
21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler. |
|
|
|
22. Changed the option for creating symbolic links for 16-bit man pages from |
|
-s to -sf so that re-installing does not cause issues. |
|
|
|
23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it. |
|
|
|
24. Fixed a very old bug in pcretest that caused errors with restarted DFA |
|
matches in certain environments (the workspace was not being correctly |
|
retained). Also added to pcre_dfa_exec() a simple plausibility check on |
|
some of the workspace data at the beginning of a restart. |
|
|
|
25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R |
|
was not doing so when it should - probably a typo introduced by SVN 528 |
|
(change 8.10/14). |
|
|
|
26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the |
|
\w+ when the character tables indicated that \x{c4} was a word character. |
|
There were several related cases, all because the tests for doing a table |
|
lookup were testing for characters less than 127 instead of 255. |
|
|
|
27. If a pattern contains capturing parentheses that are not used in a match, |
|
their slots in the ovector are set to -1. For those that are higher than |
|
any matched groups, this happens at the end of processing. In the case when |
|
there were back references that the ovector was too small to contain |
|
(causing temporary malloc'd memory to be used during matching), and the |
|
highest capturing number was not used, memory off the end of the ovector |
|
was incorrectly being set to -1. (It was using the size of the temporary |
|
memory instead of the true size.) |
|
|
|
28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an |
|
ovector size, it uses memory at the end of the block that it has got. |
|
|
|
29. Check for an overlong MARK name and give an error at compile time. The |
|
limit is 255 for the 8-bit library and 65535 for the 16-bit library. |
|
|
|
30. JIT compiler update. |
|
|
|
31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger |
|
Rill for the patch. |
|
|
|
32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11. |
|
|
|
33. Variable renamings in the PCRE-JIT compiler. No functionality change. |
|
|
|
34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of |
|
SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib) |
|
was enabled. |
|
|
|
35. Improve JIT code generation for greedy plus quantifier. |
|
|
|
36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group |
|
1 to "aa" instead of to an empty string. The bug affected repeated groups |
|
that could potentially match an empty string. |
|
|
|
37. Optimizing single character iterators in JIT. |
|
|
|
38. Wide characters specified with \uxxxx in JavaScript mode are now subject to |
|
the same checks as \x{...} characters in non-JavaScript mode. Specifically, |
|
codepoints that are too big for the mode are faulted, and in a UTF mode, |
|
disallowed codepoints are also faulted. |
|
|
|
39. If PCRE was compiled with UTF support, in three places in the DFA |
|
matcher there was code that should only have been obeyed in UTF mode, but |
|
was being obeyed unconditionally. In 8-bit mode this could cause incorrect |
|
processing when bytes with values greater than 127 were present. In 16-bit |
|
mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In |
|
both cases the values are those that cannot be the first data item in a UTF |
|
character. The three items that might have provoked this were recursions, |
|
possessively repeated groups, and atomic groups. |
|
|
|
40. Ensure that libpcre is explicitly listed in the link commands for pcretest |
|
and pcregrep, because some OS require shared objects to be explicitly |
|
passed to ld, causing the link step to fail if they are not. |
|
|
|
41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit |
|
mode, patterns that started with \h* or \R* might be incorrectly matched. |
|
|
|
|
Version 8.30 04-February-2012 |
Version 8.30 04-February-2012 |
----------------------------- |
----------------------------- |
|
|