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

Diff of /code/trunk/ChangeLog

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

revision 532 by ph10, Tue Jun 1 16:21:42 2010 UTC revision 1115 by chpe, Tue Oct 16 15:57:19 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.10 03 May-2010  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    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
60    
61    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
62        structure could go wrong in environments where size_t is not the same size
63        as int.
64    
65    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
66        set.
67    
68    15. The EBCDIC support had decayed; later updates to the code had included
69        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
70        general tidy up of EBCDIC-related issues, and the documentation was also
71        not quite right. There is now a test that can be run on ASCII systems to
72        check some of the EBCDIC-related things (but is it not a full test).
73    
74    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
75        in a small tidy to the code.
76    
77    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
78    
79    18. If the --only-matching (-o) option in pcregrep is specified multiple
80        times, each one causes appropriate output. For example, -o1 -o2 outputs the
81        substrings matched by the 1st and 2nd capturing parentheses. A separating
82        string can be specified by --om-separator (default empty).
83    
84    19. Improving the first n character searches.
85    
86    20. Turn case lists for horizontal and vertical white space into macros so that
87        they are defined only once.
88    
89    21. This set of changes together give more compatible Unicode case-folding
90        behaviour for characters that have more than one other case when UCP
91        support is available.
92    
93        (a) The Unicode property table now has offsets into a new table of sets of
94            three or more characters that are case-equivalent. The MultiStage2.py
95            script that generates these tables (the pcre_ucd.c file) now scans
96            CaseFolding.txt instead of UnicodeData.txt for character case
97            information.
98    
99        (b) The code for adding characters or ranges of characters to a character
100            class has been abstracted into a generalized function that also handles
101            case-independence. In UTF-mode with UCP support, this uses the new data
102            to handle characters with more than one other case.
103    
104        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
105            whose other case is greater than 256 are now correctly matched
106            caselessly. Previously, the high codepoint matched the low one, but not
107            vice versa.
108    
109        (d) The processing of \h, \H, \v, and \ in character classes now makes use
110            of the new class addition function, using character lists defined as
111            macros alongside the case definitions of 20 above.
112    
113        (e) Caseless back references now work with characters that have more than
114            one other case.
115    
116        (f) General caseless matching of characters with more than one other case
117            is supported.
118    
119    22. Unicode character properties were updated from Unicode 6.2.0
120    
121    23. Improved CMake support under Windows. Patch by Daniel Richard G.
122    
123    24. Add support for 32-bit character strings, and UTF-32
124    
125    
126    Version 8.31 06-July-2012
127    -------------------------
128    
129    1.  Fixing a wrong JIT test case and some compiler warnings.
130    
131    2.  Removed a bashism from the RunTest script.
132    
133    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
134        to unsigned type, result still unsigned" that was given by an MS compiler
135        on encountering the code "-sizeof(xxx)".
136    
137    4.  Partial matching support is added to the JIT compiler.
138    
139    5.  Fixed several bugs concerned with partial matching of items that consist
140        of more than one character:
141    
142        (a) /^(..)\1/ did not partially match "aba" because checking references was
143            done on an "all or nothing" basis. This also applied to repeated
144            references.
145    
146        (b) \R did not give a hard partial match if \r was found at the end of the
147            subject.
148    
149        (c) \X did not give a hard partial match after matching one or more
150            characters at the end of the subject.
151    
152        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
153            a partial match for the string "\r".
154    
155        (e) When newline was set to CRLF, the metacharacter "." did not recognize
156            a partial match for a CR character at the end of the subject string.
157    
158    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
159        running pcretest, the text "(JIT)" added to the output whenever JIT is
160        actually used to run the match.
161    
162    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
163        or /S+[+] with a digit between 1 and 7.
164    
165    8.  OP_NOT now supports any UTF character not just single-byte ones.
166    
167    9.  (*MARK) control verb is now supported by the JIT compiler.
168    
169    10. The command "./RunTest list" lists the available tests without actually
170        running any of them. (Because I keep forgetting what they all are.)
171    
172    11. Add PCRE_INFO_MAXLOOKBEHIND.
173    
174    12. Applied a (slightly modified) user-supplied patch that improves performance
175        when the heap is used for recursion (compiled with --disable-stack-for-
176        recursion). Instead of malloc and free for each heap frame each time a
177        logical recursion happens, frames are retained on a chain and re-used where
178        possible. This sometimes gives as much as 30% improvement.
179    
180    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
181        call.
182    
183    14. As documented, (*COMMIT) is now confined to within a positive assertion.
184    
185    15. It is now possible to link pcretest with libedit as an alternative to
186        libreadline.
187    
188    16. (*COMMIT) control verb is now supported by the JIT compiler.
189    
190    17. The Unicode data tables have been updated to Unicode 6.1.0.
191    
192    18. Added --file-list option to pcregrep.
193    
194    19. Added binary file support to pcregrep, including the -a, --binary-files,
195        -I, and --text options.
196    
197    20. The madvise function is renamed for posix_madvise for QNX compatibility
198        reasons. Fixed by Giuseppe D'Angelo.
199    
200    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
201    
202    22. Changed the option for creating symbolic links for 16-bit man pages from
203        -s to -sf so that re-installing does not cause issues.
204    
205    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
206    
207    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
208        matches in certain environments (the workspace was not being correctly
209        retained). Also added to pcre_dfa_exec() a simple plausibility check on
210        some of the workspace data at the beginning of a restart.
211    
212    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
213        was not doing so when it should - probably a typo introduced by SVN 528
214        (change 8.10/14).
215    
216    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
217        \w+ when the character tables indicated that \x{c4} was a word character.
218        There were several related cases, all because the tests for doing a table
219        lookup were testing for characters less than 127 instead of 255.
220    
221    27. If a pattern contains capturing parentheses that are not used in a match,
222        their slots in the ovector are set to -1. For those that are higher than
223        any matched groups, this happens at the end of processing. In the case when
224        there were back references that the ovector was too small to contain
225        (causing temporary malloc'd memory to be used during matching), and the
226        highest capturing number was not used, memory off the end of the ovector
227        was incorrectly being set to -1. (It was using the size of the temporary
228        memory instead of the true size.)
229    
230    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
231        ovector size, it uses memory at the end of the block that it has got.
232    
233    29. Check for an overlong MARK name and give an error at compile time. The
234        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
235    
236    30. JIT compiler update.
237    
238    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
239        Rill for the patch.
240    
241    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
242    
243    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
244    
245    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
246        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
247        was enabled.
248    
249    35. Improve JIT code generation for greedy plus quantifier.
250    
251    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
252        1 to "aa" instead of to an empty string. The bug affected repeated groups
253        that could potentially match an empty string.
254    
255    37. Optimizing single character iterators in JIT.
256    
257    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
258        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
259        codepoints that are too big for the mode are faulted, and in a UTF mode,
260        disallowed codepoints are also faulted.
261    
262    39. If PCRE was compiled with UTF support, in three places in the DFA
263        matcher there was code that should only have been obeyed in UTF mode, but
264        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
265        processing when bytes with values greater than 127 were present. In 16-bit
266        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
267        both cases the values are those that cannot be the first data item in a UTF
268        character. The three items that might have provoked this were recursions,
269        possessively repeated groups, and atomic groups.
270    
271    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
272        and pcregrep, because some OS require shared objects to be explicitly
273        passed to ld, causing the link step to fail if they are not.
274    
275    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
276        mode, patterns that started with \h* or \R* might be incorrectly matched.
277    
278    
279    Version 8.30 04-February-2012
280    -----------------------------
281    
282    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
283        name is defined in ctype.h.
284    
285    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
286        only in quite long subpatterns.
287    
288    3.  Removed the function pcre_info(), which has been obsolete and deprecated
289        since it was replaced by pcre_fullinfo() in February 2000.
290    
291    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
292        match a (*MARK), and the match failed at the start of the subject, a
293        reference to memory before the start of the subject could occur. This bug
294        was introduced by fix 17 of release 8.21.
295    
296    5.  A reference to an unset group with zero minimum repetition was giving
297        totally wrong answers (in non-JavaScript-compatibility mode). For example,
298        /(another)?(\1?)test/ matched against "hello world test". This bug was
299        introduced in release 8.13.
300    
301    6.  Add support for 16-bit character strings (a large amount of work involving
302        many changes and refactorings).
303    
304    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
305        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
306        from a file.
307    
308    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
309        rounding is not applied in this particular case).
310    
311    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
312        if they appear, or are escaped, in patterns.
313    
314    10. Get rid of a number of -Wunused-but-set-variable warnings.
315    
316    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
317        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
318        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
319        also returns the mark "x". This bug applied to capturing parentheses,
320        non-capturing parentheses, and atomic parentheses. It also applied to some
321        assertions.
322    
323    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
324        information out of configure.ac instead of relying on pcre.h.generic, which
325        is not stored in the repository.
326    
327    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
328        -lreadline.
329    
330    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
331    
332    15. Applied Graycode's patch to put the top-level frame on the stack rather
333        than the heap when not using the stack for recursion. This gives a
334        performance improvement in many cases when recursion is not deep.
335    
336    16. Experimental code added to "pcretest -C" to output the stack frame size.
337    
338    
339    Version 8.21 12-Dec-2011
340    ------------------------
341    
342    1.  Updating the JIT compiler.
343    
344    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
345        are added as well.
346    
347    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
348        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
349        calling _pcre_jit_exec. Some extra comments are added.
350    
351    4.  (*MARK) settings inside atomic groups that do not contain any capturing
352        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
353        was introduced by change 18 for 8.20.
354    
355    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
356        ECMA-262 standard.
357    
358    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
359        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
360        This bug was probably introduced by change 9 of 8.13.
361    
362    7.  While fixing 6 above, I noticed that a number of other items were being
363        incorrectly rejected as "not fixed length". This arose partly because newer
364        opcodes had not been added to the fixed-length checking code. I have (a)
365        corrected the bug and added tests for these items, and (b) arranged for an
366        error to occur if an unknown opcode is encountered while checking for fixed
367        length instead of just assuming "not fixed length". The items that were
368        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
369        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
370        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
371    
372    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
373        being incorrectly compiled and would have given unpredicatble results.
374    
375    9.  A possessively repeated subpattern with minimum repeat count greater than
376        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
377        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
378        the first (A) could occur when it should not.
379    
380    10. Add a cast and remove a redundant test from the code.
381    
382    11. JIT should use pcre_malloc/pcre_free for allocation.
383    
384    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
385        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
386        is anything other than /usr, -L is still shown).
387    
388    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
389    
390    14. Perl does not support \N without a following name in a [] class; PCRE now
391        also gives an error.
392    
393    15. If a forward reference was repeated with an upper limit of around 2000,
394        it caused the error "internal error: overran compiling workspace". The
395        maximum number of forward references (including repeats) was limited by the
396        internal workspace, and dependent on the LINK_SIZE. The code has been
397        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
398        the default depends on LINK_SIZE. There is a new upper limit (for safety)
399        of around 200,000 forward references. While doing this, I also speeded up
400        the filling in of repeated forward references.
401    
402    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
403        incorrectly expecting the subject to contain another "a" after the start.
404    
405    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
406        in the match, the SKIP should be ignored. This was not happening; instead
407        the SKIP was being treated as NOMATCH. For patterns such as
408        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
409        tested.
410    
411    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
412        now much more compatible with Perl, in particular in cases where the result
413        is a non-match for a non-anchored pattern. For example, if
414        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
415        "m", where previously it did not return a name. A side effect of this
416        change is that for partial matches, the last encountered mark name is
417        returned, as for non matches. A number of tests that were previously not
418        Perl-compatible have been moved into the Perl-compatible test files. The
419        refactoring has had the pleasing side effect of removing one argument from
420        the match() function, thus reducing its stack requirements.
421    
422    19. If the /S+ option was used in pcretest to study a pattern using JIT,
423        subsequent uses of /S (without +) incorrectly behaved like /S+.
424    
425    21. Retrieve executable code size support for the JIT compiler and fixing
426        some warnings.
427    
428    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
429        not work when the shorter character appeared right at the end of the
430        subject string.
431    
432    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
433        systems.
434    
435    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
436        output it when the /M option is used in pcretest.
437    
438    25. The CheckMan script was not being included in the distribution. Also, added
439        an explicit "perl" to run Perl scripts from the PrepareRelease script
440        because this is reportedly needed in Windows.
441    
442    26. If study data was being save in a file and studying had not found a set of
443        "starts with" bytes for the pattern, the data written to the file (though
444        never used) was taken from uninitialized memory and so caused valgrind to
445        complain.
446    
447    27. Updated RunTest.bat as provided by Sheri Pierce.
448    
449    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
450    
451    29. Computation of memory usage for the table of capturing group names was
452        giving an unnecessarily large value.
453    
454    
455    Version 8.20 21-Oct-2011
456    ------------------------
457    
458    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
459        a POSIX class. After further experiments with Perl, which convinced me that
460        Perl has bugs and confusions, a closing square bracket is no longer allowed
461        in a POSIX name. This bug also affected patterns with classes that started
462        with full stops.
463    
464    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
465        captured substring, but while checking the failing first alternative,
466        substring 1 is temporarily captured. If the output vector supplied to
467        pcre_exec() was not big enough for this capture, the yield of the function
468        was still zero ("insufficient space for captured substrings"). This cannot
469        be totally fixed without adding another stack variable, which seems a lot
470        of expense for a edge case. However, I have improved the situation in cases
471        such as /(a)(b)x|abc/ matched against "abc", where the return code
472        indicates that fewer than the maximum number of slots in the ovector have
473        been set.
474    
475    3.  Related to (2) above: when there are more back references in a pattern than
476        slots in the output vector, pcre_exec() uses temporary memory during
477        matching, and copies in the captures as far as possible afterwards. It was
478        using the entire output vector, but this conflicts with the specification
479        that only 2/3 is used for passing back captured substrings. Now it uses
480        only the first 2/3, for compatibility. This is, of course, another edge
481        case.
482    
483    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
484        main code base, and can be used by building with --enable-jit. When this is
485        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
486        runtime --no-jit option is given.
487    
488    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
489        ovector, the return from the function was zero, implying that there were
490        other matches that did not fit. The correct "exactly full" value is now
491        returned.
492    
493    6.  If a subpattern that was called recursively or as a subroutine contained
494        (*PRUNE) or any other control that caused it to give a non-standard return,
495        invalid errors such as "Error -26 (nested recursion at the same subject
496        position)" or even infinite loops could occur.
497    
498    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
499        computing the minimum length on reaching *ACCEPT, and so ended up with the
500        wrong value of 1 rather than 0. Further investigation indicates that
501        computing a minimum subject length in the presence of *ACCEPT is difficult
502        (think back references, subroutine calls), and so I have changed the code
503        so that no minimum is registered for a pattern that contains *ACCEPT.
504    
505    8.  If (*THEN) was present in the first (true) branch of a conditional group,
506        it was not handled as intended. [But see 16 below.]
507    
508    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
509        Sheri Pierce.
510    
511    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
512        the first byte in a match must be "a".
513    
514    11. Change 17 for 8.13 increased the recursion depth for patterns like
515        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
516        pattern contains any instances of (*THEN). If it does not, the old
517        optimizations are restored. It would be nice to do this on a per-group
518        basis, but at the moment that is not feasible.
519    
520    12. In some environments, the output of pcretest -C is CRLF terminated. This
521        broke RunTest's code that checks for the link size. A single white space
522        character after the value is now allowed for.
523    
524    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
525        For "fr", it uses the Windows-specific input and output files.
526    
527    14. If (*THEN) appeared in a group that was called recursively or as a
528        subroutine, it did not work as intended. [But see next item.]
529    
530    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
531        pattern fragments (but not containing any | characters). If A and B are
532        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
533        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
534        D. In other words, Perl considers parentheses that do not contain any |
535        characters to be part of a surrounding alternative, whereas PCRE was
536        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
537        differently. PCRE now behaves in the same way as Perl, except in the case
538        of subroutine/recursion calls such as (?1) which have in any case always
539        been different (but PCRE had them first :-).
540    
541    16. Related to 15 above: Perl does not treat the | in a conditional group as
542        creating alternatives. Such a group is treated in the same way as an
543        ordinary group without any | characters when processing (*THEN). PCRE has
544        been changed to match Perl's behaviour.
545    
546    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
547        RunGrepTest script failed.
548    
549    18. Change 22 for version 13 caused atomic groups to use more stack. This is
550        inevitable for groups that contain captures, but it can lead to a lot of
551        stack use in large patterns. The old behaviour has been restored for atomic
552        groups that do not contain any capturing parentheses.
553    
554    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
555        suppress the check for a minimum subject length at run time. (If it was
556        given to pcre_exec() or pcre_dfa_exec() it did work.)
557    
558    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
559        fail to work when decoding hex characters in data strings in EBCDIC
560        environments.
561    
562    21. It appears that in at least one Mac OS environment, the isxdigit() function
563        is implemented as a macro that evaluates to its argument more than once,
564        contravening the C 90 Standard (I haven't checked a later standard). There
565        was an instance in pcretest which caused it to go wrong when processing
566        \x{...} escapes in subject strings. The has been rewritten to avoid using
567        things like p++ in the argument of isxdigit().
568    
569    
570    Version 8.13 16-Aug-2011
571    ------------------------
572    
573    1.  The Unicode data tables have been updated to Unicode 6.0.0.
574    
575    2.  Two minor typos in pcre_internal.h have been fixed.
576    
577    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
578        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
579        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
580    
581    4.  There were a number of related bugs in the code for matching backrefences
582        caselessly in UTF-8 mode when codes for the characters concerned were
583        different numbers of bytes. For example, U+023A and U+2C65 are an upper
584        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
585        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
586        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
587        2-byte code at the end of the subject (it thought there wasn't enough data
588        left).
589    
590    5.  Comprehensive information about what went wrong is now returned by
591        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
592        as the output vector has at least 2 elements. The offset of the start of
593        the failing character and a reason code are placed in the vector.
594    
595    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
596        now returned is for the first byte of the failing character, instead of the
597        last byte inspected. This is an incompatible change, but I hope it is small
598        enough not to be a problem. It makes the returned offset consistent with
599        pcre_exec() and pcre_dfa_exec().
600    
601    7.  pcretest now gives a text phrase as well as the error number when
602        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
603        failure, the offset and reason code are output.
604    
605    8.  When \R was used with a maximizing quantifier it failed to skip backwards
606        over a \r\n pair if the subsequent match failed. Instead, it just skipped
607        back over a single character (\n). This seems wrong (because it treated the
608        two characters as a single entity when going forwards), conflicts with the
609        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
610        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
611        has been changed.
612    
613    9.  Some internal refactoring has changed the processing so that the handling
614        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
615        time (the PCRE_DOTALL option was changed this way some time ago: version
616        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
617        which was always a bit of a fudge. It also means that there is one less
618        argument for the match() function, which reduces its stack requirements
619        slightly. This change also fixes an incompatibility with Perl: the pattern
620        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
621    
622    10. More internal refactoring has drastically reduced the number of recursive
623        calls to match() for possessively repeated groups such as (abc)++ when
624        using pcre_exec().
625    
626    11. While implementing 10, a number of bugs in the handling of groups were
627        discovered and fixed:
628    
629        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
630        (a|)*(?1) gave a compile-time internal error.
631        ((a|)+)+  did not notice that the outer group could match an empty string.
632        (^a|^)+   was not marked as anchored.
633        (.*a|.*)+ was not marked as matching at start or after a newline.
634    
635    12. Yet more internal refactoring has removed another argument from the match()
636        function. Special calls to this function are now indicated by setting a
637        value in a variable in the "match data" data block.
638    
639    13. Be more explicit in pcre_study() instead of relying on "default" for
640        opcodes that mean there is no starting character; this means that when new
641        ones are added and accidentally left out of pcre_study(), testing should
642        pick them up.
643    
644    14. The -s option of pcretest has been documented for ages as being an old
645        synonym of -m (show memory usage). I have changed it to mean "force study
646        for every regex", that is, assume /S for every regex. This is similar to -i
647        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
648        using it. It makes it easier to run collections of tests with and without
649        study enabled, and thereby test pcre_study() more easily. All the standard
650        tests are now run with and without -s (but some patterns can be marked as
651        "never study" - see 20 below).
652    
653    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
654        restoration of the capturing data to the outer values was not happening
655        correctly.
656    
657    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
658        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
659        pattern had matched an empty string, and so incorrectly returned a no
660        match.
661    
662    17. There was optimizing code for the last branch of non-capturing parentheses,
663        and also for the obeyed branch of a conditional subexpression, which used
664        tail recursion to cut down on stack usage. Unfortunately, now that there is
665        the possibility of (*THEN) occurring in these branches, tail recursion is
666        no longer possible because the return has to be checked for (*THEN). These
667        two optimizations have therefore been removed. [But see 8.20/11 above.]
668    
669    18. If a pattern containing \R was studied, it was assumed that \R always
670        matched two bytes, thus causing the minimum subject length to be
671        incorrectly computed because \R can also match just one byte.
672    
673    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
674        was incorrectly computed.
675    
676    20. If /S is present twice on a test pattern in pcretest input, it now
677        *disables* studying, thereby overriding the use of -s on the command line
678        (see 14 above). This is necessary for one or two tests to keep the output
679        identical in both cases.
680    
681    21. When (*ACCEPT) was used in an assertion that matched an empty string and
682        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
683    
684    22. When an atomic group that contained a capturing parenthesis was
685        successfully matched, but the branch in which it appeared failed, the
686        capturing was not being forgotten if a higher numbered group was later
687        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
688        group 1 to "a", when in fact it should be unset. This applied to multi-
689        branched capturing and non-capturing groups, repeated or not, and also to
690        positive assertions (capturing in negative assertions does not happen
691        in PCRE) and also to nested atomic groups.
692    
693    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
694        subject after a captured substring, to make it easier to tell which of a
695        number of identical substrings has been captured.
696    
697    24. The way atomic groups are processed by pcre_exec() has been changed so that
698        if they are repeated, backtracking one repetition now resets captured
699        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
700        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
701        "aaa". Previously, it would have been "a". As part of this code
702        refactoring, the way recursive calls are handled has also been changed.
703    
704    25. If an assertion condition captured any substrings, they were not passed
705        back unless some other capturing happened later. For example, if
706        (?(?=(a))a) was matched against "a", no capturing was returned.
707    
708    26. When studying a pattern that contained subroutine calls or assertions,
709        the code for finding the minimum length of a possible match was handling
710        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
711        group 1 called group 2 while simultaneously a separate group 2 called group
712        1). A stack overflow occurred in this case. I have fixed this by limiting
713        the recursion depth to 10.
714    
715    27. Updated RunTest.bat in the distribution to the version supplied by Tom
716        Fortmann. This supports explicit test numbers on the command line, and has
717        argument validation and error reporting.
718    
719    28. An instance of \X with an unlimited repeat could fail if at any point the
720        first character it looked at was a mark character.
721    
722    29. Some minor code refactoring concerning Unicode properties and scripts
723        should reduce the stack requirement of match() slightly.
724    
725    30. Added the '=' option to pcretest to check the setting of unused capturing
726        slots at the end of the pattern, which are documented as being -1, but are
727        not included in the return count.
728    
729    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
730        compiled something random. Now it gives a compile-time error (as does
731        Perl).
732    
733    32. A *MARK encountered during the processing of a positive assertion is now
734        recorded and passed back (compatible with Perl).
735    
736    33. If --only-matching or --colour was set on a pcregrep call whose pattern
737        had alternative anchored branches, the search for a second match in a line
738        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
739        matched the line "0102" twice. The same bug affected patterns that started
740        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
741        twice.
742    
743    34. Previously, PCRE did not allow quantification of assertions. However, Perl
744        does, and because of capturing effects, quantifying parenthesized
745        assertions may at times be useful. Quantifiers are now allowed for
746        parenthesized assertions.
747    
748    35. A minor code tidy in pcre_compile() when checking options for \R usage.
749    
750    36. \g was being checked for fancy things in a character class, when it should
751        just be a literal "g".
752    
753    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
754        appearance of a nested POSIX class supersedes an apparent external class.
755        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
756        unescaped square brackets may also appear as part of class names. For
757        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
758        more like Perl. (But see 8.20/1 above.)
759    
760    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
761        was because it thought it was \N{name}, which is not supported).
762    
763    39. Add minix to OS list not supporting the -S option in pcretest.
764    
765    40. PCRE tries to detect cases of infinite recursion at compile time, but it
766        cannot analyze patterns in sufficient detail to catch mutual recursions
767        such as ((?1))((?2)). There is now a runtime test that gives an error if a
768        subgroup is called recursively as a subpattern for a second time at the
769        same position in the subject string. In previous releases this might have
770        been caught by the recursion limit, or it might have run out of stack.
771    
772    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
773        happen only once. PCRE was, however incorrectly giving a compile time error
774        "recursive call could loop indefinitely" because it cannot analyze the
775        pattern in sufficient detail. The compile time test no longer happens when
776        PCRE is compiling a conditional subpattern, but actual runaway loops are
777        now caught at runtime (see 40 above).
778    
779    42. It seems that Perl allows any characters other than a closing parenthesis
780        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
781        has been changed to be the same.
782    
783    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
784        as not to get warnings when autogen.sh is called. Also changed
785        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
786    
787    44. To help people who use pcregrep to scan files containing exceedingly long
788        lines, the following changes have been made:
789    
790        (a) The default value of the buffer size parameter has been increased from
791            8K to 20K. (The actual buffer used is three times this size.)
792    
793        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
794            PCRE is built.
795    
796        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
797            to be set at run time.
798    
799        (d) Numerical values in pcregrep options can be followed by K or M, for
800            example --buffer-size=50K.
801    
802        (e) If a line being scanned overflows pcregrep's buffer, an error is now
803            given and the return code is set to 2.
804    
805    45. Add a pointer to the latest mark to the callout data block.
806    
807    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
808        partial match of an empty string instead of no match. This was specific to
809        the use of ".".
810    
811    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
812        complete match instead of a partial match. This bug was dependent on both
813        the PCRE_UTF8 and PCRE_DOTALL options being set.
814    
815    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
816        starting byte set, because \b was not being ignored.
817    
818    
819    Version 8.12 15-Jan-2011
820    ------------------------
821    
822    1.  Fixed some typos in the markup of the man pages, and wrote a script that
823        checks for such things as part of the documentation building process.
824    
825    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
826        --match-limit and --recursion-limit options (added for 8.11). In
827        particular, this made one of the standard tests fail. (The integer value
828        went into the wrong half of a long int.)
829    
830    3.  If the --colour option was given to pcregrep with -v (invert match), it
831        did strange things, either producing crazy output, or crashing. It should,
832        of course, ignore a request for colour when reporting lines that do not
833        match.
834    
835    4.  Another pcregrep bug caused similar problems if --colour was specified with
836        -M (multiline) and the pattern match finished with a line ending.
837    
838    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
839        matched in multiline mode, the following line was shown as part of the
840        match. This seems wrong, so I have changed it.
841    
842    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
843        the check for further matches in the same line (so they could be coloured)
844        to overrun the end of the current line. If another match was found, it was
845        incorrectly shown (and then shown again when found in the next line).
846    
847    7.  If pcregrep was compiled under Windows, there was a reference to the
848        function pcregrep_exit() before it was defined. I am assuming this was
849        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
850        reported by a user. I've moved the definition above the reference.
851    
852    
853    Version 8.11 10-Dec-2010
854    ------------------------
855    
856    1.  (*THEN) was not working properly if there were untried alternatives prior
857        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
858        backtracked to try for "b" instead of moving to the next alternative branch
859        at the same level (in this case, to look for "c"). The Perl documentation
860        is clear that when (*THEN) is backtracked onto, it goes to the "next
861        alternative in the innermost enclosing group".
862    
863    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
864        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
865        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
866        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
867        (*THEN).
868    
869    3.  If \s appeared in a character class, it removed the VT character from
870        the class, even if it had been included by some previous item, for example
871        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
872        of \s, but is part of the POSIX "space" class.)
873    
874    4.  A partial match never returns an empty string (because you can always
875        match an empty string at the end of the subject); however the checking for
876        an empty string was starting at the "start of match" point. This has been
877        changed to the "earliest inspected character" point, because the returned
878        data for a partial match starts at this character. This means that, for
879        example, /(?<=abc)def/ gives a partial match for the subject "abc"
880        (previously it gave "no match").
881    
882    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
883        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
884        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
885        has an implication that the given string is incomplete (because a partial
886        match is preferred over a full match). For this reason, these items now
887        give a partial match in this situation. [Aside: previously, the one case
888        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
889        match rather than a full match, which was wrong by the old rules, but is
890        now correct.]
891    
892    6.  There was a bug in the handling of #-introduced comments, recognized when
893        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
894        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
895        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
896        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
897        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
898        places in pcre_compile().
899    
900    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
901        comments when looking ahead for named forward references to subpatterns,
902        the only newline sequence it recognized was NL. It now handles newlines
903        according to the set newline convention.
904    
905    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
906        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
907        cater for a lack of strerror(). These oversights have been fixed.
908    
909    9.  Added --match-limit and --recursion-limit to pcregrep.
910    
911    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
912    
913    11. When the -o option was used, pcregrep was setting a return code of 1, even
914        when matches were found, and --line-buffered was not being honoured.
915    
916    12. Added an optional parentheses number to the -o and --only-matching options
917        of pcregrep.
918    
919    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
920        can match an empty string. The code to do it in pcretest and pcredemo
921        needed fixing:
922    
923        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
924            only one byte after an empty string match just before CRLF (this case
925            just got forgotten; "any" and "anycrlf" were OK).
926    
927        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
928            mode when an empty string match preceded an ASCII character followed by
929            a non-ASCII character. (The code for advancing by one character rather
930            than one byte was nonsense.)
931    
932        (c) The pcredemo.c sample program did not have any code at all to handle
933            the cases when CRLF is a valid newline sequence.
934    
935    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
936        as a starting offset was within the subject string. There is now a new
937        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
938        negative or greater than the length of the string. In order to test this,
939        pcretest is extended to allow the setting of negative starting offsets.
940    
941    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
942        starting offset points to the beginning of a UTF-8 character was
943        unnecessarily clumsy. I tidied it up.
944    
945    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
946        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
947    
948    17. Nobody had reported that the --include_dir option, which was added in
949        release 7.7 should have been called --include-dir (hyphen, not underscore)
950        for compatibility with GNU grep. I have changed it to --include-dir, but
951        left --include_dir as an undocumented synonym, and the same for
952        --exclude-dir, though that is not available in GNU grep, at least as of
953        release 2.5.4.
954    
955    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
956        characters from a string of bytes) have been redefined so as not to use
957        loops, in order to improve performance in some environments. At the same
958        time, I abstracted some of the common code into auxiliary macros to save
959        repetition (this should not affect the compiled code).
960    
961    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
962        compile-time error is now given if \c is not followed by an ASCII
963        character, that is, a byte less than 128. (In EBCDIC mode, the code is
964        different, and any byte value is allowed.)
965    
966    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
967        START_OPTIMIZE option, which is now allowed at compile time - but just
968        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
969        to pcregrep and other applications that have no direct access to PCRE
970        options. The new /Y option in pcretest sets this option when calling
971        pcre_compile().
972    
973    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
974        back references. Groups containing recursive back references were forced to
975        be atomic by that change, but in the case of named groups, the amount of
976        memory required was incorrectly computed, leading to "Failed: internal
977        error: code overflow". This has been fixed.
978    
979    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
980        pcretest.c, to avoid build problems in some Borland environments.
981    
982    
983    Version 8.10 25-Jun-2010
984  ------------------------  ------------------------
985    
986  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
# Line 9  Version 8.10 03 May-2010 Line 988  Version 8.10 03 May-2010
988    
989  2.  (*ACCEPT) was not working when inside an atomic group.  2.  (*ACCEPT) was not working when inside an atomic group.
990    
991  3.  Inside a character class, \B is treated as a literal by default, but  3.  Inside a character class, \B is treated as a literal by default, but
992      faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option      faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
993      causes the error). The code is unchanged, but I tidied the documentation.      causes the error). The code is unchanged, but I tidied the documentation.
994    
995  4.  Inside a character class, PCRE always treated \R and \X as literals,  4.  Inside a character class, PCRE always treated \R and \X as literals,
996      whereas Perl faults them if its -w option is set. I have changed PCRE so      whereas Perl faults them if its -w option is set. I have changed PCRE so
997      that it faults them when PCRE_EXTRA is set.      that it faults them when PCRE_EXTRA is set.
998    
999  5.  Added support for \N, which always matches any character other than  5.  Added support for \N, which always matches any character other than
1000      newline. (It is the same as "." when PCRE_DOTALL is not set.)      newline. (It is the same as "." when PCRE_DOTALL is not set.)
1001    
1002  6.  When compiling pcregrep with newer versions of gcc which may have  6.  When compiling pcregrep with newer versions of gcc which may have
1003      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1004      declared with attribute warn_unused_result" were given. Just casting the      declared with attribute warn_unused_result" were given. Just casting the
1005      result to (void) does not stop the warnings; a more elaborate fudge is      result to (void) does not stop the warnings; a more elaborate fudge is
1006      needed. I've used a macro to implement this.      needed. I've used a macro to implement this.
1007    
1008  7.  Minor change to pcretest.c to avoid a compiler warning.  7.  Minor change to pcretest.c to avoid a compiler warning.
1009    
1010  8.  Added four artifical Unicode properties to help with an option to make  8.  Added four artifical Unicode properties to help with an option to make
1011      \s etc use properties (see next item). The new properties are: Xan      \s etc use properties (see next item). The new properties are: Xan
1012      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1013    
1014  9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes  9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1015      use Unicode properties. (*UCP) at the start of a pattern can be used to set      use Unicode properties. (*UCP) at the start of a pattern can be used to set
1016      this option. Modified pcretest to add /W to test this facility. Added      this option. Modified pcretest to add /W to test this facility. Added
1017      REG_UCP to make it available via the POSIX interface.      REG_UCP to make it available via the POSIX interface.
   
 10. Added --line-buffered to pcregrep.  
