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

Diff of /code/trunk/ChangeLog

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

revision 942 by ph10, Tue Feb 28 14:50:31 2012 UTC revision 1387 by ph10, Sat Nov 2 18:29:05 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31  Version 8.34 xx-xxxx-201x
5    --------------------------
6    
7    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8        executable memory. Patch inspired by Carsten Klein.
9    
10    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
11        this macro is never tested and has no effect, because the work to support
12        coverage involves only compiling and linking options and special targets in
13        the Makefile. The comment in config.h implied that defining the macro would
14        enable coverage support, which is totally false. There was also support for
15        setting this macro in the CMake files (my fault, I just copied it from
16        configure). SUPPORT_GCOV has now been removed.
17    
18    3.  Make a small performance improvement in strlen16() and strlen32() in
19        pcretest.
20    
21    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
22        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
23        these cases). There was also one in pcretest.c.
24    
25    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
26    
27    6.  In UTF mode, the code for checking whether a group could match an empty
28        string (which is used for indefinitely repeated groups to allow for
29        breaking an infinite loop) was broken when the group contained a repeated
30        negated single-character class with a character that occupied more than one
31        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
32        UTF-8 mode). The effect was undefined: the group might or might not be
33        deemed as matching an empty string, or the program might have crashed.
34    
35    7.  The code for checking whether a group could match an empty string was not
36        recognizing that \h, \H, \v, \V, and \R must match a character.
37    
38    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
39        an empty string. If it can, pcretest shows this in its information output.
40    
41    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
42        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
43        matched by pcre_exec() without using JIT:
44    
45        (a) If the rest of the pattern did not match after a maximal run of
46            grapheme clusters, the code for backing up to try with fewer of them
47            did not always back up over a full grapheme when characters that do not
48            have the modifier quality were involved, e.g. Hangul syllables.
49    
50        (b) If the match point in a subject started with modifier character, and
51            there was no match, the code could incorrectly back up beyond the match
52            point, and potentially beyond the first character in the subject,
53            leading to a segfault or an incorrect match result.
54    
55    10. A conditional group with an assertion condition could lead to PCRE
56        recording an incorrect first data item for a match if no other first data
57        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
58        first data item, and therefore matched "ca" after "c" instead of at the
59        start.
60    
61    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
62        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
63    
64    12. The source of pcregrep now includes z/OS-specific code so that it can be
65        compiled for z/OS as part of the special z/OS distribution.
66    
67    13. Added the -T and -TM options to pcretest.
68    
69    14. The code in pcre_compile.c for creating the table of named capturing groups
70        has been refactored. Instead of creating the table dynamically during the
71        actual compiling pass, the information is remembered during the pre-compile
72        pass (on the stack unless there are more than 20 named groups, in which
73        case malloc() is used) and the whole table is created before the actual
74        compile happens. This has simplified the code (it is now nearly 150 lines
75        shorter) and prepared the way for better handling of references to groups
76        with duplicate names.
77    
78    15. A back reference to a named subpattern when there is more than one of the
79        same name now checks them in the order in which they appear in the pattern.
80        The first one that is set is used for the reference. Previously only the
81        first one was inspected. This change makes PCRE more compatible with Perl.
82    
83    16. Unicode character properties were updated from Unicode 6.3.0.
84    
85    17. The compile-time code for auto-possessification has been refactored, based
86        on a patch by Zoltan Herczeg. It now happens after instead of during
87        compilation. The code is cleaner, and more cases are handled. The option
88        PCRE_NO_AUTO_POSSESSIFY is added for testing purposes, and the -O and /O
89        options in pcretest are provided to set it.
90    
91    18. The character VT has been added to the set of characters that match \s and
92        are generally treated as white space, following this same change in Perl
93        5.18. There is now no difference between "Perl space" and "POSIX space".
94    
95    19. The code for checking named groups as conditions, either for being set or
96        for being recursed, has been refactored (this is related to 14 and 15
97        above). Processing unduplicated named groups should now be as fast at
98        numerical groups, and processing duplicated groups should be faster than
99        before.
100    
101    20. Two patches to the CMake build system, by Alexander Barkov:
102    
103          (1) Replace the "source" command by "." in CMakeLists.txt because
104              "source" is a bash-ism.
105    
106          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
107              without these the CMake build does not work on Solaris.
108    
109    21. Perl has changed its handling of \8 and \9. If there is no previously
110        encountered capturing group of those numbers, they are treated as the
111        literal characters 8 and 9 instead of a binary zero followed by the
112        literals. PCRE now does the same.
113    
114    22. Following Perl, added \o{} to specify codepoints in octal, making it
115        possible to specify values greater than 0777 and also making them
116        unambiguous.
117    
118    23. Perl now gives an error for missing closing braces after \x{... instead of
119        treating the string as literal. PCRE now does the same.
120    
121    24. RunTest used to grumble if an inappropriate test was selected explicitly,
122        but just skip it when running all tests. This make it awkward to run ranges
123        of tests when one of them was inappropriate. Now it just skips any
124        inappropriate tests, as it always did when running all tests.
125    
126    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
127        character types such as \d or \w, too many callouts were inserted, and the
128        data that they returned was rubbish.
129    
130    26. In UCP mode, \s was not matching two of the characters that Perl matches,
131        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
132        were matched by \h. The code has now been refactored so that the lists of
133        the horizontal and vertical whitespace characters used for \h and \v (which
134        are defined only in one place) are now also used for \s.
135    
136    27. Add JIT support for the 64 bit TileGX architecture.
137        Patch by Jiong Wang (Tilera Corporation).
138    
139    28. Possessive quantifiers for classes (both explicit and automatically
140        generated) now use special opcodes instead of wrapping in ONCE brackets.
141    
142    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
143        (because it's meaningless), this was not happening when PCRE_CASELESS was
144        set. Not wrong, but inefficient.
145    
146    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
147        properties for \w, \d, etc) is present in a test regex. Otherwise if the
148        test contains no characters greater than 255, Perl doesn't realise it
149        should be using Unicode semantics.
150    
151    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
152        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
153        does in Unicode mode.
154    
155    
156    Version 8.33 28-May-2013
157    ------------------------
158    
159    1.  Added 'U' to some constants that are compared to unsigned integers, to
160        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
161        variables that are added to signed variables, to ensure the result is
162        signed and can be negated.
163    
164    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
165        CMake config files.
166    
167    3.  Revise the creation of config.h.generic so that all boolean macros are
168        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
169        overriding via -D on the command line possible.
170    
171    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
172        to unsigned int is reported to make a quite noticeable speed difference in
173        a specific Windows environment. Testing on Linux did also appear to show
174        some benefit (and it is clearly not harmful). Also fixed the definition of
175        Xop which should be unsigned.
176    
177    5.  Related to (4), changing the definition of the intermediate variable cc
178        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
179        improvements.
180    
181    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
182        unnecessary spaces.
183    
184    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
185        and later.
186    
187    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
188    
189    9.  Optimizing fast_forward_start_bits in JIT.
190    
191    10. Adding support for callouts in JIT, and fixing some issues revealed
192        during this work. Namely:
193    
194        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
195    
196        (b) Minimum length was not checked before the matching is started.
197    
198    11. The value of capture_last that is passed to callouts was incorrect in some
199        cases when there was a capture on one path that was subsequently abandoned
200        after a backtrack. Also, the capture_last value is now reset after a
201        recursion, since all captures are also reset in this case.
202    
203    12. The interpreter no longer returns the "too many substrings" error in the
204        case when an overflowing capture is in a branch that is subsequently
205        abandoned after a backtrack.
206    
207    13. In the pathological case when an offset vector of size 2 is used, pcretest
208        now prints out the matched string after a yield of 0 or 1.
209    
210    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
211        Only supported by the JIT compiler at the moment.
212    
213    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
214    
215    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
216        offset of the starting point of the matching process, provided the offsets
217        vector is large enough.
218    
219    17. The \A escape now records a lookbehind value of 1, though its execution
220        does not actually inspect the previous character. This is to ensure that,
221        in partial multi-segment matching, at least one character from the old
222        segment is retained when a new segment is processed. Otherwise, if there
223        are no lookbehinds in the pattern, \A might match incorrectly at the start
224        of a new segment.
225    
226    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
227    
228    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
229        gives some modest performance improvement in 8-bit mode.
230    
231    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
232        be expressed in certain programming languages using Universal Character
233        Names.
234    
235    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
236        which points out that "non characters" are not "characters that may not
237        appear in Unicode strings" but rather "characters that are reserved for
238        internal use and have only local meaning".
239    
240    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
241        there was a conditional group that depended on an assertion, if the
242        assertion was false, the callout that immediately followed the alternation
243        in the condition was skipped when pcre_exec() was used for matching.
244    
245    23. Allow an explicit callout to be inserted before an assertion that is the
246        condition for a conditional group, for compatibility with automatic
247        callouts, which always insert a callout at this point.
248    
249    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
250        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
251    
252    25. (*PRUNE) is now supported by the JIT compiler.
253    
254    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
255    
256    27. Fix the case where there are two or more SKIPs with arguments that may be
257        ignored.
258    
259    28. (*SKIP) is now supported by the JIT compiler.
260    
261    29. (*THEN) is now supported by the JIT compiler.
262    
263    30. Update RunTest with additional test selector options.
264    
265    31. The way PCRE handles backtracking verbs has been changed in two ways.
266    
267        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
268        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
269        backtracking. In some cases this makes it more Perl-compatible, but Perl's
270        rather obscure rules do not always do the same thing.
271    
272        (2) Previously, backtracking verbs were confined within assertions. This is
273        no longer the case for positive assertions, except for (*ACCEPT). Again,
274        this sometimes improves Perl compatibility, and sometimes does not.
275    
276    32. A number of tests that were in test 2 because Perl did things differently
277        have been moved to test 1, because either Perl or PCRE has changed, and
278        these tests are now compatible.
279    
280    32. Backtracking control verbs are now handled in the same way in JIT and
281        interpreter.
282    
283    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
284        contained a forward subroutine reference caused a compile error.
285    
286    34. Auto-detect and optimize limited repetitions in JIT.
287    
288    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
289        blocking (*UTF) etc.
290    
291    36. In the interpreter, maximizing pattern repetitions for characters and
292        character types now use tail recursion, which reduces stack usage.
293    
294    37. The value of the max lookbehind was not correctly preserved if a compiled
295        and saved regex was reloaded on a host of different endianness.
296    
297    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
298        of the compiled pattern block, expand the flags field from 16 to 32 bits
299        because it was almost full.
300    
301    39. Try madvise first before posix_madvise.
302    
303    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
304        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
305        original change locked out all matches of empty strings. This has been
306        changed so that one match of an empty string per line is recognized.
307        Subsequent searches on the same line (for colouring or for --only-matching,
308        for example) do not recognize empty strings.
309    
310    41. Applied a user patch to fix a number of spelling mistakes in comments.
311    
312    42. Data lines longer than 65536 caused pcretest to crash.
313    
314    43. Clarified the data type for length and startoffset arguments for pcre_exec
315        and pcre_dfa_exec in the function-specific man pages, where they were
316        explicitly stated to be in bytes, never having been updated. I also added
317        some clarification to the pcreapi man page.
318    
319    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
320        a segmentation fault.
321    
322    
323    Version 8.32 30-November-2012
324  -----------------------------  -----------------------------
325    
326    1.  Improved JIT compiler optimizations for first character search and single
327        character iterators.
328    
329    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
330        Patch by Daniel Richard G.
331    
332    3.  Single character iterator optimizations in the JIT compiler.
333    
334    4.  Improved JIT compiler optimizations for character ranges.
335    
336    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
337        Reported by Giuseppe D'Angelo.
338    
339    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
340        of a line, was being set incorrectly in cases where .* appeared inside
341        atomic brackets at the start of a pattern, or where there was a subsequent
342        *PRUNE or *SKIP.
343    
344    7.  Improved instruction cache flush for POWER/PowerPC.
345        Patch by Daniel Richard G.
346    
347    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
348        grep:
349    
350        (a) There is now no limit to the number of patterns to be matched.
351    
352        (b) An error is given if a pattern is too long.
353    
354        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
355            are now supported.
356    
357        (d) --exclude-from and --include-from (multiple use) have been added.
358    
359        (e) Exclusions and inclusions now apply to all files and directories, not
360            just to those obtained from scanning a directory recursively.
361    
362        (f) Multiple uses of -f and --file-list are now supported.
363    
364        (g) In a Windows environment, the default for -d has been changed from
365            "read" (the GNU grep default) to "skip", because otherwise the presence
366            of a directory in the file list provokes an error.
367    
368        (h) The documentation has been revised and clarified in places.
369    
370    9.  Improve the matching speed of capturing brackets.
371    
372    10. Changed the meaning of \X so that it now matches a Unicode extended
373        grapheme cluster.
374    
375    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
376        out POSIX threads when JIT support is configured.
377    
378    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
379    
380    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
381        structure could go wrong in environments where size_t is not the same size
382        as int.
383    
384    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
385        set.
386    
387    15. The EBCDIC support had decayed; later updates to the code had included
388        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
389        general tidy up of EBCDIC-related issues, and the documentation was also
390        not quite right. There is now a test that can be run on ASCII systems to
391        check some of the EBCDIC-related things (but is it not a full test).
392    
393    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
394        in a small tidy to the code.
395    
396    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
397    
398    18. If the --only-matching (-o) option in pcregrep is specified multiple
399        times, each one causes appropriate output. For example, -o1 -o2 outputs the
400        substrings matched by the 1st and 2nd capturing parentheses. A separating
401        string can be specified by --om-separator (default empty).
402    
403    19. Improving the first n character searches.
404    
405    20. Turn case lists for horizontal and vertical white space into macros so that
406        they are defined only once.
407    
408    21. This set of changes together give more compatible Unicode case-folding
409        behaviour for characters that have more than one other case when UCP
410        support is available.
411    
412        (a) The Unicode property table now has offsets into a new table of sets of
413            three or more characters that are case-equivalent. The MultiStage2.py
414            script that generates these tables (the pcre_ucd.c file) now scans
415            CaseFolding.txt instead of UnicodeData.txt for character case
416            information.
417    
418        (b) The code for adding characters or ranges of characters to a character
419            class has been abstracted into a generalized function that also handles
420            case-independence. In UTF-mode with UCP support, this uses the new data
421            to handle characters with more than one other case.
422    
423        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
424            whose other case is greater than 256 are now correctly matched
425            caselessly. Previously, the high codepoint matched the low one, but not
426            vice versa.
427    
428        (d) The processing of \h, \H, \v, and \ in character classes now makes use
429            of the new class addition function, using character lists defined as
430            macros alongside the case definitions of 20 above.
431    
432        (e) Caseless back references now work with characters that have more than
433            one other case.
434    
435        (f) General caseless matching of characters with more than one other case
436            is supported.
437    
438    22. Unicode character properties were updated from Unicode 6.2.0
439    
440    23. Improved CMake support under Windows. Patch by Daniel Richard G.
441    
442    24. Add support for 32-bit character strings, and UTF-32
443    
444    25. Major JIT compiler update (code refactoring and bugfixing).
445        Experimental Sparc 32 support is added.
446    
447    26. Applied a modified version of Daniel Richard G's patch to create
448        pcre.h.generic and config.h.generic by "make" instead of in the
449        PrepareRelease script.
450    
451    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
452        pcre_compile.c when checking for a zero character.
453    
454    28. Introducing a native interface for JIT. Through this interface, the compiled
455        machine code can be directly executed. The purpose of this interface is to
456        provide fast pattern matching, so several sanity checks are not performed.
457        However, feature tests are still performed. The new interface provides
458        1.4x speedup compared to the old one.
459    
460    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
461        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
462        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
463    
464    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
465        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
466        the "old" RFC 2279). Instead, it ended up passing a negative length to
467        pcre_exec().
468    
469    31. Add support for GCC's visibility feature to hide internal functions.
470    
471    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
472        "unknown -C option" after outputting 0 or 1.
473    
474    33. There is now support for generating a code coverage report for the test
475        suite in environments where gcc is the compiler and lcov is installed. This
476        is mainly for the benefit of the developers.
477    
478    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
479        unaddressable using valgrind annotations, allowing valgrind to detect
480        invalid memory accesses. This is mainly for the benefit of the developers.
481    
482    25. (*UTF) can now be used to start a pattern in any of the three libraries.
483    
484    26. Give configure error if --enable-cpp but no C++ compiler found.
485    
486    
487    Version 8.31 06-July-2012
488    -------------------------
489    
490  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
491    
492  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
493    
494  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
495      to unsigned type, result still unsigned" that was given by an MS compiler      to unsigned type, result still unsigned" that was given by an MS compiler
496      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
497    
498  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
# Line 18  Version 8.31 Line 501  Version 8.31
501      of more than one character:      of more than one character:
502    
503      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
504          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
505          references.          references.
506    
507      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
508          subject.          subject.
509    
510      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
511          characters at the end of the subject.          characters at the end of the subject.
512    
513      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
# Line 33  Version 8.31 Line 516  Version 8.31
516      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
517          a partial match for a CR character at the end of the subject string.          a partial match for a CR character at the end of the subject string.
518    
519  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
520      running pcretest, the text "(JIT)" added to the output whenever JIT is      running pcretest, the text "(JIT)" added to the output whenever JIT is
521      actually used to run the match.      actually used to run the match.
522    
523  7.  Individual JIT compile options can be set in pcretest by following -s+[+]  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
524      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
525    
526  8.  OP_NOT now supports any UTF character not just single-byte ones.  8.  OP_NOT now supports any UTF character not just single-byte ones.
# Line 46  Version 8.31 Line 529  Version 8.31
529    
530  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
531      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
532    
533  11. Add PCRE_INFO_MAXLOOKBEHIND.  11. Add PCRE_INFO_MAXLOOKBEHIND.
534    
535  12. Applied a (slightly modified) user-supplied patch that improves performance  12. Applied a (slightly modified) user-supplied patch that improves performance
536      when the heap is used for recursion (compiled with --disable-stack-for-      when the heap is used for recursion (compiled with --disable-stack-for-
537      recursion). Instead of malloc and free for each heap frame each time a      recursion). Instead of malloc and free for each heap frame each time a
538      logical recursion happens, frames are retained on a chain and re-used where      logical recursion happens, frames are retained on a chain and re-used where
539      possible. This sometimes gives as much as 30% improvement.      possible. This sometimes gives as much as 30% improvement.
540    
541  13. As documented, (*COMMIT) is now confined to within a recursive subpattern  13. As documented, (*COMMIT) is now confined to within a recursive subpattern
542      call.      call.
543    
544  14. As documented, (*COMMIT) is now confined to within a positive assertion.  14. As documented, (*COMMIT) is now confined to within a positive assertion.
545    
546  15. It is now possible to link pcretest with libedit as an alternative to  15. It is now possible to link pcretest with libedit as an alternative to
547      libreadline.      libreadline.
548    
549  16. (*COMMIT) control verb is now supported by the JIT compiler.  16. (*COMMIT) control verb is now supported by the JIT compiler.
550    
551  6.  The Unicode data tables have been updated to Unicode 6.1.0.  17. The Unicode data tables have been updated to Unicode 6.1.0.
552    
553    18. Added --file-list option to pcregrep.
554    
555    19. Added binary file support to pcregrep, including the -a, --binary-files,
556        -I, and --text options.
557    
558    20. The madvise function is renamed for posix_madvise for QNX compatibility
559        reasons. Fixed by Giuseppe D'Angelo.
560    
561    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
562    
563    22. Changed the option for creating symbolic links for 16-bit man pages from
564        -s to -sf so that re-installing does not cause issues.
565    
566    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
567    
568    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
569        matches in certain environments (the workspace was not being correctly
570        retained). Also added to pcre_dfa_exec() a simple plausibility check on
571        some of the workspace data at the beginning of a restart.
572    
573    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
574        was not doing so when it should - probably a typo introduced by SVN 528
575        (change 8.10/14).
576    
577    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
578        \w+ when the character tables indicated that \x{c4} was a word character.
579        There were several related cases, all because the tests for doing a table
580        lookup were testing for characters less than 127 instead of 255.
581    
582    27. If a pattern contains capturing parentheses that are not used in a match,
583        their slots in the ovector are set to -1. For those that are higher than
584        any matched groups, this happens at the end of processing. In the case when
585        there were back references that the ovector was too small to contain
586        (causing temporary malloc'd memory to be used during matching), and the
587        highest capturing number was not used, memory off the end of the ovector
588        was incorrectly being set to -1. (It was using the size of the temporary
589        memory instead of the true size.)
590    
591    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
592        ovector size, it uses memory at the end of the block that it has got.
593    
594    29. Check for an overlong MARK name and give an error at compile time. The
595        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
596    
597    30. JIT compiler update.
598    
599    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
600        Rill for the patch.
601    
602    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
603    
604    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
605    
606    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
607        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
608        was enabled.
609    
610    35. Improve JIT code generation for greedy plus quantifier.
611    
612    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
613        1 to "aa" instead of to an empty string. The bug affected repeated groups
614        that could potentially match an empty string.
615    
616    37. Optimizing single character iterators in JIT.
617    
618    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
619        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
620        codepoints that are too big for the mode are faulted, and in a UTF mode,
621        disallowed codepoints are also faulted.
622    
623    39. If PCRE was compiled with UTF support, in three places in the DFA
624        matcher there was code that should only have been obeyed in UTF mode, but
625        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
626        processing when bytes with values greater than 127 were present. In 16-bit
627        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
628        both cases the values are those that cannot be the first data item in a UTF
629        character. The three items that might have provoked this were recursions,
630        possessively repeated groups, and atomic groups.
631    
632    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
633        and pcregrep, because some OS require shared objects to be explicitly
634        passed to ld, causing the link step to fail if they are not.
635    
636    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
637        mode, patterns that started with \h* or \R* might be incorrectly matched.
638    
639    
640  Version 8.30 04-February-2012  Version 8.30 04-February-2012
# Line 1258  Version 7.9 11-Apr-09 Line 1827  Version 7.9 11-Apr-09
1827  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1828      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1829      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1830      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1831        8.33.]
1832    
1833  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1834      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1501  Version 7.7 07-May-08 Line 2071  Version 7.7 07-May-08
2071      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2072      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2073      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2074      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2075      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2076      was subsequently set up correctly.)      was subsequently set up correctly.)
2077    

Legend:
Removed from v.942  
changed lines
  Added in v.1387

  ViewVC Help
Powered by ViewVC 1.1.5