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

Diff of /code/trunk/ChangeLog

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

revision 515 by ph10, Tue May 4 09:12:25 2010 UTC revision 886 by ph10, Tue Jan 17 14:25:07 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.10 03 May-2010  Version 8.30
5    ------------
6    
7    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
8        name is defined in ctype.h.
9    
10    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
11        only in quite long subpatterns.
12    
13    3.  Removed the function pcre_info(), which has been obsolete and deprecated
14        since it was replaced by pcre_fullinfo() in February 2000.
15    
16    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
17        match a (*MARK), and the match failed at the start of the subject, a
18        reference to memory before the start of the subject could occur. This bug
19        was introduced by fix 17 of release 8.21.
20    
21    5.  A reference to an unset group with zero minimum repetition was giving
22        totally wrong answers (in non-JavaScript-compatibility mode). For example,
23        /(another)?(\1?)test/ matched against "hello world test". This bug was
24        introduced in release 8.13.
25    
26    6.  Add support for 16-bit character strings (a large amount of work involving
27        many changes and refactorings).
28    
29    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
30        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
31        from a file.
32    
33    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
34        rounding is not applied in this particular case).
35    
36    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
37        if they appear, or are escaped, in patterns.
38    
39    10. Get rid of a number of -Wunused-but-set-variable warnings.
40    
41    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
42        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
43        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
44        also returns the mark "x". This bug applied to capturing parentheses,
45        non-capturing parentheses, and atomic parentheses.
46    
47    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
48        information out of configure.ac instead of relying on pcre.h.generic, which
49        is not stored in the repository.
50    
51    
52    Version 8.21 12-Dec-2011
53    ------------------------
54    
55    1.  Updating the JIT compiler.
56    
57    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
58        are added as well.
59    
60    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
61        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
62        calling _pcre_jit_exec. Some extra comments are added.
63    
64    4.  (*MARK) settings inside atomic groups that do not contain any capturing
65        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
66        was introduced by change 18 for 8.20.
67    
68    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
69        ECMA-262 standard.
70    
71    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
72        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
73        This bug was probably introduced by change 9 of 8.13.
74    
75    7.  While fixing 6 above, I noticed that a number of other items were being
76        incorrectly rejected as "not fixed length". This arose partly because newer
77        opcodes had not been added to the fixed-length checking code. I have (a)
78        corrected the bug and added tests for these items, and (b) arranged for an
79        error to occur if an unknown opcode is encountered while checking for fixed
80        length instead of just assuming "not fixed length". The items that were
81        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
82        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
83        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
84    
85    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
86        being incorrectly compiled and would have given unpredicatble results.
87    
88    9.  A possessively repeated subpattern with minimum repeat count greater than
89        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
90        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
91        the first (A) could occur when it should not.
92    
93    10. Add a cast and remove a redundant test from the code.
94    
95    11. JIT should use pcre_malloc/pcre_free for allocation.
96    
97    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
98        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
99        is anything other than /usr, -L is still shown).
100    
101    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
102    
103    14. Perl does not support \N without a following name in a [] class; PCRE now
104        also gives an error.
105    
106    15. If a forward reference was repeated with an upper limit of around 2000,
107        it caused the error "internal error: overran compiling workspace". The
108        maximum number of forward references (including repeats) was limited by the
109        internal workspace, and dependent on the LINK_SIZE. The code has been
110        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
111        the default depends on LINK_SIZE. There is a new upper limit (for safety)
112        of around 200,000 forward references. While doing this, I also speeded up
113        the filling in of repeated forward references.
114    
115    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
116        incorrectly expecting the subject to contain another "a" after the start.
117    
118    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
119        in the match, the SKIP should be ignored. This was not happening; instead
120        the SKIP was being treated as NOMATCH. For patterns such as
121        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
122        tested.
123    
124    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
125        now much more compatible with Perl, in particular in cases where the result
126        is a non-match for a non-anchored pattern. For example, if
127        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
128        "m", where previously it did not return a name. A side effect of this
129        change is that for partial matches, the last encountered mark name is
130        returned, as for non matches. A number of tests that were previously not
131        Perl-compatible have been moved into the Perl-compatible test files. The
132        refactoring has had the pleasing side effect of removing one argument from
133        the match() function, thus reducing its stack requirements.
134    
135    19. If the /S+ option was used in pcretest to study a pattern using JIT,
136        subsequent uses of /S (without +) incorrectly behaved like /S+.
137    
138    21. Retrieve executable code size support for the JIT compiler and fixing
139        some warnings.
140    
141    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
142        not work when the shorter character appeared right at the end of the
143        subject string.
144    
145    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
146        systems.
147    
148    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
149        output it when the /M option is used in pcretest.
150    
151    25. The CheckMan script was not being included in the distribution. Also, added
152        an explicit "perl" to run Perl scripts from the PrepareRelease script
153        because this is reportedly needed in Windows.
154    
155    26. If study data was being save in a file and studying had not found a set of
156        "starts with" bytes for the pattern, the data written to the file (though
157        never used) was taken from uninitialized memory and so caused valgrind to
158        complain.
159    
160    27. Updated RunTest.bat as provided by Sheri Pierce.
161    
162    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
163    
164    29. Computation of memory usage for the table of capturing group names was
165        giving an unnecessarily large value.
166    
167    
168    Version 8.20 21-Oct-2011
169    ------------------------
170    
171    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
172        a POSIX class. After further experiments with Perl, which convinced me that
173        Perl has bugs and confusions, a closing square bracket is no longer allowed
174        in a POSIX name. This bug also affected patterns with classes that started
175        with full stops.
176    
177    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
178        captured substring, but while checking the failing first alternative,
179        substring 1 is temporarily captured. If the output vector supplied to
180        pcre_exec() was not big enough for this capture, the yield of the function
181        was still zero ("insufficient space for captured substrings"). This cannot
182        be totally fixed without adding another stack variable, which seems a lot
183        of expense for a edge case. However, I have improved the situation in cases
184        such as /(a)(b)x|abc/ matched against "abc", where the return code
185        indicates that fewer than the maximum number of slots in the ovector have
186        been set.
187    
188    3.  Related to (2) above: when there are more back references in a pattern than
189        slots in the output vector, pcre_exec() uses temporary memory during
190        matching, and copies in the captures as far as possible afterwards. It was
191        using the entire output vector, but this conflicts with the specification
192        that only 2/3 is used for passing back captured substrings. Now it uses
193        only the first 2/3, for compatibility. This is, of course, another edge
194        case.
195    
196    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
197        main code base, and can be used by building with --enable-jit. When this is
198        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
199        runtime --no-jit option is given.
200    
201    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
202        ovector, the return from the function was zero, implying that there were
203        other matches that did not fit. The correct "exactly full" value is now
204        returned.
205    
206    6.  If a subpattern that was called recursively or as a subroutine contained
207        (*PRUNE) or any other control that caused it to give a non-standard return,
208        invalid errors such as "Error -26 (nested recursion at the same subject
209        position)" or even infinite loops could occur.
210    
211    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
212        computing the minimum length on reaching *ACCEPT, and so ended up with the
213        wrong value of 1 rather than 0. Further investigation indicates that
214        computing a minimum subject length in the presence of *ACCEPT is difficult
215        (think back references, subroutine calls), and so I have changed the code
216        so that no minimum is registered for a pattern that contains *ACCEPT.
217    
218    8.  If (*THEN) was present in the first (true) branch of a conditional group,
219        it was not handled as intended. [But see 16 below.]
220    
221    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
222        Sheri Pierce.
223    
224    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
225        the first byte in a match must be "a".
226    
227    11. Change 17 for 8.13 increased the recursion depth for patterns like
228        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
229        pattern contains any instances of (*THEN). If it does not, the old
230        optimizations are restored. It would be nice to do this on a per-group
231        basis, but at the moment that is not feasible.
232    
233    12. In some environments, the output of pcretest -C is CRLF terminated. This
234        broke RunTest's code that checks for the link size. A single white space
235        character after the value is now allowed for.
236    
237    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
238        For "fr", it uses the Windows-specific input and output files.
239    
240    14. If (*THEN) appeared in a group that was called recursively or as a
241        subroutine, it did not work as intended. [But see next item.]
242    
243    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
244        pattern fragments (but not containing any | characters). If A and B are
245        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
246        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
247        D. In other words, Perl considers parentheses that do not contain any |
248        characters to be part of a surrounding alternative, whereas PCRE was
249        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
250        differently. PCRE now behaves in the same way as Perl, except in the case
251        of subroutine/recursion calls such as (?1) which have in any case always
252        been different (but PCRE had them first :-).
253    
254    16. Related to 15 above: Perl does not treat the | in a conditional group as
255        creating alternatives. Such a group is treated in the same way as an
256        ordinary group without any | characters when processing (*THEN). PCRE has
257        been changed to match Perl's behaviour.
258    
259    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
260        RunGrepTest script failed.
261    
262    18. Change 22 for version 13 caused atomic groups to use more stack. This is
263        inevitable for groups that contain captures, but it can lead to a lot of
264        stack use in large patterns. The old behaviour has been restored for atomic
265        groups that do not contain any capturing parentheses.
266    
267    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
268        suppress the check for a minimum subject length at run time. (If it was
269        given to pcre_exec() or pcre_dfa_exec() it did work.)
270    
271    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
272        fail to work when decoding hex characters in data strings in EBCDIC
273        environments.
274    
275    21. It appears that in at least one Mac OS environment, the isxdigit() function
276        is implemented as a macro that evaluates to its argument more than once,
277        contravening the C 90 Standard (I haven't checked a later standard). There
278        was an instance in pcretest which caused it to go wrong when processing
279        \x{...} escapes in subject strings. The has been rewritten to avoid using
280        things like p++ in the argument of isxdigit().
281    
282    
283    Version 8.13 16-Aug-2011
284    ------------------------
285    
286    1.  The Unicode data tables have been updated to Unicode 6.0.0.
287    
288    2.  Two minor typos in pcre_internal.h have been fixed.
289    
290    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
291        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
292        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
293    
294    4.  There were a number of related bugs in the code for matching backrefences
295        caselessly in UTF-8 mode when codes for the characters concerned were
296        different numbers of bytes. For example, U+023A and U+2C65 are an upper
297        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
298        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
299        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
300        2-byte code at the end of the subject (it thought there wasn't enough data
301        left).
302    
303    5.  Comprehensive information about what went wrong is now returned by
304        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
305        as the output vector has at least 2 elements. The offset of the start of
306        the failing character and a reason code are placed in the vector.
307    
308    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
309        now returned is for the first byte of the failing character, instead of the
310        last byte inspected. This is an incompatible change, but I hope it is small
311        enough not to be a problem. It makes the returned offset consistent with
312        pcre_exec() and pcre_dfa_exec().
313    
314    7.  pcretest now gives a text phrase as well as the error number when
315        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
316        failure, the offset and reason code are output.
317    
318    8.  When \R was used with a maximizing quantifier it failed to skip backwards
319        over a \r\n pair if the subsequent match failed. Instead, it just skipped
320        back over a single character (\n). This seems wrong (because it treated the
321        two characters as a single entity when going forwards), conflicts with the
322        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
323        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
324        has been changed.
325    
326    9.  Some internal refactoring has changed the processing so that the handling
327        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
328        time (the PCRE_DOTALL option was changed this way some time ago: version
329        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
330        which was always a bit of a fudge. It also means that there is one less
331        argument for the match() function, which reduces its stack requirements
332        slightly. This change also fixes an incompatibility with Perl: the pattern
333        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
334    
335    10. More internal refactoring has drastically reduced the number of recursive
336        calls to match() for possessively repeated groups such as (abc)++ when
337        using pcre_exec().
338    
339    11. While implementing 10, a number of bugs in the handling of groups were
340        discovered and fixed:
341    
342        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
343        (a|)*(?1) gave a compile-time internal error.
344        ((a|)+)+  did not notice that the outer group could match an empty string.
345        (^a|^)+   was not marked as anchored.
346        (.*a|.*)+ was not marked as matching at start or after a newline.
347    
348    12. Yet more internal refactoring has removed another argument from the match()
349        function. Special calls to this function are now indicated by setting a
350        value in a variable in the "match data" data block.
351    
352    13. Be more explicit in pcre_study() instead of relying on "default" for
353        opcodes that mean there is no starting character; this means that when new
354        ones are added and accidentally left out of pcre_study(), testing should
355        pick them up.
356    
357    14. The -s option of pcretest has been documented for ages as being an old
358        synonym of -m (show memory usage). I have changed it to mean "force study
359        for every regex", that is, assume /S for every regex. This is similar to -i
360        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
361        using it. It makes it easier to run collections of tests with and without
362        study enabled, and thereby test pcre_study() more easily. All the standard
363        tests are now run with and without -s (but some patterns can be marked as
364        "never study" - see 20 below).
365    
366    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
367        restoration of the capturing data to the outer values was not happening
368        correctly.
369    
370    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
371        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
372        pattern had matched an empty string, and so incorrectly returned a no
373        match.
374    
375    17. There was optimizing code for the last branch of non-capturing parentheses,
376        and also for the obeyed branch of a conditional subexpression, which used
377        tail recursion to cut down on stack usage. Unfortunately, now that there is
378        the possibility of (*THEN) occurring in these branches, tail recursion is
379        no longer possible because the return has to be checked for (*THEN). These
380        two optimizations have therefore been removed. [But see 8.20/11 above.]
381    
382    18. If a pattern containing \R was studied, it was assumed that \R always
383        matched two bytes, thus causing the minimum subject length to be
384        incorrectly computed because \R can also match just one byte.
385    
386    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
387        was incorrectly computed.
388    
389    20. If /S is present twice on a test pattern in pcretest input, it now
390        *disables* studying, thereby overriding the use of -s on the command line
391        (see 14 above). This is necessary for one or two tests to keep the output
392        identical in both cases.
393    
394    21. When (*ACCEPT) was used in an assertion that matched an empty string and
395        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
396    
397    22. When an atomic group that contained a capturing parenthesis was
398        successfully matched, but the branch in which it appeared failed, the
399        capturing was not being forgotten if a higher numbered group was later
400        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
401        group 1 to "a", when in fact it should be unset. This applied to multi-
402        branched capturing and non-capturing groups, repeated or not, and also to
403        positive assertions (capturing in negative assertions does not happen
404        in PCRE) and also to nested atomic groups.
405    
406    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
407        subject after a captured substring, to make it easier to tell which of a
408        number of identical substrings has been captured.
409    
410    24. The way atomic groups are processed by pcre_exec() has been changed so that
411        if they are repeated, backtracking one repetition now resets captured
412        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
413        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
414        "aaa". Previously, it would have been "a". As part of this code
415        refactoring, the way recursive calls are handled has also been changed.
416    
417    25. If an assertion condition captured any substrings, they were not passed
418        back unless some other capturing happened later. For example, if
419        (?(?=(a))a) was matched against "a", no capturing was returned.
420    
421    26. When studying a pattern that contained subroutine calls or assertions,
422        the code for finding the minimum length of a possible match was handling
423        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
424        group 1 called group 2 while simultaneously a separate group 2 called group
425        1). A stack overflow occurred in this case. I have fixed this by limiting
426        the recursion depth to 10.
427    
428    27. Updated RunTest.bat in the distribution to the version supplied by Tom
429        Fortmann. This supports explicit test numbers on the command line, and has
430        argument validation and error reporting.
431    
432    28. An instance of \X with an unlimited repeat could fail if at any point the
433        first character it looked at was a mark character.
434    
435    29. Some minor code refactoring concerning Unicode properties and scripts
436        should reduce the stack requirement of match() slightly.
437    
438    30. Added the '=' option to pcretest to check the setting of unused capturing
439        slots at the end of the pattern, which are documented as being -1, but are
440        not included in the return count.
441    
442    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
443        compiled something random. Now it gives a compile-time error (as does
444        Perl).
445    
446    32. A *MARK encountered during the processing of a positive assertion is now
447        recorded and passed back (compatible with Perl).
448    
449    33. If --only-matching or --colour was set on a pcregrep call whose pattern
450        had alternative anchored branches, the search for a second match in a line
451        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
452        matched the line "0102" twice. The same bug affected patterns that started
453        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
454        twice.
455    
456    34. Previously, PCRE did not allow quantification of assertions. However, Perl
457        does, and because of capturing effects, quantifying parenthesized
458        assertions may at times be useful. Quantifiers are now allowed for
459        parenthesized assertions.
460    
461    35. A minor code tidy in pcre_compile() when checking options for \R usage.
462    
463    36. \g was being checked for fancy things in a character class, when it should
464        just be a literal "g".
465    
466    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
467        appearance of a nested POSIX class supersedes an apparent external class.
468        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
469        unescaped square brackets may also appear as part of class names. For
470        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
471        more like Perl. (But see 8.20/1 above.)
472    
473    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
474        was because it thought it was \N{name}, which is not supported).
475    
476    39. Add minix to OS list not supporting the -S option in pcretest.
477    
478    40. PCRE tries to detect cases of infinite recursion at compile time, but it
479        cannot analyze patterns in sufficient detail to catch mutual recursions
480        such as ((?1))((?2)). There is now a runtime test that gives an error if a
481        subgroup is called recursively as a subpattern for a second time at the
482        same position in the subject string. In previous releases this might have
483        been caught by the recursion limit, or it might have run out of stack.
484    
485    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
486        happen only once. PCRE was, however incorrectly giving a compile time error
487        "recursive call could loop indefinitely" because it cannot analyze the
488        pattern in sufficient detail. The compile time test no longer happens when
489        PCRE is compiling a conditional subpattern, but actual runaway loops are
490        now caught at runtime (see 40 above).
491    
492    42. It seems that Perl allows any characters other than a closing parenthesis
493        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
494        has been changed to be the same.
495    
496    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
497        as not to get warnings when autogen.sh is called. Also changed
498        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
499    
500    44. To help people who use pcregrep to scan files containing exceedingly long
501        lines, the following changes have been made:
502    
503        (a) The default value of the buffer size parameter has been increased from
504            8K to 20K. (The actual buffer used is three times this size.)
505    
506        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
507            PCRE is built.
508    
509        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
510            to be set at run time.
511    
512        (d) Numerical values in pcregrep options can be followed by K or M, for
513            example --buffer-size=50K.
514    
515        (e) If a line being scanned overflows pcregrep's buffer, an error is now
516            given and the return code is set to 2.
517    
518    45. Add a pointer to the latest mark to the callout data block.
519    
520    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
521        partial match of an empty string instead of no match. This was specific to
522        the use of ".".
523    
524    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
525        complete match instead of a partial match. This bug was dependent on both
526        the PCRE_UTF8 and PCRE_DOTALL options being set.
527    
528    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
529        starting byte set, because \b was not being ignored.
530    
531    
532    Version 8.12 15-Jan-2011
533    ------------------------
534    
535    1.  Fixed some typos in the markup of the man pages, and wrote a script that
536        checks for such things as part of the documentation building process.
537    
538    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
539        --match-limit and --recursion-limit options (added for 8.11). In
540        particular, this made one of the standard tests fail. (The integer value
541        went into the wrong half of a long int.)
542    
543    3.  If the --colour option was given to pcregrep with -v (invert match), it
544        did strange things, either producing crazy output, or crashing. It should,
545        of course, ignore a request for colour when reporting lines that do not
546        match.
547    
548    4.  Another pcregrep bug caused similar problems if --colour was specified with
549        -M (multiline) and the pattern match finished with a line ending.
550    
551    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
552        matched in multiline mode, the following line was shown as part of the
553        match. This seems wrong, so I have changed it.
554    
555    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
556        the check for further matches in the same line (so they could be coloured)
557        to overrun the end of the current line. If another match was found, it was
558        incorrectly shown (and then shown again when found in the next line).
559    
560    7.  If pcregrep was compiled under Windows, there was a reference to the
561        function pcregrep_exit() before it was defined. I am assuming this was
562        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
563        reported by a user. I've moved the definition above the reference.
564    
565    
566    Version 8.11 10-Dec-2010
567    ------------------------
568    
569    1.  (*THEN) was not working properly if there were untried alternatives prior
570        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
571        backtracked to try for "b" instead of moving to the next alternative branch
572        at the same level (in this case, to look for "c"). The Perl documentation
573        is clear that when (*THEN) is backtracked onto, it goes to the "next
574        alternative in the innermost enclosing group".
575    
576    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
577        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
578        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
579        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
580        (*THEN).
581    
582    3.  If \s appeared in a character class, it removed the VT character from
583        the class, even if it had been included by some previous item, for example
584        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
585        of \s, but is part of the POSIX "space" class.)
586    
587    4.  A partial match never returns an empty string (because you can always
588        match an empty string at the end of the subject); however the checking for
589        an empty string was starting at the "start of match" point. This has been
590        changed to the "earliest inspected character" point, because the returned
591        data for a partial match starts at this character. This means that, for
592        example, /(?<=abc)def/ gives a partial match for the subject "abc"
593        (previously it gave "no match").
594    
595    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
596        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
597        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
598        has an implication that the given string is incomplete (because a partial
599        match is preferred over a full match). For this reason, these items now
600        give a partial match in this situation. [Aside: previously, the one case
601        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
602        match rather than a full match, which was wrong by the old rules, but is
603        now correct.]
604    
605    6.  There was a bug in the handling of #-introduced comments, recognized when
606        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
607        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
608        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
609        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
610        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
611        places in pcre_compile().
612    
613    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
614        comments when looking ahead for named forward references to subpatterns,
615        the only newline sequence it recognized was NL. It now handles newlines
616        according to the set newline convention.
617    
618    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
619        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
620        cater for a lack of strerror(). These oversights have been fixed.
621    
622    9.  Added --match-limit and --recursion-limit to pcregrep.
623    
624    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
625    
626    11. When the -o option was used, pcregrep was setting a return code of 1, even
627        when matches were found, and --line-buffered was not being honoured.
628    
629    12. Added an optional parentheses number to the -o and --only-matching options
630        of pcregrep.
631    
632    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
633        can match an empty string. The code to do it in pcretest and pcredemo
634        needed fixing:
635    
636        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
637            only one byte after an empty string match just before CRLF (this case
638            just got forgotten; "any" and "anycrlf" were OK).
639    
640        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
641            mode when an empty string match preceded an ASCII character followed by
642            a non-ASCII character. (The code for advancing by one character rather
643            than one byte was nonsense.)
644    
645        (c) The pcredemo.c sample program did not have any code at all to handle
646            the cases when CRLF is a valid newline sequence.
647    
648    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
649        as a starting offset was within the subject string. There is now a new
650        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
651        negative or greater than the length of the string. In order to test this,
652        pcretest is extended to allow the setting of negative starting offsets.
653    
654    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
655        starting offset points to the beginning of a UTF-8 character was
656        unnecessarily clumsy. I tidied it up.
657    
658    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
659        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
660    
661    17. Nobody had reported that the --include_dir option, which was added in
662        release 7.7 should have been called --include-dir (hyphen, not underscore)
663        for compatibility with GNU grep. I have changed it to --include-dir, but
664        left --include_dir as an undocumented synonym, and the same for
665        --exclude-dir, though that is not available in GNU grep, at least as of
666        release 2.5.4.
667    
668    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
669        characters from a string of bytes) have been redefined so as not to use
670        loops, in order to improve performance in some environments. At the same
671        time, I abstracted some of the common code into auxiliary macros to save
672        repetition (this should not affect the compiled code).
673    
674    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
675        compile-time error is now given if \c is not followed by an ASCII
676        character, that is, a byte less than 128. (In EBCDIC mode, the code is
677        different, and any byte value is allowed.)
678    
679    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
680        START_OPTIMIZE option, which is now allowed at compile time - but just
681        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
682        to pcregrep and other applications that have no direct access to PCRE
683        options. The new /Y option in pcretest sets this option when calling
684        pcre_compile().
685    
686    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
687        back references. Groups containing recursive back references were forced to
688        be atomic by that change, but in the case of named groups, the amount of
689        memory required was incorrectly computed, leading to "Failed: internal
690        error: code overflow". This has been fixed.
691    
692    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
693        pcretest.c, to avoid build problems in some Borland environments.
694    
695    
696    Version 8.10 25-Jun-2010
697  ------------------------  ------------------------
698    
699  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
# Line 9  Version 8.10 03 May-2010 Line 701  Version 8.10 03 May-2010
701    
702  2.  (*ACCEPT) was not working when inside an atomic group.  2.  (*ACCEPT) was not working when inside an atomic group.
703    
704  3.  Inside a character class, \B is treated as a literal by default, but  3.  Inside a character class, \B is treated as a literal by default, but
705      faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option      faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
706      causes the error). The code is unchanged, but I tidied the documentation.      causes the error). The code is unchanged, but I tidied the documentation.
707    
708  4.  Inside a character class, PCRE always treated \R and \X as literals,  4.  Inside a character class, PCRE always treated \R and \X as literals,
709      whereas Perl faults them if its -w option is set. I have changed PCRE so      whereas Perl faults them if its -w option is set. I have changed PCRE so
710      that it faults them when PCRE_EXTRA is set.      that it faults them when PCRE_EXTRA is set.
711    
712  5.  Added support for \N, which always matches any character other than  5.  Added support for \N, which always matches any character other than
713      newline. (It is the same as "." when PCRE_DOTALL is not set.)      newline. (It is the same as "." when PCRE_DOTALL is not set.)
714    
715  6.  When compiling pcregrep with newer versions of gcc which may have  6.  When compiling pcregrep with newer versions of gcc which may have
716      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
717      declared with attribute warn_unused_result" were given. Just casting the      declared with attribute warn_unused_result" were given. Just casting the
718      result to (void) does not stop the warnings; a more elaborate fudge is      result to (void) does not stop the warnings; a more elaborate fudge is
719      needed. I've used a macro to implement this.      needed. I've used a macro to implement this.
720    
721    7.  Minor change to pcretest.c to avoid a compiler warning.
722    
723    8.  Added four artifical Unicode properties to help with an option to make
724        \s etc use properties (see next item). The new properties are: Xan
725        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
726    
727    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
728        use Unicode properties. (*UCP) at the start of a pattern can be used to set
729        this option. Modified pcretest to add /W to test this facility. Added
730        REG_UCP to make it available via the POSIX interface.
731    
732    10. Added --line-buffered to pcregrep.
733    
734    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
735        studied, and the match started with a letter with a code point greater than
736        127 whose first byte was different to the first byte of the other case of
737        the letter, the other case of this starting letter was not recognized
738        (#976).
739    
740    12. If a pattern that was studied started with a repeated Unicode property
741        test, for example, \p{Nd}+, there was the theoretical possibility of
742        setting up an incorrect bitmap of starting bytes, but fortunately it could
743        not have actually happened in practice until change 8 above was made (it
744        added property types that matched character-matching opcodes).
745    
746    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
747        possible starting bytes for non-anchored patterns.
748    
749    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
750        \R, and also a number of cases that involve Unicode properties, both
751        explicit and implicit when PCRE_UCP is set.
752    
753    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
754        input, it could crash or give wrong results if characters with values
755        greater than 0xc0 were present in the subject string. (Detail: it assumed
756        UTF-8 input when processing these items.)
757    
758    16. Added a lot of (int) casts to avoid compiler warnings in systems where
759        size_t is 64-bit (#991).
760    
761    17. Added a check for running out of memory when PCRE is compiled with
762        --disable-stack-for-recursion (#990).
763    
764    18. If the last data line in a file for pcretest does not have a newline on
765        the end, a newline was missing in the output.
766    
767    19. The default pcre_chartables.c file recognizes only ASCII characters (values
768        less than 128) in its various bitmaps. However, there is a facility for
769        generating tables according to the current locale when PCRE is compiled. It
770        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
771        characters, are recognized by isspace() and therefore were getting set in
772        these tables, and indeed these tables seem to approximate to ISO 8859. This
773        caused a problem in UTF-8 mode when pcre_study() was used to create a list
774        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
775        which of course cannot start UTF-8 characters. I have changed the code so
776        that only real ASCII characters (less than 128) and the correct starting
777        bytes for UTF-8 encodings are set for characters greater than 127 when in
778        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
779        altogether.)
780    
781    20. Added the /T option to pcretest so as to be able to run tests with non-
782        standard character tables, thus making it possible to include the tests
783        used for 19 above in the standard set of tests.
784    
785    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
786        reference to a subpattern the other side of a comment that contains an
787        opening parenthesis caused either an internal compiling error, or a
788        reference to the wrong subpattern.
789    
790    
791  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Legend:
Removed from v.515  
changed lines
  Added in v.886

  ViewVC Help
Powered by ViewVC 1.1.5