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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.532  
changed lines
  Added in v.919

  ViewVC Help
Powered by ViewVC 1.1.5