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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.200  
changed lines
  Added in v.912

  ViewVC Help
Powered by ViewVC 1.1.5