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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.205  
changed lines
  Added in v.881

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12