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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.641  
changed lines
  Added in v.758

  ViewVC Help
Powered by ViewVC 1.1.5