/[pcre]/code/branches/pcre16/ChangeLog
ViewVC logotype

Diff of /code/branches/pcre16/ChangeLog

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

code/trunk/ChangeLog revision 616 by ph10, Mon Jul 11 15:55:25 2011 UTC code/branches/pcre16/ChangeLog revision 818 by ph10, Thu Dec 22 20:11:31 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.13 30-Apr-2011  Version 8.22
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 the code for calculating the fixed length of lookbehind
11        assertions.
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    
17    Version 8.21 12-Dec-2011
18    ------------------------
19    
20    1.  Updating the JIT compiler.
21    
22    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
23        are added as well.
24    
25    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
26        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
27        calling _pcre_jit_exec. Some extra comments are added.
28    
29    4.  (*MARK) settings inside atomic groups that do not contain any capturing
30        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
31        was introduced by change 18 for 8.20.
32    
33    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
34        ECMA-262 standard.
35    
36    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
37        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
38        This bug was probably introduced by change 9 of 8.13.
39    
40    7.  While fixing 6 above, I noticed that a number of other items were being
41        incorrectly rejected as "not fixed length". This arose partly because newer
42        opcodes had not been added to the fixed-length checking code. I have (a)
43        corrected the bug and added tests for these items, and (b) arranged for an
44        error to occur if an unknown opcode is encountered while checking for fixed
45        length instead of just assuming "not fixed length". The items that were
46        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
47        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
48        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
49    
50    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
51        being incorrectly compiled and would have given unpredicatble results.
52    
53    9.  A possessively repeated subpattern with minimum repeat count greater than
54        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
55        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
56        the first (A) could occur when it should not.
57    
58    10. Add a cast and remove a redundant test from the code.
59    
60    11. JIT should use pcre_malloc/pcre_free for allocation.
61    
62    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
63        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
64        is anything other than /usr, -L is still shown).
65    
66    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
67    
68    14. Perl does not support \N without a following name in a [] class; PCRE now
69        also gives an error.
70    
71    15. If a forward reference was repeated with an upper limit of around 2000,
72        it caused the error "internal error: overran compiling workspace". The
73        maximum number of forward references (including repeats) was limited by the
74        internal workspace, and dependent on the LINK_SIZE. The code has been
75        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
76        the default depends on LINK_SIZE. There is a new upper limit (for safety)
77        of around 200,000 forward references. While doing this, I also speeded up
78        the filling in of repeated forward references.
79    
80    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
81        incorrectly expecting the subject to contain another "a" after the start.
82    
83    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
84        in the match, the SKIP should be ignored. This was not happening; instead
85        the SKIP was being treated as NOMATCH. For patterns such as
86        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
87        tested.
88    
89    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
90        now much more compatible with Perl, in particular in cases where the result
91        is a non-match for a non-anchored pattern. For example, if
92        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
93        "m", where previously it did not return a name. A side effect of this
94        change is that for partial matches, the last encountered mark name is
95        returned, as for non matches. A number of tests that were previously not
96        Perl-compatible have been moved into the Perl-compatible test files. The
97        refactoring has had the pleasing side effect of removing one argument from
98        the match() function, thus reducing its stack requirements.
99    
100    19. If the /S+ option was used in pcretest to study a pattern using JIT,
101        subsequent uses of /S (without +) incorrectly behaved like /S+.
102    
103    21. Retrieve executable code size support for the JIT compiler and fixing
104        some warnings.
105    
106    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
107        not work when the shorter character appeared right at the end of the
108        subject string.
109    
110    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
111        systems.
112    
113    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
114        output it when the /M option is used in pcretest.
115    
116    25. The CheckMan script was not being included in the distribution. Also, added
117        an explicit "perl" to run Perl scripts from the PrepareRelease script
118        because this is reportedly needed in Windows.
119    
120    26. If study data was being save in a file and studying had not found a set of
121        "starts with" bytes for the pattern, the data written to the file (though
122        never used) was taken from uninitialized memory and so caused valgrind to
123        complain.
124    
125    27. Updated RunTest.bat as provided by Sheri Pierce.
126    
127    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
128    
129    29. Computation of memory usage for the table of capturing group names was
130        giving an unnecessarily large value.
131    
132    
133    Version 8.20 21-Oct-2011
134    ------------------------
135    
136    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
137        a POSIX class. After further experiments with Perl, which convinced me that
138        Perl has bugs and confusions, a closing square bracket is no longer allowed
139        in a POSIX name. This bug also affected patterns with classes that started
140        with full stops.
141    
142    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
143        captured substring, but while checking the failing first alternative,
144        substring 1 is temporarily captured. If the output vector supplied to
145        pcre_exec() was not big enough for this capture, the yield of the function
146        was still zero ("insufficient space for captured substrings"). This cannot
147        be totally fixed without adding another stack variable, which seems a lot
148        of expense for a edge case. However, I have improved the situation in cases
149        such as /(a)(b)x|abc/ matched against "abc", where the return code
150        indicates that fewer than the maximum number of slots in the ovector have
151        been set.
152    
153    3.  Related to (2) above: when there are more back references in a pattern than
154        slots in the output vector, pcre_exec() uses temporary memory during
155        matching, and copies in the captures as far as possible afterwards. It was
156        using the entire output vector, but this conflicts with the specification
157        that only 2/3 is used for passing back captured substrings. Now it uses
158        only the first 2/3, for compatibility. This is, of course, another edge
159        case.
160    
161    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
162        main code base, and can be used by building with --enable-jit. When this is
163        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
164        runtime --no-jit option is given.
165    
166    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
167        ovector, the return from the function was zero, implying that there were
168        other matches that did not fit. The correct "exactly full" value is now
169        returned.
170    
171    6.  If a subpattern that was called recursively or as a subroutine contained
172        (*PRUNE) or any other control that caused it to give a non-standard return,
173        invalid errors such as "Error -26 (nested recursion at the same subject
174        position)" or even infinite loops could occur.
175    
176    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
177        computing the minimum length on reaching *ACCEPT, and so ended up with the
178        wrong value of 1 rather than 0. Further investigation indicates that
179        computing a minimum subject length in the presence of *ACCEPT is difficult
180        (think back references, subroutine calls), and so I have changed the code
181        so that no minimum is registered for a pattern that contains *ACCEPT.
182    
183    8.  If (*THEN) was present in the first (true) branch of a conditional group,
184        it was not handled as intended. [But see 16 below.]
185    
186    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
187        Sheri Pierce.
188    
189    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
190        the first byte in a match must be "a".
191    
192    11. Change 17 for 8.13 increased the recursion depth for patterns like
193        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
194        pattern contains any instances of (*THEN). If it does not, the old
195        optimizations are restored. It would be nice to do this on a per-group
196        basis, but at the moment that is not feasible.
197    
198    12. In some environments, the output of pcretest -C is CRLF terminated. This
199        broke RunTest's code that checks for the link size. A single white space
200        character after the value is now allowed for.
201    
202    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
203        For "fr", it uses the Windows-specific input and output files.
204    
205    14. If (*THEN) appeared in a group that was called recursively or as a
206        subroutine, it did not work as intended. [But see next item.]
207    
208    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
209        pattern fragments (but not containing any | characters). If A and B are
210        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
211        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
212        D. In other words, Perl considers parentheses that do not contain any |
213        characters to be part of a surrounding alternative, whereas PCRE was
214        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
215        differently. PCRE now behaves in the same way as Perl, except in the case
216        of subroutine/recursion calls such as (?1) which have in any case always
217        been different (but PCRE had them first :-).
218    
219    16. Related to 15 above: Perl does not treat the | in a conditional group as
220        creating alternatives. Such a group is treated in the same way as an
221        ordinary group without any | characters when processing (*THEN). PCRE has
222        been changed to match Perl's behaviour.
223    
224    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
225        RunGrepTest script failed.
226    
227    18. Change 22 for version 13 caused atomic groups to use more stack. This is
228        inevitable for groups that contain captures, but it can lead to a lot of
229        stack use in large patterns. The old behaviour has been restored for atomic
230        groups that do not contain any capturing parentheses.
231    
232    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
233        suppress the check for a minimum subject length at run time. (If it was
234        given to pcre_exec() or pcre_dfa_exec() it did work.)
235    
236    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
237        fail to work when decoding hex characters in data strings in EBCDIC
238        environments.
239    
240    21. It appears that in at least one Mac OS environment, the isxdigit() function
241        is implemented as a macro that evaluates to its argument more than once,
242        contravening the C 90 Standard (I haven't checked a later standard). There
243        was an instance in pcretest which caused it to go wrong when processing
244        \x{...} escapes in subject strings. The has been rewritten to avoid using
245        things like p++ in the argument of isxdigit().
246    
247    
248    Version 8.13 16-Aug-2011
249  ------------------------  ------------------------
250    
251  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 20  Version 8.13 30-Apr-2011 Line 264  Version 8.13 30-Apr-2011
264      code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a      code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
265      2-byte code at the end of the subject (it thought there wasn't enough data      2-byte code at the end of the subject (it thought there wasn't enough data
266      left).      left).
267    
268  5.  Comprehensive information about what went wrong is now returned by  5.  Comprehensive information about what went wrong is now returned by
269      pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long      pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
270      as the output vector has at least 2 elements. The offset of the start of      as the output vector has at least 2 elements. The offset of the start of
271      the failing character and a reason code are placed in the vector.      the failing character and a reason code are placed in the vector.
272    
273  6.  When the UTF-8 string check fails for pcre_compile(), the offset that is  6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
274      now returned is for the first byte of the failing character, instead of the      now returned is for the first byte of the failing character, instead of the
275      last byte inspected. This is an incompatible change, but I hope it is small      last byte inspected. This is an incompatible change, but I hope it is small
276      enough not to be a problem. It makes the returned offset consistent with      enough not to be a problem. It makes the returned offset consistent with
277      pcre_exec() and pcre_dfa_exec().      pcre_exec() and pcre_dfa_exec().
278    
279  7.  pcretest now gives a text phrase as well as the error number when  7.  pcretest now gives a text phrase as well as the error number when
280      pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check      pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
281      failure, the offset and reason code are output.      failure, the offset and reason code are output.
282    
283  8.  When \R was used with a maximizing quantifier it failed to skip backwards  8.  When \R was used with a maximizing quantifier it failed to skip backwards
284      over a \r\n pair if the subsequent match failed. Instead, it just skipped      over a \r\n pair if the subsequent match failed. Instead, it just skipped
285      back over a single character (\n). This seems wrong (because it treated the      back over a single character (\n). This seems wrong (because it treated the
286      two characters as a single entity when going forwards), conflicts with the      two characters as a single entity when going forwards), conflicts with the
287      documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the      documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
288      behaviour of \R* different to (\R)*, which also seems wrong. The behaviour      behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
289      has been changed.      has been changed.
290    
291  9.  Some internal refactoring has changed the processing so that the handling  9.  Some internal refactoring has changed the processing so that the handling
292      of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile      of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
293      time (the PCRE_DOTALL option was changed this way some time ago: version      time (the PCRE_DOTALL option was changed this way some time ago: version
294      7.7 change 16). This has made it possible to abolish the OP_OPT op code,      7.7 change 16). This has made it possible to abolish the OP_OPT op code,
295      which was always a bit of a fudge. It also means that there is one less      which was always a bit of a fudge. It also means that there is one less
296      argument for the match() function, which reduces its stack requirements      argument for the match() function, which reduces its stack requirements
297      slightly. This change also fixes an incompatibility with Perl: the pattern      slightly. This change also fixes an incompatibility with Perl: the pattern
298      (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.      (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
299    
300  10. More internal refactoring has drastically reduced the number of recursive  10. More internal refactoring has drastically reduced the number of recursive
301      calls to match() for possessively repeated groups such as (abc)++ when      calls to match() for possessively repeated groups such as (abc)++ when
302      using pcre_exec().      using pcre_exec().
303    
304  11. While implementing 10, a number of bugs in the handling of groups were  11. While implementing 10, a number of bugs in the handling of groups were
305      discovered and fixed:      discovered and fixed:
306    
307      (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).      (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
308      (a|)*(?1) gave a compile-time internal error.      (a|)*(?1) gave a compile-time internal error.
309      ((a|)+)+  did not notice that the outer group could match an empty string.      ((a|)+)+  did not notice that the outer group could match an empty string.
310      (^a|^)+   was not marked as anchored.      (^a|^)+   was not marked as anchored.
311      (.*a|.*)+ was not marked as matching at start or after a newline.      (.*a|.*)+ was not marked as matching at start or after a newline.
312    
313  12. Yet more internal refactoring has removed another argument from the match()  12. Yet more internal refactoring has removed another argument from the match()
314      function. Special calls to this function are now indicated by setting a      function. Special calls to this function are now indicated by setting a
315      value in a variable in the "match data" data block.      value in a variable in the "match data" data block.
316    
317  13. Be more explicit in pcre_study() instead of relying on "default" for  13. Be more explicit in pcre_study() instead of relying on "default" for
318      opcodes that mean there is no starting character; this means that when new      opcodes that mean there is no starting character; this means that when new
319      ones are added and accidentally left out of pcre_study(), testing should      ones are added and accidentally left out of pcre_study(), testing should
320      pick them up.      pick them up.
321    
322  14. The -s option of pcretest has been documented for ages as being an old  14. The -s option of pcretest has been documented for ages as being an old
323      synonym of -m (show memory usage). I have changed it to mean "force study      synonym of -m (show memory usage). I have changed it to mean "force study
324      for every regex", that is, assume /S for every regex. This is similar to -i      for every regex", that is, assume /S for every regex. This is similar to -i
325      and -d etc. It's slightly incompatible, but I'm hoping nobody is still      and -d etc. It's slightly incompatible, but I'm hoping nobody is still
326      using it. It makes it easier to run collections of tests with and without      using it. It makes it easier to run collections of tests with and without
327      study enabled, and thereby test pcre_study() more easily. All the standard      study enabled, and thereby test pcre_study() more easily. All the standard
328      tests are now run with and without -s (but some patterns can be marked as      tests are now run with and without -s (but some patterns can be marked as
329      "never study" - see 20 below).      "never study" - see 20 below).
330    
331  15. When (*ACCEPT) was used in a subpattern that was called recursively, the  15. When (*ACCEPT) was used in a subpattern that was called recursively, the
332      restoration of the capturing data to the outer values was not happening      restoration of the capturing data to the outer values was not happening
333      correctly.      correctly.
334    
335  16. If a recursively called subpattern ended with (*ACCEPT) and matched an  16. If a recursively called subpattern ended with (*ACCEPT) and matched an
336      empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole      empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
337      pattern had matched an empty string, and so incorrectly returned a no      pattern had matched an empty string, and so incorrectly returned a no
338      match.      match.
339    
340  17. There was optimizing code for the last branch of non-capturing parentheses,  17. There was optimizing code for the last branch of non-capturing parentheses,
341      and also for the obeyed branch of a conditional subexpression, which used      and also for the obeyed branch of a conditional subexpression, which used
342      tail recursion to cut down on stack usage. Unfortunately, not that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
343      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
344      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
345      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
346    
347  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
348      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
349      incorrectly computed because \R can also match just one byte.      incorrectly computed because \R can also match just one byte.
350    
351  19. If a pattern containing (*ACCEPT) was studied, the minimum subject length  19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
352      was incorrectly computed.      was incorrectly computed.
353    
354  20. If /S is present twice on a test pattern in pcretest input, it *disables*  20. If /S is present twice on a test pattern in pcretest input, it now
355      studying, thereby overriding the use of -s on the command line. This is      *disables* studying, thereby overriding the use of -s on the command line
356      necessary for one or two tests to keep the output identical in both cases.      (see 14 above). This is necessary for one or two tests to keep the output
357        identical in both cases.
358    
359  21. When (*ACCEPT) was used in an assertion that matched an empty string and  21. When (*ACCEPT) was used in an assertion that matched an empty string and
360      PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.      PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
361    
362  22. When an atomic group that contained a capturing parenthesis was  22. When an atomic group that contained a capturing parenthesis was
363      successfully matched, but the branch in which it appeared failed, the      successfully matched, but the branch in which it appeared failed, the
364      capturing was not being forgotten if a higher numbered group was later      capturing was not being forgotten if a higher numbered group was later
365      captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing      captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
366      group 1 to "a", when in fact it should be unset. This applied to multi-      group 1 to "a", when in fact it should be unset. This applied to multi-
367      branched capturing and non-capturing groups, repeated or not, and also to      branched capturing and non-capturing groups, repeated or not, and also to
368      positive assertions (capturing in negative assertions is not well defined      positive assertions (capturing in negative assertions does not happen
369      in PCRE) and also to nested atomic groups.      in PCRE) and also to nested atomic groups.
370    
371  23. Add the ++ qualifier feature to pcretest, to show the remainder of the  23. Add the ++ qualifier feature to pcretest, to show the remainder of the
372      subject after a captured substring (to make it easier to tell which of a      subject after a captured substring, to make it easier to tell which of a
373      number of identical substrings has been captured).      number of identical substrings has been captured.
374    
375    24. The way atomic groups are processed by pcre_exec() has been changed so that
376        if they are repeated, backtracking one repetition now resets captured
377        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
378        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
379        "aaa". Previously, it would have been "a". As part of this code
380        refactoring, the way recursive calls are handled has also been changed.
381    
382    25. If an assertion condition captured any substrings, they were not passed
383        back unless some other capturing happened later. For example, if
384        (?(?=(a))a) was matched against "a", no capturing was returned.
385    
386    26. When studying a pattern that contained subroutine calls or assertions,
387        the code for finding the minimum length of a possible match was handling
388        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
389        group 1 called group 2 while simultaneously a separate group 2 called group
390        1). A stack overflow occurred in this case. I have fixed this by limiting
391        the recursion depth to 10.
392    
393    27. Updated RunTest.bat in the distribution to the version supplied by Tom
394        Fortmann. This supports explicit test numbers on the command line, and has
395        argument validation and error reporting.
396    
397    28. An instance of \X with an unlimited repeat could fail if at any point the
398        first character it looked at was a mark character.
399    
400    29. Some minor code refactoring concerning Unicode properties and scripts
401        should reduce the stack requirement of match() slightly.
402    
403    30. Added the '=' option to pcretest to check the setting of unused capturing
404        slots at the end of the pattern, which are documented as being -1, but are
405        not included in the return count.
406    
407    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
408        compiled something random. Now it gives a compile-time error (as does
409        Perl).
410    
411    32. A *MARK encountered during the processing of a positive assertion is now
412        recorded and passed back (compatible with Perl).
413    
414    33. If --only-matching or --colour was set on a pcregrep call whose pattern
415        had alternative anchored branches, the search for a second match in a line
416        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
417        matched the line "0102" twice. The same bug affected patterns that started
418        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
419        twice.
420    
421    34. Previously, PCRE did not allow quantification of assertions. However, Perl
422        does, and because of capturing effects, quantifying parenthesized
423        assertions may at times be useful. Quantifiers are now allowed for
424        parenthesized assertions.
425    
426    35. A minor code tidy in pcre_compile() when checking options for \R usage.
427    
428    36. \g was being checked for fancy things in a character class, when it should
429        just be a literal "g".
430    
431    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
432        appearance of a nested POSIX class supersedes an apparent external class.
433        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
434        unescaped square brackets may also appear as part of class names. For
435        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
436        more like Perl. (But see 8.20/1 above.)
437    
438    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
439        was because it thought it was \N{name}, which is not supported).
440    
441    39. Add minix to OS list not supporting the -S option in pcretest.
442    
443    40. PCRE tries to detect cases of infinite recursion at compile time, but it
444        cannot analyze patterns in sufficient detail to catch mutual recursions
445        such as ((?1))((?2)). There is now a runtime test that gives an error if a
446        subgroup is called recursively as a subpattern for a second time at the
447        same position in the subject string. In previous releases this might have
448        been caught by the recursion limit, or it might have run out of stack.
449    
450    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
451        happen only once. PCRE was, however incorrectly giving a compile time error
452        "recursive call could loop indefinitely" because it cannot analyze the
453        pattern in sufficient detail. The compile time test no longer happens when
454        PCRE is compiling a conditional subpattern, but actual runaway loops are
455        now caught at runtime (see 40 above).
456    
457    42. It seems that Perl allows any characters other than a closing parenthesis
458        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
459        has been changed to be the same.
460    
461    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
462        as not to get warnings when autogen.sh is called. Also changed
463        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
464    
465    44. To help people who use pcregrep to scan files containing exceedingly long
466        lines, the following changes have been made:
467    
468        (a) The default value of the buffer size parameter has been increased from
469            8K to 20K. (The actual buffer used is three times this size.)
470    
471        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
472            PCRE is built.
473    
474        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
475            to be set at run time.
476    
477        (d) Numerical values in pcregrep options can be followed by K or M, for
478            example --buffer-size=50K.
479    
480        (e) If a line being scanned overflows pcregrep's buffer, an error is now
481            given and the return code is set to 2.
482    
483    45. Add a pointer to the latest mark to the callout data block.
484    
485    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
486        partial match of an empty string instead of no match. This was specific to
487        the use of ".".
488    
489    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
490        complete match instead of a partial match. This bug was dependent on both
491        the PCRE_UTF8 and PCRE_DOTALL options being set.
492    
493    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
494        starting byte set, because \b was not being ignored.
495    
496    
497  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011

Legend:
Removed from v.616  
changed lines
  Added in v.818

  ViewVC Help
Powered by ViewVC 1.1.5