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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.383  
changed lines
  Added in v.422

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12