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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.644  
changed lines
  Added in v.753

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12