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

Diff of /code/trunk/ChangeLog

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

revision 160 by ph10, Wed May 2 10:58:35 2007 UTC revision 500 by ph10, Sat Mar 6 19:00:29 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.2 01-May-07  Version 8.02 01-Mar-2010
5    ------------------------
6    
7    1.  The Unicode data tables have been updated to Unicode 5.2.0.
8    
9    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
10        configured.
11    
12    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
13        original author of that file, following a query about its status.
14    
15    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
16        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
17    
18    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
19        quantifier applied to a forward-referencing subroutine call, could compile
20        incorrect code or give the error "internal error: previously-checked
21        referenced subpattern not found".
22    
23    6.  Both MS Visual Studio and Symbian OS have problems with initializing
24        variables to point to external functions. For these systems, therefore,
25        pcre_malloc etc. are now initialized to local functions that call the
26        relevant global functions.
27    
28    7.  There were two entries missing in the vectors called coptable and poptable
29        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
30        I've fixed the data, and added a kludgy way of testing at compile time that
31        the lengths are correct (equal to the number of opcodes).
32    
33    8.  Following on from 7, I added a similar kludge to check the length of the
34        eint vector in pcreposix.c.
35    
36    9.  Error texts for pcre_compile() are held as one long string to avoid too
37        much relocation at load time. To find a text, the string is searched,
38        counting zeros. There was no check for running off the end of the string,
39        which could happen if a new error number was added without updating the
40        string.
41    
42    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
43    
44    11. \K was not working if it appeared in an atomic group or in a group that
45        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
46        \K is "not well defined" if used in an assertion. PCRE now accepts it if
47        the assertion is positive, but not if it is negative.
48    
49    
50    Version 8.01 19-Jan-2010
51    ------------------------
52    
53    1.  If a pattern contained a conditional subpattern with only one branch (in
54        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
55        computed the wrong minimum data length (which is of course zero for such
56        subpatterns). This could cause incorrect "no match" results.
57    
58    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
59        the pattern is reset in the first branch, pcre_compile() failed with
60        "internal error: code overflow at offset...". This happened only when
61        the reset was to the original external option setting. (An optimization
62        abstracts leading options settings into an external setting, which was the
63        cause of this.)
64    
65    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
66        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
67        assertion pattern did not match (meaning that the assertion was true), it
68        was incorrectly treated as false if the SKIP had been reached during the
69        matching. This also applied to assertions used as conditions.
70    
71    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
72        assertion subpattern, including such a pattern used as a condition,
73        unpredictable results occurred, instead of the error return
74        PCRE_ERROR_DFA_UITEM.
75    
76    5.  The C++ GlobalReplace function was not working like Perl for the special
77        situation when an empty string is matched. It now does the fancy magic
78        stuff that is necessary.
79    
80    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
81        removed. (These were left over from very, very early versions of PCRE.)
82    
83    7.  Some cosmetic changes to the code to make life easier when compiling it
84        as part of something else:
85    
86        (a) Change DEBUG to PCRE_DEBUG.
87    
88        (b) In pcre_compile(), rename the member of the "branch_chain" structure
89            called "current" as "current_branch", to prevent a collision with the
90            Linux macro when compiled as a kernel module.
91    
92        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
93            prevent a collision with the Linux macro when compiled as a kernel
94            module.
95    
96    8.  In pcre_compile() there are some checks for integer overflows that used to
97        cast potentially large values to (double). This has been changed to that
98        when building, a check for int64_t is made, and if it is found, it is used
99        instead, thus avoiding the use of floating point arithmetic. (There is no
100        other use of FP in PCRE.) If int64_t is not found, the fallback is to
101        double.
102    
103    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
104        2005 (difference between two addresses compared to an unsigned value).
105    
106    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
107        custom one, because of the following reported problem in Windows:
108    
109          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
110              under Win32.
111          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
112              therefore missing the function definition.
113          - The compiler thus generates a "C" signature for the test function.
114          - The linker fails to find the "C" function.
115          - PCRE fails to configure if asked to do so against libbz2.
116    
117    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
118        messages were output:
119    
120          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
121          rerunning libtoolize, to keep the correct libtool macros in-tree.
122          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
123    
124        I have done both of these things.
125    
126    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
127        most of the time, it *can* run out if it is given a pattern that contains a
128        runaway infinite recursion. I updated the discussion in the pcrestack man
129        page.
130    
131    13. Now that we have gone to the x.xx style of version numbers, the minor
132        version may start with zero. Using 08 or 09 is a bad idea because users
133        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
134        interpreted as invalid octal numbers. I've updated the previous comment in
135        configure.ac, and also added a check that gives an error if 08 or 09 are
136        used.
137    
138    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
139        causing partial matching to fail when the end of the subject matched \W
140        in a UTF-8 pattern where \W was quantified with a minimum of 3.
141    
142    15. There were some discrepancies between the declarations in pcre_internal.h
143        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
144        their definitions. The declarations used "const uschar *" and the
145        definitions used USPTR. Even though USPTR is normally defined as "const
146        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
147        reported that: "This difference in casting confuses some C++ compilers, for
148        example, SunCC recognizes above declarations as different functions and
149        generates broken code for hbpcre." I have changed the declarations to use
150        USPTR.
151    
152    16. GNU libtool is named differently on some systems. The autogen.sh script now
153        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
154        (FreeBSD).
155    
156    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
157        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
158        comment: "Figure out how to create a longlong from a string: strtoll and
159        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
160        instance, but it only takes 2 args instead of 3!"
161    
162    18. A subtle bug concerned with back references has been fixed by a change of
163        specification, with a corresponding code fix. A pattern such as
164        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
165        refers, was giving matches when it shouldn't. For example, xa=xaaa would
166        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
167        same bug. Such groups have to be quantified to be useful, or contained
168        inside another quantified group. (If there's no repetition, the reference
169        can never match.) The problem arises because, having left the group and
170        moved on to the rest of the pattern, a later failure that backtracks into
171        the group uses the captured value from the final iteration of the group
172        rather than the correct earlier one. I have fixed this in PCRE by forcing
173        any group that contains a reference to itself to be an atomic group; that
174        is, there cannot be any backtracking into it once it has completed. This is
175        similar to recursive and subroutine calls.
176    
177    
178    Version 8.00 19-Oct-09
179    ----------------------
180    
181    1.  The table for translating pcre_compile() error codes into POSIX error codes
182        was out-of-date, and there was no check on the pcre_compile() error code
183        being within the table. This could lead to an OK return being given in
184        error.
185    
186    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
187        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
188        in a Windows environment.
189    
190    3.  The pcregrep --count option prints the count for each file even when it is
191        zero, as does GNU grep. However, pcregrep was also printing all files when
192        --files-with-matches was added. Now, when both options are given, it prints
193        counts only for those files that have at least one match. (GNU grep just
194        prints the file name in this circumstance, but including the count seems
195        more useful - otherwise, why use --count?) Also ensured that the
196        combination -clh just lists non-zero counts, with no names.
197    
198    4.  The long form of the pcregrep -F option was incorrectly implemented as
199        --fixed_strings instead of --fixed-strings. This is an incompatible change,
200        but it seems right to fix it, and I didn't think it was worth preserving
201        the old behaviour.
202    
203    5.  The command line items --regex=pattern and --regexp=pattern were not
204        recognized by pcregrep, which required --regex pattern or --regexp pattern
205        (with a space rather than an '='). The man page documented the '=' forms,
206        which are compatible with GNU grep; these now work.
207    
208    6.  No libpcreposix.pc file was created for pkg-config; there was just
209        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
210    
211    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
212        when UCP support is not needed, by modifying the Python script that
213        generates it from Unicode data files. This should not matter if the module
214        is correctly used as a library, but I received one complaint about 50K of
215        unwanted data. My guess is that the person linked everything into his
216        program rather than using a library. Anyway, it does no harm.
217    
218    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
219        was a minimum greater than 1 for a wide character in a possessive
220        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
221        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
222        character. Chaos in the form of incorrect output or a compiling loop could
223        result.
224    
225    9.  The restrictions on what a pattern can contain when partial matching is
226        requested for pcre_exec() have been removed. All patterns can now be
227        partially matched by this function. In addition, if there are at least two
228        slots in the offset vector, the offset of the earliest inspected character
229        for the match and the offset of the end of the subject are set in them when
230        PCRE_ERROR_PARTIAL is returned.
231    
232    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
233        synonymous with PCRE_PARTIAL, for backwards compatibility, and
234        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
235        and may be more useful for multi-segment matching.
236    
237    11. Partial matching with pcre_exec() is now more intuitive. A partial match
238        used to be given if ever the end of the subject was reached; now it is
239        given only if matching could not proceed because another character was
240        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
241        string "Z", which now yields "no match" instead of "partial match". In the
242        case of pcre_dfa_exec(), "no match" is given if every matching path for the
243        final character ended with (*FAIL).
244    
245    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
246        if the pattern had a "must contain" character that was already found in the
247        earlier partial match, unless partial matching was again requested. For
248        example, with the pattern /dog.(body)?/, the "must contain" character is
249        "g". If the first part-match was for the string "dog", restarting with
250        "sbody" failed. This bug has been fixed.
251    
252    13. The string returned by pcre_dfa_exec() after a partial match has been
253        changed so that it starts at the first inspected character rather than the
254        first character of the match. This makes a difference only if the pattern
255        starts with a lookbehind assertion or \b or \B (\K is not supported by
256        pcre_dfa_exec()). It's an incompatible change, but it makes the two
257        matching functions compatible, and I think it's the right thing to do.
258    
259    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
260        so that the demonstration program is easily available in environments where
261        PCRE has not been installed from source.
262    
263    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
264        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
265        library.
266    
267    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
268        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
269        is not the first non-POSIX option to be added. Clearly some people find
270        these options useful.
271    
272    17. If a caller to the POSIX matching function regexec() passes a non-zero
273        value for nmatch with a NULL value for pmatch, the value of
274        nmatch is forced to zero.
275    
276    18. RunGrepTest did not have a test for the availability of the -u option of
277        the diff command, as RunTest does. It now checks in the same way as
278        RunTest, and also checks for the -b option.
279    
280    19. If an odd number of negated classes containing just a single character
281        interposed, within parentheses, between a forward reference to a named
282        subpattern and the definition of the subpattern, compilation crashed with
283        an internal error, complaining that it could not find the referenced
284        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
285        [The bug was that it was starting one character too far in when skipping
286        over the character class, thus treating the ] as data rather than
287        terminating the class. This meant it could skip too much.]
288    
289    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
290        /g option in pcretest when the pattern contains \K, which makes it possible
291        to have an empty string match not at the start, even when the pattern is
292        anchored. Updated pcretest and pcredemo to use this option.
293    
294    21. If the maximum number of capturing subpatterns in a recursion was greater
295        than the maximum at the outer level, the higher number was returned, but
296        with unset values at the outer level. The correct (outer level) value is
297        now given.
298    
299    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
300        PCRE did not set those parentheses (unlike Perl). I have now found a way to
301        make it do so. The string so far is captured, making this feature
302        compatible with Perl.
303    
304    23. The tests have been re-organized, adding tests 11 and 12, to make it
305        possible to check the Perl 5.10 features against Perl 5.10.
306    
307    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
308        pattern matches a fixed length string. PCRE did not allow this; now it
309        does. Neither allows recursion.
310    
311    25. I finally figured out how to implement a request to provide the minimum
312        length of subject string that was needed in order to match a given pattern.
313        (It was back references and recursion that I had previously got hung up
314        on.) This code has now been added to pcre_study(); it finds a lower bound
315        to the length of subject needed. It is not necessarily the greatest lower
316        bound, but using it to avoid searching strings that are too short does give
317        some useful speed-ups. The value is available to calling programs via
318        pcre_fullinfo().
319    
320    26. While implementing 25, I discovered to my embarrassment that pcretest had
321        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
322        study optimizations had never been tested with that matching function.
323        Oops. What is worse, even when it was passed study data, there was a bug in
324        pcre_dfa_exec() that meant it never actually used it. Double oops. There
325        were also very few tests of studied patterns with pcre_dfa_exec().
326    
327    27. If (?| is used to create subpatterns with duplicate numbers, they are now
328        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
329        on the other side of the coin, they are no longer allowed to have different
330        names, because these cannot be distinguished in PCRE, and this has caused
331        confusion. (This is a difference from Perl.)
332    
333    28. When duplicate subpattern names are present (necessarily with different
334        numbers, as required by 27 above), and a test is made by name in a
335        conditional pattern, either for a subpattern having been matched, or for
336        recursion in such a pattern, all the associated numbered subpatterns are
337        tested, and the overall condition is true if the condition is true for any
338        one of them. This is the way Perl works, and is also more like the way
339        testing by number works.
340    
341    
342    Version 7.9 11-Apr-09
343    ---------------------
344    
345    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
346        (pcretest), all targets were linked against these libraries. This included
347        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
348        libraries. This caused unwanted dependencies to be created. This problem
349        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
350        pcretest is linked with readline.
351    
352    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
353        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
354        moved outside it again, because FALSE and TRUE are already defined in AIX,
355        but BOOL is not.
356    
357    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
358        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
359    
360    4.  The pcregrep documentation said spaces were inserted as well as colons (or
361        hyphens) following file names and line numbers when outputting matching
362        lines. This is not true; no spaces are inserted. I have also clarified the
363        wording for the --colour (or --color) option.
364    
365    5.  In pcregrep, when --colour was used with -o, the list of matching strings
366        was not coloured; this is different to GNU grep, so I have changed it to be
367        the same.
368    
369    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
370        each matching line was coloured. Now it goes on to look for further matches
371        of any of the test patterns, which is the same behaviour as GNU grep.
372    
373    7.  A pattern that could match an empty string could cause pcregrep to loop; it
374        doesn't make sense to accept an empty string match in pcregrep, so I have
375        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
376        seems to be how GNU grep behaves.
377    
378    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
379        start or after a newline", because the conditional assertion was not being
380        correctly handled. The rule now is that both the assertion and what follows
381        in the first alternative must satisfy the test.
382    
383    9.  If auto-callout was enabled in a pattern with a conditional group whose
384        condition was an assertion, PCRE could crash during matching, both with
385        pcre_exec() and pcre_dfa_exec().
386    
387    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
388        used for matching.
389    
390    11. Unicode property support in character classes was not working for
391        characters (bytes) greater than 127 when not in UTF-8 mode.
392    
393    12. Added the -M command line option to pcretest.
394    
395    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
396    
397    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
398    
399    16. Added comments and documentation about mis-use of no_arg in the C++
400        wrapper.
401    
402    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
403        from Martin Jerabek that uses macro names for all relevant character and
404        string constants.
405    
406    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
407        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
408        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
409        these, but not everybody uses configure.
410    
411    19. A conditional group that had only one branch was not being correctly
412        recognized as an item that could match an empty string. This meant that an
413        enclosing group might also not be so recognized, causing infinite looping
414        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
415        with the subject "ab", where knowledge that the repeated group can match
416        nothing is needed in order to break the loop.
417    
418    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
419        exec(), but without supplying a callout function, matching went wrong.
420    
421    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
422        leak if the size of the offset vector was greater than 30. When the vector
423        is smaller, the saved offsets during recursion go onto a local stack
424        vector, but for larger vectors malloc() is used. It was failing to free
425        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
426        error, in fact).
427    
428    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
429        heapframe that is used only when UTF-8 support is enabled. This caused no
430        problem, but was untidy.
431    
432    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
433        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
434        included within another project.
435    
436    24. Steven Van Ingelgem's patches to add more options to the CMake support,
437        slightly modified by me:
438    
439          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
440              not building pcregrep.
441    
442          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
443              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
444    
445    25. Forward references, both numeric and by name, in patterns that made use of
446        duplicate group numbers, could behave incorrectly or give incorrect errors,
447        because when scanning forward to find the reference group, PCRE was not
448        taking into account the duplicate group numbers. A pattern such as
449        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
450    
451    26. Changed a few more instances of "const unsigned char *" to USPTR, making
452        the feature of a custom pointer more persuasive (as requested by a user).
453    
454    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
455        pcretest.c, inside #ifndefs, because it seems they are sometimes already
456        pre-defined.
457    
458    28. Added support for (*UTF8) at the start of a pattern.
459    
460    29. Arrange for flags added by the "release type" setting in CMake to be shown
461        in the configuration summary.
462    
463    
464    Version 7.8 05-Sep-08
465    ---------------------
466    
467    1.  Replaced UCP searching code with optimized version as implemented for Ad
468        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
469        stage table and inline lookup instead of a function, giving speed ups of 2
470        to 5 times on some simple patterns that I tested. Permission was given to
471        distribute the MultiStage2.py script that generates the tables (it's not in
472        the tarball, but is in the Subversion repository).
473    
474    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
475        scripts.
476    
477    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
478        a group with a zero qualifier. The result of the study could be incorrect,
479        or the function might crash, depending on the pattern.
480    
481    4.  Caseless matching was not working for non-ASCII characters in back
482        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
483        It now works when Unicode Property Support is available.
484    
485    5.  In pcretest, an escape such as \x{de} in the data was always generating
486        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
487        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
488        truncation.
489    
490    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
491    
492    7.  Added two (int) casts to pcregrep when printing the difference of two
493        pointers, in case they are 64-bit values.
494    
495    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
496        test 2 if it fails.
497    
498    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
499        and a #define of that name to empty if it is not externally set. This is to
500        allow users of MSVC to set it if necessary.
501    
502    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
503        the convenience functions in the pcre_get.c source file.
504    
505    11. An option change at the start of a pattern that had top-level alternatives
506        could cause overwriting and/or a crash. This command provoked a crash in
507        some environments:
508    
509          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
510    
511        This potential security problem was recorded as CVE-2008-2371.
512    
513    12. For a pattern where the match had to start at the beginning or immediately
514        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
515        pcre_dfa_exec() could read past the end of the passed subject if there was
516        no match. To help with detecting such bugs (e.g. with valgrind), I modified
517        pcretest so that it places the subject at the end of its malloc-ed buffer.
518    
519    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
520        exec() might read past the end of the data buffer in UTF-8 mode.
521    
522    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
523        the data contained the byte 0x85 as part of a UTF-8 character within its
524        first line. This applied both to normal and DFA matching.
525    
526    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
527        /^[^d]*?$/8 failed to match "abc".
528    
529    16. Added a missing copyright notice to pcrecpp_internal.h.
530    
531    17. Make it more clear in the documentation that values returned from
532        pcre_exec() in ovector are byte offsets, not character counts.
533    
534    18. Tidied a few places to stop certain compilers from issuing warnings.
535    
536    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
537        supplied by Stefan Weber. I made a further small update for 7.8 because
538        there is a change of source arrangements: the pcre_searchfuncs.c module is
539        replaced by pcre_ucd.c.
540    
541    
542    Version 7.7 07-May-08
543    ---------------------
544    
545    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
546        a string to a long long, pretend we don't even have a long long." This is
547        done by checking for the strtoq, strtoll, and _strtoi64 functions.
548    
549    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
550        pre-7.6 versions, which defined a global no_arg variable instead of putting
551        it in the RE class. (See also #8 below.)
552    
553    3.  Remove a line of dead code, identified by coverity and reported by Nuno
554        Lopes.
555    
556    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
557    
558        (1) The include/exclude patterns were being applied to the whole pathnames
559            of files, instead of just to the final components.
560    
561        (2) If there was more than one level of directory, the subdirectories were
562            skipped unless they satisfied the include/exclude conditions. This is
563            inconsistent with GNU grep (and could even be seen as contrary to the
564            pcregrep specification - which I improved to make it absolutely clear).
565            The action now is always to scan all levels of directory, and just
566            apply the include/exclude patterns to regular files.
567    
568    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
569        --exclude_dir in the tests to avoid scanning .svn directories.
570    
571    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
572        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
573        doesn't support NULs in patterns.
574    
575    7.  Added some missing "const"s to declarations of static tables in
576        pcre_compile.c and pcre_dfa_exec.c.
577    
578    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
579        caused by fix #2  above. (Subsequently also a second patch to fix the
580        first patch. And a third patch - this was a messy problem.)
581    
582    9.  Applied Craig's patch to remove the use of push_back().
583    
584    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
585        matching function regexec().
586    
587    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
588        which, however, unlike Perl's \g{...}, are subroutine calls, not back
589        references. PCRE supports relative numbers with this syntax (I don't think
590        Oniguruma does).
591    
592    12. Previously, a group with a zero repeat such as (...){0} was completely
593        omitted from the compiled regex. However, this means that if the group
594        was called as a subroutine from elsewhere in the pattern, things went wrong
595        (an internal error was given). Such groups are now left in the compiled
596        pattern, with a new opcode that causes them to be skipped at execution
597        time.
598    
599    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
600        to the way PCRE behaves:
601    
602        (a) A lone ] character is dis-allowed (Perl treats it as data).
603    
604        (b) A back reference to an unmatched subpattern matches an empty string
605            (Perl fails the current match path).
606    
607        (c) A data ] in a character class must be notated as \] because if the
608            first data character in a class is ], it defines an empty class. (In
609            Perl it is not possible to have an empty class.) The empty class []
610            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
611            The negative empty class [^] matches any one character, independently
612            of the DOTALL setting.
613    
614    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
615        non-existent subpattern following a character class starting with ']' and
616        containing () gave an internal compiling error instead of "reference to
617        non-existent subpattern". Fortunately, when the pattern did exist, the
618        compiled code was correct. (When scanning forwards to check for the
619        existencd of the subpattern, it was treating the data ']' as terminating
620        the class, so got the count wrong. When actually compiling, the reference
621        was subsequently set up correctly.)
622    
623    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
624        it was being rejected as not supported by pcre_dfa_exec(), even though
625        other assertions are supported. I have made pcre_dfa_exec() support
626        (*FAIL).
627    
628    16. The implementation of 13c above involved the invention of a new opcode,
629        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
630        cannot be changed at match time, I realized I could make a small
631        improvement to matching performance by compiling OP_ALLANY instead of
632        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
633        on the OP_ANY path.
634    
635    17. Compiling pcretest on Windows with readline support failed without the
636        following two fixes: (1) Make the unistd.h include conditional on
637        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
638    
639    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
640        ncurses library to be included for pcretest when ReadLine support is
641        requested, but also to allow for it to be overridden. This patch came from
642        Daniel Bergström.
643    
644    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
645        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
646        any errors with the current Unicode tables. Thanks to Peter Kankowski for
647        spotting this.
648    
649    
650    Version 7.6 28-Jan-08
651    ---------------------
652    
653    1.  A character class containing a very large number of characters with
654        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
655        overflow.
656    
657    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
658        HAVE_LONG_LONG is not defined.
659    
660    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
661        bring them up to date and include new features. This patch includes:
662    
663        - Fixed PH's badly added libz and libbz2 support.
664        - Fixed a problem with static linking.
665        - Added pcredemo. [But later removed - see 7 below.]
666        - Fixed dftables problem and added an option.
667        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
668            HAVE_LONG_LONG.
669        - Added readline support for pcretest.
670        - Added an listing of the option settings after cmake has run.
671    
672    4.  A user submitted a patch to Makefile that makes it easy to create
673        "pcre.dll" under mingw when using Configure/Make. I added stuff to
674        Makefile.am that cause it to include this special target, without
675        affecting anything else. Note that the same mingw target plus all
676        the other distribution libraries and programs are now supported
677        when configuring with CMake (see 6 below) instead of with
678        Configure/Make.
679    
680    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
681        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
682        exported in the Windows port". It has not yet been confirmed that the patch
683        solves the problem, but it does no harm.
684    
685    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
686        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
687        with CMake, and also correct the comment about stack recursion.
688    
689    7.  Remove the automatic building of pcredemo from the ./configure system and
690        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
691        of a program that users should build themselves after PCRE is installed, so
692        building it automatically is not really right. What is more, it gave
693        trouble in some build environments.
694    
695    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
696    
697    
698    Version 7.5 10-Jan-08
699    ---------------------
700    
701    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
702        values in parens when parsing an RE using the C++ wrapper."
703    
704    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
705        Characters greater than 255 were excluded from the class instead of being
706        included.
707    
708    3.  The same bug as (2) above applied to negated POSIX classes such as
709        [:^space:].
710    
711    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
712        defined or documented. It seems to have been a typo for PCRE_STATIC, so
713        I have changed it.
714    
715    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
716        first named subpattern) and a construct such as (?&a) would reference the
717        first named subpattern whose name started with "a" (in other words, the
718        length check was missing). Both these problems are fixed. "Subpattern name
719        expected" is now given for (?&) (a zero-length name), and this patch also
720        makes it give the same error for \k'' (previously it complained that that
721        was a reference to a non-existent subpattern).
722    
723    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
724        this is right because (?- can be followed by option settings as well as by
725        digits. I have, however, made the messages clearer.
726    
727    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
728        than the number used in the conditional) now cause a compile-time error.
729        This is actually not compatible with Perl, which accepts such patterns, but
730        treats the conditional as always being FALSE (as PCRE used to), but it
731        seems to me that giving a diagnostic is better.
732    
733    8.  Change "alphameric" to the more common word "alphanumeric" in comments
734        and messages.
735    
736    9.  Fix two occurrences of "backslash" in comments that should have been
737        "backspace".
738    
739    10. Remove two redundant lines of code that can never be obeyed (their function
740        was moved elsewhere).
741    
742    11. The program that makes PCRE's Unicode character property table had a bug
743        which caused it to generate incorrect table entries for sequences of
744        characters that have the same character type, but are in different scripts.
745        It amalgamated them into a single range, with the script of the first of
746        them. In other words, some characters were in the wrong script. There were
747        thirteen such cases, affecting characters in the following ranges:
748    
749          U+002b0 - U+002c1
750          U+0060c - U+0060d
751          U+0061e - U+00612
752          U+0064b - U+0065e
753          U+0074d - U+0076d
754          U+01800 - U+01805
755          U+01d00 - U+01d77
756          U+01d9b - U+01dbf
757          U+0200b - U+0200f
758          U+030fc - U+030fe
759          U+03260 - U+0327f
760          U+0fb46 - U+0fbb1
761          U+10450 - U+1049d
762    
763    12. The -o option (show only the matching part of a line) for pcregrep was not
764        compatible with GNU grep in that, if there was more than one match in a
765        line, it showed only the first of them. It now behaves in the same way as
766        GNU grep.
767    
768    13. If the -o and -v options were combined for pcregrep, it printed a blank
769        line for every non-matching line. GNU grep prints nothing, and pcregrep now
770        does the same. The return code can be used to tell if there were any
771        non-matching lines.
772    
773    14. Added --file-offsets and --line-offsets to pcregrep.
774    
775    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
776        infinitely looping recursion. The bug was that positive lookaheads were not
777        being skipped when checking for a possible empty match (negative lookaheads
778        and both kinds of lookbehind were skipped).
779    
780    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
781        inclusion of <windows.h> to before rather than after the definition of
782        INVALID_FILE_ATTRIBUTES (patch from David Byron).
783    
784    17. Specifying a possessive quantifier with a specific limit for a Unicode
785        character property caused pcre_compile() to compile bad code, which led at
786        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
787        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
788        caused the error; without that there was no problem.
789    
790    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
791    
792    19. Added --enable-pcretest-libreadline.
793    
794    20. In pcrecpp.cc, the variable 'count' was incremented twice in
795        RE::GlobalReplace(). As a result, the number of replacements returned was
796        double what it should be. I removed one of the increments, but Craig sent a
797        later patch that removed the other one (the right fix) and added unit tests
798        that check the return values (which was not done before).
799    
800    21. Several CMake things:
801    
802        (1) Arranged that, when cmake is used on Unix, the libraries end up with
803            the names libpcre and libpcreposix, not just pcre and pcreposix.
804    
805        (2) The above change means that pcretest and pcregrep are now correctly
806            linked with the newly-built libraries, not previously installed ones.
807    
808        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
809    
810    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
811        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
812        UTF-8 newline character). The key issue is that the pattern starts .*;
813        this means that the match must be either at the beginning, or after a
814        newline. The bug was in the code for advancing after a failed match and
815        checking that the new position followed a newline. It was not taking
816        account of UTF-8 characters correctly.
817    
818    23. PCRE was behaving differently from Perl in the way it recognized POSIX
819        character classes. PCRE was not treating the sequence [:...:] as a
820        character class unless the ... were all letters. Perl, however, seems to
821        allow any characters between [: and :], though of course it rejects as
822        unknown any "names" that contain non-letters, because all the known class
823        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
824        for example, whereas PCRE did not - it did not recognize a POSIX character
825        class. This seemed a bit dangerous, so the code has been changed to be
826        closer to Perl. The behaviour is not identical to Perl, because PCRE will
827        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
828        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
829        Perl does, and where it didn't before.
830    
831    24. Rewrite so as to remove the single use of %n from pcregrep because in some
832        Windows environments %n is disabled by default.
833    
834    
835    Version 7.4 21-Sep-07
836    ---------------------
837    
838    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
839        means that a class such as [\s] counted as "explicit reference to CR or
840        LF". That isn't really right - the whole point of the change was to try to
841        help when there was an actual mention of one of the two characters. So now
842        the change happens only if \r or \n (or a literal CR or LF) character is
843        encountered.
844    
845    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
846        of both had grown to the point where there were only 3 bits left.
847        Fortunately, there was spare space in the data structure, and so I have
848        moved the internal flags into a new 16-bit field to free up more option
849        bits.
850    
851    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
852        but did not set the internal JCHANGED flag - either of these is enough to
853        control the way the "get" function works - but the PCRE_INFO_JCHANGED
854        facility is supposed to tell if (?J) was ever used, so now (?J) at the
855        start sets both bits.
856    
857    4.  Added options (at build time, compile time, exec time) to change \R from
858        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
859    
860    5.  doc/pcresyntax.html was missing from the distribution.
861    
862    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
863        compatibility, even though it is no longer used.
864    
865    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
866        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
867        windows.h file is present (where different names are used). [This was
868        reversed later after testing - see 16 below.]
869    
870    8.  Changed all #include <config.h> to #include "config.h". There were also
871        some further <pcre.h> cases that I changed to "pcre.h".
872    
873    9.  When pcregrep was used with the --colour option, it missed the line ending
874        sequence off the lines that it output.
875    
876    10. It was pointed out to me that arrays of string pointers cause lots of
877        relocations when a shared library is dynamically loaded. A technique of
878        using a single long string with a table of offsets can drastically reduce
879        these. I have refactored PCRE in four places to do this. The result is
880        dramatic:
881    
882          Originally:                          290
883          After changing UCP table:            187
884          After changing error message table:   43
885          After changing table of "verbs"       36
886          After changing table of Posix names   22
887    
888        Thanks to the folks working on Gregex for glib for this insight.
889    
890    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
891        unicode-properties was also set.
892    
893    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
894    
895    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
896        checked only for CRLF.
897    
898    14. Added casts to pcretest.c to avoid compiler warnings.
899    
900    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
901    
902    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
903        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
904        entirely. This removes changes made in 7 above.
905    
906    17. The CMake files have been updated, and there is now more information about
907        building with CMake in the NON-UNIX-USE document.
908    
909    
910    Version 7.3 28-Aug-07
911    ---------------------
912    
913     1. In the rejigging of the build system that eventually resulted in 7.1, the
914        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
915        brackets there is not right, since it causes compilers to look for an
916        installed pcre.h, not the version that is in the source that is being
917        compiled (which of course may be different). I have changed it back to:
918    
919          #include "pcre.h"
920    
921        I have a vague recollection that the change was concerned with compiling in
922        different directories, but in the new build system, that is taken care of
923        by the VPATH setting the Makefile.
924    
925     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
926        when the subject happened to end in the byte 0x85 (e.g. if the last
927        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
928        characters but of course it shouldn't be taken as a newline when it is part
929        of another character. The bug was that, for an unlimited repeat of . in
930        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
931        characters when looking for a newline.
932    
933     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
934    
935     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
936        in debug output.
937    
938     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
939        long printing in the pcrecpp unittest when running under MinGW.
940    
941     6. ESC_K was left out of the EBCDIC table.
942    
943     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
944        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
945        limit also applies to "virtual nesting" when a pattern is recursive, and in
946        this case 1000 isn't so big. I have been able to remove this limit at the
947        expense of backing off one optimization in certain circumstances. Normally,
948        when pcre_exec() would call its internal match() function recursively and
949        immediately return the result unconditionally, it uses a "tail recursion"
950        feature to save stack. However, when a subpattern that can match an empty
951        string has an unlimited repetition quantifier, it no longer makes this
952        optimization. That gives it a stack frame in which to save the data for
953        checking that an empty string has been matched. Previously this was taken
954        from the 1000-entry workspace that had been reserved. So now there is no
955        explicit limit, but more stack is used.
956    
957     8. Applied Daniel's patches to solve problems with the import/export magic
958        syntax that is required for Windows, and which was going wrong for the
959        pcreposix and pcrecpp parts of the library. These were overlooked when this
960        problem was solved for the main library.
961    
962     9. There were some crude static tests to avoid integer overflow when computing
963        the size of patterns that contain repeated groups with explicit upper
964        limits. As the maximum quantifier is 65535, the maximum group length was
965        set at 30,000 so that the product of these two numbers did not overflow a
966        32-bit integer. However, it turns out that people want to use groups that
967        are longer than 30,000 bytes (though not repeat them that many times).
968        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
969        made it possible to implement the integer overflow checks in a much more
970        dynamic way, which I have now done. The artificial limitation on group
971        length has been removed - we now have only the limit on the total length of
972        the compiled pattern, which depends on the LINK_SIZE setting.
973    
974    10. Fixed a bug in the documentation for get/copy named substring when
975        duplicate names are permitted. If none of the named substrings are set, the
976        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
977        empty string.
978    
979    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
980        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
981        because the ] is interpreted as the first data character and the
982        terminating ] is not found. PCRE has been made compatible with Perl in this
983        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
984        cause memory overwriting.
985    
986    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
987        string has been matched (to stop an infinite loop). It was not recognizing
988        a conditional subpattern that could match an empty string if that
989        subpattern was within another subpattern. For example, it looped when
990        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
991        condition was not nested. This bug has been fixed.
992    
993    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
994        past the start of the subject in the presence of bytes with the top bit
995        set, for example "\x8aBCD".
996    
997    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
998        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
999    
1000    14. Optimized (?!) to (*FAIL).
1001    
1002    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1003        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1004        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1005        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1006        does: it's just the validity check that is more restrictive.
1007    
1008    16. Inserted checks for integer overflows during escape sequence (backslash)
1009        processing, and also fixed erroneous offset values for syntax errors during
1010        backslash processing.
1011    
1012    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1013        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1014    
1015    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1016        caused an overrun.
1017    
1018    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1019        something other than just ASCII characters) inside a group that had an
1020        unlimited repeat caused a loop at compile time (while checking to see
1021        whether the group could match an empty string).
1022    
1023    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1024        [\P{Any}] did so. (Error in the code for printing property names.)
1025    
1026    21. An orphan \E inside a character class could cause a crash.
1027    
1028    22. A repeated capturing bracket such as (A)? could cause a wild memory
1029        reference during compilation.
1030    
1031    23. There are several functions in pcre_compile() that scan along a compiled
1032        expression for various reasons (e.g. to see if it's fixed length for look
1033        behind). There were bugs in these functions when a repeated \p or \P was
1034        present in the pattern. These operators have additional parameters compared
1035        with \d, etc, and these were not being taken into account when moving along
1036        the compiled data. Specifically:
1037    
1038        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1039            length.
1040    
1041        (b) An item such as \pL+ within a repeated group could cause crashes or
1042            loops.
1043    
1044        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1045            "reference to non-existent subpattern" error.
1046    
1047        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1048    
1049    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1050        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1051    
1052    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1053    
1054    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1055        character were causing crashes (broken optimization).
1056    
1057    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1058        \p or \P) caused a compile-time loop.
1059    
1060    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1061        break. For example, the unstudied pattern [\r\n]A does not match the string
1062        "\r\nA" because change 7.0/46 below moves the current point on by two
1063        characters after failing to match at the start. However, the pattern \nA
1064        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1065        the same is true. There doesn't seem any very clean way out of this, but
1066        what I have chosen to do makes the common cases work: PCRE now takes note
1067        of whether there can be an explicit match for \r or \n anywhere in the
1068        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1069        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1070        pattern has explicit CR or LF references.
1071    
1072    29. Added (*CR) etc for changing newline setting at start of pattern.
1073    
1074    
1075    Version 7.2 19-Jun-07
1076  ---------------------  ---------------------
1077    
1078   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
# Line 12  Version 7.2 01-May-07 Line 1083  Version 7.2 01-May-07
1083    
1084   3. Add code to configure.ac to remove -g from the CFLAGS default settings.   3. Add code to configure.ac to remove -g from the CFLAGS default settings.
1085    
1086     4. Some of the "internals" tests were previously cut out when the link size
1087        was not 2, because the output contained actual offsets. The recent new
1088        "Z" feature of pcretest means that these can be cut out, making the tests
1089        usable with all link sizes.
1090    
1091     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
1092        stack recursion. This gives a massive performance boost under BSD, but just
1093        a small improvement under Linux. However, it saves one field in the frame
1094        in all cases.
1095    
1096     6. Added more features from the forthcoming Perl 5.10:
1097    
1098        (a) (?-n) (where n is a string of digits) is a relative subroutine or
1099            recursion call. It refers to the nth most recently opened parentheses.
1100    
1101        (b) (?+n) is also a relative subroutine call; it refers to the nth next
1102            to be opened parentheses.
1103    
1104        (c) Conditions that refer to capturing parentheses can be specified
1105            relatively, for example, (?(-2)... or (?(+3)...
1106    
1107        (d) \K resets the start of the current match so that everything before
1108            is not part of it.
1109    
1110        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1111    
1112        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1113            reference syntax.
1114    
1115        (g) (?| introduces a group in which the numbering of parentheses in each
1116            alternative starts with the same number.
1117    
1118        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1119    
1120     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1121        PCRE_INFO_JCHANGED.
1122    
1123     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1124        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1125        for detecting groups that can match an empty string.
1126    
1127     9. A pattern with a very large number of alternatives (more than several
1128        hundred) was running out of internal workspace during the pre-compile
1129        phase, where pcre_compile() figures out how much memory will be needed. A
1130        bit of new cunning has reduced the workspace needed for groups with
1131        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1132        workspace instead of running out of the 4096 that are available.
1133    
1134    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1135    
1136    11. Applied patch from Google to remove an optimization that didn't quite work.
1137        The report of the bug said:
1138    
1139          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1140          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1141          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1142    
1143    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1144        it matched the wrong number of bytes.
1145    
1146    
1147  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07
1148  ---------------------  ---------------------

Legend:
Removed from v.160  
changed lines
  Added in v.500

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12