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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.648  
changed lines
  Added in v.743

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12