ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 342 by ph10, Sun Apr 20 17:10:13 2008 UTC revision 773 by ph10, Wed Nov 30 18:10:27 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.7 05-Mar-08  Version 8.21
5    ------------
7    1.  Updating the JIT compiler.
9    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
10        are added as well.
12    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
13        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
14        calling _pcre_jit_exec. Some extra comments are added.
16    4.  Mark settings inside atomic groups that do not contain any capturing
17        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
18        was introduced by change 18 for 8.20.
20    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
21        ECMA-262 standard.
23    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
24        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
25        This bug was probably introduced by change 9 of 8.13.
27    7.  While fixing 6 above, I noticed that a number of other items were being
28        incorrectly rejected as "not fixed length". This arose partly because newer
29        opcodes had not been added to the fixed-length checking code. I have (a)
30        corrected the bug and added tests for these items, and (b) arranged for an
31        error to occur if an unknown opcode is encountered while checking for fixed
32        length instead of just assuming "not fixed length". The items that were
33        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
34        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
35        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
37    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
38        being incorrectly compiled and would have given unpredicatble results.
40    9.  A possessively repeated subpattern with minimum repeat count greater than
41        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
42        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
43        the first (A) could occur when it should not.
45    10. Add a cast and remove a redundant test from the code.
47    11. JIT should use pcre_malloc/pcre_free for allocation.
49    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
50        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
51        is anything other than /usr, -L is still shown).
53    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
55    14. Perl does not support \N without a following name in a [] class; PCRE now
56        also gives an error.
58    15. If a forward reference was repeated with an upper limit of around 2000,
59        it caused the error "internal error: overran compiling workspace". The
60        maximum number of forward references (including repeats) was limited by the
61        internal workspace, and dependent on the LINK_SIZE. The code has been
62        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
63        the default depends on LINK_SIZE. There is a new upper limit (for safety)
64        of around 200,000 forward references. While doing this, I also speeded up
65        the filling in of repeated forward references.
67    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
68        incorrectly expecting the subject to contain another "a" after the start.
70    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
71        in the match, the SKIP should be ignored. This was not happening; instead
72        the SKIP was being treated as NOMATCH. For patterns such as
73        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
74        tested.
76    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
77        now much more compatible with Perl, in particular in cases where the result
78        is a non-match for a non-anchored pattern. For example, if
79        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
80        "m", where previously it did not return a name. A side effect of this
81        change is that for partial matches, the last encountered mark name is
82        returned, as for non matches. A number of tests that were previously not
83        Perl-compatible have been moved into the Perl-compatible test files. The
84        refactoring has had the pleasing side effect of removing one argument from
85        the match() function, thus reducing its stack requirements.
88    Version 8.20 21-Oct-2011
89    ------------------------
91    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
92        a POSIX class. After further experiments with Perl, which convinced me that
93        Perl has bugs and confusions, a closing square bracket is no longer allowed
94        in a POSIX name. This bug also affected patterns with classes that started
95        with full stops.
97    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
98        captured substring, but while checking the failing first alternative,
99        substring 1 is temporarily captured. If the output vector supplied to
100        pcre_exec() was not big enough for this capture, the yield of the function
101        was still zero ("insufficient space for captured substrings"). This cannot
102        be totally fixed without adding another stack variable, which seems a lot
103        of expense for a edge case. However, I have improved the situation in cases
104        such as /(a)(b)x|abc/ matched against "abc", where the return code
105        indicates that fewer than the maximum number of slots in the ovector have
106        been set.
108    3.  Related to (2) above: when there are more back references in a pattern than
109        slots in the output vector, pcre_exec() uses temporary memory during
110        matching, and copies in the captures as far as possible afterwards. It was
111        using the entire output vector, but this conflicts with the specification
112        that only 2/3 is used for passing back captured substrings. Now it uses
113        only the first 2/3, for compatibility. This is, of course, another edge
114        case.
116    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
117        main code base, and can be used by building with --enable-jit. When this is
118        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
119        runtime --no-jit option is given.
121    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
122        ovector, the return from the function was zero, implying that there were
123        other matches that did not fit. The correct "exactly full" value is now
124        returned.
126    6.  If a subpattern that was called recursively or as a subroutine contained
127        (*PRUNE) or any other control that caused it to give a non-standard return,
128        invalid errors such as "Error -26 (nested recursion at the same subject
129        position)" or even infinite loops could occur.
131    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
132        computing the minimum length on reaching *ACCEPT, and so ended up with the
133        wrong value of 1 rather than 0. Further investigation indicates that
134        computing a minimum subject length in the presence of *ACCEPT is difficult
135        (think back references, subroutine calls), and so I have changed the code
136        so that no minimum is registered for a pattern that contains *ACCEPT.
138    8.  If (*THEN) was present in the first (true) branch of a conditional group,
139        it was not handled as intended. [But see 16 below.]
141    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
142        Sheri Pierce.
144    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
145        the first byte in a match must be "a".
147    11. Change 17 for 8.13 increased the recursion depth for patterns like
148        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
149        pattern contains any instances of (*THEN). If it does not, the old
150        optimizations are restored. It would be nice to do this on a per-group
151        basis, but at the moment that is not feasible.
153    12. In some environments, the output of pcretest -C is CRLF terminated. This
154        broke RunTest's code that checks for the link size. A single white space
155        character after the value is now allowed for.
157    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
158        For "fr", it uses the Windows-specific input and output files.
160    14. If (*THEN) appeared in a group that was called recursively or as a
161        subroutine, it did not work as intended. [But see next item.]
163    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
164        pattern fragments (but not containing any | characters). If A and B are
165        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
166        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
167        D. In other words, Perl considers parentheses that do not contain any |
168        characters to be part of a surrounding alternative, whereas PCRE was
169        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
170        differently. PCRE now behaves in the same way as Perl, except in the case
171        of subroutine/recursion calls such as (?1) which have in any case always
172        been different (but PCRE had them first :-).
174    16. Related to 15 above: Perl does not treat the | in a conditional group as
175        creating alternatives. Such a group is treated in the same way as an
176        ordinary group without any | characters when processing (*THEN). PCRE has
177        been changed to match Perl's behaviour.
179    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
180        RunGrepTest script failed.
182    18. Change 22 for version 13 caused atomic groups to use more stack. This is
183        inevitable for groups that contain captures, but it can lead to a lot of
184        stack use in large patterns. The old behaviour has been restored for atomic
185        groups that do not contain any capturing parentheses.
187    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
188        suppress the check for a minimum subject length at run time. (If it was
189        given to pcre_exec() or pcre_dfa_exec() it did work.)
191    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
192        fail to work when decoding hex characters in data strings in EBCDIC
193        environments.
195    21. It appears that in at least one Mac OS environment, the isxdigit() function
196        is implemented as a macro that evaluates to its argument more than once,
197        contravening the C 90 Standard (I haven't checked a later standard). There
198        was an instance in pcretest which caused it to go wrong when processing
199        \x{...} escapes in subject strings. The has been rewritten to avoid using
200        things like p++ in the argument of isxdigit().
203    Version 8.13 16-Aug-2011
204    ------------------------
206    1.  The Unicode data tables have been updated to Unicode 6.0.0.
208    2.  Two minor typos in pcre_internal.h have been fixed.
210    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
211        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
212        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
214    4.  There were a number of related bugs in the code for matching backrefences
215        caselessly in UTF-8 mode when codes for the characters concerned were
216        different numbers of bytes. For example, U+023A and U+2C65 are an upper
217        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
218        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
219        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
220        2-byte code at the end of the subject (it thought there wasn't enough data
221        left).
223    5.  Comprehensive information about what went wrong is now returned by
224        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
225        as the output vector has at least 2 elements. The offset of the start of
226        the failing character and a reason code are placed in the vector.
228    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
229        now returned is for the first byte of the failing character, instead of the
230        last byte inspected. This is an incompatible change, but I hope it is small
231        enough not to be a problem. It makes the returned offset consistent with
232        pcre_exec() and pcre_dfa_exec().
234    7.  pcretest now gives a text phrase as well as the error number when
235        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
236        failure, the offset and reason code are output.
238    8.  When \R was used with a maximizing quantifier it failed to skip backwards
239        over a \r\n pair if the subsequent match failed. Instead, it just skipped
240        back over a single character (\n). This seems wrong (because it treated the
241        two characters as a single entity when going forwards), conflicts with the
242        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
243        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
244        has been changed.
246    9.  Some internal refactoring has changed the processing so that the handling
247        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
248        time (the PCRE_DOTALL option was changed this way some time ago: version
249        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
250        which was always a bit of a fudge. It also means that there is one less
251        argument for the match() function, which reduces its stack requirements
252        slightly. This change also fixes an incompatibility with Perl: the pattern
253        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
255    10. More internal refactoring has drastically reduced the number of recursive
256        calls to match() for possessively repeated groups such as (abc)++ when
257        using pcre_exec().
259    11. While implementing 10, a number of bugs in the handling of groups were
260        discovered and fixed:
262        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
263        (a|)*(?1) gave a compile-time internal error.
264        ((a|)+)+  did not notice that the outer group could match an empty string.
265        (^a|^)+   was not marked as anchored.
266        (.*a|.*)+ was not marked as matching at start or after a newline.
268    12. Yet more internal refactoring has removed another argument from the match()
269        function. Special calls to this function are now indicated by setting a
270        value in a variable in the "match data" data block.
272    13. Be more explicit in pcre_study() instead of relying on "default" for
273        opcodes that mean there is no starting character; this means that when new
274        ones are added and accidentally left out of pcre_study(), testing should
275        pick them up.
277    14. The -s option of pcretest has been documented for ages as being an old
278        synonym of -m (show memory usage). I have changed it to mean "force study
279        for every regex", that is, assume /S for every regex. This is similar to -i
280        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
281        using it. It makes it easier to run collections of tests with and without
282        study enabled, and thereby test pcre_study() more easily. All the standard
283        tests are now run with and without -s (but some patterns can be marked as
284        "never study" - see 20 below).
286    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
287        restoration of the capturing data to the outer values was not happening
288        correctly.
290    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
291        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
292        pattern had matched an empty string, and so incorrectly returned a no
293        match.
295    17. There was optimizing code for the last branch of non-capturing parentheses,
296        and also for the obeyed branch of a conditional subexpression, which used
297        tail recursion to cut down on stack usage. Unfortunately, now that there is
298        the possibility of (*THEN) occurring in these branches, tail recursion is
299        no longer possible because the return has to be checked for (*THEN). These
300        two optimizations have therefore been removed. [But see 8.20/11 above.]
302    18. If a pattern containing \R was studied, it was assumed that \R always
303        matched two bytes, thus causing the minimum subject length to be
304        incorrectly computed because \R can also match just one byte.
306    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
307        was incorrectly computed.
309    20. If /S is present twice on a test pattern in pcretest input, it now
310        *disables* studying, thereby overriding the use of -s on the command line
311        (see 14 above). This is necessary for one or two tests to keep the output
312        identical in both cases.
314    21. When (*ACCEPT) was used in an assertion that matched an empty string and
315        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
317    22. When an atomic group that contained a capturing parenthesis was
318        successfully matched, but the branch in which it appeared failed, the
319        capturing was not being forgotten if a higher numbered group was later
320        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
321        group 1 to "a", when in fact it should be unset. This applied to multi-
322        branched capturing and non-capturing groups, repeated or not, and also to
323        positive assertions (capturing in negative assertions does not happen
324        in PCRE) and also to nested atomic groups.
326    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
327        subject after a captured substring, to make it easier to tell which of a
328        number of identical substrings has been captured.
330    24. The way atomic groups are processed by pcre_exec() has been changed so that
331        if they are repeated, backtracking one repetition now resets captured
332        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
333        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
334        "aaa". Previously, it would have been "a". As part of this code
335        refactoring, the way recursive calls are handled has also been changed.
337    25. If an assertion condition captured any substrings, they were not passed
338        back unless some other capturing happened later. For example, if
339        (?(?=(a))a) was matched against "a", no capturing was returned.
341    26. When studying a pattern that contained subroutine calls or assertions,
342        the code for finding the minimum length of a possible match was handling
343        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
344        group 1 called group 2 while simultaneously a separate group 2 called group
345        1). A stack overflow occurred in this case. I have fixed this by limiting
346        the recursion depth to 10.
348    27. Updated RunTest.bat in the distribution to the version supplied by Tom
349        Fortmann. This supports explicit test numbers on the command line, and has
350        argument validation and error reporting.
352    28. An instance of \X with an unlimited repeat could fail if at any point the
353        first character it looked at was a mark character.
355    29. Some minor code refactoring concerning Unicode properties and scripts
356        should reduce the stack requirement of match() slightly.
358    30. Added the '=' option to pcretest to check the setting of unused capturing
359        slots at the end of the pattern, which are documented as being -1, but are
360        not included in the return count.
362    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
363        compiled something random. Now it gives a compile-time error (as does
364        Perl).
366    32. A *MARK encountered during the processing of a positive assertion is now
367        recorded and passed back (compatible with Perl).
369    33. If --only-matching or --colour was set on a pcregrep call whose pattern
370        had alternative anchored branches, the search for a second match in a line
371        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
372        matched the line "0102" twice. The same bug affected patterns that started
373        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
374        twice.
376    34. Previously, PCRE did not allow quantification of assertions. However, Perl
377        does, and because of capturing effects, quantifying parenthesized
378        assertions may at times be useful. Quantifiers are now allowed for
379        parenthesized assertions.
381    35. A minor code tidy in pcre_compile() when checking options for \R usage.
383    36. \g was being checked for fancy things in a character class, when it should
384        just be a literal "g".
386    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
387        appearance of a nested POSIX class supersedes an apparent external class.
388        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
389        unescaped square brackets may also appear as part of class names. For
390        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
391        more like Perl. (But see 8.20/1 above.)
393    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
394        was because it thought it was \N{name}, which is not supported).
396    39. Add minix to OS list not supporting the -S option in pcretest.
398    40. PCRE tries to detect cases of infinite recursion at compile time, but it
399        cannot analyze patterns in sufficient detail to catch mutual recursions
400        such as ((?1))((?2)). There is now a runtime test that gives an error if a
401        subgroup is called recursively as a subpattern for a second time at the
402        same position in the subject string. In previous releases this might have
403        been caught by the recursion limit, or it might have run out of stack.
405    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
406        happen only once. PCRE was, however incorrectly giving a compile time error
407        "recursive call could loop indefinitely" because it cannot analyze the
408        pattern in sufficient detail. The compile time test no longer happens when
409        PCRE is compiling a conditional subpattern, but actual runaway loops are
410        now caught at runtime (see 40 above).
412    42. It seems that Perl allows any characters other than a closing parenthesis
413        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
414        has been changed to be the same.
416    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
417        as not to get warnings when autogen.sh is called. Also changed
418        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
420    44. To help people who use pcregrep to scan files containing exceedingly long
421        lines, the following changes have been made:
423        (a) The default value of the buffer size parameter has been increased from
424            8K to 20K. (The actual buffer used is three times this size.)
426        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
427            PCRE is built.
429        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
430            to be set at run time.
432        (d) Numerical values in pcregrep options can be followed by K or M, for
433            example --buffer-size=50K.
435        (e) If a line being scanned overflows pcregrep's buffer, an error is now
436            given and the return code is set to 2.
438    45. Add a pointer to the latest mark to the callout data block.
440    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
441        partial match of an empty string instead of no match. This was specific to
442        the use of ".".
444    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
445        complete match instead of a partial match. This bug was dependent on both
446        the PCRE_UTF8 and PCRE_DOTALL options being set.
448    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
449        starting byte set, because \b was not being ignored.
452    Version 8.12 15-Jan-2011
453    ------------------------
455    1.  Fixed some typos in the markup of the man pages, and wrote a script that
456        checks for such things as part of the documentation building process.
458    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
459        --match-limit and --recursion-limit options (added for 8.11). In
460        particular, this made one of the standard tests fail. (The integer value
461        went into the wrong half of a long int.)
463    3.  If the --colour option was given to pcregrep with -v (invert match), it
464        did strange things, either producing crazy output, or crashing. It should,
465        of course, ignore a request for colour when reporting lines that do not
466        match.
468    4.  Another pcregrep bug caused similar problems if --colour was specified with
469        -M (multiline) and the pattern match finished with a line ending.
471    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
472        matched in multiline mode, the following line was shown as part of the
473        match. This seems wrong, so I have changed it.
475    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
476        the check for further matches in the same line (so they could be coloured)
477        to overrun the end of the current line. If another match was found, it was
478        incorrectly shown (and then shown again when found in the next line).
480    7.  If pcregrep was compiled under Windows, there was a reference to the
481        function pcregrep_exit() before it was defined. I am assuming this was
482        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
483        reported by a user. I've moved the definition above the reference.
486    Version 8.11 10-Dec-2010
487    ------------------------
489    1.  (*THEN) was not working properly if there were untried alternatives prior
490        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
491        backtracked to try for "b" instead of moving to the next alternative branch
492        at the same level (in this case, to look for "c"). The Perl documentation
493        is clear that when (*THEN) is backtracked onto, it goes to the "next
494        alternative in the innermost enclosing group".
496    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
497        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
498        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
499        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
500        (*THEN).
502    3.  If \s appeared in a character class, it removed the VT character from
503        the class, even if it had been included by some previous item, for example
504        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
505        of \s, but is part of the POSIX "space" class.)
507    4.  A partial match never returns an empty string (because you can always
508        match an empty string at the end of the subject); however the checking for
509        an empty string was starting at the "start of match" point. This has been
510        changed to the "earliest inspected character" point, because the returned
511        data for a partial match starts at this character. This means that, for
512        example, /(?<=abc)def/ gives a partial match for the subject "abc"
513        (previously it gave "no match").
515    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
516        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
517        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
518        has an implication that the given string is incomplete (because a partial
519        match is preferred over a full match). For this reason, these items now
520        give a partial match in this situation. [Aside: previously, the one case
521        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
522        match rather than a full match, which was wrong by the old rules, but is
523        now correct.]
525    6.  There was a bug in the handling of #-introduced comments, recognized when
526        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
527        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
528        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
529        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
530        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
531        places in pcre_compile().
533    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
534        comments when looking ahead for named forward references to subpatterns,
535        the only newline sequence it recognized was NL. It now handles newlines
536        according to the set newline convention.
538    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
539        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
540        cater for a lack of strerror(). These oversights have been fixed.
542    9.  Added --match-limit and --recursion-limit to pcregrep.
544    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
546    11. When the -o option was used, pcregrep was setting a return code of 1, even
547        when matches were found, and --line-buffered was not being honoured.
549    12. Added an optional parentheses number to the -o and --only-matching options
550        of pcregrep.
552    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
553        can match an empty string. The code to do it in pcretest and pcredemo
554        needed fixing:
556        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
557            only one byte after an empty string match just before CRLF (this case
558            just got forgotten; "any" and "anycrlf" were OK).
560        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
561            mode when an empty string match preceded an ASCII character followed by
562            a non-ASCII character. (The code for advancing by one character rather
563            than one byte was nonsense.)
565        (c) The pcredemo.c sample program did not have any code at all to handle
566            the cases when CRLF is a valid newline sequence.
568    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
569        as a starting offset was within the subject string. There is now a new
570        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
571        negative or greater than the length of the string. In order to test this,
572        pcretest is extended to allow the setting of negative starting offsets.
574    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
575        starting offset points to the beginning of a UTF-8 character was
576        unnecessarily clumsy. I tidied it up.
578    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
579        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
581    17. Nobody had reported that the --include_dir option, which was added in
582        release 7.7 should have been called --include-dir (hyphen, not underscore)
583        for compatibility with GNU grep. I have changed it to --include-dir, but
584        left --include_dir as an undocumented synonym, and the same for
585        --exclude-dir, though that is not available in GNU grep, at least as of
586        release 2.5.4.
588    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
589        characters from a string of bytes) have been redefined so as not to use
590        loops, in order to improve performance in some environments. At the same
591        time, I abstracted some of the common code into auxiliary macros to save
592        repetition (this should not affect the compiled code).
594    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
595        compile-time error is now given if \c is not followed by an ASCII
596        character, that is, a byte less than 128. (In EBCDIC mode, the code is
597        different, and any byte value is allowed.)
599    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
600        START_OPTIMIZE option, which is now allowed at compile time - but just
601        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
602        to pcregrep and other applications that have no direct access to PCRE
603        options. The new /Y option in pcretest sets this option when calling
604        pcre_compile().
606    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
607        back references. Groups containing recursive back references were forced to
608        be atomic by that change, but in the case of named groups, the amount of
609        memory required was incorrectly computed, leading to "Failed: internal
610        error: code overflow". This has been fixed.
612    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
613        pcretest.c, to avoid build problems in some Borland environments.
616    Version 8.10 25-Jun-2010
617    ------------------------
619    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
620        THEN.
622    2.  (*ACCEPT) was not working when inside an atomic group.
624    3.  Inside a character class, \B is treated as a literal by default, but
625        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
626        causes the error). The code is unchanged, but I tidied the documentation.
628    4.  Inside a character class, PCRE always treated \R and \X as literals,
629        whereas Perl faults them if its -w option is set. I have changed PCRE so
630        that it faults them when PCRE_EXTRA is set.
632    5.  Added support for \N, which always matches any character other than
633        newline. (It is the same as "." when PCRE_DOTALL is not set.)
635    6.  When compiling pcregrep with newer versions of gcc which may have
636        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
637        declared with attribute warn_unused_result" were given. Just casting the
638        result to (void) does not stop the warnings; a more elaborate fudge is
639        needed. I've used a macro to implement this.
641    7.  Minor change to pcretest.c to avoid a compiler warning.
643    8.  Added four artifical Unicode properties to help with an option to make
644        \s etc use properties (see next item). The new properties are: Xan
645        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
647    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
648        use Unicode properties. (*UCP) at the start of a pattern can be used to set
649        this option. Modified pcretest to add /W to test this facility. Added
650        REG_UCP to make it available via the POSIX interface.
652    10. Added --line-buffered to pcregrep.
654    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
655        studied, and the match started with a letter with a code point greater than
656        127 whose first byte was different to the first byte of the other case of
657        the letter, the other case of this starting letter was not recognized
658        (#976).
660    12. If a pattern that was studied started with a repeated Unicode property
661        test, for example, \p{Nd}+, there was the theoretical possibility of
662        setting up an incorrect bitmap of starting bytes, but fortunately it could
663        not have actually happened in practice until change 8 above was made (it
664        added property types that matched character-matching opcodes).
666    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
667        possible starting bytes for non-anchored patterns.
669    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
670        \R, and also a number of cases that involve Unicode properties, both
671        explicit and implicit when PCRE_UCP is set.
673    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
674        input, it could crash or give wrong results if characters with values
675        greater than 0xc0 were present in the subject string. (Detail: it assumed
676        UTF-8 input when processing these items.)
678    16. Added a lot of (int) casts to avoid compiler warnings in systems where
679        size_t is 64-bit (#991).
681    17. Added a check for running out of memory when PCRE is compiled with
682        --disable-stack-for-recursion (#990).
684    18. If the last data line in a file for pcretest does not have a newline on
685        the end, a newline was missing in the output.
687    19. The default pcre_chartables.c file recognizes only ASCII characters (values
688        less than 128) in its various bitmaps. However, there is a facility for
689        generating tables according to the current locale when PCRE is compiled. It
690        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
691        characters, are recognized by isspace() and therefore were getting set in
692        these tables, and indeed these tables seem to approximate to ISO 8859. This
693        caused a problem in UTF-8 mode when pcre_study() was used to create a list
694        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
695        which of course cannot start UTF-8 characters. I have changed the code so
696        that only real ASCII characters (less than 128) and the correct starting
697        bytes for UTF-8 encodings are set for characters greater than 127 when in
698        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
699        altogether.)
701    20. Added the /T option to pcretest so as to be able to run tests with non-
702        standard character tables, thus making it possible to include the tests
703        used for 19 above in the standard set of tests.
705    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
706        reference to a subpattern the other side of a comment that contains an
707        opening parenthesis caused either an internal compiling error, or a
708        reference to the wrong subpattern.
711    Version 8.02 19-Mar-2010
712    ------------------------
714    1.  The Unicode data tables have been updated to Unicode 5.2.0.
716    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
717        configured.
719    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
720        original author of that file, following a query about its status.
722    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
723        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
725    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
726        quantifier applied to a forward-referencing subroutine call, could compile
727        incorrect code or give the error "internal error: previously-checked
728        referenced subpattern not found".
730    6.  Both MS Visual Studio and Symbian OS have problems with initializing
731        variables to point to external functions. For these systems, therefore,
732        pcre_malloc etc. are now initialized to local functions that call the
733        relevant global functions.
735    7.  There were two entries missing in the vectors called coptable and poptable
736        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
737        I've fixed the data, and added a kludgy way of testing at compile time that
738        the lengths are correct (equal to the number of opcodes).
740    8.  Following on from 7, I added a similar kludge to check the length of the
741        eint vector in pcreposix.c.
743    9.  Error texts for pcre_compile() are held as one long string to avoid too
744        much relocation at load time. To find a text, the string is searched,
745        counting zeros. There was no check for running off the end of the string,
746        which could happen if a new error number was added without updating the
747        string.
749    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
751    11. \K was not working if it appeared in an atomic group or in a group that
752        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
753        \K is "not well defined" if used in an assertion. PCRE now accepts it if
754        the assertion is positive, but not if it is negative.
756    12. Change 11 fortuitously reduced the size of the stack frame used in the
757        "match()" function of pcre_exec.c by one pointer. Forthcoming
758        implementation of support for (*MARK) will need an extra pointer on the
759        stack; I have reserved it now, so that the stack frame size does not
760        decrease.
762    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
763        item in branch that calls a recursion is a subroutine call - as in the
764        second branch in the above example - was incorrectly given the compile-
765        time error "recursive call could loop indefinitely" because pcre_compile()
766        was not correctly checking the subroutine for matching a non-empty string.
768    14. The checks for overrunning compiling workspace could trigger after an
769        overrun had occurred. This is a "should never occur" error, but it can be
770        triggered by pathological patterns such as hundreds of nested parentheses.
771        The checks now trigger 100 bytes before the end of the workspace.
773    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
776    Version 8.01 19-Jan-2010
777    ------------------------
779    1.  If a pattern contained a conditional subpattern with only one branch (in
780        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
781        computed the wrong minimum data length (which is of course zero for such
782        subpatterns). This could cause incorrect "no match" results.
784    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
785        the pattern is reset in the first branch, pcre_compile() failed with
786        "internal error: code overflow at offset...". This happened only when
787        the reset was to the original external option setting. (An optimization
788        abstracts leading options settings into an external setting, which was the
789        cause of this.)
791    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
792        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
793        assertion pattern did not match (meaning that the assertion was true), it
794        was incorrectly treated as false if the SKIP had been reached during the
795        matching. This also applied to assertions used as conditions.
797    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
798        assertion subpattern, including such a pattern used as a condition,
799        unpredictable results occurred, instead of the error return
802    5.  The C++ GlobalReplace function was not working like Perl for the special
803        situation when an empty string is matched. It now does the fancy magic
804        stuff that is necessary.
806    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
807        removed. (These were left over from very, very early versions of PCRE.)
809    7.  Some cosmetic changes to the code to make life easier when compiling it
810        as part of something else:
812        (a) Change DEBUG to PCRE_DEBUG.
814        (b) In pcre_compile(), rename the member of the "branch_chain" structure
815            called "current" as "current_branch", to prevent a collision with the
816            Linux macro when compiled as a kernel module.
818        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
819            prevent a collision with the Linux macro when compiled as a kernel
820            module.
822    8.  In pcre_compile() there are some checks for integer overflows that used to
823        cast potentially large values to (double). This has been changed to that
824        when building, a check for int64_t is made, and if it is found, it is used
825        instead, thus avoiding the use of floating point arithmetic. (There is no
826        other use of FP in PCRE.) If int64_t is not found, the fallback is to
827        double.
829    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
830        2005 (difference between two addresses compared to an unsigned value).
832    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
833        custom one, because of the following reported problem in Windows:
835          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
836              under Win32.
837          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
838              therefore missing the function definition.
839          - The compiler thus generates a "C" signature for the test function.
840          - The linker fails to find the "C" function.
841          - PCRE fails to configure if asked to do so against libbz2.
843    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
844        messages were output:
846          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
847          rerunning libtoolize, to keep the correct libtool macros in-tree.
848          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
850        I have done both of these things.
852    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
853        most of the time, it *can* run out if it is given a pattern that contains a
854        runaway infinite recursion. I updated the discussion in the pcrestack man
855        page.
857    13. Now that we have gone to the x.xx style of version numbers, the minor
858        version may start with zero. Using 08 or 09 is a bad idea because users
859        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
860        interpreted as invalid octal numbers. I've updated the previous comment in
861        configure.ac, and also added a check that gives an error if 08 or 09 are
862        used.
864    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
865        causing partial matching to fail when the end of the subject matched \W
866        in a UTF-8 pattern where \W was quantified with a minimum of 3.
868    15. There were some discrepancies between the declarations in pcre_internal.h
869        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
870        their definitions. The declarations used "const uschar *" and the
871        definitions used USPTR. Even though USPTR is normally defined as "const
872        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
873        reported that: "This difference in casting confuses some C++ compilers, for
874        example, SunCC recognizes above declarations as different functions and
875        generates broken code for hbpcre." I have changed the declarations to use
876        USPTR.
878    16. GNU libtool is named differently on some systems. The autogen.sh script now
879        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
880        (FreeBSD).
882    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
883        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
884        comment: "Figure out how to create a longlong from a string: strtoll and
885        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
886        instance, but it only takes 2 args instead of 3!"
888    18. A subtle bug concerned with back references has been fixed by a change of
889        specification, with a corresponding code fix. A pattern such as
890        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
891        refers, was giving matches when it shouldn't. For example, xa=xaaa would
892        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
893        same bug. Such groups have to be quantified to be useful, or contained
894        inside another quantified group. (If there's no repetition, the reference
895        can never match.) The problem arises because, having left the group and
896        moved on to the rest of the pattern, a later failure that backtracks into
897        the group uses the captured value from the final iteration of the group
898        rather than the correct earlier one. I have fixed this in PCRE by forcing
899        any group that contains a reference to itself to be an atomic group; that
900        is, there cannot be any backtracking into it once it has completed. This is
901        similar to recursive and subroutine calls.
904    Version 8.00 19-Oct-09
905    ----------------------
907    1.  The table for translating pcre_compile() error codes into POSIX error codes
908        was out-of-date, and there was no check on the pcre_compile() error code
909        being within the table. This could lead to an OK return being given in
910        error.
912    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
913        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
914        in a Windows environment.
916    3.  The pcregrep --count option prints the count for each file even when it is
917        zero, as does GNU grep. However, pcregrep was also printing all files when
918        --files-with-matches was added. Now, when both options are given, it prints
919        counts only for those files that have at least one match. (GNU grep just
920        prints the file name in this circumstance, but including the count seems
921        more useful - otherwise, why use --count?) Also ensured that the
922        combination -clh just lists non-zero counts, with no names.
924    4.  The long form of the pcregrep -F option was incorrectly implemented as
925        --fixed_strings instead of --fixed-strings. This is an incompatible change,
926        but it seems right to fix it, and I didn't think it was worth preserving
927        the old behaviour.
929    5.  The command line items --regex=pattern and --regexp=pattern were not
930        recognized by pcregrep, which required --regex pattern or --regexp pattern
931        (with a space rather than an '='). The man page documented the '=' forms,
932        which are compatible with GNU grep; these now work.
934    6.  No libpcreposix.pc file was created for pkg-config; there was just
935        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
937    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
938        when UCP support is not needed, by modifying the Python script that
939        generates it from Unicode data files. This should not matter if the module
940        is correctly used as a library, but I received one complaint about 50K of
941        unwanted data. My guess is that the person linked everything into his
942        program rather than using a library. Anyway, it does no harm.
944    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
945        was a minimum greater than 1 for a wide character in a possessive
946        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
947        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
948        character. Chaos in the form of incorrect output or a compiling loop could
949        result.
951    9.  The restrictions on what a pattern can contain when partial matching is
952        requested for pcre_exec() have been removed. All patterns can now be
953        partially matched by this function. In addition, if there are at least two
954        slots in the offset vector, the offset of the earliest inspected character
955        for the match and the offset of the end of the subject are set in them when
956        PCRE_ERROR_PARTIAL is returned.
958    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
959        synonymous with PCRE_PARTIAL, for backwards compatibility, and
960        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
961        and may be more useful for multi-segment matching.
963    11. Partial matching with pcre_exec() is now more intuitive. A partial match
964        used to be given if ever the end of the subject was reached; now it is
965        given only if matching could not proceed because another character was
966        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
967        string "Z", which now yields "no match" instead of "partial match". In the
968        case of pcre_dfa_exec(), "no match" is given if every matching path for the
969        final character ended with (*FAIL).
971    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
972        if the pattern had a "must contain" character that was already found in the
973        earlier partial match, unless partial matching was again requested. For
974        example, with the pattern /dog.(body)?/, the "must contain" character is
975        "g". If the first part-match was for the string "dog", restarting with
976        "sbody" failed. This bug has been fixed.
978    13. The string returned by pcre_dfa_exec() after a partial match has been
979        changed so that it starts at the first inspected character rather than the
980        first character of the match. This makes a difference only if the pattern
981        starts with a lookbehind assertion or \b or \B (\K is not supported by
982        pcre_dfa_exec()). It's an incompatible change, but it makes the two
983        matching functions compatible, and I think it's the right thing to do.
985    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
986        so that the demonstration program is easily available in environments where
987        PCRE has not been installed from source.
989    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
990        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
991        library.
993    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
994        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
995        is not the first non-POSIX option to be added. Clearly some people find
996        these options useful.
998    17. If a caller to the POSIX matching function regexec() passes a non-zero
999        value for nmatch with a NULL value for pmatch, the value of
1000        nmatch is forced to zero.
1002    18. RunGrepTest did not have a test for the availability of the -u option of
1003        the diff command, as RunTest does. It now checks in the same way as
1004        RunTest, and also checks for the -b option.
1006    19. If an odd number of negated classes containing just a single character
1007        interposed, within parentheses, between a forward reference to a named
1008        subpattern and the definition of the subpattern, compilation crashed with
1009        an internal error, complaining that it could not find the referenced
1010        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1011        [The bug was that it was starting one character too far in when skipping
1012        over the character class, thus treating the ] as data rather than
1013        terminating the class. This meant it could skip too much.]
1015    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1016        /g option in pcretest when the pattern contains \K, which makes it possible
1017        to have an empty string match not at the start, even when the pattern is
1018        anchored. Updated pcretest and pcredemo to use this option.
1020    21. If the maximum number of capturing subpatterns in a recursion was greater
1021        than the maximum at the outer level, the higher number was returned, but
1022        with unset values at the outer level. The correct (outer level) value is
1023        now given.
1025    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1026        PCRE did not set those parentheses (unlike Perl). I have now found a way to
1027        make it do so. The string so far is captured, making this feature
1028        compatible with Perl.
1030    23. The tests have been re-organized, adding tests 11 and 12, to make it
1031        possible to check the Perl 5.10 features against Perl 5.10.
1033    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1034        pattern matches a fixed length string. PCRE did not allow this; now it
1035        does. Neither allows recursion.
1037    25. I finally figured out how to implement a request to provide the minimum
1038        length of subject string that was needed in order to match a given pattern.
1039        (It was back references and recursion that I had previously got hung up
1040        on.) This code has now been added to pcre_study(); it finds a lower bound
1041        to the length of subject needed. It is not necessarily the greatest lower
1042        bound, but using it to avoid searching strings that are too short does give
1043        some useful speed-ups. The value is available to calling programs via
1044        pcre_fullinfo().
1046    26. While implementing 25, I discovered to my embarrassment that pcretest had
1047        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1048        study optimizations had never been tested with that matching function.
1049        Oops. What is worse, even when it was passed study data, there was a bug in
1050        pcre_dfa_exec() that meant it never actually used it. Double oops. There
1051        were also very few tests of studied patterns with pcre_dfa_exec().
1053    27. If (?| is used to create subpatterns with duplicate numbers, they are now
1054        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1055        on the other side of the coin, they are no longer allowed to have different
1056        names, because these cannot be distinguished in PCRE, and this has caused
1057        confusion. (This is a difference from Perl.)
1059    28. When duplicate subpattern names are present (necessarily with different
1060        numbers, as required by 27 above), and a test is made by name in a
1061        conditional pattern, either for a subpattern having been matched, or for
1062        recursion in such a pattern, all the associated numbered subpatterns are
1063        tested, and the overall condition is true if the condition is true for any
1064        one of them. This is the way Perl works, and is also more like the way
1065        testing by number works.
1068    Version 7.9 11-Apr-09
1069    ---------------------
1071    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
1072        (pcretest), all targets were linked against these libraries. This included
1073        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1074        libraries. This caused unwanted dependencies to be created. This problem
1075        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1076        pcretest is linked with readline.
1078    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
1079        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1080        moved outside it again, because FALSE and TRUE are already defined in AIX,
1081        but BOOL is not.
1083    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1084        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1086    4.  The pcregrep documentation said spaces were inserted as well as colons (or
1087        hyphens) following file names and line numbers when outputting matching
1088        lines. This is not true; no spaces are inserted. I have also clarified the
1089        wording for the --colour (or --color) option.
1091    5.  In pcregrep, when --colour was used with -o, the list of matching strings
1092        was not coloured; this is different to GNU grep, so I have changed it to be
1093        the same.
1095    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
1096        each matching line was coloured. Now it goes on to look for further matches
1097        of any of the test patterns, which is the same behaviour as GNU grep.
1099    7.  A pattern that could match an empty string could cause pcregrep to loop; it
1100        doesn't make sense to accept an empty string match in pcregrep, so I have
1101        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1102        seems to be how GNU grep behaves.
1104    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1105        start or after a newline", because the conditional assertion was not being
1106        correctly handled. The rule now is that both the assertion and what follows
1107        in the first alternative must satisfy the test.
1109    9.  If auto-callout was enabled in a pattern with a conditional group whose
1110        condition was an assertion, PCRE could crash during matching, both with
1111        pcre_exec() and pcre_dfa_exec().
1113    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1114        used for matching.
1116    11. Unicode property support in character classes was not working for
1117        characters (bytes) greater than 127 when not in UTF-8 mode.
1119    12. Added the -M command line option to pcretest.
1121    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1123    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1125    16. Added comments and documentation about mis-use of no_arg in the C++
1126        wrapper.
1128    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1129        from Martin Jerabek that uses macro names for all relevant character and
1130        string constants.
1132    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1133        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1134        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1135        these, but not everybody uses configure.
1137    19. A conditional group that had only one branch was not being correctly
1138        recognized as an item that could match an empty string. This meant that an
1139        enclosing group might also not be so recognized, causing infinite looping
1140        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1141        with the subject "ab", where knowledge that the repeated group can match
1142        nothing is needed in order to break the loop.
1144    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1145        exec(), but without supplying a callout function, matching went wrong.
1147    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1148        leak if the size of the offset vector was greater than 30. When the vector
1149        is smaller, the saved offsets during recursion go onto a local stack
1150        vector, but for larger vectors malloc() is used. It was failing to free
1151        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1152        error, in fact).
1154    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1155        heapframe that is used only when UTF-8 support is enabled. This caused no
1156        problem, but was untidy.
1158    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1159        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1160        included within another project.
1162    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1163        slightly modified by me:
1165          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1166              not building pcregrep.
1168          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1169              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1171    25. Forward references, both numeric and by name, in patterns that made use of
1172        duplicate group numbers, could behave incorrectly or give incorrect errors,
1173        because when scanning forward to find the reference group, PCRE was not
1174        taking into account the duplicate group numbers. A pattern such as
1175        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1177    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1178        the feature of a custom pointer more persuasive (as requested by a user).
1180    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1181        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1182        pre-defined.
1184    28. Added support for (*UTF8) at the start of a pattern.
1186    29. Arrange for flags added by the "release type" setting in CMake to be shown
1187        in the configuration summary.
1190    Version 7.8 05-Sep-08
1191    ---------------------
1193    1.  Replaced UCP searching code with optimized version as implemented for Ad
1194        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1195        stage table and inline lookup instead of a function, giving speed ups of 2
1196        to 5 times on some simple patterns that I tested. Permission was given to
1197        distribute the MultiStage2.py script that generates the tables (it's not in
1198        the tarball, but is in the Subversion repository).
1200    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1201        scripts.
1203    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1204        a group with a zero qualifier. The result of the study could be incorrect,
1205        or the function might crash, depending on the pattern.
1207    4.  Caseless matching was not working for non-ASCII characters in back
1208        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1209        It now works when Unicode Property Support is available.
1211    5.  In pcretest, an escape such as \x{de} in the data was always generating
1212        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1213        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1214        truncation.
1216    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1218    7.  Added two (int) casts to pcregrep when printing the difference of two
1219        pointers, in case they are 64-bit values.
1221    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
1222        test 2 if it fails.
1224    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1225        and a #define of that name to empty if it is not externally set. This is to
1226        allow users of MSVC to set it if necessary.
1228    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1229        the convenience functions in the pcre_get.c source file.
1231    11. An option change at the start of a pattern that had top-level alternatives
1232        could cause overwriting and/or a crash. This command provoked a crash in
1233        some environments:
1235          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1237        This potential security problem was recorded as CVE-2008-2371.
1239    12. For a pattern where the match had to start at the beginning or immediately
1240        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1241        pcre_dfa_exec() could read past the end of the passed subject if there was
1242        no match. To help with detecting such bugs (e.g. with valgrind), I modified
1243        pcretest so that it places the subject at the end of its malloc-ed buffer.
1245    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1246        exec() might read past the end of the data buffer in UTF-8 mode.
1248    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1249        the data contained the byte 0x85 as part of a UTF-8 character within its
1250        first line. This applied both to normal and DFA matching.
1252    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1253        /^[^d]*?$/8 failed to match "abc".
1255    16. Added a missing copyright notice to pcrecpp_internal.h.
1257    17. Make it more clear in the documentation that values returned from
1258        pcre_exec() in ovector are byte offsets, not character counts.
1260    18. Tidied a few places to stop certain compilers from issuing warnings.
1262    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1263        supplied by Stefan Weber. I made a further small update for 7.8 because
1264        there is a change of source arrangements: the pcre_searchfuncs.c module is
1265        replaced by pcre_ucd.c.
1268    Version 7.7 07-May-08
1269  ---------------------  ---------------------
1271  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
1272      a string to a long long, pretend we don't even have a long long." This is      a string to a long long, pretend we don't even have a long long." This is
1273      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
1275  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1276      pre-7.6 versions, which defined a global no_arg variable instead of putting      pre-7.6 versions, which defined a global no_arg variable instead of putting
1277      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
1279  3.  Remove a line of dead code, identified by coverity and reported by Nuno  3.  Remove a line of dead code, identified by coverity and reported by Nuno
1280      Lopes.      Lopes.
1282  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
1284      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
1285          of files, instead of just to the final components.          of files, instead of just to the final components.
1287      (2) If there was more than one level of directory, the subdirectories were      (2) If there was more than one level of directory, the subdirectories were
1288          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
1289          inconsistent with GNU grep (and could even be seen as contrary to the          inconsistent with GNU grep (and could even be seen as contrary to the
1290          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
1291          The action now is always to scan all levels of directory, and just          The action now is always to scan all levels of directory, and just
1292          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
1294  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1295      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
1297  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
1298      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1299      doesn't support NULs in patterns.      doesn't support NULs in patterns.
1301  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
1302      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
1304  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1305      caused by fix #2  above. (Subsequently also a second patch to fix the      caused by fix #2  above. (Subsequently also a second patch to fix the
1306      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
1308  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
1310  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1311      matching function regexec().      matching function regexec().
1313  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1314      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
1315      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
1316      Oniguruma does).      Oniguruma does).
1318  12. Previously, a group with a zero repeat such as (...){0} was completely  12. Previously, a group with a zero repeat such as (...){0} was completely
1319      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
1320      was called as a subroutine from elsewhere in the pattern, things went wrong      was called as a subroutine from elsewhere in the pattern, things went wrong
1321      (an internal error was given). Such groups are now left in the compiled      (an internal error was given). Such groups are now left in the compiled
1322      pattern, with a new opcode that causes them to be skipped at execution      pattern, with a new opcode that causes them to be skipped at execution
1323      time.      time.
1325  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1326      to the way PCRE behaves:      to the way PCRE behaves:
1328      (a) A lone ] character is dis-allowed (Perl treats it as data).      (a) A lone ] character is dis-allowed (Perl treats it as data).
1330      (b) A back reference to an unmatched subpattern matches an empty string      (b) A back reference to an unmatched subpattern matches an empty string
1331          (Perl fails the current match path).          (Perl fails the current match path).
1333      (c) A data ] in a character class must be notated as \] because if the      (c) A data ] in a character class must be notated as \] because if the
1334          first data character in a class is ], it defines an empty class. (In          first data character in a class is ], it defines an empty class. (In
1335          Perl it is not possible to have an empty class.) The empty class []          Perl it is not possible to have an empty class.) The empty class []
1336          never matches; it forces failure and is equivalent to (*FAIL) or (?!).          never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1337          The negative empty class [^] matches any one character, independently          The negative empty class [^] matches any one character, independently
1338          of the DOTALL setting.          of the DOTALL setting.
1340  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1341      non-existent subpattern following a character class starting with ']' and      non-existent subpattern following a character class starting with ']' and
1342      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
1343      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
1344      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
1345      existencd of the subpattern, it was treating the data ']' as terminating      existencd of the subpattern, it was treating the data ']' as terminating
1346      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
1347      was subsequently set up correctly.)      was subsequently set up correctly.)
1349  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1350      it was being rejected as not supported by pcre_dfa_exec(), even though      it was being rejected as not supported by pcre_dfa_exec(), even though
1351      other assertions are supported. I have made pcre_dfa_exec() support      other assertions are supported. I have made pcre_dfa_exec() support
1352      (*FAIL).      (*FAIL).
1354  16. The implementation of 13c above involved the invention of a new opcode,  16. The implementation of 13c above involved the invention of a new opcode,
1355      OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s      OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1356      cannot be changed at match time, I realized I could make a small      cannot be changed at match time, I realized I could make a small
1357      improvement to matching performance by compiling OP_ALLANY instead of      improvement to matching performance by compiling OP_ALLANY instead of
1358      OP_ANY for "." when DOTALL was set, and then removing the runtime tests      OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1359      on the OP_ANY path.      on the OP_ANY path.
1361    17. Compiling pcretest on Windows with readline support failed without the
1362        following two fixes: (1) Make the unistd.h include conditional on
1363        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1365    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1366        ncurses library to be included for pcretest when ReadLine support is
1367        requested, but also to allow for it to be overridden. This patch came from
1368        Daniel Bergström.
1370    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1371        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1372        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1373        spotting this.
1376  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08

Removed from v.342  
changed lines
  Added in v.773

  ViewVC Help
Powered by ViewVC 1.1.5