ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 374 by ph10, Fri Sep 5 16:42:28 2008 UTC revision 427 by ph10, Fri Aug 28 09:55:54 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 8.00 ??-???-??
5    ----------------------
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.
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.
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.
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.
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.
34    6.  No libpcreposix.pc file was created for pkg-config; there was just
35        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
37    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
38        when UCP support is not needed, by modifying the Python script that
39        generates it from Unicode data files. This should not matter if the module
40        is correctly used as a library, but I received one complaint about 50K of
41        unwanted data. My guess is that the person linked everything into his
42        program rather than using a library. Anyway, it does no harm.
44    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
45        was a minimum greater than 1 for a wide character in a possessive
46        repetition. Chaos could result.
48    9.  The restrictions on what a pattern can contain when partial matching is
49        requested for pcre_exec() have been removed. All patterns can now be
50        partially matched by this function. In addition, if there are at least two
51        slots in the offset vector, the offsets of the first-encountered partial
52        match are set in them when PCRE_ERROR_PARTIAL is returned.
54    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
55        synonymous with PCRE_PARTIAL, for backwards compatibility, and
56        PCRE_PARTIAL_HARD, which causes a longer partial match to supersede a
57        shorter full match, and may be more useful for multi-segment matching,
58        especially with pcre_exec().
61    Version 7.9 11-Apr-09
62    ---------------------
64    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
65        (pcretest), all targets were linked against these libraries. This included
66        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
67        libraries. This caused unwanted dependencies to be created. This problem
68        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
69        pcretest is linked with readline.
71    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
72        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
73        moved outside it again, because FALSE and TRUE are already defined in AIX,
74        but BOOL is not.
76    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
77        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
79    4.  The pcregrep documentation said spaces were inserted as well as colons (or
80        hyphens) following file names and line numbers when outputting matching
81        lines. This is not true; no spaces are inserted. I have also clarified the
82        wording for the --colour (or --color) option.
84    5.  In pcregrep, when --colour was used with -o, the list of matching strings
85        was not coloured; this is different to GNU grep, so I have changed it to be
86        the same.
88    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
89        each matching line was coloured. Now it goes on to look for further matches
90        of any of the test patterns, which is the same behaviour as GNU grep.
92    7.  A pattern that could match an empty string could cause pcregrep to loop; it
93        doesn't make sense to accept an empty string match in pcregrep, so I have
94        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
95        seems to be how GNU grep behaves.
97    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
98        start or after a newline", because the conditional assertion was not being
99        correctly handled. The rule now is that both the assertion and what follows
100        in the first alternative must satisfy the test.
102    9.  If auto-callout was enabled in a pattern with a conditional group whose
103        condition was an assertion, PCRE could crash during matching, both with
104        pcre_exec() and pcre_dfa_exec().
106    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
107        used for matching.
109    11. Unicode property support in character classes was not working for
110        characters (bytes) greater than 127 when not in UTF-8 mode.
112    12. Added the -M command line option to pcretest.
114    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
116    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
118    16. Added comments and documentation about mis-use of no_arg in the C++
119        wrapper.
121    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
122        from Martin Jerabek that uses macro names for all relevant character and
123        string constants.
125    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
126        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
127        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
128        these, but not everybody uses configure.
130    19. A conditional group that had only one branch was not being correctly
131        recognized as an item that could match an empty string. This meant that an
132        enclosing group might also not be so recognized, causing infinite looping
133        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
134        with the subject "ab", where knowledge that the repeated group can match
135        nothing is needed in order to break the loop.
137    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
138        exec(), but without supplying a callout function, matching went wrong.
140    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
141        leak if the size of the offset vector was greater than 30. When the vector
142        is smaller, the saved offsets during recursion go onto a local stack
143        vector, but for larger vectors malloc() is used. It was failing to free
144        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
145        error, in fact).
147    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
148        heapframe that is used only when UTF-8 support is enabled. This caused no
149        problem, but was untidy.
151    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
152        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
153        included within another project.
155    24. Steven Van Ingelgem's patches to add more options to the CMake support,
156        slightly modified by me:
158          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
159              not building pcregrep.
161          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
162              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
164    25. Forward references, both numeric and by name, in patterns that made use of
165        duplicate group numbers, could behave incorrectly or give incorrect errors,
166        because when scanning forward to find the reference group, PCRE was not
167        taking into account the duplicate group numbers. A pattern such as
168        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
170    26. Changed a few more instances of "const unsigned char *" to USPTR, making
171        the feature of a custom pointer more persuasive (as requested by a user).
173    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
174        pcretest.c, inside #ifndefs, because it seems they are sometimes already
175        pre-defined.
177    28. Added support for (*UTF8) at the start of a pattern.
179    29. Arrange for flags added by the "release type" setting in CMake to be shown
180        in the configuration summary.
183  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08
184  ---------------------  ---------------------

Removed from v.374  
changed lines
  Added in v.427

  ViewVC Help
Powered by ViewVC 1.1.5