/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 923 by ph10, Tue Feb 21 13:25:05 2012 UTC revision 963 by ph10, Sat Apr 21 18:06:31 2012 UTC
# Line 9  Version 8.31 Line 9  Version 8.31
9  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
10    
11  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
12      to unsigned type, result still unsigned" that was given by an MS compiler      to unsigned type, result still unsigned" that was given by an MS compiler
13      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
14    
15  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
16    
17  5.  Fixed several bugs concerned with partial matching of items that consist  5.  Fixed several bugs concerned with partial matching of items that consist
18      of more than one character:      of more than one character:
19    
20      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
21          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
22          references.          references.
23    
24      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
25          subject.          subject.
26    
27      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
28          characters at the end of the subject.          characters at the end of the subject.
29    
30      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
31          a partial match for the string "\r".          a partial match for the string "\r".
32    
33      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
34          a partial match for a CR character at the end of the subject string.          a partial match for a CR character at the end of the subject string.
35    
36  6.  When matching is performed using JIT-compiled code, the flag bit  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
37      PCRE_EXTRA_USED_JIT is set in the pcre_extra block and can be tested by the      running pcretest, the text "(JIT)" added to the output whenever JIT is
38      caller. This bit is checked by pcretest if JIT is requested by /S++ or -s++      actually used to run the match.
39      (instead of just /S+ or -s+) and the text "(JIT)" added to the output if  
40      the bit is set.  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
   
 7.  Individual JIT compile options can be set in pcretest by following -s+[+]  
41      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
42    
43    8.  OP_NOT now supports any UTF character not just single-byte ones.
44    
45    9.  (*MARK) control verb is now supported by the JIT compiler.
46    
47    10. The command "./RunTest list" lists the available tests without actually
48        running any of them. (Because I keep forgetting what they all are.)
49    
50    11. Add PCRE_INFO_MAXLOOKBEHIND.
51    
52    12. Applied a (slightly modified) user-supplied patch that improves performance
53        when the heap is used for recursion (compiled with --disable-stack-for-
54        recursion). Instead of malloc and free for each heap frame each time a
55        logical recursion happens, frames are retained on a chain and re-used where
56        possible. This sometimes gives as much as 30% improvement.
57    
58    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
59        call.
60    
61    14. As documented, (*COMMIT) is now confined to within a positive assertion.
62    
63    15. It is now possible to link pcretest with libedit as an alternative to
64        libreadline.
65    
66    16. (*COMMIT) control verb is now supported by the JIT compiler.
67    
68    17. The Unicode data tables have been updated to Unicode 6.1.0.
69    
70    18. Added --file-list option to pcregrep.
71    
72    19. Added binary file support to pcregrep, including the -a, --binary-files,
73        -I, and --text options.
74    
75    20. The madvise function is renamed for posix_madvise for QNX compatibility
76        reasons. Fixed by Giuseppe D'Angelo.
77    
78    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
79    
80    22. Changed the option for creating symbolic links for 16-bit man pages from
81        -s to -sf so that re-installing does not cause issues.
82    
83    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
84    
85    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
86        matches in certain environments (the workspace was not being correctly
87        retained). Also added to pcre_dfa_exec() a simple plausibility check on
88        some of the workspace data at the beginning of a restart.
89    
90    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
91        was not doing so when it should - probably a typo introduced by SVN 528
92        (change 8.10/14).
93    
94    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
95        \w+ when the character tables indicated that \x{c4} was a word character.
96        There were several related cases, all because the tests for doing a table
97        lookup were testing for characters less than 127 instead of 255.
98    
99    27. If a pattern contains capturing parentheses that are not used in a match,
100        their slots in the ovector are set to -1. For those that are higher than
101        any matched groups, this happens at the end of processing. In the case when
102        there were back references that the ovector was too small to contain
103        (causing temporary malloc'd memory to be used during matching), and the
104        highest capturing number was not used, memory off the end of the ovector
105        was incorrectly being set to -1. (It was using the size of the temporary
106        memory instead of the true size.)
107    
108    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
109        ovector size, it uses memory at the end of the block that it has got.
110    
111    
112  Version 8.30 04-February-2012  Version 8.30 04-February-2012
113  -----------------------------  -----------------------------
Legend:
Removed from v.923  
changed lines
  Added in v.963
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12