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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.284  
changed lines
  Added in v.659

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12