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

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12