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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.212  
changed lines
  Added in v.719

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12