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

Diff of /code/trunk/ChangeLog

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

revision 381 by ph10, Tue Mar 3 16:08:23 2009 UTC revision 418 by ph10, Fri Apr 24 09:17:18 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    
13    Version 7.9 11-Apr-09
14  ---------------------  ---------------------
15    
16  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
17      (pcretest), all targets were linked against these libraries. This included      (pcretest), all targets were linked against these libraries. This included
18      libpcre, libpcreposix, and libpcrecpp, even though they do not use these      libpcre, libpcreposix, and libpcrecpp, even though they do not use these
19      libraries. This caused unwanted dependencies to be created. This problem      libraries. This caused unwanted dependencies to be created. This problem
20      has been fixed, and now only pcregrep is linked with bzlib/zlib and only      has been fixed, and now only pcregrep is linked with bzlib/zlib and only
21      pcretest is linked with readline.      pcretest is linked with readline.
22    
23  2.  The "typedef int BOOL" in pcre_internal.h that was included inside the  2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
24      "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been      "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
25      moved outside it again, because FALSE and TRUE are already defined in AIX,      moved outside it again, because FALSE and TRUE are already defined in AIX,
26      but BOOL is not.      but BOOL is not.
27    
28  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
29      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.
30    
31  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
32      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
33      lines. This is not true; no spaces are inserted. I have also clarified the      lines. This is not true; no spaces are inserted. I have also clarified the
34      wording for the --colour (or --color) option.      wording for the --colour (or --color) option.
35    
36  5.  In pcregrep, when --colour was used with -o, the list of matching strings  5.  In pcregrep, when --colour was used with -o, the list of matching strings
37      was not coloured; this is different to GNU grep, so I have changed it to be      was not coloured; this is different to GNU grep, so I have changed it to be
38      the same.      the same.
39    
40  6.  When --colo(u)r was used in pcregrep, only the first matching substring in  6.  When --colo(u)r was used in pcregrep, only the first matching substring in
41      each matching line was coloured. Now it goes on to look for further matches      each matching line was coloured. Now it goes on to look for further matches
42      of any of the test patterns, which is the same behaviour as GNU grep.      of any of the test patterns, which is the same behaviour as GNU grep.
43    
44  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
45      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
46      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
47      seems to be how GNU grep behaves.      seems to be how GNU grep behaves.
48    
49  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
50      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
51      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
52      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
53    
54  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
55      could crash during matching.      condition was an assertion, PCRE could crash during matching, both with
56        pcre_exec() and pcre_dfa_exec().
57    
58    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
59        used for matching.
60    
61    11. Unicode property support in character classes was not working for
62        characters (bytes) greater than 127 when not in UTF-8 mode.
63    
64    12. Added the -M command line option to pcretest.
65    
66    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
67    
68    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
69    
70    16. Added comments and documentation about mis-use of no_arg in the C++
71        wrapper.
72    
73    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
74        from Martin Jerabek that uses macro names for all relevant character and
75        string constants.
76    
77    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
78        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
79        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
80        these, but not everybody uses configure.
81    
82    19. A conditional group that had only one branch was not being correctly
83        recognized as an item that could match an empty string. This meant that an
84        enclosing group might also not be so recognized, causing infinite looping
85        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
86        with the subject "ab", where knowledge that the repeated group can match
87        nothing is needed in order to break the loop.
88    
89    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
90        exec(), but without supplying a callout function, matching went wrong.
91    
92    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
93        leak if the size of the offset vector was greater than 30. When the vector
94        is smaller, the saved offsets during recursion go onto a local stack
95        vector, but for larger vectors malloc() is used. It was failing to free
96        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
97        error, in fact).
98    
99    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
100        heapframe that is used only when UTF-8 support is enabled. This caused no
101        problem, but was untidy.
102    
103    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
104        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
105        included within another project.
106    
107    24. Steven Van Ingelgem's patches to add more options to the CMake support,
108        slightly modified by me:
109    
110          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
111              not building pcregrep.
112    
113          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
114              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
115    
116    25. Forward references, both numeric and by name, in patterns that made use of
117        duplicate group numbers, could behave incorrectly or give incorrect errors,
118        because when scanning forward to find the reference group, PCRE was not
119        taking into account the duplicate group numbers. A pattern such as
120        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
121    
122    26. Changed a few more instances of "const unsigned char *" to USPTR, making
123        the feature of a custom pointer more persuasive (as requested by a user).
124    
125    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
126        pcretest.c, inside #ifndefs, because it seems they are sometimes already
127        pre-defined.
128    
129    28. Added support for (*UTF8) at the start of a pattern.
130    
131    29. Arrange for flags added by the "release type" setting in CMake to be shown
132        in the configuration summary.
133    
134    
135  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08
136  ---------------------  ---------------------

Legend:
Removed from v.381  
changed lines
  Added in v.418

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12