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

Diff of /code/trunk/ChangeLog

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

revision 277 by ph10, Mon Nov 26 17:03:45 2007 UTC revision 425 by ph10, Mon Aug 17 14:48:48 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 12-Nov-07  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    6.  No libpcreposix.pc file was created for pkg-config; there was just
35        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
36    
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.
43    
44    
45    Version 7.9 11-Apr-09
46    ---------------------
47    
48    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
49        (pcretest), all targets were linked against these libraries. This included
50        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
51        libraries. This caused unwanted dependencies to be created. This problem
52        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
53        pcretest is linked with readline.
54    
55    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
56        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
57        moved outside it again, because FALSE and TRUE are already defined in AIX,
58        but BOOL is not.
59    
60    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
61        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
62    
63    4.  The pcregrep documentation said spaces were inserted as well as colons (or
64        hyphens) following file names and line numbers when outputting matching
65        lines. This is not true; no spaces are inserted. I have also clarified the
66        wording for the --colour (or --color) option.
67    
68    5.  In pcregrep, when --colour was used with -o, the list of matching strings
69        was not coloured; this is different to GNU grep, so I have changed it to be
70        the same.
71    
72    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
73        each matching line was coloured. Now it goes on to look for further matches
74        of any of the test patterns, which is the same behaviour as GNU grep.
75    
76    7.  A pattern that could match an empty string could cause pcregrep to loop; it
77        doesn't make sense to accept an empty string match in pcregrep, so I have
78        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
79        seems to be how GNU grep behaves.
80    
81    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
82        start or after a newline", because the conditional assertion was not being
83        correctly handled. The rule now is that both the assertion and what follows
84        in the first alternative must satisfy the test.
85    
86    9.  If auto-callout was enabled in a pattern with a conditional group whose
87        condition was an assertion, PCRE could crash during matching, both with
88        pcre_exec() and pcre_dfa_exec().
89    
90    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
91        used for matching.
92    
93    11. Unicode property support in character classes was not working for
94        characters (bytes) greater than 127 when not in UTF-8 mode.
95    
96    12. Added the -M command line option to pcretest.
97    
98    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
99    
100    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
101    
102    16. Added comments and documentation about mis-use of no_arg in the C++
103        wrapper.
104    
105    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
106        from Martin Jerabek that uses macro names for all relevant character and
107        string constants.
108    
109    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
110        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
111        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
112        these, but not everybody uses configure.
113    
114    19. A conditional group that had only one branch was not being correctly
115        recognized as an item that could match an empty string. This meant that an
116        enclosing group might also not be so recognized, causing infinite looping
117        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
118        with the subject "ab", where knowledge that the repeated group can match
119        nothing is needed in order to break the loop.
120    
121    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
122        exec(), but without supplying a callout function, matching went wrong.
123    
124    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
125        leak if the size of the offset vector was greater than 30. When the vector
126        is smaller, the saved offsets during recursion go onto a local stack
127        vector, but for larger vectors malloc() is used. It was failing to free
128        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
129        error, in fact).
130    
131    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
132        heapframe that is used only when UTF-8 support is enabled. This caused no
133        problem, but was untidy.
134    
135    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
136        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
137        included within another project.
138    
139    24. Steven Van Ingelgem's patches to add more options to the CMake support,
140        slightly modified by me:
141    
142          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
143              not building pcregrep.
144    
145          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
146              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
147    
148    25. Forward references, both numeric and by name, in patterns that made use of
149        duplicate group numbers, could behave incorrectly or give incorrect errors,
150        because when scanning forward to find the reference group, PCRE was not
151        taking into account the duplicate group numbers. A pattern such as
152        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
153    
154    26. Changed a few more instances of "const unsigned char *" to USPTR, making
155        the feature of a custom pointer more persuasive (as requested by a user).
156    
157    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
158        pcretest.c, inside #ifndefs, because it seems they are sometimes already
159        pre-defined.
160    
161    28. Added support for (*UTF8) at the start of a pattern.
162    
163    29. Arrange for flags added by the "release type" setting in CMake to be shown
164        in the configuration summary.
165    
166    
167    Version 7.8 05-Sep-08
168    ---------------------
169    
170    1.  Replaced UCP searching code with optimized version as implemented for Ad
171        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
172        stage table and inline lookup instead of a function, giving speed ups of 2
173        to 5 times on some simple patterns that I tested. Permission was given to
174        distribute the MultiStage2.py script that generates the tables (it's not in
175        the tarball, but is in the Subversion repository).
176    
177    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
178        scripts.
179    
180    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
181        a group with a zero qualifier. The result of the study could be incorrect,
182        or the function might crash, depending on the pattern.
183    
184    4.  Caseless matching was not working for non-ASCII characters in back
185        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
186        It now works when Unicode Property Support is available.
187    
188    5.  In pcretest, an escape such as \x{de} in the data was always generating
189        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
190        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
191        truncation.
192    
193    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
194    
195    7.  Added two (int) casts to pcregrep when printing the difference of two
196        pointers, in case they are 64-bit values.
197    
198    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
199        test 2 if it fails.
200    
201    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
202        and a #define of that name to empty if it is not externally set. This is to
203        allow users of MSVC to set it if necessary.
204    
205    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
206        the convenience functions in the pcre_get.c source file.
207    
208    11. An option change at the start of a pattern that had top-level alternatives
209        could cause overwriting and/or a crash. This command provoked a crash in
210        some environments:
211    
212          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
213    
214        This potential security problem was recorded as CVE-2008-2371.
215    
216    12. For a pattern where the match had to start at the beginning or immediately
217        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
218        pcre_dfa_exec() could read past the end of the passed subject if there was
219        no match. To help with detecting such bugs (e.g. with valgrind), I modified
220        pcretest so that it places the subject at the end of its malloc-ed buffer.
221    
222    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
223        exec() might read past the end of the data buffer in UTF-8 mode.
224    
225    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
226        the data contained the byte 0x85 as part of a UTF-8 character within its
227        first line. This applied both to normal and DFA matching.
228    
229    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
230        /^[^d]*?$/8 failed to match "abc".
231    
232    16. Added a missing copyright notice to pcrecpp_internal.h.
233    
234    17. Make it more clear in the documentation that values returned from
235        pcre_exec() in ovector are byte offsets, not character counts.
236    
237    18. Tidied a few places to stop certain compilers from issuing warnings.
238    
239    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
240        supplied by Stefan Weber. I made a further small update for 7.8 because
241        there is a change of source arrangements: the pcre_searchfuncs.c module is
242        replaced by pcre_ucd.c.
243    
244    
245    Version 7.7 07-May-08
246    ---------------------
247    
248    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
249        a string to a long long, pretend we don't even have a long long." This is
250        done by checking for the strtoq, strtoll, and _strtoi64 functions.
251    
252    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
253        pre-7.6 versions, which defined a global no_arg variable instead of putting
254        it in the RE class. (See also #8 below.)
255    
256    3.  Remove a line of dead code, identified by coverity and reported by Nuno
257        Lopes.
258    
259    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
260    
261        (1) The include/exclude patterns were being applied to the whole pathnames
262            of files, instead of just to the final components.
263    
264        (2) If there was more than one level of directory, the subdirectories were
265            skipped unless they satisfied the include/exclude conditions. This is
266            inconsistent with GNU grep (and could even be seen as contrary to the
267            pcregrep specification - which I improved to make it absolutely clear).
268            The action now is always to scan all levels of directory, and just
269            apply the include/exclude patterns to regular files.
270    
271    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
272        --exclude_dir in the tests to avoid scanning .svn directories.
273    
274    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
275        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
276        doesn't support NULs in patterns.
277    
278    7.  Added some missing "const"s to declarations of static tables in
279        pcre_compile.c and pcre_dfa_exec.c.
280    
281    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
282        caused by fix #2  above. (Subsequently also a second patch to fix the
283        first patch. And a third patch - this was a messy problem.)
284    
285    9.  Applied Craig's patch to remove the use of push_back().
286    
287    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
288        matching function regexec().
289    
290    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
291        which, however, unlike Perl's \g{...}, are subroutine calls, not back
292        references. PCRE supports relative numbers with this syntax (I don't think
293        Oniguruma does).
294    
295    12. Previously, a group with a zero repeat such as (...){0} was completely
296        omitted from the compiled regex. However, this means that if the group
297        was called as a subroutine from elsewhere in the pattern, things went wrong
298        (an internal error was given). Such groups are now left in the compiled
299        pattern, with a new opcode that causes them to be skipped at execution
300        time.
301    
302    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
303        to the way PCRE behaves:
304    
305        (a) A lone ] character is dis-allowed (Perl treats it as data).
306    
307        (b) A back reference to an unmatched subpattern matches an empty string
308            (Perl fails the current match path).
309    
310        (c) A data ] in a character class must be notated as \] because if the
311            first data character in a class is ], it defines an empty class. (In
312            Perl it is not possible to have an empty class.) The empty class []
313            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
314            The negative empty class [^] matches any one character, independently
315            of the DOTALL setting.
316    
317    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
318        non-existent subpattern following a character class starting with ']' and
319        containing () gave an internal compiling error instead of "reference to
320        non-existent subpattern". Fortunately, when the pattern did exist, the
321        compiled code was correct. (When scanning forwards to check for the
322        existencd of the subpattern, it was treating the data ']' as terminating
323        the class, so got the count wrong. When actually compiling, the reference
324        was subsequently set up correctly.)
325    
326    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
327        it was being rejected as not supported by pcre_dfa_exec(), even though
328        other assertions are supported. I have made pcre_dfa_exec() support
329        (*FAIL).
330    
331    16. The implementation of 13c above involved the invention of a new opcode,
332        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
333        cannot be changed at match time, I realized I could make a small
334        improvement to matching performance by compiling OP_ALLANY instead of
335        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
336        on the OP_ANY path.
337    
338    17. Compiling pcretest on Windows with readline support failed without the
339        following two fixes: (1) Make the unistd.h include conditional on
340        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
341    
342    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
343        ncurses library to be included for pcretest when ReadLine support is
344        requested, but also to allow for it to be overridden. This patch came from
345        Daniel Bergström.
346    
347    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
348        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
349        any errors with the current Unicode tables. Thanks to Peter Kankowski for
350        spotting this.
351    
352    
353    Version 7.6 28-Jan-08
354    ---------------------
355    
356    1.  A character class containing a very large number of characters with
357        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
358        overflow.
359    
360    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
361        HAVE_LONG_LONG is not defined.
362    
363    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
364        bring them up to date and include new features. This patch includes:
365    
366        - Fixed PH's badly added libz and libbz2 support.
367        - Fixed a problem with static linking.
368        - Added pcredemo. [But later removed - see 7 below.]
369        - Fixed dftables problem and added an option.
370        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
371            HAVE_LONG_LONG.
372        - Added readline support for pcretest.
373        - Added an listing of the option settings after cmake has run.
374    
375    4.  A user submitted a patch to Makefile that makes it easy to create
376        "pcre.dll" under mingw when using Configure/Make. I added stuff to
377        Makefile.am that cause it to include this special target, without
378        affecting anything else. Note that the same mingw target plus all
379        the other distribution libraries and programs are now supported
380        when configuring with CMake (see 6 below) instead of with
381        Configure/Make.
382    
383    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
384        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
385        exported in the Windows port". It has not yet been confirmed that the patch
386        solves the problem, but it does no harm.
387    
388    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
389        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
390        with CMake, and also correct the comment about stack recursion.
391    
392    7.  Remove the automatic building of pcredemo from the ./configure system and
393        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
394        of a program that users should build themselves after PCRE is installed, so
395        building it automatically is not really right. What is more, it gave
396        trouble in some build environments.
397    
398    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
399    
400    
401    Version 7.5 10-Jan-08
402  ---------------------  ---------------------
403    
404  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
405      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
406    
407  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
408      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
409      included.      included.
410    
411  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
412      [:^space:].      [:^space:].
413    
414  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
415      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
416      I have changed it.      I have changed it.
417    
418  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
419      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
420      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
421      length check was missing). Both these problems are fixed. "Subpattern name      length check was missing). Both these problems are fixed. "Subpattern name
422      expected" is now given for (?&) (a zero-length name), and this patch also      expected" is now given for (?&) (a zero-length name), and this patch also
423      makes it give the same error for \k'' (previously it complained that that      makes it give the same error for \k'' (previously it complained that that
424      was a reference to a non-existent subpattern).      was a reference to a non-existent subpattern).
425    
426  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
427      this is right because (?- can be followed by option settings as well as by      this is right because (?- can be followed by option settings as well as by
428      digits. I have, however, made the messages clearer.      digits. I have, however, made the messages clearer.
429    
430  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
431      than the number used in the conditional) now cause a compile-time error.      than the number used in the conditional) now cause a compile-time error.
432      This is actually not compatible with Perl, which accepts such patterns, but      This is actually not compatible with Perl, which accepts such patterns, but
433      treats the conditional as always being FALSE (as PCRE used to), but it      treats the conditional as always being FALSE (as PCRE used to), but it
434      seems to me that giving a diagnostic is better.      seems to me that giving a diagnostic is better.
435    
436  8.  Change "alphameric" to the more common word "alphanumeric" in comments  8.  Change "alphameric" to the more common word "alphanumeric" in comments
437      and messages.      and messages.
438    
439  9.  Fix two occurrences of "backslash" in comments that should have been  9.  Fix two occurrences of "backslash" in comments that should have been
440      "backspace".      "backspace".
441    
442  10. Remove two redundant lines of code that can never be obeyed (their function  10. Remove two redundant lines of code that can never be obeyed (their function
443      was moved elsewhere).      was moved elsewhere).
444    
445  11. The program that makes PCRE's Unicode character property table had a bug  11. The program that makes PCRE's Unicode character property table had a bug
446      which caused it to generate incorrect table entries for sequences of      which caused it to generate incorrect table entries for sequences of
447      characters that have the same character type, but are in different scripts.      characters that have the same character type, but are in different scripts.
448      It amalgamated them into a single range, with the script of the first of      It amalgamated them into a single range, with the script of the first of
449      them. In other words, some characters were in the wrong script. There were      them. In other words, some characters were in the wrong script. There were
450      thirteen such cases, affecting characters in the following ranges:      thirteen such cases, affecting characters in the following ranges:
451    
452        U+002b0 - U+002c1        U+002b0 - U+002c1
453        U+0060c - U+0060d        U+0060c - U+0060d
454        U+0061e - U+00612        U+0061e - U+00612
455        U+0064b - U+0065e        U+0064b - U+0065e
456        U+0074d - U+0076d        U+0074d - U+0076d
457        U+01800 - U+01805        U+01800 - U+01805
# Line 66  Version 7.5 12-Nov-07 Line 463  Version 7.5 12-Nov-07
463        U+0fb46 - U+0fbb1        U+0fb46 - U+0fbb1
464        U+10450 - U+1049d        U+10450 - U+1049d
465    
466    12. The -o option (show only the matching part of a line) for pcregrep was not
467        compatible with GNU grep in that, if there was more than one match in a
468        line, it showed only the first of them. It now behaves in the same way as
469        GNU grep.
470    
471    13. If the -o and -v options were combined for pcregrep, it printed a blank
472        line for every non-matching line. GNU grep prints nothing, and pcregrep now
473        does the same. The return code can be used to tell if there were any
474        non-matching lines.
475    
476    14. Added --file-offsets and --line-offsets to pcregrep.
477    
478    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
479        infinitely looping recursion. The bug was that positive lookaheads were not
480        being skipped when checking for a possible empty match (negative lookaheads
481        and both kinds of lookbehind were skipped).
482    
483    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
484        inclusion of <windows.h> to before rather than after the definition of
485        INVALID_FILE_ATTRIBUTES (patch from David Byron).
486    
487    17. Specifying a possessive quantifier with a specific limit for a Unicode
488        character property caused pcre_compile() to compile bad code, which led at
489        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
490        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
491        caused the error; without that there was no problem.
492    
493    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
494    
495    19. Added --enable-pcretest-libreadline.
496    
497    20. In pcrecpp.cc, the variable 'count' was incremented twice in
498        RE::GlobalReplace(). As a result, the number of replacements returned was
499        double what it should be. I removed one of the increments, but Craig sent a
500        later patch that removed the other one (the right fix) and added unit tests
501        that check the return values (which was not done before).
502    
503    21. Several CMake things:
504    
505        (1) Arranged that, when cmake is used on Unix, the libraries end up with
506            the names libpcre and libpcreposix, not just pcre and pcreposix.
507    
508        (2) The above change means that pcretest and pcregrep are now correctly
509            linked with the newly-built libraries, not previously installed ones.
510    
511        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
512    
513    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
514        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
515        UTF-8 newline character). The key issue is that the pattern starts .*;
516        this means that the match must be either at the beginning, or after a
517        newline. The bug was in the code for advancing after a failed match and
518        checking that the new position followed a newline. It was not taking
519        account of UTF-8 characters correctly.
520    
521    23. PCRE was behaving differently from Perl in the way it recognized POSIX
522        character classes. PCRE was not treating the sequence [:...:] as a
523        character class unless the ... were all letters. Perl, however, seems to
524        allow any characters between [: and :], though of course it rejects as
525        unknown any "names" that contain non-letters, because all the known class
526        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
527        for example, whereas PCRE did not - it did not recognize a POSIX character
528        class. This seemed a bit dangerous, so the code has been changed to be
529        closer to Perl. The behaviour is not identical to Perl, because PCRE will
530        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
531        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
532        Perl does, and where it didn't before.
533    
534    24. Rewrite so as to remove the single use of %n from pcregrep because in some
535        Windows environments %n is disabled by default.
536    
537    
538  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07
539  ---------------------  ---------------------

Legend:
Removed from v.277  
changed lines
  Added in v.425

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12