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

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 1019 by ph10, Mon Aug 27 13:15:02 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.13 02-Aug-2011  Version 8.32
5    ------------
6    
7    1.  Improved JIT compiler optimizations for first character search and single
8        character iterators.
9    
10    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
11        Patch by Daniel Richard G.
12    
13    3.  Single character iterator optimizations in the JIT compiler.
14    
15    4.  Improved JIT compiler optimizations for character ranges.
16    
17    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
18        Reported by Giuseppe D'Angelo.
19    
20    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
21        of a line, was being set incorrectly in cases where .* appeared inside
22        atomic brackets at the start of a pattern, or where there was a subsequent
23        *PRUNE or *SKIP.
24    
25    7.  Improved instruction cache flush for POWER/PowerPC.
26        Patch by Daniel Richard G.
27    
28    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
29        grep:
30    
31        (a) There is now no limit to the number of patterns to be matched.
32    
33        (b) An error is given if a pattern is too long.
34    
35        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
36            are now supported.
37    
38        (d) --exclude-from and --include-from (multiple use) have been added.
39    
40        (e) Exclusions and inclusions now apply to all files and directories, not
41            just to those obtained from scanning a directory recursively.
42    
43        (f) Multiple uses of -f and --file-list are now supported.
44    
45        (g) In a Windows environment, the default for -d has been changed from
46            "read" (the GNU grep default) to "skip", because otherwise the presence
47            of a directory in the file list provokes an error.
48    
49        (h) The documentation has been revised and clarified in places.
50    
51    9.  Improve the matching speed of capturing brackets.
52    
53    10. Changed the meaning of \X so that it now matches a Unicode extended
54        grapheme cluster.
55    
56    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
57        out POSIX threads when JIT support is configured.
58    
59    
60    
61    Version 8.31 06-July-2012
62    -------------------------
63    
64    1.  Fixing a wrong JIT test case and some compiler warnings.
65    
66    2.  Removed a bashism from the RunTest script.
67    
68    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
69        to unsigned type, result still unsigned" that was given by an MS compiler
70        on encountering the code "-sizeof(xxx)".
71    
72    4.  Partial matching support is added to the JIT compiler.
73    
74    5.  Fixed several bugs concerned with partial matching of items that consist
75        of more than one character:
76    
77        (a) /^(..)\1/ did not partially match "aba" because checking references was
78            done on an "all or nothing" basis. This also applied to repeated
79            references.
80    
81        (b) \R did not give a hard partial match if \r was found at the end of the
82            subject.
83    
84        (c) \X did not give a hard partial match after matching one or more
85            characters at the end of the subject.
86    
87        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
88            a partial match for the string "\r".
89    
90        (e) When newline was set to CRLF, the metacharacter "." did not recognize
91            a partial match for a CR character at the end of the subject string.
92    
93    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
94        running pcretest, the text "(JIT)" added to the output whenever JIT is
95        actually used to run the match.
96    
97    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
98        or /S+[+] with a digit between 1 and 7.
99    
100    8.  OP_NOT now supports any UTF character not just single-byte ones.
101    
102    9.  (*MARK) control verb is now supported by the JIT compiler.
103    
104    10. The command "./RunTest list" lists the available tests without actually
105        running any of them. (Because I keep forgetting what they all are.)
106    
107    11. Add PCRE_INFO_MAXLOOKBEHIND.
108    
109    12. Applied a (slightly modified) user-supplied patch that improves performance
110        when the heap is used for recursion (compiled with --disable-stack-for-
111        recursion). Instead of malloc and free for each heap frame each time a
112        logical recursion happens, frames are retained on a chain and re-used where
113        possible. This sometimes gives as much as 30% improvement.
114    
115    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
116        call.
117    
118    14. As documented, (*COMMIT) is now confined to within a positive assertion.
119    
120    15. It is now possible to link pcretest with libedit as an alternative to
121        libreadline.
122    
123    16. (*COMMIT) control verb is now supported by the JIT compiler.
124    
125    17. The Unicode data tables have been updated to Unicode 6.1.0.
126    
127    18. Added --file-list option to pcregrep.
128    
129    19. Added binary file support to pcregrep, including the -a, --binary-files,
130        -I, and --text options.
131    
132    20. The madvise function is renamed for posix_madvise for QNX compatibility
133        reasons. Fixed by Giuseppe D'Angelo.
134    
135    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
136    
137    22. Changed the option for creating symbolic links for 16-bit man pages from
138        -s to -sf so that re-installing does not cause issues.
139    
140    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
141    
142    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
143        matches in certain environments (the workspace was not being correctly
144        retained). Also added to pcre_dfa_exec() a simple plausibility check on
145        some of the workspace data at the beginning of a restart.
146    
147    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
148        was not doing so when it should - probably a typo introduced by SVN 528
149        (change 8.10/14).
150    
151    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
152        \w+ when the character tables indicated that \x{c4} was a word character.
153        There were several related cases, all because the tests for doing a table
154        lookup were testing for characters less than 127 instead of 255.
155    
156    27. If a pattern contains capturing parentheses that are not used in a match,
157        their slots in the ovector are set to -1. For those that are higher than
158        any matched groups, this happens at the end of processing. In the case when
159        there were back references that the ovector was too small to contain
160        (causing temporary malloc'd memory to be used during matching), and the
161        highest capturing number was not used, memory off the end of the ovector
162        was incorrectly being set to -1. (It was using the size of the temporary
163        memory instead of the true size.)
164    
165    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
166        ovector size, it uses memory at the end of the block that it has got.
167    
168    29. Check for an overlong MARK name and give an error at compile time. The
169        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
170    
171    30. JIT compiler update.
172    
173    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
174        Rill for the patch.
175    
176    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
177    
178    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
179    
180    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
181        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
182        was enabled.
183    
184    35. Improve JIT code generation for greedy plus quantifier.
185    
186    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
187        1 to "aa" instead of to an empty string. The bug affected repeated groups
188        that could potentially match an empty string.
189    
190    37. Optimizing single character iterators in JIT.
191    
192    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
193        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
194        codepoints that are too big for the mode are faulted, and in a UTF mode,
195        disallowed codepoints are also faulted.
196    
197    39. If PCRE was compiled with UTF support, in three places in the DFA
198        matcher there was code that should only have been obeyed in UTF mode, but
199        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
200        processing when bytes with values greater than 127 were present. In 16-bit
201        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
202        both cases the values are those that cannot be the first data item in a UTF
203        character. The three items that might have provoked this were recursions,
204        possessively repeated groups, and atomic groups.
205    
206    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
207        and pcregrep, because some OS require shared objects to be explicitly
208        passed to ld, causing the link step to fail if they are not.
209    
210    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
211        mode, patterns that started with \h* or \R* might be incorrectly matched.
212    
213    
214    Version 8.30 04-February-2012
215    -----------------------------
216    
217    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
218        name is defined in ctype.h.
219    
220    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
221        only in quite long subpatterns.
222    
223    3.  Removed the function pcre_info(), which has been obsolete and deprecated
224        since it was replaced by pcre_fullinfo() in February 2000.
225    
226    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
227        match a (*MARK), and the match failed at the start of the subject, a
228        reference to memory before the start of the subject could occur. This bug
229        was introduced by fix 17 of release 8.21.
230    
231    5.  A reference to an unset group with zero minimum repetition was giving
232        totally wrong answers (in non-JavaScript-compatibility mode). For example,
233        /(another)?(\1?)test/ matched against "hello world test". This bug was
234        introduced in release 8.13.
235    
236    6.  Add support for 16-bit character strings (a large amount of work involving
237        many changes and refactorings).
238    
239    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
240        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
241        from a file.
242    
243    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
244        rounding is not applied in this particular case).
245    
246    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
247        if they appear, or are escaped, in patterns.
248    
249    10. Get rid of a number of -Wunused-but-set-variable warnings.
250    
251    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
252        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
253        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
254        also returns the mark "x". This bug applied to capturing parentheses,
255        non-capturing parentheses, and atomic parentheses. It also applied to some
256        assertions.
257    
258    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
259        information out of configure.ac instead of relying on pcre.h.generic, which
260        is not stored in the repository.
261    
262    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
263        -lreadline.
264    
265    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
266    
267    15. Applied Graycode's patch to put the top-level frame on the stack rather
268        than the heap when not using the stack for recursion. This gives a
269        performance improvement in many cases when recursion is not deep.
270    
271    16. Experimental code added to "pcretest -C" to output the stack frame size.
272    
273    
274    Version 8.21 12-Dec-2011
275    ------------------------
276    
277    1.  Updating the JIT compiler.
278    
279    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
280        are added as well.
281    
282    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
283        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
284        calling _pcre_jit_exec. Some extra comments are added.
285    
286    4.  (*MARK) settings inside atomic groups that do not contain any capturing
287        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
288        was introduced by change 18 for 8.20.
289    
290    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
291        ECMA-262 standard.
292    
293    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
294        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
295        This bug was probably introduced by change 9 of 8.13.
296    
297    7.  While fixing 6 above, I noticed that a number of other items were being
298        incorrectly rejected as "not fixed length". This arose partly because newer
299        opcodes had not been added to the fixed-length checking code. I have (a)
300        corrected the bug and added tests for these items, and (b) arranged for an
301        error to occur if an unknown opcode is encountered while checking for fixed
302        length instead of just assuming "not fixed length". The items that were
303        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
304        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
305        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
306    
307    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
308        being incorrectly compiled and would have given unpredicatble results.
309    
310    9.  A possessively repeated subpattern with minimum repeat count greater than
311        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
312        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
313        the first (A) could occur when it should not.
314    
315    10. Add a cast and remove a redundant test from the code.
316    
317    11. JIT should use pcre_malloc/pcre_free for allocation.
318    
319    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
320        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
321        is anything other than /usr, -L is still shown).
322    
323    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
324    
325    14. Perl does not support \N without a following name in a [] class; PCRE now
326        also gives an error.
327    
328    15. If a forward reference was repeated with an upper limit of around 2000,
329        it caused the error "internal error: overran compiling workspace". The
330        maximum number of forward references (including repeats) was limited by the
331        internal workspace, and dependent on the LINK_SIZE. The code has been
332        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
333        the default depends on LINK_SIZE. There is a new upper limit (for safety)
334        of around 200,000 forward references. While doing this, I also speeded up
335        the filling in of repeated forward references.
336    
337    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
338        incorrectly expecting the subject to contain another "a" after the start.
339    
340    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
341        in the match, the SKIP should be ignored. This was not happening; instead
342        the SKIP was being treated as NOMATCH. For patterns such as
343        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
344        tested.
345    
346    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
347        now much more compatible with Perl, in particular in cases where the result
348        is a non-match for a non-anchored pattern. For example, if
349        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
350        "m", where previously it did not return a name. A side effect of this
351        change is that for partial matches, the last encountered mark name is
352        returned, as for non matches. A number of tests that were previously not
353        Perl-compatible have been moved into the Perl-compatible test files. The
354        refactoring has had the pleasing side effect of removing one argument from
355        the match() function, thus reducing its stack requirements.
356    
357    19. If the /S+ option was used in pcretest to study a pattern using JIT,
358        subsequent uses of /S (without +) incorrectly behaved like /S+.
359    
360    21. Retrieve executable code size support for the JIT compiler and fixing
361        some warnings.
362    
363    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
364        not work when the shorter character appeared right at the end of the
365        subject string.
366    
367    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
368        systems.
369    
370    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
371        output it when the /M option is used in pcretest.
372    
373    25. The CheckMan script was not being included in the distribution. Also, added
374        an explicit "perl" to run Perl scripts from the PrepareRelease script
375        because this is reportedly needed in Windows.
376    
377    26. If study data was being save in a file and studying had not found a set of
378        "starts with" bytes for the pattern, the data written to the file (though
379        never used) was taken from uninitialized memory and so caused valgrind to
380        complain.
381    
382    27. Updated RunTest.bat as provided by Sheri Pierce.
383    
384    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
385    
386    29. Computation of memory usage for the table of capturing group names was
387        giving an unnecessarily large value.
388    
389    
390    Version 8.20 21-Oct-2011
391    ------------------------
392    
393    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
394        a POSIX class. After further experiments with Perl, which convinced me that
395        Perl has bugs and confusions, a closing square bracket is no longer allowed
396        in a POSIX name. This bug also affected patterns with classes that started
397        with full stops.
398    
399    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
400        captured substring, but while checking the failing first alternative,
401        substring 1 is temporarily captured. If the output vector supplied to
402        pcre_exec() was not big enough for this capture, the yield of the function
403        was still zero ("insufficient space for captured substrings"). This cannot
404        be totally fixed without adding another stack variable, which seems a lot
405        of expense for a edge case. However, I have improved the situation in cases
406        such as /(a)(b)x|abc/ matched against "abc", where the return code
407        indicates that fewer than the maximum number of slots in the ovector have
408        been set.
409    
410    3.  Related to (2) above: when there are more back references in a pattern than
411        slots in the output vector, pcre_exec() uses temporary memory during
412        matching, and copies in the captures as far as possible afterwards. It was
413        using the entire output vector, but this conflicts with the specification
414        that only 2/3 is used for passing back captured substrings. Now it uses
415        only the first 2/3, for compatibility. This is, of course, another edge
416        case.
417    
418    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
419        main code base, and can be used by building with --enable-jit. When this is
420        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
421        runtime --no-jit option is given.
422    
423    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
424        ovector, the return from the function was zero, implying that there were
425        other matches that did not fit. The correct "exactly full" value is now
426        returned.
427    
428    6.  If a subpattern that was called recursively or as a subroutine contained
429        (*PRUNE) or any other control that caused it to give a non-standard return,
430        invalid errors such as "Error -26 (nested recursion at the same subject
431        position)" or even infinite loops could occur.
432    
433    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
434        computing the minimum length on reaching *ACCEPT, and so ended up with the
435        wrong value of 1 rather than 0. Further investigation indicates that
436        computing a minimum subject length in the presence of *ACCEPT is difficult
437        (think back references, subroutine calls), and so I have changed the code
438        so that no minimum is registered for a pattern that contains *ACCEPT.
439    
440    8.  If (*THEN) was present in the first (true) branch of a conditional group,
441        it was not handled as intended. [But see 16 below.]
442    
443    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
444        Sheri Pierce.
445    
446    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
447        the first byte in a match must be "a".
448    
449    11. Change 17 for 8.13 increased the recursion depth for patterns like
450        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
451        pattern contains any instances of (*THEN). If it does not, the old
452        optimizations are restored. It would be nice to do this on a per-group
453        basis, but at the moment that is not feasible.
454    
455    12. In some environments, the output of pcretest -C is CRLF terminated. This
456        broke RunTest's code that checks for the link size. A single white space
457        character after the value is now allowed for.
458    
459    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
460        For "fr", it uses the Windows-specific input and output files.
461    
462    14. If (*THEN) appeared in a group that was called recursively or as a
463        subroutine, it did not work as intended. [But see next item.]
464    
465    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
466        pattern fragments (but not containing any | characters). If A and B are
467        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
468        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
469        D. In other words, Perl considers parentheses that do not contain any |
470        characters to be part of a surrounding alternative, whereas PCRE was
471        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
472        differently. PCRE now behaves in the same way as Perl, except in the case
473        of subroutine/recursion calls such as (?1) which have in any case always
474        been different (but PCRE had them first :-).
475    
476    16. Related to 15 above: Perl does not treat the | in a conditional group as
477        creating alternatives. Such a group is treated in the same way as an
478        ordinary group without any | characters when processing (*THEN). PCRE has
479        been changed to match Perl's behaviour.
480    
481    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
482        RunGrepTest script failed.
483    
484    18. Change 22 for version 13 caused atomic groups to use more stack. This is
485        inevitable for groups that contain captures, but it can lead to a lot of
486        stack use in large patterns. The old behaviour has been restored for atomic
487        groups that do not contain any capturing parentheses.
488    
489    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
490        suppress the check for a minimum subject length at run time. (If it was
491        given to pcre_exec() or pcre_dfa_exec() it did work.)
492    
493    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
494        fail to work when decoding hex characters in data strings in EBCDIC
495        environments.
496    
497    21. It appears that in at least one Mac OS environment, the isxdigit() function
498        is implemented as a macro that evaluates to its argument more than once,
499        contravening the C 90 Standard (I haven't checked a later standard). There
500        was an instance in pcretest which caused it to go wrong when processing
501        \x{...} escapes in subject strings. The has been rewritten to avoid using
502        things like p++ in the argument of isxdigit().
503    
504    
505    Version 8.13 16-Aug-2011
506  ------------------------  ------------------------
507    
508  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 98  Version 8.13 02-Aug-2011 Line 599  Version 8.13 02-Aug-2011
599      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
600      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
601      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
602      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
603    
604  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
605      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 690  Version 8.13 02-Aug-2011
690      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
691      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
692      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
693      more like Perl.      more like Perl. (But see 8.20/1 above.)
694    
695  38. 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
696      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 725  Version 8.13 02-Aug-2011
725      (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
726          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
727    
728      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
729          PCRE is built.          PCRE is built.
730    
731      (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
# Line 245  Version 8.13 02-Aug-2011 Line 746  Version 8.13 02-Aug-2011
746  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
747      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
748      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
749    
750  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
751      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
752    
753    
754  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011

Legend:
Removed from v.657  
changed lines
  Added in v.1019

  ViewVC Help
Powered by ViewVC 1.1.5