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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.98  
changed lines
  Added in v.750

  ViewVC Help
Powered by ViewVC 1.1.5