ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 408 by ph10, Fri Mar 27 17:52:03 2009 UTC revision 745 by ph10, Mon Nov 14 11:41:03 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.9 xx-xxx-09  Version 8.21
5    ------------
7    1.  Updating the JIT compiler.
9    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
10        are added as well.
12    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
13        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
14        calling _pcre_jit_exec. Some extra comments are added.
16    4.  Mark settings inside atomic groups that do not contain any capturing
17        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
18        was introduced by change 18 for 8.20.
20    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
21        ECMA-262 standard.
24    Version 8.20 21-Oct-2011
25    ------------------------
27    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
28        a POSIX class. After further experiments with Perl, which convinced me that
29        Perl has bugs and confusions, a closing square bracket is no longer allowed
30        in a POSIX name. This bug also affected patterns with classes that started
31        with full stops.
33    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
34        captured substring, but while checking the failing first alternative,
35        substring 1 is temporarily captured. If the output vector supplied to
36        pcre_exec() was not big enough for this capture, the yield of the function
37        was still zero ("insufficient space for captured substrings"). This cannot
38        be totally fixed without adding another stack variable, which seems a lot
39        of expense for a edge case. However, I have improved the situation in cases
40        such as /(a)(b)x|abc/ matched against "abc", where the return code
41        indicates that fewer than the maximum number of slots in the ovector have
42        been set.
44    3.  Related to (2) above: when there are more back references in a pattern than
45        slots in the output vector, pcre_exec() uses temporary memory during
46        matching, and copies in the captures as far as possible afterwards. It was
47        using the entire output vector, but this conflicts with the specification
48        that only 2/3 is used for passing back captured substrings. Now it uses
49        only the first 2/3, for compatibility. This is, of course, another edge
50        case.
52    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
53        main code base, and can be used by building with --enable-jit. When this is
54        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
55        runtime --no-jit option is given.
57    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
58        ovector, the return from the function was zero, implying that there were
59        other matches that did not fit. The correct "exactly full" value is now
60        returned.
62    6.  If a subpattern that was called recursively or as a subroutine contained
63        (*PRUNE) or any other control that caused it to give a non-standard return,
64        invalid errors such as "Error -26 (nested recursion at the same subject
65        position)" or even infinite loops could occur.
67    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
68        computing the minimum length on reaching *ACCEPT, and so ended up with the
69        wrong value of 1 rather than 0. Further investigation indicates that
70        computing a minimum subject length in the presence of *ACCEPT is difficult
71        (think back references, subroutine calls), and so I have changed the code
72        so that no minimum is registered for a pattern that contains *ACCEPT.
74    8.  If (*THEN) was present in the first (true) branch of a conditional group,
75        it was not handled as intended. [But see 16 below.]
77    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
78        Sheri Pierce.
80    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
81        the first byte in a match must be "a".
83    11. Change 17 for 8.13 increased the recursion depth for patterns like
84        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
85        pattern contains any instances of (*THEN). If it does not, the old
86        optimizations are restored. It would be nice to do this on a per-group
87        basis, but at the moment that is not feasible.
89    12. In some environments, the output of pcretest -C is CRLF terminated. This
90        broke RunTest's code that checks for the link size. A single white space
91        character after the value is now allowed for.
93    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
94        For "fr", it uses the Windows-specific input and output files.
96    14. If (*THEN) appeared in a group that was called recursively or as a
97        subroutine, it did not work as intended. [But see next item.]
99    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
100        pattern fragments (but not containing any | characters). If A and B are
101        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
102        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
103        D. In other words, Perl considers parentheses that do not contain any |
104        characters to be part of a surrounding alternative, whereas PCRE was
105        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
106        differently. PCRE now behaves in the same way as Perl, except in the case
107        of subroutine/recursion calls such as (?1) which have in any case always
108        been different (but PCRE had them first :-).
110    16. Related to 15 above: Perl does not treat the | in a conditional group as
111        creating alternatives. Such a group is treated in the same way as an
112        ordinary group without any | characters when processing (*THEN). PCRE has
113        been changed to match Perl's behaviour.
115    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
116        RunGrepTest script failed.
118    18. Change 22 for version 13 caused atomic groups to use more stack. This is
119        inevitable for groups that contain captures, but it can lead to a lot of
120        stack use in large patterns. The old behaviour has been restored for atomic
121        groups that do not contain any capturing parentheses.
123    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
124        suppress the check for a minimum subject length at run time. (If it was
125        given to pcre_exec() or pcre_dfa_exec() it did work.)
127    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
128        fail to work when decoding hex characters in data strings in EBCDIC
129        environments.
131    21. It appears that in at least one Mac OS environment, the isxdigit() function
132        is implemented as a macro that evaluates to its argument more than once,
133        contravening the C 90 Standard (I haven't checked a later standard). There
134        was an instance in pcretest which caused it to go wrong when processing
135        \x{...} escapes in subject strings. The has been rewritten to avoid using
136        things like p++ in the argument of isxdigit().
139    Version 8.13 16-Aug-2011
140    ------------------------
142    1.  The Unicode data tables have been updated to Unicode 6.0.0.
144    2.  Two minor typos in pcre_internal.h have been fixed.
146    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
147        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
148        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
150    4.  There were a number of related bugs in the code for matching backrefences
151        caselessly in UTF-8 mode when codes for the characters concerned were
152        different numbers of bytes. For example, U+023A and U+2C65 are an upper
153        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
154        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
155        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
156        2-byte code at the end of the subject (it thought there wasn't enough data
157        left).
159    5.  Comprehensive information about what went wrong is now returned by
160        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
161        as the output vector has at least 2 elements. The offset of the start of
162        the failing character and a reason code are placed in the vector.
164    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
165        now returned is for the first byte of the failing character, instead of the
166        last byte inspected. This is an incompatible change, but I hope it is small
167        enough not to be a problem. It makes the returned offset consistent with
168        pcre_exec() and pcre_dfa_exec().
170    7.  pcretest now gives a text phrase as well as the error number when
171        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
172        failure, the offset and reason code are output.
174    8.  When \R was used with a maximizing quantifier it failed to skip backwards
175        over a \r\n pair if the subsequent match failed. Instead, it just skipped
176        back over a single character (\n). This seems wrong (because it treated the
177        two characters as a single entity when going forwards), conflicts with the
178        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
179        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
180        has been changed.
182    9.  Some internal refactoring has changed the processing so that the handling
183        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
184        time (the PCRE_DOTALL option was changed this way some time ago: version
185        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
186        which was always a bit of a fudge. It also means that there is one less
187        argument for the match() function, which reduces its stack requirements
188        slightly. This change also fixes an incompatibility with Perl: the pattern
189        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
191    10. More internal refactoring has drastically reduced the number of recursive
192        calls to match() for possessively repeated groups such as (abc)++ when
193        using pcre_exec().
195    11. While implementing 10, a number of bugs in the handling of groups were
196        discovered and fixed:
198        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
199        (a|)*(?1) gave a compile-time internal error.
200        ((a|)+)+  did not notice that the outer group could match an empty string.
201        (^a|^)+   was not marked as anchored.
202        (.*a|.*)+ was not marked as matching at start or after a newline.
204    12. Yet more internal refactoring has removed another argument from the match()
205        function. Special calls to this function are now indicated by setting a
206        value in a variable in the "match data" data block.
208    13. Be more explicit in pcre_study() instead of relying on "default" for
209        opcodes that mean there is no starting character; this means that when new
210        ones are added and accidentally left out of pcre_study(), testing should
211        pick them up.
213    14. The -s option of pcretest has been documented for ages as being an old
214        synonym of -m (show memory usage). I have changed it to mean "force study
215        for every regex", that is, assume /S for every regex. This is similar to -i
216        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
217        using it. It makes it easier to run collections of tests with and without
218        study enabled, and thereby test pcre_study() more easily. All the standard
219        tests are now run with and without -s (but some patterns can be marked as
220        "never study" - see 20 below).
222    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
223        restoration of the capturing data to the outer values was not happening
224        correctly.
226    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
227        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
228        pattern had matched an empty string, and so incorrectly returned a no
229        match.
231    17. There was optimizing code for the last branch of non-capturing parentheses,
232        and also for the obeyed branch of a conditional subexpression, which used
233        tail recursion to cut down on stack usage. Unfortunately, now that there is
234        the possibility of (*THEN) occurring in these branches, tail recursion is
235        no longer possible because the return has to be checked for (*THEN). These
236        two optimizations have therefore been removed. [But see 8.20/11 above.]
238    18. If a pattern containing \R was studied, it was assumed that \R always
239        matched two bytes, thus causing the minimum subject length to be
240        incorrectly computed because \R can also match just one byte.
242    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
243        was incorrectly computed.
245    20. If /S is present twice on a test pattern in pcretest input, it now
246        *disables* studying, thereby overriding the use of -s on the command line
247        (see 14 above). This is necessary for one or two tests to keep the output
248        identical in both cases.
250    21. When (*ACCEPT) was used in an assertion that matched an empty string and
251        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
253    22. When an atomic group that contained a capturing parenthesis was
254        successfully matched, but the branch in which it appeared failed, the
255        capturing was not being forgotten if a higher numbered group was later
256        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
257        group 1 to "a", when in fact it should be unset. This applied to multi-
258        branched capturing and non-capturing groups, repeated or not, and also to
259        positive assertions (capturing in negative assertions does not happen
260        in PCRE) and also to nested atomic groups.
262    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
263        subject after a captured substring, to make it easier to tell which of a
264        number of identical substrings has been captured.
266    24. The way atomic groups are processed by pcre_exec() has been changed so that
267        if they are repeated, backtracking one repetition now resets captured
268        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
269        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
270        "aaa". Previously, it would have been "a". As part of this code
271        refactoring, the way recursive calls are handled has also been changed.
273    25. If an assertion condition captured any substrings, they were not passed
274        back unless some other capturing happened later. For example, if
275        (?(?=(a))a) was matched against "a", no capturing was returned.
277    26. When studying a pattern that contained subroutine calls or assertions,
278        the code for finding the minimum length of a possible match was handling
279        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
280        group 1 called group 2 while simultaneously a separate group 2 called group
281        1). A stack overflow occurred in this case. I have fixed this by limiting
282        the recursion depth to 10.
284    27. Updated RunTest.bat in the distribution to the version supplied by Tom
285        Fortmann. This supports explicit test numbers on the command line, and has
286        argument validation and error reporting.
288    28. An instance of \X with an unlimited repeat could fail if at any point the
289        first character it looked at was a mark character.
291    29. Some minor code refactoring concerning Unicode properties and scripts
292        should reduce the stack requirement of match() slightly.
294    30. Added the '=' option to pcretest to check the setting of unused capturing
295        slots at the end of the pattern, which are documented as being -1, but are
296        not included in the return count.
298    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
299        compiled something random. Now it gives a compile-time error (as does
300        Perl).
302    32. A *MARK encountered during the processing of a positive assertion is now
303        recorded and passed back (compatible with Perl).
305    33. If --only-matching or --colour was set on a pcregrep call whose pattern
306        had alternative anchored branches, the search for a second match in a line
307        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
308        matched the line "0102" twice. The same bug affected patterns that started
309        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
310        twice.
312    34. Previously, PCRE did not allow quantification of assertions. However, Perl
313        does, and because of capturing effects, quantifying parenthesized
314        assertions may at times be useful. Quantifiers are now allowed for
315        parenthesized assertions.
317    35. A minor code tidy in pcre_compile() when checking options for \R usage.
319    36. \g was being checked for fancy things in a character class, when it should
320        just be a literal "g".
322    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
323        appearance of a nested POSIX class supersedes an apparent external class.
324        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
325        unescaped square brackets may also appear as part of class names. For
326        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
327        more like Perl. (But see 8.20/1 above.)
329    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
330        was because it thought it was \N{name}, which is not supported).
332    39. Add minix to OS list not supporting the -S option in pcretest.
334    40. PCRE tries to detect cases of infinite recursion at compile time, but it
335        cannot analyze patterns in sufficient detail to catch mutual recursions
336        such as ((?1))((?2)). There is now a runtime test that gives an error if a
337        subgroup is called recursively as a subpattern for a second time at the
338        same position in the subject string. In previous releases this might have
339        been caught by the recursion limit, or it might have run out of stack.
341    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
342        happen only once. PCRE was, however incorrectly giving a compile time error
343        "recursive call could loop indefinitely" because it cannot analyze the
344        pattern in sufficient detail. The compile time test no longer happens when
345        PCRE is compiling a conditional subpattern, but actual runaway loops are
346        now caught at runtime (see 40 above).
348    42. It seems that Perl allows any characters other than a closing parenthesis
349        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
350        has been changed to be the same.
352    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
353        as not to get warnings when autogen.sh is called. Also changed
354        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
356    44. To help people who use pcregrep to scan files containing exceedingly long
357        lines, the following changes have been made:
359        (a) The default value of the buffer size parameter has been increased from
360            8K to 20K. (The actual buffer used is three times this size.)
362        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
363            PCRE is built.
365        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
366            to be set at run time.
368        (d) Numerical values in pcregrep options can be followed by K or M, for
369            example --buffer-size=50K.
371        (e) If a line being scanned overflows pcregrep's buffer, an error is now
372            given and the return code is set to 2.
374    45. Add a pointer to the latest mark to the callout data block.
376    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
377        partial match of an empty string instead of no match. This was specific to
378        the use of ".".
380    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
381        complete match instead of a partial match. This bug was dependent on both
382        the PCRE_UTF8 and PCRE_DOTALL options being set.
384    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
385        starting byte set, because \b was not being ignored.
388    Version 8.12 15-Jan-2011
389    ------------------------
391    1.  Fixed some typos in the markup of the man pages, and wrote a script that
392        checks for such things as part of the documentation building process.
394    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
395        --match-limit and --recursion-limit options (added for 8.11). In
396        particular, this made one of the standard tests fail. (The integer value
397        went into the wrong half of a long int.)
399    3.  If the --colour option was given to pcregrep with -v (invert match), it
400        did strange things, either producing crazy output, or crashing. It should,
401        of course, ignore a request for colour when reporting lines that do not
402        match.
404    4.  Another pcregrep bug caused similar problems if --colour was specified with
405        -M (multiline) and the pattern match finished with a line ending.
407    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
408        matched in multiline mode, the following line was shown as part of the
409        match. This seems wrong, so I have changed it.
411    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
412        the check for further matches in the same line (so they could be coloured)
413        to overrun the end of the current line. If another match was found, it was
414        incorrectly shown (and then shown again when found in the next line).
416    7.  If pcregrep was compiled under Windows, there was a reference to the
417        function pcregrep_exit() before it was defined. I am assuming this was
418        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
419        reported by a user. I've moved the definition above the reference.
422    Version 8.11 10-Dec-2010
423    ------------------------
425    1.  (*THEN) was not working properly if there were untried alternatives prior
426        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
427        backtracked to try for "b" instead of moving to the next alternative branch
428        at the same level (in this case, to look for "c"). The Perl documentation
429        is clear that when (*THEN) is backtracked onto, it goes to the "next
430        alternative in the innermost enclosing group".
432    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
433        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
434        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
435        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
436        (*THEN).
438    3.  If \s appeared in a character class, it removed the VT character from
439        the class, even if it had been included by some previous item, for example
440        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
441        of \s, but is part of the POSIX "space" class.)
443    4.  A partial match never returns an empty string (because you can always
444        match an empty string at the end of the subject); however the checking for
445        an empty string was starting at the "start of match" point. This has been
446        changed to the "earliest inspected character" point, because the returned
447        data for a partial match starts at this character. This means that, for
448        example, /(?<=abc)def/ gives a partial match for the subject "abc"
449        (previously it gave "no match").
451    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
452        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
453        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
454        has an implication that the given string is incomplete (because a partial
455        match is preferred over a full match). For this reason, these items now
456        give a partial match in this situation. [Aside: previously, the one case
457        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
458        match rather than a full match, which was wrong by the old rules, but is
459        now correct.]
461    6.  There was a bug in the handling of #-introduced comments, recognized when
462        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
463        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
464        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
465        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
466        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
467        places in pcre_compile().
469    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
470        comments when looking ahead for named forward references to subpatterns,
471        the only newline sequence it recognized was NL. It now handles newlines
472        according to the set newline convention.
474    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
475        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
476        cater for a lack of strerror(). These oversights have been fixed.
478    9.  Added --match-limit and --recursion-limit to pcregrep.
480    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
482    11. When the -o option was used, pcregrep was setting a return code of 1, even
483        when matches were found, and --line-buffered was not being honoured.
485    12. Added an optional parentheses number to the -o and --only-matching options
486        of pcregrep.
488    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
489        can match an empty string. The code to do it in pcretest and pcredemo
490        needed fixing:
492        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
493            only one byte after an empty string match just before CRLF (this case
494            just got forgotten; "any" and "anycrlf" were OK).
496        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
497            mode when an empty string match preceded an ASCII character followed by
498            a non-ASCII character. (The code for advancing by one character rather
499            than one byte was nonsense.)
501        (c) The pcredemo.c sample program did not have any code at all to handle
502            the cases when CRLF is a valid newline sequence.
504    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
505        as a starting offset was within the subject string. There is now a new
506        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
507        negative or greater than the length of the string. In order to test this,
508        pcretest is extended to allow the setting of negative starting offsets.
510    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
511        starting offset points to the beginning of a UTF-8 character was
512        unnecessarily clumsy. I tidied it up.
514    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
515        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
517    17. Nobody had reported that the --include_dir option, which was added in
518        release 7.7 should have been called --include-dir (hyphen, not underscore)
519        for compatibility with GNU grep. I have changed it to --include-dir, but
520        left --include_dir as an undocumented synonym, and the same for
521        --exclude-dir, though that is not available in GNU grep, at least as of
522        release 2.5.4.
524    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
525        characters from a string of bytes) have been redefined so as not to use
526        loops, in order to improve performance in some environments. At the same
527        time, I abstracted some of the common code into auxiliary macros to save
528        repetition (this should not affect the compiled code).
530    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
531        compile-time error is now given if \c is not followed by an ASCII
532        character, that is, a byte less than 128. (In EBCDIC mode, the code is
533        different, and any byte value is allowed.)
535    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
536        START_OPTIMIZE option, which is now allowed at compile time - but just
537        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
538        to pcregrep and other applications that have no direct access to PCRE
539        options. The new /Y option in pcretest sets this option when calling
540        pcre_compile().
542    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
543        back references. Groups containing recursive back references were forced to
544        be atomic by that change, but in the case of named groups, the amount of
545        memory required was incorrectly computed, leading to "Failed: internal
546        error: code overflow". This has been fixed.
548    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
549        pcretest.c, to avoid build problems in some Borland environments.
552    Version 8.10 25-Jun-2010
553    ------------------------
555    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
556        THEN.
558    2.  (*ACCEPT) was not working when inside an atomic group.
560    3.  Inside a character class, \B is treated as a literal by default, but
561        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
562        causes the error). The code is unchanged, but I tidied the documentation.
564    4.  Inside a character class, PCRE always treated \R and \X as literals,
565        whereas Perl faults them if its -w option is set. I have changed PCRE so
566        that it faults them when PCRE_EXTRA is set.
568    5.  Added support for \N, which always matches any character other than
569        newline. (It is the same as "." when PCRE_DOTALL is not set.)
571    6.  When compiling pcregrep with newer versions of gcc which may have
572        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
573        declared with attribute warn_unused_result" were given. Just casting the
574        result to (void) does not stop the warnings; a more elaborate fudge is
575        needed. I've used a macro to implement this.
577    7.  Minor change to pcretest.c to avoid a compiler warning.
579    8.  Added four artifical Unicode properties to help with an option to make
580        \s etc use properties (see next item). The new properties are: Xan
581        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
583    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
584        use Unicode properties. (*UCP) at the start of a pattern can be used to set
585        this option. Modified pcretest to add /W to test this facility. Added
586        REG_UCP to make it available via the POSIX interface.
588    10. Added --line-buffered to pcregrep.
590    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
591        studied, and the match started with a letter with a code point greater than
592        127 whose first byte was different to the first byte of the other case of
593        the letter, the other case of this starting letter was not recognized
594        (#976).
596    12. If a pattern that was studied started with a repeated Unicode property
597        test, for example, \p{Nd}+, there was the theoretical possibility of
598        setting up an incorrect bitmap of starting bytes, but fortunately it could
599        not have actually happened in practice until change 8 above was made (it
600        added property types that matched character-matching opcodes).
602    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
603        possible starting bytes for non-anchored patterns.
605    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
606        \R, and also a number of cases that involve Unicode properties, both
607        explicit and implicit when PCRE_UCP is set.
609    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
610        input, it could crash or give wrong results if characters with values
611        greater than 0xc0 were present in the subject string. (Detail: it assumed
612        UTF-8 input when processing these items.)
614    16. Added a lot of (int) casts to avoid compiler warnings in systems where
615        size_t is 64-bit (#991).
617    17. Added a check for running out of memory when PCRE is compiled with
618        --disable-stack-for-recursion (#990).
620    18. If the last data line in a file for pcretest does not have a newline on
621        the end, a newline was missing in the output.
623    19. The default pcre_chartables.c file recognizes only ASCII characters (values
624        less than 128) in its various bitmaps. However, there is a facility for
625        generating tables according to the current locale when PCRE is compiled. It
626        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
627        characters, are recognized by isspace() and therefore were getting set in
628        these tables, and indeed these tables seem to approximate to ISO 8859. This
629        caused a problem in UTF-8 mode when pcre_study() was used to create a list
630        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
631        which of course cannot start UTF-8 characters. I have changed the code so
632        that only real ASCII characters (less than 128) and the correct starting
633        bytes for UTF-8 encodings are set for characters greater than 127 when in
634        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
635        altogether.)
637    20. Added the /T option to pcretest so as to be able to run tests with non-
638        standard character tables, thus making it possible to include the tests
639        used for 19 above in the standard set of tests.
641    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
642        reference to a subpattern the other side of a comment that contains an
643        opening parenthesis caused either an internal compiling error, or a
644        reference to the wrong subpattern.
647    Version 8.02 19-Mar-2010
648    ------------------------
650    1.  The Unicode data tables have been updated to Unicode 5.2.0.
652    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
653        configured.
655    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
656        original author of that file, following a query about its status.
658    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
659        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
661    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
662        quantifier applied to a forward-referencing subroutine call, could compile
663        incorrect code or give the error "internal error: previously-checked
664        referenced subpattern not found".
666    6.  Both MS Visual Studio and Symbian OS have problems with initializing
667        variables to point to external functions. For these systems, therefore,
668        pcre_malloc etc. are now initialized to local functions that call the
669        relevant global functions.
671    7.  There were two entries missing in the vectors called coptable and poptable
672        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
673        I've fixed the data, and added a kludgy way of testing at compile time that
674        the lengths are correct (equal to the number of opcodes).
676    8.  Following on from 7, I added a similar kludge to check the length of the
677        eint vector in pcreposix.c.
679    9.  Error texts for pcre_compile() are held as one long string to avoid too
680        much relocation at load time. To find a text, the string is searched,
681        counting zeros. There was no check for running off the end of the string,
682        which could happen if a new error number was added without updating the
683        string.
685    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
687    11. \K was not working if it appeared in an atomic group or in a group that
688        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
689        \K is "not well defined" if used in an assertion. PCRE now accepts it if
690        the assertion is positive, but not if it is negative.
692    12. Change 11 fortuitously reduced the size of the stack frame used in the
693        "match()" function of pcre_exec.c by one pointer. Forthcoming
694        implementation of support for (*MARK) will need an extra pointer on the
695        stack; I have reserved it now, so that the stack frame size does not
696        decrease.
698    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
699        item in branch that calls a recursion is a subroutine call - as in the
700        second branch in the above example - was incorrectly given the compile-
701        time error "recursive call could loop indefinitely" because pcre_compile()
702        was not correctly checking the subroutine for matching a non-empty string.
704    14. The checks for overrunning compiling workspace could trigger after an
705        overrun had occurred. This is a "should never occur" error, but it can be
706        triggered by pathological patterns such as hundreds of nested parentheses.
707        The checks now trigger 100 bytes before the end of the workspace.
709    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
712    Version 8.01 19-Jan-2010
713    ------------------------
715    1.  If a pattern contained a conditional subpattern with only one branch (in
716        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
717        computed the wrong minimum data length (which is of course zero for such
718        subpatterns). This could cause incorrect "no match" results.
720    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
721        the pattern is reset in the first branch, pcre_compile() failed with
722        "internal error: code overflow at offset...". This happened only when
723        the reset was to the original external option setting. (An optimization
724        abstracts leading options settings into an external setting, which was the
725        cause of this.)
727    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
728        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
729        assertion pattern did not match (meaning that the assertion was true), it
730        was incorrectly treated as false if the SKIP had been reached during the
731        matching. This also applied to assertions used as conditions.
733    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
734        assertion subpattern, including such a pattern used as a condition,
735        unpredictable results occurred, instead of the error return
738    5.  The C++ GlobalReplace function was not working like Perl for the special
739        situation when an empty string is matched. It now does the fancy magic
740        stuff that is necessary.
742    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
743        removed. (These were left over from very, very early versions of PCRE.)
745    7.  Some cosmetic changes to the code to make life easier when compiling it
746        as part of something else:
748        (a) Change DEBUG to PCRE_DEBUG.
750        (b) In pcre_compile(), rename the member of the "branch_chain" structure
751            called "current" as "current_branch", to prevent a collision with the
752            Linux macro when compiled as a kernel module.
754        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
755            prevent a collision with the Linux macro when compiled as a kernel
756            module.
758    8.  In pcre_compile() there are some checks for integer overflows that used to
759        cast potentially large values to (double). This has been changed to that
760        when building, a check for int64_t is made, and if it is found, it is used
761        instead, thus avoiding the use of floating point arithmetic. (There is no
762        other use of FP in PCRE.) If int64_t is not found, the fallback is to
763        double.
765    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
766        2005 (difference between two addresses compared to an unsigned value).
768    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
769        custom one, because of the following reported problem in Windows:
771          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
772              under Win32.
773          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
774              therefore missing the function definition.
775          - The compiler thus generates a "C" signature for the test function.
776          - The linker fails to find the "C" function.
777          - PCRE fails to configure if asked to do so against libbz2.
779    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
780        messages were output:
782          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
783          rerunning libtoolize, to keep the correct libtool macros in-tree.
784          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
786        I have done both of these things.
788    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
789        most of the time, it *can* run out if it is given a pattern that contains a
790        runaway infinite recursion. I updated the discussion in the pcrestack man
791        page.
793    13. Now that we have gone to the x.xx style of version numbers, the minor
794        version may start with zero. Using 08 or 09 is a bad idea because users
795        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
796        interpreted as invalid octal numbers. I've updated the previous comment in
797        configure.ac, and also added a check that gives an error if 08 or 09 are
798        used.
800    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
801        causing partial matching to fail when the end of the subject matched \W
802        in a UTF-8 pattern where \W was quantified with a minimum of 3.
804    15. There were some discrepancies between the declarations in pcre_internal.h
805        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
806        their definitions. The declarations used "const uschar *" and the
807        definitions used USPTR. Even though USPTR is normally defined as "const
808        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
809        reported that: "This difference in casting confuses some C++ compilers, for
810        example, SunCC recognizes above declarations as different functions and
811        generates broken code for hbpcre." I have changed the declarations to use
812        USPTR.
814    16. GNU libtool is named differently on some systems. The autogen.sh script now
815        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
816        (FreeBSD).
818    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
819        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
820        comment: "Figure out how to create a longlong from a string: strtoll and
821        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
822        instance, but it only takes 2 args instead of 3!"
824    18. A subtle bug concerned with back references has been fixed by a change of
825        specification, with a corresponding code fix. A pattern such as
826        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
827        refers, was giving matches when it shouldn't. For example, xa=xaaa would
828        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
829        same bug. Such groups have to be quantified to be useful, or contained
830        inside another quantified group. (If there's no repetition, the reference
831        can never match.) The problem arises because, having left the group and
832        moved on to the rest of the pattern, a later failure that backtracks into
833        the group uses the captured value from the final iteration of the group
834        rather than the correct earlier one. I have fixed this in PCRE by forcing
835        any group that contains a reference to itself to be an atomic group; that
836        is, there cannot be any backtracking into it once it has completed. This is
837        similar to recursive and subroutine calls.
840    Version 8.00 19-Oct-09
841    ----------------------
843    1.  The table for translating pcre_compile() error codes into POSIX error codes
844        was out-of-date, and there was no check on the pcre_compile() error code
845        being within the table. This could lead to an OK return being given in
846        error.
848    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
849        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
850        in a Windows environment.
852    3.  The pcregrep --count option prints the count for each file even when it is
853        zero, as does GNU grep. However, pcregrep was also printing all files when
854        --files-with-matches was added. Now, when both options are given, it prints
855        counts only for those files that have at least one match. (GNU grep just
856        prints the file name in this circumstance, but including the count seems
857        more useful - otherwise, why use --count?) Also ensured that the
858        combination -clh just lists non-zero counts, with no names.
860    4.  The long form of the pcregrep -F option was incorrectly implemented as
861        --fixed_strings instead of --fixed-strings. This is an incompatible change,
862        but it seems right to fix it, and I didn't think it was worth preserving
863        the old behaviour.
865    5.  The command line items --regex=pattern and --regexp=pattern were not
866        recognized by pcregrep, which required --regex pattern or --regexp pattern
867        (with a space rather than an '='). The man page documented the '=' forms,
868        which are compatible with GNU grep; these now work.
870    6.  No libpcreposix.pc file was created for pkg-config; there was just
871        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
873    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
874        when UCP support is not needed, by modifying the Python script that
875        generates it from Unicode data files. This should not matter if the module
876        is correctly used as a library, but I received one complaint about 50K of
877        unwanted data. My guess is that the person linked everything into his
878        program rather than using a library. Anyway, it does no harm.
880    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
881        was a minimum greater than 1 for a wide character in a possessive
882        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
883        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
884        character. Chaos in the form of incorrect output or a compiling loop could
885        result.
887    9.  The restrictions on what a pattern can contain when partial matching is
888        requested for pcre_exec() have been removed. All patterns can now be
889        partially matched by this function. In addition, if there are at least two
890        slots in the offset vector, the offset of the earliest inspected character
891        for the match and the offset of the end of the subject are set in them when
892        PCRE_ERROR_PARTIAL is returned.
894    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
895        synonymous with PCRE_PARTIAL, for backwards compatibility, and
896        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
897        and may be more useful for multi-segment matching.
899    11. Partial matching with pcre_exec() is now more intuitive. A partial match
900        used to be given if ever the end of the subject was reached; now it is
901        given only if matching could not proceed because another character was
902        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
903        string "Z", which now yields "no match" instead of "partial match". In the
904        case of pcre_dfa_exec(), "no match" is given if every matching path for the
905        final character ended with (*FAIL).
907    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
908        if the pattern had a "must contain" character that was already found in the
909        earlier partial match, unless partial matching was again requested. For
910        example, with the pattern /dog.(body)?/, the "must contain" character is
911        "g". If the first part-match was for the string "dog", restarting with
912        "sbody" failed. This bug has been fixed.
914    13. The string returned by pcre_dfa_exec() after a partial match has been
915        changed so that it starts at the first inspected character rather than the
916        first character of the match. This makes a difference only if the pattern
917        starts with a lookbehind assertion or \b or \B (\K is not supported by
918        pcre_dfa_exec()). It's an incompatible change, but it makes the two
919        matching functions compatible, and I think it's the right thing to do.
921    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
922        so that the demonstration program is easily available in environments where
923        PCRE has not been installed from source.
925    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
926        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
927        library.
929    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
930        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
931        is not the first non-POSIX option to be added. Clearly some people find
932        these options useful.
934    17. If a caller to the POSIX matching function regexec() passes a non-zero
935        value for nmatch with a NULL value for pmatch, the value of
936        nmatch is forced to zero.
938    18. RunGrepTest did not have a test for the availability of the -u option of
939        the diff command, as RunTest does. It now checks in the same way as
940        RunTest, and also checks for the -b option.
942    19. If an odd number of negated classes containing just a single character
943        interposed, within parentheses, between a forward reference to a named
944        subpattern and the definition of the subpattern, compilation crashed with
945        an internal error, complaining that it could not find the referenced
946        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
947        [The bug was that it was starting one character too far in when skipping
948        over the character class, thus treating the ] as data rather than
949        terminating the class. This meant it could skip too much.]
951    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
952        /g option in pcretest when the pattern contains \K, which makes it possible
953        to have an empty string match not at the start, even when the pattern is
954        anchored. Updated pcretest and pcredemo to use this option.
956    21. If the maximum number of capturing subpatterns in a recursion was greater
957        than the maximum at the outer level, the higher number was returned, but
958        with unset values at the outer level. The correct (outer level) value is
959        now given.
961    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
962        PCRE did not set those parentheses (unlike Perl). I have now found a way to
963        make it do so. The string so far is captured, making this feature
964        compatible with Perl.
966    23. The tests have been re-organized, adding tests 11 and 12, to make it
967        possible to check the Perl 5.10 features against Perl 5.10.
969    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
970        pattern matches a fixed length string. PCRE did not allow this; now it
971        does. Neither allows recursion.
973    25. I finally figured out how to implement a request to provide the minimum
974        length of subject string that was needed in order to match a given pattern.
975        (It was back references and recursion that I had previously got hung up
976        on.) This code has now been added to pcre_study(); it finds a lower bound
977        to the length of subject needed. It is not necessarily the greatest lower
978        bound, but using it to avoid searching strings that are too short does give
979        some useful speed-ups. The value is available to calling programs via
980        pcre_fullinfo().
982    26. While implementing 25, I discovered to my embarrassment that pcretest had
983        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
984        study optimizations had never been tested with that matching function.
985        Oops. What is worse, even when it was passed study data, there was a bug in
986        pcre_dfa_exec() that meant it never actually used it. Double oops. There
987        were also very few tests of studied patterns with pcre_dfa_exec().
989    27. If (?| is used to create subpatterns with duplicate numbers, they are now
990        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
991        on the other side of the coin, they are no longer allowed to have different
992        names, because these cannot be distinguished in PCRE, and this has caused
993        confusion. (This is a difference from Perl.)
995    28. When duplicate subpattern names are present (necessarily with different
996        numbers, as required by 27 above), and a test is made by name in a
997        conditional pattern, either for a subpattern having been matched, or for
998        recursion in such a pattern, all the associated numbered subpatterns are
999        tested, and the overall condition is true if the condition is true for any
1000        one of them. This is the way Perl works, and is also more like the way
1001        testing by number works.
1004    Version 7.9 11-Apr-09
1005  ---------------------  ---------------------
1007  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
# Line 17  Version 7.9 xx-xxx-09 Line 1017  Version 7.9 xx-xxx-09
1017      but BOOL is not.      but BOOL is not.
1019  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1020      PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.      PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1022  4.  The pcregrep documentation said spaces were inserted as well as colons (or  4.  The pcregrep documentation said spaces were inserted as well as colons (or
1023      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
# Line 94  Version 7.9 xx-xxx-09 Line 1094  Version 7.9 xx-xxx-09
1094  23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name  23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1095      CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is      CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1096      included within another project.      included within another project.
1098  24. Steven Van Ingelgem's patches to add more options to the CMake support,  24. Steven Van Ingelgem's patches to add more options to the CMake support,
1099      slightly modified by me:      slightly modified by me:
1101        (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including        (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1102            not building pcregrep.            not building pcregrep.
1104        (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only        (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1105            if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.            if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1107  25. Forward references, both numeric and by name, in patterns that made use of  25. Forward references, both numeric and by name, in patterns that made use of
1108      duplicate group numbers, could behave incorrectly or give incorrect errors,      duplicate group numbers, could behave incorrectly or give incorrect errors,
1109      because when scanning forward to find the reference group, PCRE was not      because when scanning forward to find the reference group, PCRE was not
1110      taking into account the duplicate group numbers. A pattern such as      taking into account the duplicate group numbers. A pattern such as
1111      ^X(?3)(a)(?|(b)|(q))(Y) is an example.      ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1113    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1114        the feature of a custom pointer more persuasive (as requested by a user).
1116    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1117        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1118        pre-defined.
1120    28. Added support for (*UTF8) at the start of a pattern.
1122    29. Arrange for flags added by the "release type" setting in CMake to be shown
1123        in the configuration summary.
1126  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08

Removed from v.408  
changed lines
  Added in v.745

  ViewVC Help
Powered by ViewVC 1.1.5