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

Diff of /code/trunk/ChangeLog

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

revision 131 by ph10, Mon Mar 26 15:10:12 2007 UTC revision 189 by ph10, Thu Jul 5 11:50:49 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.1 12-Mar-07  Version 7.3 05-Jul-07
5    ---------------------
6    
7     1. In the rejigging of the build system that eventually resulted in 7.1, the
8        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
9        brackets there is not right, since it causes compilers to look for an
10        installed pcre.h, not the version that is in the source that is being
11        compiled (which of course may be different). I have changed it back to:
12    
13          #include "pcre.h"
14    
15        I have a vague recollection that the change was concerned with compiling in
16        different directories, but in the new build system, that is taken care of
17        by the VPATH setting the Makefile.
18    
19    
20    
21    Version 7.2 19-Jun-07
22    ---------------------
23    
24     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
25        which is apparently normally available under Windows.
26    
27     2. Re-jig the pcregrep tests with different newline settings in an attempt
28        to make them independent of the local environment's newline setting.
29    
30     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
31    
32     4. Some of the "internals" tests were previously cut out when the link size
33        was not 2, because the output contained actual offsets. The recent new
34        "Z" feature of pcretest means that these can be cut out, making the tests
35        usable with all link sizes.
36    
37     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
38        stack recursion. This gives a massive performance boost under BSD, but just
39        a small improvement under Linux. However, it saves one field in the frame
40        in all cases.
41    
42     6. Added more features from the forthcoming Perl 5.10:
43    
44        (a) (?-n) (where n is a string of digits) is a relative subroutine or
45            recursion call. It refers to the nth most recently opened parentheses.
46    
47        (b) (?+n) is also a relative subroutine call; it refers to the nth next
48            to be opened parentheses.
49    
50        (c) Conditions that refer to capturing parentheses can be specified
51            relatively, for example, (?(-2)... or (?(+3)...
52    
53        (d) \K resets the start of the current match so that everything before
54            is not part of it.
55    
56        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
57    
58        (f) \g{name} is another synonym - part of Perl 5.10's unification of
59            reference syntax.
60    
61        (g) (?| introduces a group in which the numbering of parentheses in each
62            alternative starts with the same number.
63    
64        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
65    
66     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
67        PCRE_INFO_JCHANGED.
68    
69     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
70        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
71        for detecting groups that can match an empty string.
72    
73     9. A pattern with a very large number of alternatives (more than several
74        hundred) was running out of internal workspace during the pre-compile
75        phase, where pcre_compile() figures out how much memory will be needed. A
76        bit of new cunning has reduced the workspace needed for groups with
77        alternatives. The 1000-alternative test pattern now uses 12 bytes of
78        workspace instead of running out of the 4096 that are available.
79    
80    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
81    
82    11. Applied patch from Google to remove an optimization that didn't quite work.
83        The report of the bug said:
84    
85          pcrecpp::RE("a*").FullMatch("aaa") matches, while
86          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
87          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
88    
89    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
90        it matched the wrong number of bytes.
91    
92    
93    Version 7.1 24-Apr-07
94  ---------------------  ---------------------
95    
96   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
# Line 33  Version 7.1 12-Mar-07 Line 122  Version 7.1 12-Mar-07
122   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
123      Weber: (1) pcre_internal.h was missing some function renames; (2) updated      Weber: (1) pcre_internal.h was missing some function renames; (2) updated
124      makevp.bat for the current PCRE, using the additional files      makevp.bat for the current PCRE, using the additional files
125      makevp-c.txt, makevp-l.txt, and pcregexp.pas.      makevp_c.txt, makevp_l.txt, and pcregexp.pas.
126    
127   6. A Windows user reported a minor discrepancy with test 2, which turned out   6. A Windows user reported a minor discrepancy with test 2, which turned out
128      to be caused by a trailing space on an input line that had got lost in his      to be caused by a trailing space on an input line that had got lost in his
# Line 115  Version 7.1 12-Mar-07 Line 204  Version 7.1 12-Mar-07
204    
205  14. If erroroffset was passed as NULL to pcre_compile, it provoked a  14. If erroroffset was passed as NULL to pcre_compile, it provoked a
206      segmentation fault instead of returning the appropriate error message.      segmentation fault instead of returning the appropriate error message.
207    
208  15. In multiline mode when the newline sequence was set to "any", the pattern  15. In multiline mode when the newline sequence was set to "any", the pattern
209      ^$ would give a match between the \r and \n of a subject such as "A\r\nB".      ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
210      This doesn't seem right; it now treats the CRLF combination as the line      This doesn't seem right; it now treats the CRLF combination as the line
211      ending, and so does not match in that case. It's only a pattern such as ^$      ending, and so does not match in that case. It's only a pattern such as ^$
212      that would hit this one: something like ^ABC$ would have failed after \r      that would hit this one: something like ^ABC$ would have failed after \r
213      and then tried again after \r\n.      and then tried again after \r\n.
214    
215  16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"  16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
216      in an attempt to make files that differ only in their line terminators      in an attempt to make files that differ only in their line terminators
217      compare equal. This works on Linux.      compare equal. This works on Linux.
218    
219    17. Under certain error circumstances pcregrep might try to free random memory
220        as it exited. This is now fixed, thanks to valgrind.
221    
222    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
223        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
224        was because its rules for how to advance for /g after matching an empty
225        string at the end of a line did not allow for this case. They now check for
226        it specially.
227    
228    20. pcretest is supposed to handle patterns and data of any length, by
229        extending its buffers when necessary. It was getting this wrong when the
230        buffer for a data line had to be extended.
231    
232    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
233        CRLF as a newline sequence.
234    
235    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
236        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
237        I have nevertheless tidied it up.
238    
239    23. Added some casts to kill warnings from HP-UX ia64 compiler.
240    
241    24. Added a man page for pcre-config.
242    
243    
244  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06

Legend:
Removed from v.131  
changed lines
  Added in v.189

  ViewVC Help
Powered by ViewVC 1.1.5