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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.604  
changed lines
  Added in v.779

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12