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

Diff of /code/trunk/ChangeLog

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

revision 165 by ph10, Wed May 9 10:50:57 2007 UTC revision 200 by ph10, Wed Aug 1 09:10:40 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.2 01-May-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     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
20        when the subject happened to end in the byte 0x85 (e.g. if the last
21        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
22        characters but of course it shouldn't be taken as a newline when it is part
23        of another character. The bug was that, for an unlimited repeat of . in
24        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
25        characters when looking for a newline.
26    
27     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
28    
29     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
30        in debug output.
31    
32     5. Arrange to use "%I64d" instead of "%lld" for long printing in the pcrecpp
33        unittest when running under MinGW.
34    
35     6. ESC_K was left out of the EBCDIC table.
36    
37     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
38        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
39        limit also applies to "virtual nesting" when a pattern is recursive, and in
40        this case 1000 isn't so big. I have been able to remove this limit at the
41        expense of backing off one optimization in certain circumstances. Normally,
42        when pcre_exec() would call its internal match() function recursively and
43        immediately return the result unconditionally, it uses a "tail recursion"
44        feature to save stack. However, when a subpattern that can match an empty
45        string has an unlimited repetition quantifier, it no longer makes this
46        optimization. That gives it a stack frame in which to save the data for
47        checking that an empty string has been matched. Previously this was taken
48        from the 1000-entry workspace that had been reserved. So now there is no
49        explicit limit, but more stack is used.
50    
51     8. Applied Daniel's patches to solve problems with the import/export magic
52        syntax that is required for Windows, and which was going wrong for the
53        pcreposix and pcrecpp parts of the library. These were overlooked when this
54        problem was solved for the main library.
55    
56    
57    Version 7.2 19-Jun-07
58  ---------------------  ---------------------
59    
60   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
# Line 22  Version 7.2 01-May-07 Line 75  Version 7.2 01-May-07
75      a small improvement under Linux. However, it saves one field in the frame      a small improvement under Linux. However, it saves one field in the frame
76      in all cases.      in all cases.
77    
78     6. Added more features from the forthcoming Perl 5.10:
79    
80        (a) (?-n) (where n is a string of digits) is a relative subroutine or
81            recursion call. It refers to the nth most recently opened parentheses.
82    
83        (b) (?+n) is also a relative subroutine call; it refers to the nth next
84            to be opened parentheses.
85    
86        (c) Conditions that refer to capturing parentheses can be specified
87            relatively, for example, (?(-2)... or (?(+3)...
88    
89        (d) \K resets the start of the current match so that everything before
90            is not part of it.
91    
92        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
93    
94        (f) \g{name} is another synonym - part of Perl 5.10's unification of
95            reference syntax.
96    
97        (g) (?| introduces a group in which the numbering of parentheses in each
98            alternative starts with the same number.
99    
100        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
101    
102     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
103        PCRE_INFO_JCHANGED.
104    
105     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
106        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
107        for detecting groups that can match an empty string.
108    
109     9. A pattern with a very large number of alternatives (more than several
110        hundred) was running out of internal workspace during the pre-compile
111        phase, where pcre_compile() figures out how much memory will be needed. A
112        bit of new cunning has reduced the workspace needed for groups with
113        alternatives. The 1000-alternative test pattern now uses 12 bytes of
114        workspace instead of running out of the 4096 that are available.
115    
116    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
117    
118    11. Applied patch from Google to remove an optimization that didn't quite work.
119        The report of the bug said:
120    
121          pcrecpp::RE("a*").FullMatch("aaa") matches, while
122          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
123          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
124    
125    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
126        it matched the wrong number of bytes.
127    
128    
129  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07
130  ---------------------  ---------------------

Legend:
Removed from v.165  
changed lines
  Added in v.200

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12