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

Diff of /code/trunk/ChangeLog

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

revision 172 by ph10, Tue Jun 5 10:40:13 2007 UTC revision 974 by zherczeg, Sat Jun 2 05:56:58 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.2 05-June-07  Version 8.31
5    -----------------------------
6    
7    1.  Fixing a wrong JIT test case and some compiler warnings.
8    
9    2.  Removed a bashism from the RunTest script.
10    
11    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
12        to unsigned type, result still unsigned" that was given by an MS compiler
13        on encountering the code "-sizeof(xxx)".
14    
15    4.  Partial matching support is added to the JIT compiler.
16    
17    5.  Fixed several bugs concerned with partial matching of items that consist
18        of more than one character:
19    
20        (a) /^(..)\1/ did not partially match "aba" because checking references was
21            done on an "all or nothing" basis. This also applied to repeated
22            references.
23    
24        (b) \R did not give a hard partial match if \r was found at the end of the
25            subject.
26    
27        (c) \X did not give a hard partial match after matching one or more
28            characters at the end of the subject.
29    
30        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
31            a partial match for the string "\r".
32    
33        (e) When newline was set to CRLF, the metacharacter "." did not recognize
34            a partial match for a CR character at the end of the subject string.
35    
36    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
37        running pcretest, the text "(JIT)" added to the output whenever JIT is
38        actually used to run the match.
39    
40    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
41        or /S+[+] with a digit between 1 and 7.
42    
43    8.  OP_NOT now supports any UTF character not just single-byte ones.
44    
45    9.  (*MARK) control verb is now supported by the JIT compiler.
46    
47    10. The command "./RunTest list" lists the available tests without actually
48        running any of them. (Because I keep forgetting what they all are.)
49    
50    11. Add PCRE_INFO_MAXLOOKBEHIND.
51    
52    12. Applied a (slightly modified) user-supplied patch that improves performance
53        when the heap is used for recursion (compiled with --disable-stack-for-
54        recursion). Instead of malloc and free for each heap frame each time a
55        logical recursion happens, frames are retained on a chain and re-used where
56        possible. This sometimes gives as much as 30% improvement.
57    
58    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
59        call.
60    
61    14. As documented, (*COMMIT) is now confined to within a positive assertion.
62    
63    15. It is now possible to link pcretest with libedit as an alternative to
64        libreadline.
65    
66    16. (*COMMIT) control verb is now supported by the JIT compiler.
67    
68    17. The Unicode data tables have been updated to Unicode 6.1.0.
69    
70    18. Added --file-list option to pcregrep.
71    
72    19. Added binary file support to pcregrep, including the -a, --binary-files,
73        -I, and --text options.
74    
75    20. The madvise function is renamed for posix_madvise for QNX compatibility
76        reasons. Fixed by Giuseppe D'Angelo.
77    
78    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
79    
80    22. Changed the option for creating symbolic links for 16-bit man pages from
81        -s to -sf so that re-installing does not cause issues.
82    
83    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
84    
85    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
86        matches in certain environments (the workspace was not being correctly
87        retained). Also added to pcre_dfa_exec() a simple plausibility check on
88        some of the workspace data at the beginning of a restart.
89    
90    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
91        was not doing so when it should - probably a typo introduced by SVN 528
92        (change 8.10/14).
93    
94    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
95        \w+ when the character tables indicated that \x{c4} was a word character.
96        There were several related cases, all because the tests for doing a table
97        lookup were testing for characters less than 127 instead of 255.
98    
99    27. If a pattern contains capturing parentheses that are not used in a match,
100        their slots in the ovector are set to -1. For those that are higher than
101        any matched groups, this happens at the end of processing. In the case when
102        there were back references that the ovector was too small to contain
103        (causing temporary malloc'd memory to be used during matching), and the
104        highest capturing number was not used, memory off the end of the ovector
105        was incorrectly being set to -1. (It was using the size of the temporary
106        memory instead of the true size.)
107    
108    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
109        ovector size, it uses memory at the end of the block that it has got.
110    
111    29. Check for an overlong MARK name and give an error at compile time. The
112        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
113    
114    30. JIT compiler update.
115    
116    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
117        Rill for the patch.
118    
119    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
120    
121    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
122    
123    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
124        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
125        was enabled.
126    
127    35. Improve JIT code generation for greedy plus quantifier.
128    
129    
130    Version 8.30 04-February-2012
131    -----------------------------
132    
133    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
134        name is defined in ctype.h.
135    
136    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
137        only in quite long subpatterns.
138    
139    3.  Removed the function pcre_info(), which has been obsolete and deprecated
140        since it was replaced by pcre_fullinfo() in February 2000.
141    
142    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
143        match a (*MARK), and the match failed at the start of the subject, a
144        reference to memory before the start of the subject could occur. This bug
145        was introduced by fix 17 of release 8.21.
146    
147    5.  A reference to an unset group with zero minimum repetition was giving
148        totally wrong answers (in non-JavaScript-compatibility mode). For example,
149        /(another)?(\1?)test/ matched against "hello world test". This bug was
150        introduced in release 8.13.
151    
152    6.  Add support for 16-bit character strings (a large amount of work involving
153        many changes and refactorings).
154    
155    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
156        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
157        from a file.
158    
159    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
160        rounding is not applied in this particular case).
161    
162    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
163        if they appear, or are escaped, in patterns.
164    
165    10. Get rid of a number of -Wunused-but-set-variable warnings.
166    
167    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
168        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
169        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
170        also returns the mark "x". This bug applied to capturing parentheses,
171        non-capturing parentheses, and atomic parentheses. It also applied to some
172        assertions.
173    
174    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
175        information out of configure.ac instead of relying on pcre.h.generic, which
176        is not stored in the repository.
177    
178    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
179        -lreadline.
180    
181    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
182    
183    15. Applied Graycode's patch to put the top-level frame on the stack rather
184        than the heap when not using the stack for recursion. This gives a
185        performance improvement in many cases when recursion is not deep.
186    
187    16. Experimental code added to "pcretest -C" to output the stack frame size.
188    
189    
190    Version 8.21 12-Dec-2011
191    ------------------------
192    
193    1.  Updating the JIT compiler.
194    
195    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
196        are added as well.
197    
198    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
199        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
200        calling _pcre_jit_exec. Some extra comments are added.
201    
202    4.  (*MARK) settings inside atomic groups that do not contain any capturing
203        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
204        was introduced by change 18 for 8.20.
205    
206    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
207        ECMA-262 standard.
208    
209    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
210        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
211        This bug was probably introduced by change 9 of 8.13.
212    
213    7.  While fixing 6 above, I noticed that a number of other items were being
214        incorrectly rejected as "not fixed length". This arose partly because newer
215        opcodes had not been added to the fixed-length checking code. I have (a)
216        corrected the bug and added tests for these items, and (b) arranged for an
217        error to occur if an unknown opcode is encountered while checking for fixed
218        length instead of just assuming "not fixed length". The items that were
219        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
220        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
221        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
222    
223    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
224        being incorrectly compiled and would have given unpredicatble results.
225    
226    9.  A possessively repeated subpattern with minimum repeat count greater than
227        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
228        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
229        the first (A) could occur when it should not.
230    
231    10. Add a cast and remove a redundant test from the code.
232    
233    11. JIT should use pcre_malloc/pcre_free for allocation.
234    
235    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
236        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
237        is anything other than /usr, -L is still shown).
238    
239    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
240    
241    14. Perl does not support \N without a following name in a [] class; PCRE now
242        also gives an error.
243    
244    15. If a forward reference was repeated with an upper limit of around 2000,
245        it caused the error "internal error: overran compiling workspace". The
246        maximum number of forward references (including repeats) was limited by the
247        internal workspace, and dependent on the LINK_SIZE. The code has been
248        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
249        the default depends on LINK_SIZE. There is a new upper limit (for safety)
250        of around 200,000 forward references. While doing this, I also speeded up
251        the filling in of repeated forward references.
252    
253    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
254        incorrectly expecting the subject to contain another "a" after the start.
255    
256    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
257        in the match, the SKIP should be ignored. This was not happening; instead
258        the SKIP was being treated as NOMATCH. For patterns such as
259        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
260        tested.
261    
262    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
263        now much more compatible with Perl, in particular in cases where the result
264        is a non-match for a non-anchored pattern. For example, if
265        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
266        "m", where previously it did not return a name. A side effect of this
267        change is that for partial matches, the last encountered mark name is
268        returned, as for non matches. A number of tests that were previously not
269        Perl-compatible have been moved into the Perl-compatible test files. The
270        refactoring has had the pleasing side effect of removing one argument from
271        the match() function, thus reducing its stack requirements.
272    
273    19. If the /S+ option was used in pcretest to study a pattern using JIT,
274        subsequent uses of /S (without +) incorrectly behaved like /S+.
275    
276    21. Retrieve executable code size support for the JIT compiler and fixing
277        some warnings.
278    
279    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
280        not work when the shorter character appeared right at the end of the
281        subject string.
282    
283    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
284        systems.
285    
286    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
287        output it when the /M option is used in pcretest.
288    
289    25. The CheckMan script was not being included in the distribution. Also, added
290        an explicit "perl" to run Perl scripts from the PrepareRelease script
291        because this is reportedly needed in Windows.
292    
293    26. If study data was being save in a file and studying had not found a set of
294        "starts with" bytes for the pattern, the data written to the file (though
295        never used) was taken from uninitialized memory and so caused valgrind to
296        complain.
297    
298    27. Updated RunTest.bat as provided by Sheri Pierce.
299    
300    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
301    
302    29. Computation of memory usage for the table of capturing group names was
303        giving an unnecessarily large value.
304    
305    
306    Version 8.20 21-Oct-2011
307    ------------------------
308    
309    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
310        a POSIX class. After further experiments with Perl, which convinced me that
311        Perl has bugs and confusions, a closing square bracket is no longer allowed
312        in a POSIX name. This bug also affected patterns with classes that started
313        with full stops.
314    
315    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
316        captured substring, but while checking the failing first alternative,
317        substring 1 is temporarily captured. If the output vector supplied to
318        pcre_exec() was not big enough for this capture, the yield of the function
319        was still zero ("insufficient space for captured substrings"). This cannot
320        be totally fixed without adding another stack variable, which seems a lot
321        of expense for a edge case. However, I have improved the situation in cases
322        such as /(a)(b)x|abc/ matched against "abc", where the return code
323        indicates that fewer than the maximum number of slots in the ovector have
324        been set.
325    
326    3.  Related to (2) above: when there are more back references in a pattern than
327        slots in the output vector, pcre_exec() uses temporary memory during
328        matching, and copies in the captures as far as possible afterwards. It was
329        using the entire output vector, but this conflicts with the specification
330        that only 2/3 is used for passing back captured substrings. Now it uses
331        only the first 2/3, for compatibility. This is, of course, another edge
332        case.
333    
334    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
335        main code base, and can be used by building with --enable-jit. When this is
336        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
337        runtime --no-jit option is given.
338    
339    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
340        ovector, the return from the function was zero, implying that there were
341        other matches that did not fit. The correct "exactly full" value is now
342        returned.
343    
344    6.  If a subpattern that was called recursively or as a subroutine contained
345        (*PRUNE) or any other control that caused it to give a non-standard return,
346        invalid errors such as "Error -26 (nested recursion at the same subject
347        position)" or even infinite loops could occur.
348    
349    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
350        computing the minimum length on reaching *ACCEPT, and so ended up with the
351        wrong value of 1 rather than 0. Further investigation indicates that
352        computing a minimum subject length in the presence of *ACCEPT is difficult
353        (think back references, subroutine calls), and so I have changed the code
354        so that no minimum is registered for a pattern that contains *ACCEPT.
355    
356    8.  If (*THEN) was present in the first (true) branch of a conditional group,
357        it was not handled as intended. [But see 16 below.]
358    
359    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
360        Sheri Pierce.
361    
362    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
363        the first byte in a match must be "a".
364    
365    11. Change 17 for 8.13 increased the recursion depth for patterns like
366        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
367        pattern contains any instances of (*THEN). If it does not, the old
368        optimizations are restored. It would be nice to do this on a per-group
369        basis, but at the moment that is not feasible.
370    
371    12. In some environments, the output of pcretest -C is CRLF terminated. This
372        broke RunTest's code that checks for the link size. A single white space
373        character after the value is now allowed for.
374    
375    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
376        For "fr", it uses the Windows-specific input and output files.
377    
378    14. If (*THEN) appeared in a group that was called recursively or as a
379        subroutine, it did not work as intended. [But see next item.]
380    
381    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
382        pattern fragments (but not containing any | characters). If A and B are
383        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
384        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
385        D. In other words, Perl considers parentheses that do not contain any |
386        characters to be part of a surrounding alternative, whereas PCRE was
387        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
388        differently. PCRE now behaves in the same way as Perl, except in the case
389        of subroutine/recursion calls such as (?1) which have in any case always
390        been different (but PCRE had them first :-).
391    
392    16. Related to 15 above: Perl does not treat the | in a conditional group as
393        creating alternatives. Such a group is treated in the same way as an
394        ordinary group without any | characters when processing (*THEN). PCRE has
395        been changed to match Perl's behaviour.
396    
397    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
398        RunGrepTest script failed.
399    
400    18. Change 22 for version 13 caused atomic groups to use more stack. This is
401        inevitable for groups that contain captures, but it can lead to a lot of
402        stack use in large patterns. The old behaviour has been restored for atomic
403        groups that do not contain any capturing parentheses.
404    
405    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
406        suppress the check for a minimum subject length at run time. (If it was
407        given to pcre_exec() or pcre_dfa_exec() it did work.)
408    
409    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
410        fail to work when decoding hex characters in data strings in EBCDIC
411        environments.
412    
413    21. It appears that in at least one Mac OS environment, the isxdigit() function
414        is implemented as a macro that evaluates to its argument more than once,
415        contravening the C 90 Standard (I haven't checked a later standard). There
416        was an instance in pcretest which caused it to go wrong when processing
417        \x{...} escapes in subject strings. The has been rewritten to avoid using
418        things like p++ in the argument of isxdigit().
419    
420    
421    Version 8.13 16-Aug-2011
422    ------------------------
423    
424    1.  The Unicode data tables have been updated to Unicode 6.0.0.
425    
426    2.  Two minor typos in pcre_internal.h have been fixed.
427    
428    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
429        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
430        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
431    
432    4.  There were a number of related bugs in the code for matching backrefences
433        caselessly in UTF-8 mode when codes for the characters concerned were
434        different numbers of bytes. For example, U+023A and U+2C65 are an upper
435        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
436        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
437        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
438        2-byte code at the end of the subject (it thought there wasn't enough data
439        left).
440    
441    5.  Comprehensive information about what went wrong is now returned by
442        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
443        as the output vector has at least 2 elements. The offset of the start of
444        the failing character and a reason code are placed in the vector.
445    
446    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
447        now returned is for the first byte of the failing character, instead of the
448        last byte inspected. This is an incompatible change, but I hope it is small
449        enough not to be a problem. It makes the returned offset consistent with
450        pcre_exec() and pcre_dfa_exec().
451    
452    7.  pcretest now gives a text phrase as well as the error number when
453        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
454        failure, the offset and reason code are output.
455    
456    8.  When \R was used with a maximizing quantifier it failed to skip backwards
457        over a \r\n pair if the subsequent match failed. Instead, it just skipped
458        back over a single character (\n). This seems wrong (because it treated the
459        two characters as a single entity when going forwards), conflicts with the
460        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
461        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
462        has been changed.
463    
464    9.  Some internal refactoring has changed the processing so that the handling
465        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
466        time (the PCRE_DOTALL option was changed this way some time ago: version
467        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
468        which was always a bit of a fudge. It also means that there is one less
469        argument for the match() function, which reduces its stack requirements
470        slightly. This change also fixes an incompatibility with Perl: the pattern
471        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
472    
473    10. More internal refactoring has drastically reduced the number of recursive
474        calls to match() for possessively repeated groups such as (abc)++ when
475        using pcre_exec().
476    
477    11. While implementing 10, a number of bugs in the handling of groups were
478        discovered and fixed:
479    
480        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
481        (a|)*(?1) gave a compile-time internal error.
482        ((a|)+)+  did not notice that the outer group could match an empty string.
483        (^a|^)+   was not marked as anchored.
484        (.*a|.*)+ was not marked as matching at start or after a newline.
485    
486    12. Yet more internal refactoring has removed another argument from the match()
487        function. Special calls to this function are now indicated by setting a
488        value in a variable in the "match data" data block.
489    
490    13. Be more explicit in pcre_study() instead of relying on "default" for
491        opcodes that mean there is no starting character; this means that when new
492        ones are added and accidentally left out of pcre_study(), testing should
493        pick them up.
494    
495    14. The -s option of pcretest has been documented for ages as being an old
496        synonym of -m (show memory usage). I have changed it to mean "force study
497        for every regex", that is, assume /S for every regex. This is similar to -i
498        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
499        using it. It makes it easier to run collections of tests with and without
500        study enabled, and thereby test pcre_study() more easily. All the standard
501        tests are now run with and without -s (but some patterns can be marked as
502        "never study" - see 20 below).
503    
504    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
505        restoration of the capturing data to the outer values was not happening
506        correctly.
507    
508    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
509        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
510        pattern had matched an empty string, and so incorrectly returned a no
511        match.
512    
513    17. There was optimizing code for the last branch of non-capturing parentheses,
514        and also for the obeyed branch of a conditional subexpression, which used
515        tail recursion to cut down on stack usage. Unfortunately, now that there is
516        the possibility of (*THEN) occurring in these branches, tail recursion is
517        no longer possible because the return has to be checked for (*THEN). These
518        two optimizations have therefore been removed. [But see 8.20/11 above.]
519    
520    18. If a pattern containing \R was studied, it was assumed that \R always
521        matched two bytes, thus causing the minimum subject length to be
522        incorrectly computed because \R can also match just one byte.
523    
524    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
525        was incorrectly computed.
526    
527    20. If /S is present twice on a test pattern in pcretest input, it now
528        *disables* studying, thereby overriding the use of -s on the command line
529        (see 14 above). This is necessary for one or two tests to keep the output
530        identical in both cases.
531    
532    21. When (*ACCEPT) was used in an assertion that matched an empty string and
533        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
534    
535    22. When an atomic group that contained a capturing parenthesis was
536        successfully matched, but the branch in which it appeared failed, the
537        capturing was not being forgotten if a higher numbered group was later
538        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
539        group 1 to "a", when in fact it should be unset. This applied to multi-
540        branched capturing and non-capturing groups, repeated or not, and also to
541        positive assertions (capturing in negative assertions does not happen
542        in PCRE) and also to nested atomic groups.
543    
544    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
545        subject after a captured substring, to make it easier to tell which of a
546        number of identical substrings has been captured.
547    
548    24. The way atomic groups are processed by pcre_exec() has been changed so that
549        if they are repeated, backtracking one repetition now resets captured
550        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
551        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
552        "aaa". Previously, it would have been "a". As part of this code
553        refactoring, the way recursive calls are handled has also been changed.
554    
555    25. If an assertion condition captured any substrings, they were not passed
556        back unless some other capturing happened later. For example, if
557        (?(?=(a))a) was matched against "a", no capturing was returned.
558    
559    26. When studying a pattern that contained subroutine calls or assertions,
560        the code for finding the minimum length of a possible match was handling
561        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
562        group 1 called group 2 while simultaneously a separate group 2 called group
563        1). A stack overflow occurred in this case. I have fixed this by limiting
564        the recursion depth to 10.
565    
566    27. Updated RunTest.bat in the distribution to the version supplied by Tom
567        Fortmann. This supports explicit test numbers on the command line, and has
568        argument validation and error reporting.
569    
570    28. An instance of \X with an unlimited repeat could fail if at any point the
571        first character it looked at was a mark character.
572    
573    29. Some minor code refactoring concerning Unicode properties and scripts
574        should reduce the stack requirement of match() slightly.
575    
576    30. Added the '=' option to pcretest to check the setting of unused capturing
577        slots at the end of the pattern, which are documented as being -1, but are
578        not included in the return count.
579    
580    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
581        compiled something random. Now it gives a compile-time error (as does
582        Perl).
583    
584    32. A *MARK encountered during the processing of a positive assertion is now
585        recorded and passed back (compatible with Perl).
586    
587    33. If --only-matching or --colour was set on a pcregrep call whose pattern
588        had alternative anchored branches, the search for a second match in a line
589        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
590        matched the line "0102" twice. The same bug affected patterns that started
591        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
592        twice.
593    
594    34. Previously, PCRE did not allow quantification of assertions. However, Perl
595        does, and because of capturing effects, quantifying parenthesized
596        assertions may at times be useful. Quantifiers are now allowed for
597        parenthesized assertions.
598    
599    35. A minor code tidy in pcre_compile() when checking options for \R usage.
600    
601    36. \g was being checked for fancy things in a character class, when it should
602        just be a literal "g".
603    
604    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
605        appearance of a nested POSIX class supersedes an apparent external class.
606        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
607        unescaped square brackets may also appear as part of class names. For
608        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
609        more like Perl. (But see 8.20/1 above.)
610    
611    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
612        was because it thought it was \N{name}, which is not supported).
613    
614    39. Add minix to OS list not supporting the -S option in pcretest.
615    
616    40. PCRE tries to detect cases of infinite recursion at compile time, but it
617        cannot analyze patterns in sufficient detail to catch mutual recursions
618        such as ((?1))((?2)). There is now a runtime test that gives an error if a
619        subgroup is called recursively as a subpattern for a second time at the
620        same position in the subject string. In previous releases this might have
621        been caught by the recursion limit, or it might have run out of stack.
622    
623    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
624        happen only once. PCRE was, however incorrectly giving a compile time error
625        "recursive call could loop indefinitely" because it cannot analyze the
626        pattern in sufficient detail. The compile time test no longer happens when
627        PCRE is compiling a conditional subpattern, but actual runaway loops are
628        now caught at runtime (see 40 above).
629    
630    42. It seems that Perl allows any characters other than a closing parenthesis
631        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
632        has been changed to be the same.
633    
634    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
635        as not to get warnings when autogen.sh is called. Also changed
636        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
637    
638    44. To help people who use pcregrep to scan files containing exceedingly long
639        lines, the following changes have been made:
640    
641        (a) The default value of the buffer size parameter has been increased from
642            8K to 20K. (The actual buffer used is three times this size.)
643    
644        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
645            PCRE is built.
646    
647        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
648            to be set at run time.
649    
650        (d) Numerical values in pcregrep options can be followed by K or M, for
651            example --buffer-size=50K.
652    
653        (e) If a line being scanned overflows pcregrep's buffer, an error is now
654            given and the return code is set to 2.
655    
656    45. Add a pointer to the latest mark to the callout data block.
657    
658    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
659        partial match of an empty string instead of no match. This was specific to
660        the use of ".".
661    
662    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
663        complete match instead of a partial match. This bug was dependent on both
664        the PCRE_UTF8 and PCRE_DOTALL options being set.
665    
666    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
667        starting byte set, because \b was not being ignored.
668    
669    
670    Version 8.12 15-Jan-2011
671    ------------------------
672    
673    1.  Fixed some typos in the markup of the man pages, and wrote a script that
674        checks for such things as part of the documentation building process.
675    
676    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
677        --match-limit and --recursion-limit options (added for 8.11). In
678        particular, this made one of the standard tests fail. (The integer value
679        went into the wrong half of a long int.)
680    
681    3.  If the --colour option was given to pcregrep with -v (invert match), it
682        did strange things, either producing crazy output, or crashing. It should,
683        of course, ignore a request for colour when reporting lines that do not
684        match.
685    
686    4.  Another pcregrep bug caused similar problems if --colour was specified with
687        -M (multiline) and the pattern match finished with a line ending.
688    
689    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
690        matched in multiline mode, the following line was shown as part of the
691        match. This seems wrong, so I have changed it.
692    
693    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
694        the check for further matches in the same line (so they could be coloured)
695        to overrun the end of the current line. If another match was found, it was
696        incorrectly shown (and then shown again when found in the next line).
697    
698    7.  If pcregrep was compiled under Windows, there was a reference to the
699        function pcregrep_exit() before it was defined. I am assuming this was
700        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
701        reported by a user. I've moved the definition above the reference.
702    
703    
704    Version 8.11 10-Dec-2010
705    ------------------------
706    
707    1.  (*THEN) was not working properly if there were untried alternatives prior
708        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
709        backtracked to try for "b" instead of moving to the next alternative branch
710        at the same level (in this case, to look for "c"). The Perl documentation
711        is clear that when (*THEN) is backtracked onto, it goes to the "next
712        alternative in the innermost enclosing group".
713    
714    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
715        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
716        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
717        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
718        (*THEN).
719    
720    3.  If \s appeared in a character class, it removed the VT character from
721        the class, even if it had been included by some previous item, for example
722        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
723        of \s, but is part of the POSIX "space" class.)
724    
725    4.  A partial match never returns an empty string (because you can always
726        match an empty string at the end of the subject); however the checking for
727        an empty string was starting at the "start of match" point. This has been
728        changed to the "earliest inspected character" point, because the returned
729        data for a partial match starts at this character. This means that, for
730        example, /(?<=abc)def/ gives a partial match for the subject "abc"
731        (previously it gave "no match").
732    
733    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
734        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
735        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
736        has an implication that the given string is incomplete (because a partial
737        match is preferred over a full match). For this reason, these items now
738        give a partial match in this situation. [Aside: previously, the one case
739        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
740        match rather than a full match, which was wrong by the old rules, but is
741        now correct.]
742    
743    6.  There was a bug in the handling of #-introduced comments, recognized when
744        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
745        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
746        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
747        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
748        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
749        places in pcre_compile().
750    
751    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
752        comments when looking ahead for named forward references to subpatterns,
753        the only newline sequence it recognized was NL. It now handles newlines
754        according to the set newline convention.
755    
756    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
757        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
758        cater for a lack of strerror(). These oversights have been fixed.
759    
760    9.  Added --match-limit and --recursion-limit to pcregrep.
761    
762    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
763    
764    11. When the -o option was used, pcregrep was setting a return code of 1, even
765        when matches were found, and --line-buffered was not being honoured.
766    
767    12. Added an optional parentheses number to the -o and --only-matching options
768        of pcregrep.
769    
770    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
771        can match an empty string. The code to do it in pcretest and pcredemo
772        needed fixing:
773    
774        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
775            only one byte after an empty string match just before CRLF (this case
776            just got forgotten; "any" and "anycrlf" were OK).
777    
778        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
779            mode when an empty string match preceded an ASCII character followed by
780            a non-ASCII character. (The code for advancing by one character rather
781            than one byte was nonsense.)
782    
783        (c) The pcredemo.c sample program did not have any code at all to handle
784            the cases when CRLF is a valid newline sequence.
785    
786    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
787        as a starting offset was within the subject string. There is now a new
788        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
789        negative or greater than the length of the string. In order to test this,
790        pcretest is extended to allow the setting of negative starting offsets.
791    
792    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
793        starting offset points to the beginning of a UTF-8 character was
794        unnecessarily clumsy. I tidied it up.
795    
796    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
797        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
798    
799    17. Nobody had reported that the --include_dir option, which was added in
800        release 7.7 should have been called --include-dir (hyphen, not underscore)
801        for compatibility with GNU grep. I have changed it to --include-dir, but
802        left --include_dir as an undocumented synonym, and the same for
803        --exclude-dir, though that is not available in GNU grep, at least as of
804        release 2.5.4.
805    
806    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
807        characters from a string of bytes) have been redefined so as not to use
808        loops, in order to improve performance in some environments. At the same
809        time, I abstracted some of the common code into auxiliary macros to save
810        repetition (this should not affect the compiled code).
811    
812    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
813        compile-time error is now given if \c is not followed by an ASCII
814        character, that is, a byte less than 128. (In EBCDIC mode, the code is
815        different, and any byte value is allowed.)
816    
817    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
818        START_OPTIMIZE option, which is now allowed at compile time - but just
819        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
820        to pcregrep and other applications that have no direct access to PCRE
821        options. The new /Y option in pcretest sets this option when calling
822        pcre_compile().
823    
824    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
825        back references. Groups containing recursive back references were forced to
826        be atomic by that change, but in the case of named groups, the amount of
827        memory required was incorrectly computed, leading to "Failed: internal
828        error: code overflow". This has been fixed.
829    
830    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
831        pcretest.c, to avoid build problems in some Borland environments.
832    
833    
834    Version 8.10 25-Jun-2010
835    ------------------------
836    
837    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
838        THEN.
839    
840    2.  (*ACCEPT) was not working when inside an atomic group.
841    
842    3.  Inside a character class, \B is treated as a literal by default, but
843        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
844        causes the error). The code is unchanged, but I tidied the documentation.
845    
846    4.  Inside a character class, PCRE always treated \R and \X as literals,
847        whereas Perl faults them if its -w option is set. I have changed PCRE so
848        that it faults them when PCRE_EXTRA is set.
849    
850    5.  Added support for \N, which always matches any character other than
851        newline. (It is the same as "." when PCRE_DOTALL is not set.)
852    
853    6.  When compiling pcregrep with newer versions of gcc which may have
854        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
855        declared with attribute warn_unused_result" were given. Just casting the
856        result to (void) does not stop the warnings; a more elaborate fudge is
857        needed. I've used a macro to implement this.
858    
859    7.  Minor change to pcretest.c to avoid a compiler warning.
860    
861    8.  Added four artifical Unicode properties to help with an option to make
862        \s etc use properties (see next item). The new properties are: Xan
863        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
864    
865    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
866        use Unicode properties. (*UCP) at the start of a pattern can be used to set
867        this option. Modified pcretest to add /W to test this facility. Added
868        REG_UCP to make it available via the POSIX interface.
869    
870    10. Added --line-buffered to pcregrep.
871    
872    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
873        studied, and the match started with a letter with a code point greater than
874        127 whose first byte was different to the first byte of the other case of
875        the letter, the other case of this starting letter was not recognized
876        (#976).
877    
878    12. If a pattern that was studied started with a repeated Unicode property
879        test, for example, \p{Nd}+, there was the theoretical possibility of
880        setting up an incorrect bitmap of starting bytes, but fortunately it could
881        not have actually happened in practice until change 8 above was made (it
882        added property types that matched character-matching opcodes).
883    
884    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
885        possible starting bytes for non-anchored patterns.
886    
887    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
888        \R, and also a number of cases that involve Unicode properties, both
889        explicit and implicit when PCRE_UCP is set.
890    
891    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
892        input, it could crash or give wrong results if characters with values
893        greater than 0xc0 were present in the subject string. (Detail: it assumed
894        UTF-8 input when processing these items.)
895    
896    16. Added a lot of (int) casts to avoid compiler warnings in systems where
897        size_t is 64-bit (#991).
898    
899    17. Added a check for running out of memory when PCRE is compiled with
900        --disable-stack-for-recursion (#990).
901    
902    18. If the last data line in a file for pcretest does not have a newline on
903        the end, a newline was missing in the output.
904    
905    19. The default pcre_chartables.c file recognizes only ASCII characters (values
906        less than 128) in its various bitmaps. However, there is a facility for
907        generating tables according to the current locale when PCRE is compiled. It
908        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
909        characters, are recognized by isspace() and therefore were getting set in
910        these tables, and indeed these tables seem to approximate to ISO 8859. This
911        caused a problem in UTF-8 mode when pcre_study() was used to create a list
912        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
913        which of course cannot start UTF-8 characters. I have changed the code so
914        that only real ASCII characters (less than 128) and the correct starting
915        bytes for UTF-8 encodings are set for characters greater than 127 when in
916        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
917        altogether.)
918    
919    20. Added the /T option to pcretest so as to be able to run tests with non-
920        standard character tables, thus making it possible to include the tests
921        used for 19 above in the standard set of tests.
922    
923    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
924        reference to a subpattern the other side of a comment that contains an
925        opening parenthesis caused either an internal compiling error, or a
926        reference to the wrong subpattern.
927    
928    
929    Version 8.02 19-Mar-2010
930    ------------------------
931    
932    1.  The Unicode data tables have been updated to Unicode 5.2.0.
933    
934    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
935        configured.
936    
937    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
938        original author of that file, following a query about its status.
939    
940    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
941        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
942    
943    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
944        quantifier applied to a forward-referencing subroutine call, could compile
945        incorrect code or give the error "internal error: previously-checked
946        referenced subpattern not found".
947    
948    6.  Both MS Visual Studio and Symbian OS have problems with initializing
949        variables to point to external functions. For these systems, therefore,
950        pcre_malloc etc. are now initialized to local functions that call the
951        relevant global functions.
952    
953    7.  There were two entries missing in the vectors called coptable and poptable
954        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
955        I've fixed the data, and added a kludgy way of testing at compile time that
956        the lengths are correct (equal to the number of opcodes).
957    
958    8.  Following on from 7, I added a similar kludge to check the length of the
959        eint vector in pcreposix.c.
960    
961    9.  Error texts for pcre_compile() are held as one long string to avoid too
962        much relocation at load time. To find a text, the string is searched,
963        counting zeros. There was no check for running off the end of the string,
964        which could happen if a new error number was added without updating the
965        string.
966    
967    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
968    
969    11. \K was not working if it appeared in an atomic group or in a group that
970        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
971        \K is "not well defined" if used in an assertion. PCRE now accepts it if
972        the assertion is positive, but not if it is negative.
973    
974    12. Change 11 fortuitously reduced the size of the stack frame used in the
975        "match()" function of pcre_exec.c by one pointer. Forthcoming
976        implementation of support for (*MARK) will need an extra pointer on the
977        stack; I have reserved it now, so that the stack frame size does not
978        decrease.
979    
980    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
981        item in branch that calls a recursion is a subroutine call - as in the
982        second branch in the above example - was incorrectly given the compile-
983        time error "recursive call could loop indefinitely" because pcre_compile()
984        was not correctly checking the subroutine for matching a non-empty string.
985    
986    14. The checks for overrunning compiling workspace could trigger after an
987        overrun had occurred. This is a "should never occur" error, but it can be
988        triggered by pathological patterns such as hundreds of nested parentheses.
989        The checks now trigger 100 bytes before the end of the workspace.
990    
991    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
992    
993    
994    Version 8.01 19-Jan-2010
995    ------------------------
996    
997    1.  If a pattern contained a conditional subpattern with only one branch (in
998        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
999        computed the wrong minimum data length (which is of course zero for such
1000        subpatterns). This could cause incorrect "no match" results.
1001    
1002    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1003        the pattern is reset in the first branch, pcre_compile() failed with
1004        "internal error: code overflow at offset...". This happened only when
1005        the reset was to the original external option setting. (An optimization
1006        abstracts leading options settings into an external setting, which was the
1007        cause of this.)
1008    
1009    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1010        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1011        assertion pattern did not match (meaning that the assertion was true), it
1012        was incorrectly treated as false if the SKIP had been reached during the
1013        matching. This also applied to assertions used as conditions.
1014    
1015    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
1016        assertion subpattern, including such a pattern used as a condition,
1017        unpredictable results occurred, instead of the error return
1018        PCRE_ERROR_DFA_UITEM.
1019    
1020    5.  The C++ GlobalReplace function was not working like Perl for the special
1021        situation when an empty string is matched. It now does the fancy magic
1022        stuff that is necessary.
1023    
1024    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1025        removed. (These were left over from very, very early versions of PCRE.)
1026    
1027    7.  Some cosmetic changes to the code to make life easier when compiling it
1028        as part of something else:
1029    
1030        (a) Change DEBUG to PCRE_DEBUG.
1031    
1032        (b) In pcre_compile(), rename the member of the "branch_chain" structure
1033            called "current" as "current_branch", to prevent a collision with the
1034            Linux macro when compiled as a kernel module.
1035    
1036        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1037            prevent a collision with the Linux macro when compiled as a kernel
1038            module.
1039    
1040    8.  In pcre_compile() there are some checks for integer overflows that used to
1041        cast potentially large values to (double). This has been changed to that
1042        when building, a check for int64_t is made, and if it is found, it is used
1043        instead, thus avoiding the use of floating point arithmetic. (There is no
1044        other use of FP in PCRE.) If int64_t is not found, the fallback is to
1045        double.
1046    
1047    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
1048        2005 (difference between two addresses compared to an unsigned value).
1049    
1050    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1051        custom one, because of the following reported problem in Windows:
1052    
1053          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1054              under Win32.
1055          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1056              therefore missing the function definition.
1057          - The compiler thus generates a "C" signature for the test function.
1058          - The linker fails to find the "C" function.
1059          - PCRE fails to configure if asked to do so against libbz2.
1060    
1061    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1062        messages were output:
1063    
1064          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1065          rerunning libtoolize, to keep the correct libtool macros in-tree.
1066          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1067    
1068        I have done both of these things.
1069    
1070    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1071        most of the time, it *can* run out if it is given a pattern that contains a
1072        runaway infinite recursion. I updated the discussion in the pcrestack man
1073        page.
1074    
1075    13. Now that we have gone to the x.xx style of version numbers, the minor
1076        version may start with zero. Using 08 or 09 is a bad idea because users
1077        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1078        interpreted as invalid octal numbers. I've updated the previous comment in
1079        configure.ac, and also added a check that gives an error if 08 or 09 are
1080        used.
1081    
1082    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1083        causing partial matching to fail when the end of the subject matched \W
1084        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1085    
1086    15. There were some discrepancies between the declarations in pcre_internal.h
1087        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1088        their definitions. The declarations used "const uschar *" and the
1089        definitions used USPTR. Even though USPTR is normally defined as "const
1090        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1091        reported that: "This difference in casting confuses some C++ compilers, for
1092        example, SunCC recognizes above declarations as different functions and
1093        generates broken code for hbpcre." I have changed the declarations to use
1094        USPTR.
1095    
1096    16. GNU libtool is named differently on some systems. The autogen.sh script now
1097        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1098        (FreeBSD).
1099    
1100    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1101        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1102        comment: "Figure out how to create a longlong from a string: strtoll and
1103        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1104        instance, but it only takes 2 args instead of 3!"
1105    
1106    18. A subtle bug concerned with back references has been fixed by a change of
1107        specification, with a corresponding code fix. A pattern such as
1108        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1109        refers, was giving matches when it shouldn't. For example, xa=xaaa would
1110        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1111        same bug. Such groups have to be quantified to be useful, or contained
1112        inside another quantified group. (If there's no repetition, the reference
1113        can never match.) The problem arises because, having left the group and
1114        moved on to the rest of the pattern, a later failure that backtracks into
1115        the group uses the captured value from the final iteration of the group
1116        rather than the correct earlier one. I have fixed this in PCRE by forcing
1117        any group that contains a reference to itself to be an atomic group; that
1118        is, there cannot be any backtracking into it once it has completed. This is
1119        similar to recursive and subroutine calls.
1120    
1121    
1122    Version 8.00 19-Oct-09
1123    ----------------------
1124    
1125    1.  The table for translating pcre_compile() error codes into POSIX error codes
1126        was out-of-date, and there was no check on the pcre_compile() error code
1127        being within the table. This could lead to an OK return being given in
1128        error.
1129    
1130    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
1131        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1132        in a Windows environment.
1133    
1134    3.  The pcregrep --count option prints the count for each file even when it is
1135        zero, as does GNU grep. However, pcregrep was also printing all files when
1136        --files-with-matches was added. Now, when both options are given, it prints
1137        counts only for those files that have at least one match. (GNU grep just
1138        prints the file name in this circumstance, but including the count seems
1139        more useful - otherwise, why use --count?) Also ensured that the
1140        combination -clh just lists non-zero counts, with no names.
1141    
1142    4.  The long form of the pcregrep -F option was incorrectly implemented as
1143        --fixed_strings instead of --fixed-strings. This is an incompatible change,
1144        but it seems right to fix it, and I didn't think it was worth preserving
1145        the old behaviour.
1146    
1147    5.  The command line items --regex=pattern and --regexp=pattern were not
1148        recognized by pcregrep, which required --regex pattern or --regexp pattern
1149        (with a space rather than an '='). The man page documented the '=' forms,
1150        which are compatible with GNU grep; these now work.
1151    
1152    6.  No libpcreposix.pc file was created for pkg-config; there was just
1153        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1154    
1155    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1156        when UCP support is not needed, by modifying the Python script that
1157        generates it from Unicode data files. This should not matter if the module
1158        is correctly used as a library, but I received one complaint about 50K of
1159        unwanted data. My guess is that the person linked everything into his
1160        program rather than using a library. Anyway, it does no harm.
1161    
1162    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1163        was a minimum greater than 1 for a wide character in a possessive
1164        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1165        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1166        character. Chaos in the form of incorrect output or a compiling loop could
1167        result.
1168    
1169    9.  The restrictions on what a pattern can contain when partial matching is
1170        requested for pcre_exec() have been removed. All patterns can now be
1171        partially matched by this function. In addition, if there are at least two
1172        slots in the offset vector, the offset of the earliest inspected character
1173        for the match and the offset of the end of the subject are set in them when
1174        PCRE_ERROR_PARTIAL is returned.
1175    
1176    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1177        synonymous with PCRE_PARTIAL, for backwards compatibility, and
1178        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1179        and may be more useful for multi-segment matching.
1180    
1181    11. Partial matching with pcre_exec() is now more intuitive. A partial match
1182        used to be given if ever the end of the subject was reached; now it is
1183        given only if matching could not proceed because another character was
1184        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1185        string "Z", which now yields "no match" instead of "partial match". In the
1186        case of pcre_dfa_exec(), "no match" is given if every matching path for the
1187        final character ended with (*FAIL).
1188    
1189    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1190        if the pattern had a "must contain" character that was already found in the
1191        earlier partial match, unless partial matching was again requested. For
1192        example, with the pattern /dog.(body)?/, the "must contain" character is
1193        "g". If the first part-match was for the string "dog", restarting with
1194        "sbody" failed. This bug has been fixed.
1195    
1196    13. The string returned by pcre_dfa_exec() after a partial match has been
1197        changed so that it starts at the first inspected character rather than the
1198        first character of the match. This makes a difference only if the pattern
1199        starts with a lookbehind assertion or \b or \B (\K is not supported by
1200        pcre_dfa_exec()). It's an incompatible change, but it makes the two
1201        matching functions compatible, and I think it's the right thing to do.
1202    
1203    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1204        so that the demonstration program is easily available in environments where
1205        PCRE has not been installed from source.
1206    
1207    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1208        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1209        library.
1210    
1211    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1212        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1213        is not the first non-POSIX option to be added. Clearly some people find
1214        these options useful.
1215    
1216    17. If a caller to the POSIX matching function regexec() passes a non-zero
1217        value for nmatch with a NULL value for pmatch, the value of
1218        nmatch is forced to zero.
1219    
1220    18. RunGrepTest did not have a test for the availability of the -u option of
1221        the diff command, as RunTest does. It now checks in the same way as
1222        RunTest, and also checks for the -b option.
1223    
1224    19. If an odd number of negated classes containing just a single character
1225        interposed, within parentheses, between a forward reference to a named
1226        subpattern and the definition of the subpattern, compilation crashed with
1227        an internal error, complaining that it could not find the referenced
1228        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1229        [The bug was that it was starting one character too far in when skipping
1230        over the character class, thus treating the ] as data rather than
1231        terminating the class. This meant it could skip too much.]
1232    
1233    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1234        /g option in pcretest when the pattern contains \K, which makes it possible
1235        to have an empty string match not at the start, even when the pattern is
1236        anchored. Updated pcretest and pcredemo to use this option.
1237    
1238    21. If the maximum number of capturing subpatterns in a recursion was greater
1239        than the maximum at the outer level, the higher number was returned, but
1240        with unset values at the outer level. The correct (outer level) value is
1241        now given.
1242    
1243    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1244        PCRE did not set those parentheses (unlike Perl). I have now found a way to
1245        make it do so. The string so far is captured, making this feature
1246        compatible with Perl.
1247    
1248    23. The tests have been re-organized, adding tests 11 and 12, to make it
1249        possible to check the Perl 5.10 features against Perl 5.10.
1250    
1251    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1252        pattern matches a fixed length string. PCRE did not allow this; now it
1253        does. Neither allows recursion.
1254    
1255    25. I finally figured out how to implement a request to provide the minimum
1256        length of subject string that was needed in order to match a given pattern.
1257        (It was back references and recursion that I had previously got hung up
1258        on.) This code has now been added to pcre_study(); it finds a lower bound
1259        to the length of subject needed. It is not necessarily the greatest lower
1260        bound, but using it to avoid searching strings that are too short does give
1261        some useful speed-ups. The value is available to calling programs via
1262        pcre_fullinfo().
1263    
1264    26. While implementing 25, I discovered to my embarrassment that pcretest had
1265        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1266        study optimizations had never been tested with that matching function.
1267        Oops. What is worse, even when it was passed study data, there was a bug in
1268        pcre_dfa_exec() that meant it never actually used it. Double oops. There
1269        were also very few tests of studied patterns with pcre_dfa_exec().
1270    
1271    27. If (?| is used to create subpatterns with duplicate numbers, they are now
1272        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1273        on the other side of the coin, they are no longer allowed to have different
1274        names, because these cannot be distinguished in PCRE, and this has caused
1275        confusion. (This is a difference from Perl.)
1276    
1277    28. When duplicate subpattern names are present (necessarily with different
1278        numbers, as required by 27 above), and a test is made by name in a
1279        conditional pattern, either for a subpattern having been matched, or for
1280        recursion in such a pattern, all the associated numbered subpatterns are
1281        tested, and the overall condition is true if the condition is true for any
1282        one of them. This is the way Perl works, and is also more like the way
1283        testing by number works.
1284    
1285    
1286    Version 7.9 11-Apr-09
1287    ---------------------
1288    
1289    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
1290        (pcretest), all targets were linked against these libraries. This included
1291        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1292        libraries. This caused unwanted dependencies to be created. This problem
1293        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1294        pcretest is linked with readline.
1295    
1296    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
1297        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1298        moved outside it again, because FALSE and TRUE are already defined in AIX,
1299        but BOOL is not.
1300    
1301    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1302        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1303    
1304    4.  The pcregrep documentation said spaces were inserted as well as colons (or
1305        hyphens) following file names and line numbers when outputting matching
1306        lines. This is not true; no spaces are inserted. I have also clarified the
1307        wording for the --colour (or --color) option.
1308    
1309    5.  In pcregrep, when --colour was used with -o, the list of matching strings
1310        was not coloured; this is different to GNU grep, so I have changed it to be
1311        the same.
1312    
1313    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
1314        each matching line was coloured. Now it goes on to look for further matches
1315        of any of the test patterns, which is the same behaviour as GNU grep.
1316    
1317    7.  A pattern that could match an empty string could cause pcregrep to loop; it
1318        doesn't make sense to accept an empty string match in pcregrep, so I have
1319        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1320        seems to be how GNU grep behaves.
1321    
1322    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1323        start or after a newline", because the conditional assertion was not being
1324        correctly handled. The rule now is that both the assertion and what follows
1325        in the first alternative must satisfy the test.
1326    
1327    9.  If auto-callout was enabled in a pattern with a conditional group whose
1328        condition was an assertion, PCRE could crash during matching, both with
1329        pcre_exec() and pcre_dfa_exec().
1330    
1331    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1332        used for matching.
1333    
1334    11. Unicode property support in character classes was not working for
1335        characters (bytes) greater than 127 when not in UTF-8 mode.
1336    
1337    12. Added the -M command line option to pcretest.
1338    
1339    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1340    
1341    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1342    
1343    16. Added comments and documentation about mis-use of no_arg in the C++
1344        wrapper.
1345    
1346    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1347        from Martin Jerabek that uses macro names for all relevant character and
1348        string constants.
1349    
1350    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1351        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1352        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1353        these, but not everybody uses configure.
1354    
1355    19. A conditional group that had only one branch was not being correctly
1356        recognized as an item that could match an empty string. This meant that an
1357        enclosing group might also not be so recognized, causing infinite looping
1358        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1359        with the subject "ab", where knowledge that the repeated group can match
1360        nothing is needed in order to break the loop.
1361    
1362    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1363        exec(), but without supplying a callout function, matching went wrong.
1364    
1365    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1366        leak if the size of the offset vector was greater than 30. When the vector
1367        is smaller, the saved offsets during recursion go onto a local stack
1368        vector, but for larger vectors malloc() is used. It was failing to free
1369        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1370        error, in fact).
1371    
1372    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1373        heapframe that is used only when UTF-8 support is enabled. This caused no
1374        problem, but was untidy.
1375    
1376    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1377        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1378        included within another project.
1379    
1380    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1381        slightly modified by me:
1382    
1383          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1384              not building pcregrep.
1385    
1386          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1387              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1388    
1389    25. Forward references, both numeric and by name, in patterns that made use of
1390        duplicate group numbers, could behave incorrectly or give incorrect errors,
1391        because when scanning forward to find the reference group, PCRE was not
1392        taking into account the duplicate group numbers. A pattern such as
1393        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1394    
1395    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1396        the feature of a custom pointer more persuasive (as requested by a user).
1397    
1398    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1399        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1400        pre-defined.
1401    
1402    28. Added support for (*UTF8) at the start of a pattern.
1403    
1404    29. Arrange for flags added by the "release type" setting in CMake to be shown
1405        in the configuration summary.
1406    
1407    
1408    Version 7.8 05-Sep-08
1409    ---------------------
1410    
1411    1.  Replaced UCP searching code with optimized version as implemented for Ad
1412        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1413        stage table and inline lookup instead of a function, giving speed ups of 2
1414        to 5 times on some simple patterns that I tested. Permission was given to
1415        distribute the MultiStage2.py script that generates the tables (it's not in
1416        the tarball, but is in the Subversion repository).
1417    
1418    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1419        scripts.
1420    
1421    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1422        a group with a zero qualifier. The result of the study could be incorrect,
1423        or the function might crash, depending on the pattern.
1424    
1425    4.  Caseless matching was not working for non-ASCII characters in back
1426        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1427        It now works when Unicode Property Support is available.
1428    
1429    5.  In pcretest, an escape such as \x{de} in the data was always generating
1430        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1431        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1432        truncation.
1433    
1434    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1435    
1436    7.  Added two (int) casts to pcregrep when printing the difference of two
1437        pointers, in case they are 64-bit values.
1438    
1439    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
1440        test 2 if it fails.
1441    
1442    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1443        and a #define of that name to empty if it is not externally set. This is to
1444        allow users of MSVC to set it if necessary.
1445    
1446    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1447        the convenience functions in the pcre_get.c source file.
1448    
1449    11. An option change at the start of a pattern that had top-level alternatives
1450        could cause overwriting and/or a crash. This command provoked a crash in
1451        some environments:
1452    
1453          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1454    
1455        This potential security problem was recorded as CVE-2008-2371.
1456    
1457    12. For a pattern where the match had to start at the beginning or immediately
1458        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1459        pcre_dfa_exec() could read past the end of the passed subject if there was
1460        no match. To help with detecting such bugs (e.g. with valgrind), I modified
1461        pcretest so that it places the subject at the end of its malloc-ed buffer.
1462    
1463    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1464        exec() might read past the end of the data buffer in UTF-8 mode.
1465    
1466    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1467        the data contained the byte 0x85 as part of a UTF-8 character within its
1468        first line. This applied both to normal and DFA matching.
1469    
1470    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1471        /^[^d]*?$/8 failed to match "abc".
1472    
1473    16. Added a missing copyright notice to pcrecpp_internal.h.
1474    
1475    17. Make it more clear in the documentation that values returned from
1476        pcre_exec() in ovector are byte offsets, not character counts.
1477    
1478    18. Tidied a few places to stop certain compilers from issuing warnings.
1479    
1480    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1481        supplied by Stefan Weber. I made a further small update for 7.8 because
1482        there is a change of source arrangements: the pcre_searchfuncs.c module is
1483        replaced by pcre_ucd.c.
1484    
1485    
1486    Version 7.7 07-May-08
1487    ---------------------
1488    
1489    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
1490        a string to a long long, pretend we don't even have a long long." This is
1491        done by checking for the strtoq, strtoll, and _strtoi64 functions.
1492    
1493    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1494        pre-7.6 versions, which defined a global no_arg variable instead of putting
1495        it in the RE class. (See also #8 below.)
1496    
1497    3.  Remove a line of dead code, identified by coverity and reported by Nuno
1498        Lopes.
1499    
1500    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
1501    
1502        (1) The include/exclude patterns were being applied to the whole pathnames
1503            of files, instead of just to the final components.
1504    
1505        (2) If there was more than one level of directory, the subdirectories were
1506            skipped unless they satisfied the include/exclude conditions. This is
1507            inconsistent with GNU grep (and could even be seen as contrary to the
1508            pcregrep specification - which I improved to make it absolutely clear).
1509            The action now is always to scan all levels of directory, and just
1510            apply the include/exclude patterns to regular files.
1511    
1512    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1513        --exclude_dir in the tests to avoid scanning .svn directories.
1514    
1515    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
1516        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1517        doesn't support NULs in patterns.
1518    
1519    7.  Added some missing "const"s to declarations of static tables in
1520        pcre_compile.c and pcre_dfa_exec.c.
1521    
1522    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1523        caused by fix #2  above. (Subsequently also a second patch to fix the
1524        first patch. And a third patch - this was a messy problem.)
1525    
1526    9.  Applied Craig's patch to remove the use of push_back().
1527    
1528    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1529        matching function regexec().
1530    
1531    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1532        which, however, unlike Perl's \g{...}, are subroutine calls, not back
1533        references. PCRE supports relative numbers with this syntax (I don't think
1534        Oniguruma does).
1535    
1536    12. Previously, a group with a zero repeat such as (...){0} was completely
1537        omitted from the compiled regex. However, this means that if the group
1538        was called as a subroutine from elsewhere in the pattern, things went wrong
1539        (an internal error was given). Such groups are now left in the compiled
1540        pattern, with a new opcode that causes them to be skipped at execution
1541        time.
1542    
1543    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1544        to the way PCRE behaves:
1545    
1546        (a) A lone ] character is dis-allowed (Perl treats it as data).
1547    
1548        (b) A back reference to an unmatched subpattern matches an empty string
1549            (Perl fails the current match path).
1550    
1551        (c) A data ] in a character class must be notated as \] because if the
1552            first data character in a class is ], it defines an empty class. (In
1553            Perl it is not possible to have an empty class.) The empty class []
1554            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1555            The negative empty class [^] matches any one character, independently
1556            of the DOTALL setting.
1557    
1558    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1559        non-existent subpattern following a character class starting with ']' and
1560        containing () gave an internal compiling error instead of "reference to
1561        non-existent subpattern". Fortunately, when the pattern did exist, the
1562        compiled code was correct. (When scanning forwards to check for the
1563        existencd of the subpattern, it was treating the data ']' as terminating
1564        the class, so got the count wrong. When actually compiling, the reference
1565        was subsequently set up correctly.)
1566    
1567    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1568        it was being rejected as not supported by pcre_dfa_exec(), even though
1569        other assertions are supported. I have made pcre_dfa_exec() support
1570        (*FAIL).
1571    
1572    16. The implementation of 13c above involved the invention of a new opcode,
1573        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1574        cannot be changed at match time, I realized I could make a small
1575        improvement to matching performance by compiling OP_ALLANY instead of
1576        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1577        on the OP_ANY path.
1578    
1579    17. Compiling pcretest on Windows with readline support failed without the
1580        following two fixes: (1) Make the unistd.h include conditional on
1581        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1582    
1583    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1584        ncurses library to be included for pcretest when ReadLine support is
1585        requested, but also to allow for it to be overridden. This patch came from
1586        Daniel Bergström.
1587    
1588    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1589        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1590        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1591        spotting this.
1592    
1593    
1594    Version 7.6 28-Jan-08
1595    ---------------------
1596    
1597    1.  A character class containing a very large number of characters with
1598        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
1599        overflow.
1600    
1601    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
1602        HAVE_LONG_LONG is not defined.
1603    
1604    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
1605        bring them up to date and include new features. This patch includes:
1606    
1607        - Fixed PH's badly added libz and libbz2 support.
1608        - Fixed a problem with static linking.
1609        - Added pcredemo. [But later removed - see 7 below.]
1610        - Fixed dftables problem and added an option.
1611        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
1612            HAVE_LONG_LONG.
1613        - Added readline support for pcretest.
1614        - Added an listing of the option settings after cmake has run.
1615    
1616    4.  A user submitted a patch to Makefile that makes it easy to create
1617        "pcre.dll" under mingw when using Configure/Make. I added stuff to
1618        Makefile.am that cause it to include this special target, without
1619        affecting anything else. Note that the same mingw target plus all
1620        the other distribution libraries and programs are now supported
1621        when configuring with CMake (see 6 below) instead of with
1622        Configure/Make.
1623    
1624    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
1625        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
1626        exported in the Windows port". It has not yet been confirmed that the patch
1627        solves the problem, but it does no harm.
1628    
1629    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
1630        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
1631        with CMake, and also correct the comment about stack recursion.
1632    
1633    7.  Remove the automatic building of pcredemo from the ./configure system and
1634        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
1635        of a program that users should build themselves after PCRE is installed, so
1636        building it automatically is not really right. What is more, it gave
1637        trouble in some build environments.
1638    
1639    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
1640    
1641    
1642    Version 7.5 10-Jan-08
1643    ---------------------
1644    
1645    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
1646        values in parens when parsing an RE using the C++ wrapper."
1647    
1648    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
1649        Characters greater than 255 were excluded from the class instead of being
1650        included.
1651    
1652    3.  The same bug as (2) above applied to negated POSIX classes such as
1653        [:^space:].
1654    
1655    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
1656        defined or documented. It seems to have been a typo for PCRE_STATIC, so
1657        I have changed it.
1658    
1659    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
1660        first named subpattern) and a construct such as (?&a) would reference the
1661        first named subpattern whose name started with "a" (in other words, the
1662        length check was missing). Both these problems are fixed. "Subpattern name
1663        expected" is now given for (?&) (a zero-length name), and this patch also
1664        makes it give the same error for \k'' (previously it complained that that
1665        was a reference to a non-existent subpattern).
1666    
1667    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
1668        this is right because (?- can be followed by option settings as well as by
1669        digits. I have, however, made the messages clearer.
1670    
1671    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1672        than the number used in the conditional) now cause a compile-time error.
1673        This is actually not compatible with Perl, which accepts such patterns, but
1674        treats the conditional as always being FALSE (as PCRE used to), but it
1675        seems to me that giving a diagnostic is better.
1676    
1677    8.  Change "alphameric" to the more common word "alphanumeric" in comments
1678        and messages.
1679    
1680    9.  Fix two occurrences of "backslash" in comments that should have been
1681        "backspace".
1682    
1683    10. Remove two redundant lines of code that can never be obeyed (their function
1684        was moved elsewhere).
1685    
1686    11. The program that makes PCRE's Unicode character property table had a bug
1687        which caused it to generate incorrect table entries for sequences of
1688        characters that have the same character type, but are in different scripts.
1689        It amalgamated them into a single range, with the script of the first of
1690        them. In other words, some characters were in the wrong script. There were
1691        thirteen such cases, affecting characters in the following ranges:
1692    
1693          U+002b0 - U+002c1
1694          U+0060c - U+0060d
1695          U+0061e - U+00612
1696          U+0064b - U+0065e
1697          U+0074d - U+0076d
1698          U+01800 - U+01805
1699          U+01d00 - U+01d77
1700          U+01d9b - U+01dbf
1701          U+0200b - U+0200f
1702          U+030fc - U+030fe
1703          U+03260 - U+0327f
1704          U+0fb46 - U+0fbb1
1705          U+10450 - U+1049d
1706    
1707    12. The -o option (show only the matching part of a line) for pcregrep was not
1708        compatible with GNU grep in that, if there was more than one match in a
1709        line, it showed only the first of them. It now behaves in the same way as
1710        GNU grep.
1711    
1712    13. If the -o and -v options were combined for pcregrep, it printed a blank
1713        line for every non-matching line. GNU grep prints nothing, and pcregrep now
1714        does the same. The return code can be used to tell if there were any
1715        non-matching lines.
1716    
1717    14. Added --file-offsets and --line-offsets to pcregrep.
1718    
1719    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1720        infinitely looping recursion. The bug was that positive lookaheads were not
1721        being skipped when checking for a possible empty match (negative lookaheads
1722        and both kinds of lookbehind were skipped).
1723    
1724    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1725        inclusion of <windows.h> to before rather than after the definition of
1726        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1727    
1728    17. Specifying a possessive quantifier with a specific limit for a Unicode
1729        character property caused pcre_compile() to compile bad code, which led at
1730        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1731        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1732        caused the error; without that there was no problem.
1733    
1734    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1735    
1736    19. Added --enable-pcretest-libreadline.
1737    
1738    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1739        RE::GlobalReplace(). As a result, the number of replacements returned was
1740        double what it should be. I removed one of the increments, but Craig sent a
1741        later patch that removed the other one (the right fix) and added unit tests
1742        that check the return values (which was not done before).
1743    
1744    21. Several CMake things:
1745    
1746        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1747            the names libpcre and libpcreposix, not just pcre and pcreposix.
1748    
1749        (2) The above change means that pcretest and pcregrep are now correctly
1750            linked with the newly-built libraries, not previously installed ones.
1751    
1752        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
1753    
1754    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1755        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1756        UTF-8 newline character). The key issue is that the pattern starts .*;
1757        this means that the match must be either at the beginning, or after a
1758        newline. The bug was in the code for advancing after a failed match and
1759        checking that the new position followed a newline. It was not taking
1760        account of UTF-8 characters correctly.
1761    
1762    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1763        character classes. PCRE was not treating the sequence [:...:] as a
1764        character class unless the ... were all letters. Perl, however, seems to
1765        allow any characters between [: and :], though of course it rejects as
1766        unknown any "names" that contain non-letters, because all the known class
1767        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1768        for example, whereas PCRE did not - it did not recognize a POSIX character
1769        class. This seemed a bit dangerous, so the code has been changed to be
1770        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1771        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1772        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1773        Perl does, and where it didn't before.
1774    
1775    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1776        Windows environments %n is disabled by default.
1777    
1778    
1779    Version 7.4 21-Sep-07
1780    ---------------------
1781    
1782    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
1783        means that a class such as [\s] counted as "explicit reference to CR or
1784        LF". That isn't really right - the whole point of the change was to try to
1785        help when there was an actual mention of one of the two characters. So now
1786        the change happens only if \r or \n (or a literal CR or LF) character is
1787        encountered.
1788    
1789    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1790        of both had grown to the point where there were only 3 bits left.
1791        Fortunately, there was spare space in the data structure, and so I have
1792        moved the internal flags into a new 16-bit field to free up more option
1793        bits.
1794    
1795    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1796        but did not set the internal JCHANGED flag - either of these is enough to
1797        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1798        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1799        start sets both bits.
1800    
1801    4.  Added options (at build time, compile time, exec time) to change \R from
1802        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1803    
1804    5.  doc/pcresyntax.html was missing from the distribution.
1805    
1806    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1807        compatibility, even though it is no longer used.
1808    
1809    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1810        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1811        windows.h file is present (where different names are used). [This was
1812        reversed later after testing - see 16 below.]
1813    
1814    8.  Changed all #include <config.h> to #include "config.h". There were also
1815        some further <pcre.h> cases that I changed to "pcre.h".
1816    
1817    9.  When pcregrep was used with the --colour option, it missed the line ending
1818        sequence off the lines that it output.
1819    
1820    10. It was pointed out to me that arrays of string pointers cause lots of
1821        relocations when a shared library is dynamically loaded. A technique of
1822        using a single long string with a table of offsets can drastically reduce
1823        these. I have refactored PCRE in four places to do this. The result is
1824        dramatic:
1825    
1826          Originally:                          290
1827          After changing UCP table:            187
1828          After changing error message table:   43
1829          After changing table of "verbs"       36
1830          After changing table of Posix names   22
1831    
1832        Thanks to the folks working on Gregex for glib for this insight.
1833    
1834    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1835        unicode-properties was also set.
1836    
1837    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1838    
1839    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1840        checked only for CRLF.
1841    
1842    14. Added casts to pcretest.c to avoid compiler warnings.
1843    
1844    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1845    
1846    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1847        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1848        entirely. This removes changes made in 7 above.
1849    
1850    17. The CMake files have been updated, and there is now more information about
1851        building with CMake in the NON-UNIX-USE document.
1852    
1853    
1854    Version 7.3 28-Aug-07
1855    ---------------------
1856    
1857     1. In the rejigging of the build system that eventually resulted in 7.1, the
1858        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
1859        brackets there is not right, since it causes compilers to look for an
1860        installed pcre.h, not the version that is in the source that is being
1861        compiled (which of course may be different). I have changed it back to:
1862    
1863          #include "pcre.h"
1864    
1865        I have a vague recollection that the change was concerned with compiling in
1866        different directories, but in the new build system, that is taken care of
1867        by the VPATH setting the Makefile.
1868    
1869     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
1870        when the subject happened to end in the byte 0x85 (e.g. if the last
1871        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
1872        characters but of course it shouldn't be taken as a newline when it is part
1873        of another character. The bug was that, for an unlimited repeat of . in
1874        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
1875        characters when looking for a newline.
1876    
1877     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
1878    
1879     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1880        in debug output.
1881    
1882     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1883        long printing in the pcrecpp unittest when running under MinGW.
1884    
1885     6. ESC_K was left out of the EBCDIC table.
1886    
1887     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
1888        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
1889        limit also applies to "virtual nesting" when a pattern is recursive, and in
1890        this case 1000 isn't so big. I have been able to remove this limit at the
1891        expense of backing off one optimization in certain circumstances. Normally,
1892        when pcre_exec() would call its internal match() function recursively and
1893        immediately return the result unconditionally, it uses a "tail recursion"
1894        feature to save stack. However, when a subpattern that can match an empty
1895        string has an unlimited repetition quantifier, it no longer makes this
1896        optimization. That gives it a stack frame in which to save the data for
1897        checking that an empty string has been matched. Previously this was taken
1898        from the 1000-entry workspace that had been reserved. So now there is no
1899        explicit limit, but more stack is used.
1900    
1901     8. Applied Daniel's patches to solve problems with the import/export magic
1902        syntax that is required for Windows, and which was going wrong for the
1903        pcreposix and pcrecpp parts of the library. These were overlooked when this
1904        problem was solved for the main library.
1905    
1906     9. There were some crude static tests to avoid integer overflow when computing
1907        the size of patterns that contain repeated groups with explicit upper
1908        limits. As the maximum quantifier is 65535, the maximum group length was
1909        set at 30,000 so that the product of these two numbers did not overflow a
1910        32-bit integer. However, it turns out that people want to use groups that
1911        are longer than 30,000 bytes (though not repeat them that many times).
1912        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1913        made it possible to implement the integer overflow checks in a much more
1914        dynamic way, which I have now done. The artificial limitation on group
1915        length has been removed - we now have only the limit on the total length of
1916        the compiled pattern, which depends on the LINK_SIZE setting.
1917    
1918    10. Fixed a bug in the documentation for get/copy named substring when
1919        duplicate names are permitted. If none of the named substrings are set, the
1920        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1921        empty string.
1922    
1923    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1924        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1925        because the ] is interpreted as the first data character and the
1926        terminating ] is not found. PCRE has been made compatible with Perl in this
1927        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1928        cause memory overwriting.
1929    
1930    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1931        string has been matched (to stop an infinite loop). It was not recognizing
1932        a conditional subpattern that could match an empty string if that
1933        subpattern was within another subpattern. For example, it looped when
1934        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1935        condition was not nested. This bug has been fixed.
1936    
1937    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1938        past the start of the subject in the presence of bytes with the top bit
1939        set, for example "\x8aBCD".
1940    
1941    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1942        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1943    
1944    14. Optimized (?!) to (*FAIL).
1945    
1946    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1947        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1948        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1949        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1950        does: it's just the validity check that is more restrictive.
1951    
1952    16. Inserted checks for integer overflows during escape sequence (backslash)
1953        processing, and also fixed erroneous offset values for syntax errors during
1954        backslash processing.
1955    
1956    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1957        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1958    
1959    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1960        caused an overrun.
1961    
1962    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1963        something other than just ASCII characters) inside a group that had an
1964        unlimited repeat caused a loop at compile time (while checking to see
1965        whether the group could match an empty string).
1966    
1967    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1968        [\P{Any}] did so. (Error in the code for printing property names.)
1969    
1970    21. An orphan \E inside a character class could cause a crash.
1971    
1972    22. A repeated capturing bracket such as (A)? could cause a wild memory
1973        reference during compilation.
1974    
1975    23. There are several functions in pcre_compile() that scan along a compiled
1976        expression for various reasons (e.g. to see if it's fixed length for look
1977        behind). There were bugs in these functions when a repeated \p or \P was
1978        present in the pattern. These operators have additional parameters compared
1979        with \d, etc, and these were not being taken into account when moving along
1980        the compiled data. Specifically:
1981    
1982        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1983            length.
1984    
1985        (b) An item such as \pL+ within a repeated group could cause crashes or
1986            loops.
1987    
1988        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1989            "reference to non-existent subpattern" error.
1990    
1991        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1992    
1993    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1994        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1995    
1996    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1997    
1998    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1999        character were causing crashes (broken optimization).
2000    
2001    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
2002        \p or \P) caused a compile-time loop.
2003    
2004    28. More problems have arisen in unanchored patterns when CRLF is a valid line
2005        break. For example, the unstudied pattern [\r\n]A does not match the string
2006        "\r\nA" because change 7.0/46 below moves the current point on by two
2007        characters after failing to match at the start. However, the pattern \nA
2008        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
2009        the same is true. There doesn't seem any very clean way out of this, but
2010        what I have chosen to do makes the common cases work: PCRE now takes note
2011        of whether there can be an explicit match for \r or \n anywhere in the
2012        pattern, and if so, 7.0/46 no longer applies. As part of this change,
2013        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
2014        pattern has explicit CR or LF references.
2015    
2016    29. Added (*CR) etc for changing newline setting at start of pattern.
2017    
2018    
2019    Version 7.2 19-Jun-07
2020  ---------------------  ---------------------
2021    
2022   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 41  Version 7.2 05-June-07 Line 2056  Version 7.2 05-June-07
2056      (f) \g{name} is another synonym - part of Perl 5.10's unification of      (f) \g{name} is another synonym - part of Perl 5.10's unification of
2057          reference syntax.          reference syntax.
2058    
2059        (g) (?| introduces a group in which the numbering of parentheses in each
2060            alternative starts with the same number.
2061    
2062        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
2063    
2064   7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and   7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
2065      PCRE_INFO_JCHANGED.      PCRE_INFO_JCHANGED.
2066    
# Line 55  Version 7.2 05-June-07 Line 2075  Version 7.2 05-June-07
2075      alternatives. The 1000-alternative test pattern now uses 12 bytes of      alternatives. The 1000-alternative test pattern now uses 12 bytes of
2076      workspace instead of running out of the 4096 that are available.      workspace instead of running out of the 4096 that are available.
2077    
2078    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
2079    
2080    11. Applied patch from Google to remove an optimization that didn't quite work.
2081        The report of the bug said:
2082    
2083          pcrecpp::RE("a*").FullMatch("aaa") matches, while
2084          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
2085          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
2086    
2087    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
2088        it matched the wrong number of bytes.
2089    
2090    
2091  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07
2092  ---------------------  ---------------------

Legend:
Removed from v.172  
changed lines
  Added in v.974

  ViewVC Help
Powered by ViewVC 1.1.5