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

Diff of /code/trunk/ChangeLog

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

revision 392 by ph10, Tue Mar 17 21:30:30 2009 UTC revision 420 by ph10, Wed Aug 12 17:32:27 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.9 xx-xxx-09  Version 8.00 ??-???-??
5    ----------------------
6    
7    1.  The table for translating pcre_compile() error codes into POSIX error codes
8        was out-of-date, and there was no check on the pcre_compile() error code
9        being within the table. This could lead to an OK return being given in
10        error.
11    
12    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
13        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
14        in a Windows environment.
15    
16    3.  The pcregrep --count option prints the count for each file even when it is
17        zero, as does GNU grep. However, pcregrep was also printing all files when
18        --files-with-matches was added. Now, when both options are given, it prints
19        counts only for those files that have at least one match. (GNU grep just
20        prints the file name in this circumstance, but including the count seems
21        more useful - otherwise, why use --count?) Also ensured that the
22        combination -clh just lists non-zero counts, with no names.
23    
24    
25    Version 7.9 11-Apr-09
26  ---------------------  ---------------------
27    
28  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
# Line 17  Version 7.9 xx-xxx-09 Line 38  Version 7.9 xx-xxx-09
38      but BOOL is not.      but BOOL is not.
39    
40  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
41      PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.      PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
42    
43  4.  The pcregrep documentation said spaces were inserted as well as colons (or  4.  The pcregrep documentation said spaces were inserted as well as colons (or
44      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
# Line 42  Version 7.9 xx-xxx-09 Line 63  Version 7.9 xx-xxx-09
63      correctly handled. The rule now is that both the assertion and what follows      correctly handled. The rule now is that both the assertion and what follows
64      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
65    
66  9.  If auto-callout was enabled in a pattern with a conditional group, PCRE  9.  If auto-callout was enabled in a pattern with a conditional group whose
67      could crash during matching.      condition was an assertion, PCRE could crash during matching, both with
68        pcre_exec() and pcre_dfa_exec().
69    
70  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
71      used for matching.      used for matching.
# Line 64  Version 7.9 xx-xxx-09 Line 86  Version 7.9 xx-xxx-09
86      from Martin Jerabek that uses macro names for all relevant character and      from Martin Jerabek that uses macro names for all relevant character and
87      string constants.      string constants.
88    
89    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
90        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
91        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
92        these, but not everybody uses configure.
93    
94    19. A conditional group that had only one branch was not being correctly
95        recognized as an item that could match an empty string. This meant that an
96        enclosing group might also not be so recognized, causing infinite looping
97        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
98        with the subject "ab", where knowledge that the repeated group can match
99        nothing is needed in order to break the loop.
100    
101    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
102        exec(), but without supplying a callout function, matching went wrong.
103    
104    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
105        leak if the size of the offset vector was greater than 30. When the vector
106        is smaller, the saved offsets during recursion go onto a local stack
107        vector, but for larger vectors malloc() is used. It was failing to free
108        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
109        error, in fact).
110    
111    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
112        heapframe that is used only when UTF-8 support is enabled. This caused no
113        problem, but was untidy.
114    
115    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
116        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
117        included within another project.
118    
119    24. Steven Van Ingelgem's patches to add more options to the CMake support,
120        slightly modified by me:
121    
122          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
123              not building pcregrep.
124    
125          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
126              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
127    
128    25. Forward references, both numeric and by name, in patterns that made use of
129        duplicate group numbers, could behave incorrectly or give incorrect errors,
130        because when scanning forward to find the reference group, PCRE was not
131        taking into account the duplicate group numbers. A pattern such as
132        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
133    
134    26. Changed a few more instances of "const unsigned char *" to USPTR, making
135        the feature of a custom pointer more persuasive (as requested by a user).
136    
137    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
138        pcretest.c, inside #ifndefs, because it seems they are sometimes already
139        pre-defined.
140    
141    28. Added support for (*UTF8) at the start of a pattern.
142    
143    29. Arrange for flags added by the "release type" setting in CMake to be shown
144        in the configuration summary.
145    
146    
147  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08
148  ---------------------  ---------------------

Legend:
Removed from v.392  
changed lines
  Added in v.420

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12