1018    
1019  11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was  10. Added --line-buffered to pcregrep.
1020      studied, and the match started with a letter with a code point greater than  
1021    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1022        studied, and the match started with a letter with a code point greater than
1023      127 whose first byte was different to the first byte of the other case of      127 whose first byte was different to the first byte of the other case of
1024      the letter, the other case of this starting letter was not recognized.      the letter, the other case of this starting letter was not recognized
1025        (#976).
1026  12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a  
1027      conflict in the definition of PCRE_EXP_DECL. I have removed the include of  12. If a pattern that was studied started with a repeated Unicode property
     pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of  
     historical tidying that never got done.)  
   
 13. If a pattern that was studied started with a repeated Unicode property  
1028      test, for example, \p{Nd}+, there was the theoretical possibility of      test, for example, \p{Nd}+, there was the theoretical possibility of
1029      setting up an incorrect bitmap of starting bytes, but fortunately it could      setting up an incorrect bitmap of starting bytes, but fortunately it could
1030      not have actually happened in practice until change 8 above was made (it      not have actually happened in practice until change 8 above was made (it
1031      added property types that matched character-matching opcodes).      added property types that matched character-matching opcodes).
1032    
1033  14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of  13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1034      possible starting bytes for non-anchored patterns.      possible starting bytes for non-anchored patterns.
1035    
1036  15. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes  14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1037      \R, and also a number of cases that involve Unicode properties, both      \R, and also a number of cases that involve Unicode properties, both
1038      explicit and implicit when PCRE_UCP is set.      explicit and implicit when PCRE_UCP is set.
1039    
1040  16. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8  15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1041      input, it could crash or give wrong results if characters with values      input, it could crash or give wrong results if characters with values
1042      greater than 0xc0 were present in the subject string. (Detail: it assumed      greater than 0xc0 were present in the subject string. (Detail: it assumed
1043      UTF-8 input when processing these items.)      UTF-8 input when processing these items.)
1044    
1045  17. Added a lot of (int) casts to avoid compiler warnings in systems where  16. Added a lot of (int) casts to avoid compiler warnings in systems where
1046      size_t is 64-bit.      size_t is 64-bit (#991).
1047    
1048  18. Added a check for running out of memory when PCRE is compiled with  17. Added a check for running out of memory when PCRE is compiled with
1049      --disable-stack-for-recursion.      --disable-stack-for-recursion (#990).
1050    
1051    18. If the last data line in a file for pcretest does not have a newline on
1052        the end, a newline was missing in the output.
1053    
1054    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1055        less than 128) in its various bitmaps. However, there is a facility for
1056        generating tables according to the current locale when PCRE is compiled. It
1057        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1058        characters, are recognized by isspace() and therefore were getting set in
1059        these tables, and indeed these tables seem to approximate to ISO 8859. This
1060        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1061        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1062        which of course cannot start UTF-8 characters. I have changed the code so
1063        that only real ASCII characters (less than 128) and the correct starting
1064        bytes for UTF-8 encodings are set for characters greater than 127 when in
1065        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1066        altogether.)
1067    
1068    20. Added the /T option to pcretest so as to be able to run tests with non-
1069        standard character tables, thus making it possible to include the tests
1070        used for 19 above in the standard set of tests.
1071    
1072    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1073        reference to a subpattern the other side of a comment that contains an
1074        opening parenthesis caused either an internal compiling error, or a
1075        reference to the wrong subpattern.
1076    
1077    
1078  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Legend:
Removed from v.532  
changed lines
  Added in v.1115

  ViewVC Help
Powered by ViewVC 1.1.5