/[pcre]/code/branches/pcre16/ChangeLog
ViewVC logotype

Diff of /code/branches/pcre16/ChangeLog

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

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

Legend:
Removed from v.222  
changed lines
  Added in v.734

  ViewVC Help
Powered by ViewVC 1.1.5