/[pcre]/code/tags/pcre-8.01/ChangeLog
ViewVC logotype

Diff of /code/tags/pcre-8.01/ChangeLog

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

revision 360 by ph10, Wed Jul 9 20:00:28 2008 UTC revision 419 by ph10, Wed Aug 12 10:45:33 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.0 02 Jul-08  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    
17    Version 7.9 11-Apr-09
18    ---------------------
19    
20    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
21        (pcretest), all targets were linked against these libraries. This included
22        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
23        libraries. This caused unwanted dependencies to be created. This problem
24        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
25        pcretest is linked with readline.
26    
27    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
28        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
29        moved outside it again, because FALSE and TRUE are already defined in AIX,
30        but BOOL is not.
31    
32    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
33        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
34    
35    4.  The pcregrep documentation said spaces were inserted as well as colons (or
36        hyphens) following file names and line numbers when outputting matching
37        lines. This is not true; no spaces are inserted. I have also clarified the
38        wording for the --colour (or --color) option.
39    
40    5.  In pcregrep, when --colour was used with -o, the list of matching strings
41        was not coloured; this is different to GNU grep, so I have changed it to be
42        the same.
43    
44    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
45        each matching line was coloured. Now it goes on to look for further matches
46        of any of the test patterns, which is the same behaviour as GNU grep.
47    
48    7.  A pattern that could match an empty string could cause pcregrep to loop; it
49        doesn't make sense to accept an empty string match in pcregrep, so I have
50        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
51        seems to be how GNU grep behaves.
52    
53    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
54        start or after a newline", because the conditional assertion was not being
55        correctly handled. The rule now is that both the assertion and what follows
56        in the first alternative must satisfy the test.
57    
58    9.  If auto-callout was enabled in a pattern with a conditional group whose
59        condition was an assertion, PCRE could crash during matching, both with
60        pcre_exec() and pcre_dfa_exec().
61    
62    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
63        used for matching.
64    
65    11. Unicode property support in character classes was not working for
66        characters (bytes) greater than 127 when not in UTF-8 mode.
67    
68    12. Added the -M command line option to pcretest.
69    
70    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
71    
72    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
73    
74    16. Added comments and documentation about mis-use of no_arg in the C++
75        wrapper.
76    
77    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
78        from Martin Jerabek that uses macro names for all relevant character and
79        string constants.
80    
81    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
82        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
83        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
84        these, but not everybody uses configure.
85    
86    19. A conditional group that had only one branch was not being correctly
87        recognized as an item that could match an empty string. This meant that an
88        enclosing group might also not be so recognized, causing infinite looping
89        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
90        with the subject "ab", where knowledge that the repeated group can match
91        nothing is needed in order to break the loop.
92    
93    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
94        exec(), but without supplying a callout function, matching went wrong.
95    
96    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
97        leak if the size of the offset vector was greater than 30. When the vector
98        is smaller, the saved offsets during recursion go onto a local stack
99        vector, but for larger vectors malloc() is used. It was failing to free
100        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
101        error, in fact).
102    
103    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
104        heapframe that is used only when UTF-8 support is enabled. This caused no
105        problem, but was untidy.
106    
107    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
108        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
109        included within another project.
110    
111    24. Steven Van Ingelgem's patches to add more options to the CMake support,
112        slightly modified by me:
113    
114          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
115              not building pcregrep.
116    
117          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
118              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
119    
120    25. Forward references, both numeric and by name, in patterns that made use of
121        duplicate group numbers, could behave incorrectly or give incorrect errors,
122        because when scanning forward to find the reference group, PCRE was not
123        taking into account the duplicate group numbers. A pattern such as
124        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
125    
126    26. Changed a few more instances of "const unsigned char *" to USPTR, making
127        the feature of a custom pointer more persuasive (as requested by a user).
128    
129    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
130        pcretest.c, inside #ifndefs, because it seems they are sometimes already
131        pre-defined.
132    
133    28. Added support for (*UTF8) at the start of a pattern.
134    
135    29. Arrange for flags added by the "release type" setting in CMake to be shown
136        in the configuration summary.
137    
138    
139    Version 7.8 05-Sep-08
140  ---------------------  ---------------------
141    
142  1.  Replaced UCP searching code with optimized version as implemented for Ad  1.  Replaced UCP searching code with optimized version as implemented for Ad
# Line 31  Version 8.0 02 Jul-08 Line 166  Version 8.0 02 Jul-08
166    
167  7.  Added two (int) casts to pcregrep when printing the difference of two  7.  Added two (int) casts to pcregrep when printing the difference of two
168      pointers, in case they are 64-bit values.      pointers, in case they are 64-bit values.
169    
170  8.  Added comments about Mac OS X stack usage to the pcrestack man page and to  8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
171      test 2 if it fails.      test 2 if it fails.
172    
173  9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,  9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
174      and a #define of that name to empty if it is not externally set. This is to      and a #define of that name to empty if it is not externally set. This is to
175      allow users of MSVC to set it if necessary.      allow users of MSVC to set it if necessary.
176    
177  10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from  10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
178      the convenience functions in the pcre_get.c source file.      the convenience functions in the pcre_get.c source file.
179    
180  11. An option change at the start of a pattern that had top-level alternatives  11. An option change at the start of a pattern that had top-level alternatives
181      could cause overwriting and/or a crash. This command provoked a crash in      could cause overwriting and/or a crash. This command provoked a crash in
182      some environments:      some environments:
183    
184        printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest        printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
185    
186      This potential security problem was recorded as CVE-2008-2371.      This potential security problem was recorded as CVE-2008-2371.
187    
188    12. For a pattern where the match had to start at the beginning or immediately
189        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
190        pcre_dfa_exec() could read past the end of the passed subject if there was
191        no match. To help with detecting such bugs (e.g. with valgrind), I modified
192        pcretest so that it places the subject at the end of its malloc-ed buffer.
193    
194    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
195        exec() might read past the end of the data buffer in UTF-8 mode.
196    
197    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
198        the data contained the byte 0x85 as part of a UTF-8 character within its
199        first line. This applied both to normal and DFA matching.
200    
201    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
202        /^[^d]*?$/8 failed to match "abc".
203    
204    16. Added a missing copyright notice to pcrecpp_internal.h.
205    
206    17. Make it more clear in the documentation that values returned from
207        pcre_exec() in ovector are byte offsets, not character counts.
208    
209    18. Tidied a few places to stop certain compilers from issuing warnings.
210    
211    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
212        supplied by Stefan Weber. I made a further small update for 7.8 because
213        there is a change of source arrangements: the pcre_searchfuncs.c module is
214        replaced by pcre_ucd.c.
215    
216    
217  Version 7.7 07-May-08  Version 7.7 07-May-08
218  ---------------------  ---------------------

Legend:
Removed from v.360  
changed lines
  Added in v.419

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12