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

Diff of /code/trunk/ChangeLog

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

revision 202 by ph10, Fri Aug 3 09:44:26 2007 UTC revision 447 by ph10, Tue Sep 15 18:17:54 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-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    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. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
47        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
48        character. Chaos in the form of incorrect output or a compiling loop could
49        result.
50    
51    9.  The restrictions on what a pattern can contain when partial matching is
52        requested for pcre_exec() have been removed. All patterns can now be
53        partially matched by this function. In addition, if there are at least two
54        slots in the offset vector, the offset of the earliest inspected character
55        for the match and the offset of the end of the subject are set in them when
56        PCRE_ERROR_PARTIAL is returned.
57    
58    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
59        synonymous with PCRE_PARTIAL, for backwards compatibility, and
60        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
61        and may be more useful for multi-segment matching, especially with
62        pcre_exec().
63    
64    11. Partial matching with pcre_exec() is now more intuitive. A partial match
65        used to be given if ever the end of the subject was reached; now it is
66        given only if matching could not proceed because another character was
67        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
68        string "Z", which now yields "no match" instead of "partial match". In the
69        case of pcre_dfa_exec(), "no match" is given if every matching path for the
70        final character ended with (*FAIL).
71    
72    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
73        if the pattern had a "must contain" character that was already found in the
74        earlier partial match, unless partial matching was again requested. For
75        example, with the pattern /dog.(body)?/, the "must contain" character is
76        "g". If the first part-match was for the string "dog", restarting with
77        "sbody" failed. This bug has been fixed.
78    
79    13. The string returned by pcre_dfa_exec() after a partial match has been
80        changed so that it starts at the first inspected character rather than the
81        first character of the match. This makes a difference only if the pattern
82        starts with a lookbehind assertion or \b or \B (\K is not supported by
83        pcre_dfa_exec()). It's an incompatible change, but it makes the two
84        matching functions compatible, and I think it's the right thing to do.
85    
86    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
87        so that the demonstration program is easily available in environments where
88        PCRE has not been installed from source.
89    
90    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
91        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
92        library.
93    
94    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
95        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
96        is not the first non-POSIX option to be added. Clearly some people find
97        these options useful.
98    
99    17. If a caller to the POSIX matching function regexec() passes a non-zero
100        value for nmatch with a NULL value for pmatch, the value of
101        nmatch is forced to zero.
102    
103    18. RunGrepTest did not have a test for the availability of the -u option of
104        the diff command, as RunTest does. It now checks in the same way as
105        RunTest, and also checks for the -b option.
106    
107    19. If an odd number of negated classes containing just a single character
108        interposed, within parentheses, between a forward reference to a named
109        subpattern and the definition of the subpattern, compilation crashed with
110        an internal error, complaining that it could not find the referenced
111        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
112        [The bug was that it was starting one character too far in when skipping
113        over the character class, thus treating the ] as data rather than
114        terminating the class. This meant it could skip too much.]
115    
116    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
117        /g option in pcretest when the pattern contains \K, which makes it possible
118        to have an empty string match not at the start, even when the pattern is
119        anchored. Updated pcretest and pcredemo to use this option.
120    
121    21. If the maximum number of capturing subpatterns in a recursion was greater
122        than the maximum at the outer level, the higher number was returned, but
123        with unset values at the outer level. The correct (outer level) value is
124        now given.
125    
126    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
127        PCRE did not set those parentheses (unlike Perl). I have now found a way to
128        make it do so. The string so far is captured, making this feature
129        compatible with Perl.
130    
131    
132    Version 7.9 11-Apr-09
133    ---------------------
134    
135    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
136        (pcretest), all targets were linked against these libraries. This included
137        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
138        libraries. This caused unwanted dependencies to be created. This problem
139        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
140        pcretest is linked with readline.
141    
142    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
143        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
144        moved outside it again, because FALSE and TRUE are already defined in AIX,
145        but BOOL is not.
146    
147    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
148        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
149    
150    4.  The pcregrep documentation said spaces were inserted as well as colons (or
151        hyphens) following file names and line numbers when outputting matching
152        lines. This is not true; no spaces are inserted. I have also clarified the
153        wording for the --colour (or --color) option.
154    
155    5.  In pcregrep, when --colour was used with -o, the list of matching strings
156        was not coloured; this is different to GNU grep, so I have changed it to be
157        the same.
158    
159    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
160        each matching line was coloured. Now it goes on to look for further matches
161        of any of the test patterns, which is the same behaviour as GNU grep.
162    
163    7.  A pattern that could match an empty string could cause pcregrep to loop; it
164        doesn't make sense to accept an empty string match in pcregrep, so I have
165        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
166        seems to be how GNU grep behaves.
167    
168    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
169        start or after a newline", because the conditional assertion was not being
170        correctly handled. The rule now is that both the assertion and what follows
171        in the first alternative must satisfy the test.
172    
173    9.  If auto-callout was enabled in a pattern with a conditional group whose
174        condition was an assertion, PCRE could crash during matching, both with
175        pcre_exec() and pcre_dfa_exec().
176    
177    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
178        used for matching.
179    
180    11. Unicode property support in character classes was not working for
181        characters (bytes) greater than 127 when not in UTF-8 mode.
182    
183    12. Added the -M command line option to pcretest.
184    
185    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
186    
187    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
188    
189    16. Added comments and documentation about mis-use of no_arg in the C++
190        wrapper.
191    
192    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
193        from Martin Jerabek that uses macro names for all relevant character and
194        string constants.
195    
196    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
197        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
198        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
199        these, but not everybody uses configure.
200    
201    19. A conditional group that had only one branch was not being correctly
202        recognized as an item that could match an empty string. This meant that an
203        enclosing group might also not be so recognized, causing infinite looping
204        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
205        with the subject "ab", where knowledge that the repeated group can match
206        nothing is needed in order to break the loop.
207    
208    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
209        exec(), but without supplying a callout function, matching went wrong.
210    
211    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
212        leak if the size of the offset vector was greater than 30. When the vector
213        is smaller, the saved offsets during recursion go onto a local stack
214        vector, but for larger vectors malloc() is used. It was failing to free
215        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
216        error, in fact).
217    
218    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
219        heapframe that is used only when UTF-8 support is enabled. This caused no
220        problem, but was untidy.
221    
222    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
223        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
224        included within another project.
225    
226    24. Steven Van Ingelgem's patches to add more options to the CMake support,
227        slightly modified by me:
228    
229          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
230              not building pcregrep.
231    
232          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
233              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
234    
235    25. Forward references, both numeric and by name, in patterns that made use of
236        duplicate group numbers, could behave incorrectly or give incorrect errors,
237        because when scanning forward to find the reference group, PCRE was not
238        taking into account the duplicate group numbers. A pattern such as
239        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
240    
241    26. Changed a few more instances of "const unsigned char *" to USPTR, making
242        the feature of a custom pointer more persuasive (as requested by a user).
243    
244    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
245        pcretest.c, inside #ifndefs, because it seems they are sometimes already
246        pre-defined.
247    
248    28. Added support for (*UTF8) at the start of a pattern.
249    
250    29. Arrange for flags added by the "release type" setting in CMake to be shown
251        in the configuration summary.
252    
253    
254    Version 7.8 05-Sep-08
255    ---------------------
256    
257    1.  Replaced UCP searching code with optimized version as implemented for Ad
258        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
259        stage table and inline lookup instead of a function, giving speed ups of 2
260        to 5 times on some simple patterns that I tested. Permission was given to
261        distribute the MultiStage2.py script that generates the tables (it's not in
262        the tarball, but is in the Subversion repository).
263    
264    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
265        scripts.
266    
267    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
268        a group with a zero qualifier. The result of the study could be incorrect,
269        or the function might crash, depending on the pattern.
270    
271    4.  Caseless matching was not working for non-ASCII characters in back
272        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
273        It now works when Unicode Property Support is available.
274    
275    5.  In pcretest, an escape such as \x{de} in the data was always generating
276        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
277        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
278        truncation.
279    
280    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
281    
282    7.  Added two (int) casts to pcregrep when printing the difference of two
283        pointers, in case they are 64-bit values.
284    
285    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
286        test 2 if it fails.
287    
288    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
289        and a #define of that name to empty if it is not externally set. This is to
290        allow users of MSVC to set it if necessary.
291    
292    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
293        the convenience functions in the pcre_get.c source file.
294    
295    11. An option change at the start of a pattern that had top-level alternatives
296        could cause overwriting and/or a crash. This command provoked a crash in
297        some environments:
298    
299          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
300    
301        This potential security problem was recorded as CVE-2008-2371.
302    
303    12. For a pattern where the match had to start at the beginning or immediately
304        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
305        pcre_dfa_exec() could read past the end of the passed subject if there was
306        no match. To help with detecting such bugs (e.g. with valgrind), I modified
307        pcretest so that it places the subject at the end of its malloc-ed buffer.
308    
309    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
310        exec() might read past the end of the data buffer in UTF-8 mode.
311    
312    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
313        the data contained the byte 0x85 as part of a UTF-8 character within its
314        first line. This applied both to normal and DFA matching.
315    
316    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
317        /^[^d]*?$/8 failed to match "abc".
318    
319    16. Added a missing copyright notice to pcrecpp_internal.h.
320    
321    17. Make it more clear in the documentation that values returned from
322        pcre_exec() in ovector are byte offsets, not character counts.
323    
324    18. Tidied a few places to stop certain compilers from issuing warnings.
325    
326    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
327        supplied by Stefan Weber. I made a further small update for 7.8 because
328        there is a change of source arrangements: the pcre_searchfuncs.c module is
329        replaced by pcre_ucd.c.
330    
331    
332    Version 7.7 07-May-08
333    ---------------------
334    
335    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
336        a string to a long long, pretend we don't even have a long long." This is
337        done by checking for the strtoq, strtoll, and _strtoi64 functions.
338    
339    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
340        pre-7.6 versions, which defined a global no_arg variable instead of putting
341        it in the RE class. (See also #8 below.)
342    
343    3.  Remove a line of dead code, identified by coverity and reported by Nuno
344        Lopes.
345    
346    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
347    
348        (1) The include/exclude patterns were being applied to the whole pathnames
349            of files, instead of just to the final components.
350    
351        (2) If there was more than one level of directory, the subdirectories were
352            skipped unless they satisfied the include/exclude conditions. This is
353            inconsistent with GNU grep (and could even be seen as contrary to the
354            pcregrep specification - which I improved to make it absolutely clear).
355            The action now is always to scan all levels of directory, and just
356            apply the include/exclude patterns to regular files.
357    
358    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
359        --exclude_dir in the tests to avoid scanning .svn directories.
360    
361    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
362        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
363        doesn't support NULs in patterns.
364    
365    7.  Added some missing "const"s to declarations of static tables in
366        pcre_compile.c and pcre_dfa_exec.c.
367    
368    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
369        caused by fix #2  above. (Subsequently also a second patch to fix the
370        first patch. And a third patch - this was a messy problem.)
371    
372    9.  Applied Craig's patch to remove the use of push_back().
373    
374    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
375        matching function regexec().
376    
377    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
378        which, however, unlike Perl's \g{...}, are subroutine calls, not back
379        references. PCRE supports relative numbers with this syntax (I don't think
380        Oniguruma does).
381    
382    12. Previously, a group with a zero repeat such as (...){0} was completely
383        omitted from the compiled regex. However, this means that if the group
384        was called as a subroutine from elsewhere in the pattern, things went wrong
385        (an internal error was given). Such groups are now left in the compiled
386        pattern, with a new opcode that causes them to be skipped at execution
387        time.
388    
389    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
390        to the way PCRE behaves:
391    
392        (a) A lone ] character is dis-allowed (Perl treats it as data).
393    
394        (b) A back reference to an unmatched subpattern matches an empty string
395            (Perl fails the current match path).
396    
397        (c) A data ] in a character class must be notated as \] because if the
398            first data character in a class is ], it defines an empty class. (In
399            Perl it is not possible to have an empty class.) The empty class []
400            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
401            The negative empty class [^] matches any one character, independently
402            of the DOTALL setting.
403    
404    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
405        non-existent subpattern following a character class starting with ']' and
406        containing () gave an internal compiling error instead of "reference to
407        non-existent subpattern". Fortunately, when the pattern did exist, the
408        compiled code was correct. (When scanning forwards to check for the
409        existencd of the subpattern, it was treating the data ']' as terminating
410        the class, so got the count wrong. When actually compiling, the reference
411        was subsequently set up correctly.)
412    
413    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
414        it was being rejected as not supported by pcre_dfa_exec(), even though
415        other assertions are supported. I have made pcre_dfa_exec() support
416        (*FAIL).
417    
418    16. The implementation of 13c above involved the invention of a new opcode,
419        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
420        cannot be changed at match time, I realized I could make a small
421        improvement to matching performance by compiling OP_ALLANY instead of
422        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
423        on the OP_ANY path.
424    
425    17. Compiling pcretest on Windows with readline support failed without the
426        following two fixes: (1) Make the unistd.h include conditional on
427        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
428    
429    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
430        ncurses library to be included for pcretest when ReadLine support is
431        requested, but also to allow for it to be overridden. This patch came from
432        Daniel Bergström.
433    
434    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
435        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
436        any errors with the current Unicode tables. Thanks to Peter Kankowski for
437        spotting this.
438    
439    
440    Version 7.6 28-Jan-08
441    ---------------------
442    
443    1.  A character class containing a very large number of characters with
444        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
445        overflow.
446    
447    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
448        HAVE_LONG_LONG is not defined.
449    
450    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
451        bring them up to date and include new features. This patch includes:
452    
453        - Fixed PH's badly added libz and libbz2 support.
454        - Fixed a problem with static linking.
455        - Added pcredemo. [But later removed - see 7 below.]
456        - Fixed dftables problem and added an option.
457        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
458            HAVE_LONG_LONG.
459        - Added readline support for pcretest.
460        - Added an listing of the option settings after cmake has run.
461    
462    4.  A user submitted a patch to Makefile that makes it easy to create
463        "pcre.dll" under mingw when using Configure/Make. I added stuff to
464        Makefile.am that cause it to include this special target, without
465        affecting anything else. Note that the same mingw target plus all
466        the other distribution libraries and programs are now supported
467        when configuring with CMake (see 6 below) instead of with
468        Configure/Make.
469    
470    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
471        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
472        exported in the Windows port". It has not yet been confirmed that the patch
473        solves the problem, but it does no harm.
474    
475    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
476        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
477        with CMake, and also correct the comment about stack recursion.
478    
479    7.  Remove the automatic building of pcredemo from the ./configure system and
480        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
481        of a program that users should build themselves after PCRE is installed, so
482        building it automatically is not really right. What is more, it gave
483        trouble in some build environments.
484    
485    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
486    
487    
488    Version 7.5 10-Jan-08
489    ---------------------
490    
491    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
492        values in parens when parsing an RE using the C++ wrapper."
493    
494    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
495        Characters greater than 255 were excluded from the class instead of being
496        included.
497    
498    3.  The same bug as (2) above applied to negated POSIX classes such as
499        [:^space:].
500    
501    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
502        defined or documented. It seems to have been a typo for PCRE_STATIC, so
503        I have changed it.
504    
505    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
506        first named subpattern) and a construct such as (?&a) would reference the
507        first named subpattern whose name started with "a" (in other words, the
508        length check was missing). Both these problems are fixed. "Subpattern name
509        expected" is now given for (?&) (a zero-length name), and this patch also
510        makes it give the same error for \k'' (previously it complained that that
511        was a reference to a non-existent subpattern).
512    
513    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
514        this is right because (?- can be followed by option settings as well as by
515        digits. I have, however, made the messages clearer.
516    
517    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
518        than the number used in the conditional) now cause a compile-time error.
519        This is actually not compatible with Perl, which accepts such patterns, but
520        treats the conditional as always being FALSE (as PCRE used to), but it
521        seems to me that giving a diagnostic is better.
522    
523    8.  Change "alphameric" to the more common word "alphanumeric" in comments
524        and messages.
525    
526    9.  Fix two occurrences of "backslash" in comments that should have been
527        "backspace".
528    
529    10. Remove two redundant lines of code that can never be obeyed (their function
530        was moved elsewhere).
531    
532    11. The program that makes PCRE's Unicode character property table had a bug
533        which caused it to generate incorrect table entries for sequences of
534        characters that have the same character type, but are in different scripts.
535        It amalgamated them into a single range, with the script of the first of
536        them. In other words, some characters were in the wrong script. There were
537        thirteen such cases, affecting characters in the following ranges:
538    
539          U+002b0 - U+002c1
540          U+0060c - U+0060d
541          U+0061e - U+00612
542          U+0064b - U+0065e
543          U+0074d - U+0076d
544          U+01800 - U+01805
545          U+01d00 - U+01d77
546          U+01d9b - U+01dbf
547          U+0200b - U+0200f
548          U+030fc - U+030fe
549          U+03260 - U+0327f
550          U+0fb46 - U+0fbb1
551          U+10450 - U+1049d
552    
553    12. The -o option (show only the matching part of a line) for pcregrep was not
554        compatible with GNU grep in that, if there was more than one match in a
555        line, it showed only the first of them. It now behaves in the same way as
556        GNU grep.
557    
558    13. If the -o and -v options were combined for pcregrep, it printed a blank
559        line for every non-matching line. GNU grep prints nothing, and pcregrep now
560        does the same. The return code can be used to tell if there were any
561        non-matching lines.
562    
563    14. Added --file-offsets and --line-offsets to pcregrep.
564    
565    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
566        infinitely looping recursion. The bug was that positive lookaheads were not
567        being skipped when checking for a possible empty match (negative lookaheads
568        and both kinds of lookbehind were skipped).
569    
570    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
571        inclusion of <windows.h> to before rather than after the definition of
572        INVALID_FILE_ATTRIBUTES (patch from David Byron).
573    
574    17. Specifying a possessive quantifier with a specific limit for a Unicode
575        character property caused pcre_compile() to compile bad code, which led at
576        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
577        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
578        caused the error; without that there was no problem.
579    
580    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
581    
582    19. Added --enable-pcretest-libreadline.
583    
584    20. In pcrecpp.cc, the variable 'count' was incremented twice in
585        RE::GlobalReplace(). As a result, the number of replacements returned was
586        double what it should be. I removed one of the increments, but Craig sent a
587        later patch that removed the other one (the right fix) and added unit tests
588        that check the return values (which was not done before).
589    
590    21. Several CMake things:
591    
592        (1) Arranged that, when cmake is used on Unix, the libraries end up with
593            the names libpcre and libpcreposix, not just pcre and pcreposix.
594    
595        (2) The above change means that pcretest and pcregrep are now correctly
596            linked with the newly-built libraries, not previously installed ones.
597    
598        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
599    
600    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
601        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
602        UTF-8 newline character). The key issue is that the pattern starts .*;
603        this means that the match must be either at the beginning, or after a
604        newline. The bug was in the code for advancing after a failed match and
605        checking that the new position followed a newline. It was not taking
606        account of UTF-8 characters correctly.
607    
608    23. PCRE was behaving differently from Perl in the way it recognized POSIX
609        character classes. PCRE was not treating the sequence [:...:] as a
610        character class unless the ... were all letters. Perl, however, seems to
611        allow any characters between [: and :], though of course it rejects as
612        unknown any "names" that contain non-letters, because all the known class
613        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
614        for example, whereas PCRE did not - it did not recognize a POSIX character
615        class. This seemed a bit dangerous, so the code has been changed to be
616        closer to Perl. The behaviour is not identical to Perl, because PCRE will
617        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
618        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
619        Perl does, and where it didn't before.
620    
621    24. Rewrite so as to remove the single use of %n from pcregrep because in some
622        Windows environments %n is disabled by default.
623    
624    
625    Version 7.4 21-Sep-07
626    ---------------------
627    
628    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
629        means that a class such as [\s] counted as "explicit reference to CR or
630        LF". That isn't really right - the whole point of the change was to try to
631        help when there was an actual mention of one of the two characters. So now
632        the change happens only if \r or \n (or a literal CR or LF) character is
633        encountered.
634    
635    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
636        of both had grown to the point where there were only 3 bits left.
637        Fortunately, there was spare space in the data structure, and so I have
638        moved the internal flags into a new 16-bit field to free up more option
639        bits.
640    
641    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
642        but did not set the internal JCHANGED flag - either of these is enough to
643        control the way the "get" function works - but the PCRE_INFO_JCHANGED
644        facility is supposed to tell if (?J) was ever used, so now (?J) at the
645        start sets both bits.
646    
647    4.  Added options (at build time, compile time, exec time) to change \R from
648        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
649    
650    5.  doc/pcresyntax.html was missing from the distribution.
651    
652    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
653        compatibility, even though it is no longer used.
654    
655    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
656        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
657        windows.h file is present (where different names are used). [This was
658        reversed later after testing - see 16 below.]
659    
660    8.  Changed all #include <config.h> to #include "config.h". There were also
661        some further <pcre.h> cases that I changed to "pcre.h".
662    
663    9.  When pcregrep was used with the --colour option, it missed the line ending
664        sequence off the lines that it output.
665    
666    10. It was pointed out to me that arrays of string pointers cause lots of
667        relocations when a shared library is dynamically loaded. A technique of
668        using a single long string with a table of offsets can drastically reduce
669        these. I have refactored PCRE in four places to do this. The result is
670        dramatic:
671    
672          Originally:                          290
673          After changing UCP table:            187
674          After changing error message table:   43
675          After changing table of "verbs"       36
676          After changing table of Posix names   22
677    
678        Thanks to the folks working on Gregex for glib for this insight.
679    
680    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
681        unicode-properties was also set.
682    
683    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
684    
685    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
686        checked only for CRLF.
687    
688    14. Added casts to pcretest.c to avoid compiler warnings.
689    
690    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
691    
692    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
693        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
694        entirely. This removes changes made in 7 above.
695    
696    17. The CMake files have been updated, and there is now more information about
697        building with CMake in the NON-UNIX-USE document.
698    
699    
700    Version 7.3 28-Aug-07
701  ---------------------  ---------------------
702    
703   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 65  Version 7.3 05-Jul-07 Line 761  Version 7.3 05-Jul-07
761      length has been removed - we now have only the limit on the total length of      length has been removed - we now have only the limit on the total length of
762      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
763    
764    10. Fixed a bug in the documentation for get/copy named substring when
765        duplicate names are permitted. If none of the named substrings are set, the
766        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
767        empty string.
768    
769    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
770        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
771        because the ] is interpreted as the first data character and the
772        terminating ] is not found. PCRE has been made compatible with Perl in this
773        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
774        cause memory overwriting.
775    
776    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
777        string has been matched (to stop an infinite loop). It was not recognizing
778        a conditional subpattern that could match an empty string if that
779        subpattern was within another subpattern. For example, it looped when
780        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
781        condition was not nested. This bug has been fixed.
782    
783    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
784        past the start of the subject in the presence of bytes with the top bit
785        set, for example "\x8aBCD".
786    
787    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
788        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
789    
790    14. Optimized (?!) to (*FAIL).
791    
792    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
793        This restricts code points to be within the range 0 to 0x10FFFF, excluding
794        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
795        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
796        does: it's just the validity check that is more restrictive.
797    
798    16. Inserted checks for integer overflows during escape sequence (backslash)
799        processing, and also fixed erroneous offset values for syntax errors during
800        backslash processing.
801    
802    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
803        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
804    
805    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
806        caused an overrun.
807    
808    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
809        something other than just ASCII characters) inside a group that had an
810        unlimited repeat caused a loop at compile time (while checking to see
811        whether the group could match an empty string).
812    
813    20. Debugging a pattern containing \p or \P could cause a crash. For example,
814        [\P{Any}] did so. (Error in the code for printing property names.)
815    
816    21. An orphan \E inside a character class could cause a crash.
817    
818    22. A repeated capturing bracket such as (A)? could cause a wild memory
819        reference during compilation.
820    
821    23. There are several functions in pcre_compile() that scan along a compiled
822        expression for various reasons (e.g. to see if it's fixed length for look
823        behind). There were bugs in these functions when a repeated \p or \P was
824        present in the pattern. These operators have additional parameters compared
825        with \d, etc, and these were not being taken into account when moving along
826        the compiled data. Specifically:
827    
828        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
829            length.
830    
831        (b) An item such as \pL+ within a repeated group could cause crashes or
832            loops.
833    
834        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
835            "reference to non-existent subpattern" error.
836    
837        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
838    
839    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
840        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
841    
842    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
843    
844    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
845        character were causing crashes (broken optimization).
846    
847    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
848        \p or \P) caused a compile-time loop.
849    
850    28. More problems have arisen in unanchored patterns when CRLF is a valid line
851        break. For example, the unstudied pattern [\r\n]A does not match the string
852        "\r\nA" because change 7.0/46 below moves the current point on by two
853        characters after failing to match at the start. However, the pattern \nA
854        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
855        the same is true. There doesn't seem any very clean way out of this, but
856        what I have chosen to do makes the common cases work: PCRE now takes note
857        of whether there can be an explicit match for \r or \n anywhere in the
858        pattern, and if so, 7.0/46 no longer applies. As part of this change,
859        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
860        pattern has explicit CR or LF references.
861    
862    29. Added (*CR) etc for changing newline setting at start of pattern.
863    
864    
865  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
866  ---------------------  ---------------------

Legend:
Removed from v.202  
changed lines
  Added in v.447

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12