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

Diff of /code/trunk/ChangeLog

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

revision 967 by zherczeg, Mon May 14 07:36:39 2012 UTC revision 1392 by ph10, Wed Nov 6 18:00:09 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    32. Added the "forbid" facility to pcretest so that putting tests into the
156        wrong test files can sometimes be quickly detected.
157    
158    33. There is now a limit (default 250) on the depth of nesting of parentheses.
159        This limit is imposed to control the amount of system stack used at compile
160        time. It can be changed at build time by --with-parens-nest-limit=xxx or
161        the equivalent in CMake.
162    
163    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
164        errors. Perl warns for these when in warning mode, but PCRE has no facility
165        for giving warnings.
166    
167    
168    Version 8.33 28-May-2013
169    ------------------------
170    
171    1.  Added 'U' to some constants that are compared to unsigned integers, to
172        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
173        variables that are added to signed variables, to ensure the result is
174        signed and can be negated.
175    
176    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
177        CMake config files.
178    
179    3.  Revise the creation of config.h.generic so that all boolean macros are
180        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
181        overriding via -D on the command line possible.
182    
183    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
184        to unsigned int is reported to make a quite noticeable speed difference in
185        a specific Windows environment. Testing on Linux did also appear to show
186        some benefit (and it is clearly not harmful). Also fixed the definition of
187        Xop which should be unsigned.
188    
189    5.  Related to (4), changing the definition of the intermediate variable cc
190        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
191        improvements.
192    
193    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
194        unnecessary spaces.
195    
196    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
197        and later.
198    
199    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
200    
201    9.  Optimizing fast_forward_start_bits in JIT.
202    
203    10. Adding support for callouts in JIT, and fixing some issues revealed
204        during this work. Namely:
205    
206        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
207    
208        (b) Minimum length was not checked before the matching is started.
209    
210    11. The value of capture_last that is passed to callouts was incorrect in some
211        cases when there was a capture on one path that was subsequently abandoned
212        after a backtrack. Also, the capture_last value is now reset after a
213        recursion, since all captures are also reset in this case.
214    
215    12. The interpreter no longer returns the "too many substrings" error in the
216        case when an overflowing capture is in a branch that is subsequently
217        abandoned after a backtrack.
218    
219    13. In the pathological case when an offset vector of size 2 is used, pcretest
220        now prints out the matched string after a yield of 0 or 1.
221    
222    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
223        Only supported by the JIT compiler at the moment.
224    
225    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
226    
227    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
228        offset of the starting point of the matching process, provided the offsets
229        vector is large enough.
230    
231    17. The \A escape now records a lookbehind value of 1, though its execution
232        does not actually inspect the previous character. This is to ensure that,
233        in partial multi-segment matching, at least one character from the old
234        segment is retained when a new segment is processed. Otherwise, if there
235        are no lookbehinds in the pattern, \A might match incorrectly at the start
236        of a new segment.
237    
238    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
239    
240    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
241        gives some modest performance improvement in 8-bit mode.
242    
243    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
244        be expressed in certain programming languages using Universal Character
245        Names.
246    
247    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
248        which points out that "non characters" are not "characters that may not
249        appear in Unicode strings" but rather "characters that are reserved for
250        internal use and have only local meaning".
251    
252    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
253        there was a conditional group that depended on an assertion, if the
254        assertion was false, the callout that immediately followed the alternation
255        in the condition was skipped when pcre_exec() was used for matching.
256    
257    23. Allow an explicit callout to be inserted before an assertion that is the
258        condition for a conditional group, for compatibility with automatic
259        callouts, which always insert a callout at this point.
260    
261    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
262        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
263    
264    25. (*PRUNE) is now supported by the JIT compiler.
265    
266    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
267    
268    27. Fix the case where there are two or more SKIPs with arguments that may be
269        ignored.
270    
271    28. (*SKIP) is now supported by the JIT compiler.
272    
273    29. (*THEN) is now supported by the JIT compiler.
274    
275    30. Update RunTest with additional test selector options.
276    
277    31. The way PCRE handles backtracking verbs has been changed in two ways.
278    
279        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
280        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
281        backtracking. In some cases this makes it more Perl-compatible, but Perl's
282        rather obscure rules do not always do the same thing.
283    
284        (2) Previously, backtracking verbs were confined within assertions. This is
285        no longer the case for positive assertions, except for (*ACCEPT). Again,
286        this sometimes improves Perl compatibility, and sometimes does not.
287    
288    32. A number of tests that were in test 2 because Perl did things differently
289        have been moved to test 1, because either Perl or PCRE has changed, and
290        these tests are now compatible.
291    
292    32. Backtracking control verbs are now handled in the same way in JIT and
293        interpreter.
294    
295    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
296        contained a forward subroutine reference caused a compile error.
297    
298    34. Auto-detect and optimize limited repetitions in JIT.
299    
300    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
301        blocking (*UTF) etc.
302    
303    36. In the interpreter, maximizing pattern repetitions for characters and
304        character types now use tail recursion, which reduces stack usage.
305    
306    37. The value of the max lookbehind was not correctly preserved if a compiled
307        and saved regex was reloaded on a host of different endianness.
308    
309    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
310        of the compiled pattern block, expand the flags field from 16 to 32 bits
311        because it was almost full.
312    
313    39. Try madvise first before posix_madvise.
314    
315    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
316        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
317        original change locked out all matches of empty strings. This has been
318        changed so that one match of an empty string per line is recognized.
319        Subsequent searches on the same line (for colouring or for --only-matching,
320        for example) do not recognize empty strings.
321    
322    41. Applied a user patch to fix a number of spelling mistakes in comments.
323    
324    42. Data lines longer than 65536 caused pcretest to crash.
325    
326    43. Clarified the data type for length and startoffset arguments for pcre_exec
327        and pcre_dfa_exec in the function-specific man pages, where they were
328        explicitly stated to be in bytes, never having been updated. I also added
329        some clarification to the pcreapi man page.
330    
331    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
332        a segmentation fault.
333    
334    
335    Version 8.32 30-November-2012
336  -----------------------------  -----------------------------
337    
338    1.  Improved JIT compiler optimizations for first character search and single
339        character iterators.
340    
341    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
342        Patch by Daniel Richard G.
343    
344    3.  Single character iterator optimizations in the JIT compiler.
345    
346    4.  Improved JIT compiler optimizations for character ranges.
347    
348    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
349        Reported by Giuseppe D'Angelo.
350    
351    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
352        of a line, was being set incorrectly in cases where .* appeared inside
353        atomic brackets at the start of a pattern, or where there was a subsequent
354        *PRUNE or *SKIP.
355    
356    7.  Improved instruction cache flush for POWER/PowerPC.
357        Patch by Daniel Richard G.
358    
359    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
360        grep:
361    
362        (a) There is now no limit to the number of patterns to be matched.
363    
364        (b) An error is given if a pattern is too long.
365    
366        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
367            are now supported.
368    
369        (d) --exclude-from and --include-from (multiple use) have been added.
370    
371        (e) Exclusions and inclusions now apply to all files and directories, not
372            just to those obtained from scanning a directory recursively.
373    
374        (f) Multiple uses of -f and --file-list are now supported.
375    
376        (g) In a Windows environment, the default for -d has been changed from
377            "read" (the GNU grep default) to "skip", because otherwise the presence
378            of a directory in the file list provokes an error.
379    
380        (h) The documentation has been revised and clarified in places.
381    
382    9.  Improve the matching speed of capturing brackets.
383    
384    10. Changed the meaning of \X so that it now matches a Unicode extended
385        grapheme cluster.
386    
387    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
388        out POSIX threads when JIT support is configured.
389    
390    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
391    
392    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
393        structure could go wrong in environments where size_t is not the same size
394        as int.
395    
396    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
397        set.
398    
399    15. The EBCDIC support had decayed; later updates to the code had included
400        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
401        general tidy up of EBCDIC-related issues, and the documentation was also
402        not quite right. There is now a test that can be run on ASCII systems to
403        check some of the EBCDIC-related things (but is it not a full test).
404    
405    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
406        in a small tidy to the code.
407    
408    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
409    
410    18. If the --only-matching (-o) option in pcregrep is specified multiple
411        times, each one causes appropriate output. For example, -o1 -o2 outputs the
412        substrings matched by the 1st and 2nd capturing parentheses. A separating
413        string can be specified by --om-separator (default empty).
414    
415    19. Improving the first n character searches.
416    
417    20. Turn case lists for horizontal and vertical white space into macros so that
418        they are defined only once.
419    
420    21. This set of changes together give more compatible Unicode case-folding
421        behaviour for characters that have more than one other case when UCP
422        support is available.
423    
424        (a) The Unicode property table now has offsets into a new table of sets of
425            three or more characters that are case-equivalent. The MultiStage2.py
426            script that generates these tables (the pcre_ucd.c file) now scans
427            CaseFolding.txt instead of UnicodeData.txt for character case
428            information.
429    
430        (b) The code for adding characters or ranges of characters to a character
431            class has been abstracted into a generalized function that also handles
432            case-independence. In UTF-mode with UCP support, this uses the new data
433            to handle characters with more than one other case.
434    
435        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
436            whose other case is greater than 256 are now correctly matched
437            caselessly. Previously, the high codepoint matched the low one, but not
438            vice versa.
439    
440        (d) The processing of \h, \H, \v, and \ in character classes now makes use
441            of the new class addition function, using character lists defined as
442            macros alongside the case definitions of 20 above.
443    
444        (e) Caseless back references now work with characters that have more than
445            one other case.
446    
447        (f) General caseless matching of characters with more than one other case
448            is supported.
449    
450    22. Unicode character properties were updated from Unicode 6.2.0
451    
452    23. Improved CMake support under Windows. Patch by Daniel Richard G.
453    
454    24. Add support for 32-bit character strings, and UTF-32
455    
456    25. Major JIT compiler update (code refactoring and bugfixing).
457        Experimental Sparc 32 support is added.
458    
459    26. Applied a modified version of Daniel Richard G's patch to create
460        pcre.h.generic and config.h.generic by "make" instead of in the
461        PrepareRelease script.
462    
463    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
464        pcre_compile.c when checking for a zero character.
465    
466    28. Introducing a native interface for JIT. Through this interface, the compiled
467        machine code can be directly executed. The purpose of this interface is to
468        provide fast pattern matching, so several sanity checks are not performed.
469        However, feature tests are still performed. The new interface provides
470        1.4x speedup compared to the old one.
471    
472    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
473        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
474        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
475    
476    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
477        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
478        the "old" RFC 2279). Instead, it ended up passing a negative length to
479        pcre_exec().
480    
481    31. Add support for GCC's visibility feature to hide internal functions.
482    
483    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
484        "unknown -C option" after outputting 0 or 1.
485    
486    33. There is now support for generating a code coverage report for the test
487        suite in environments where gcc is the compiler and lcov is installed. This
488        is mainly for the benefit of the developers.
489    
490    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
491        unaddressable using valgrind annotations, allowing valgrind to detect
492        invalid memory accesses. This is mainly for the benefit of the developers.
493    
494    25. (*UTF) can now be used to start a pattern in any of the three libraries.
495    
496    26. Give configure error if --enable-cpp but no C++ compiler found.
497    
498    
499    Version 8.31 06-July-2012
500    -------------------------
501    
502  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
503    
504  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
# Line 95  Version 8.31 Line 590  Version 8.31
590      \w+ when the character tables indicated that \x{c4} was a word character.      \w+ when the character tables indicated that \x{c4} was a word character.
591      There were several related cases, all because the tests for doing a table      There were several related cases, all because the tests for doing a table
592      lookup were testing for characters less than 127 instead of 255.      lookup were testing for characters less than 127 instead of 255.
593    
594  27. If a pattern contains capturing parentheses that are not used in a match,  27. If a pattern contains capturing parentheses that are not used in a match,
595      their slots in the ovector are set to -1. For those that are higher than      their slots in the ovector are set to -1. For those that are higher than
596      any matched groups, this happens at the end of processing. In the case when      any matched groups, this happens at the end of processing. In the case when
597      there were back references that the ovector was too small to contain      there were back references that the ovector was too small to contain
598      (causing temporary malloc'd memory to be used during matching), and the      (causing temporary malloc'd memory to be used during matching), and the
599      highest capturing number was not used, memory off the end of the ovector      highest capturing number was not used, memory off the end of the ovector
600      was incorrectly being set to -1. (It was using the size of the temporary      was incorrectly being set to -1. (It was using the size of the temporary
601      memory instead of the true size.)      memory instead of the true size.)
602    
603  28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an  28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
604      ovector size, it uses memory at the end of the block that it has got.      ovector size, it uses memory at the end of the block that it has got.
605    
606  29. Check for an overlong MARK name and give an error at compile time. The  29. Check for an overlong MARK name and give an error at compile time. The
607      limit is 255 for the 8-bit library and 65535 for the 16-bit library.      limit is 255 for the 8-bit library and 65535 for the 16-bit library.
608    
609  30. JIT compiler update.  30. JIT compiler update.
# Line 116  Version 8.31 Line 611  Version 8.31
611  31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger  31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
612      Rill for the patch.      Rill for the patch.
613    
614    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
615    
616    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
617    
618    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
619        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
620        was enabled.
621    
622    35. Improve JIT code generation for greedy plus quantifier.
623    
624    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
625        1 to "aa" instead of to an empty string. The bug affected repeated groups
626        that could potentially match an empty string.
627    
628    37. Optimizing single character iterators in JIT.
629    
630    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
631        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
632        codepoints that are too big for the mode are faulted, and in a UTF mode,
633        disallowed codepoints are also faulted.
634    
635    39. If PCRE was compiled with UTF support, in three places in the DFA
636        matcher there was code that should only have been obeyed in UTF mode, but
637        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
638        processing when bytes with values greater than 127 were present. In 16-bit
639        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
640        both cases the values are those that cannot be the first data item in a UTF
641        character. The three items that might have provoked this were recursions,
642        possessively repeated groups, and atomic groups.
643    
644    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
645        and pcregrep, because some OS require shared objects to be explicitly
646        passed to ld, causing the link step to fail if they are not.
647    
648    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
649        mode, patterns that started with \h* or \R* might be incorrectly matched.
650    
651    
652  Version 8.30 04-February-2012  Version 8.30 04-February-2012
653  -----------------------------  -----------------------------
# Line 1307  Version 7.9 11-Apr-09 Line 1839  Version 7.9 11-Apr-09
1839  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
1840      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
1841      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1842      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1843        8.33.]
1844    
1845  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
1846      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 1550  Version 7.7 07-May-08 Line 2083  Version 7.7 07-May-08
2083      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2084      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2085      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2086      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2087      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2088      was subsequently set up correctly.)      was subsequently set up correctly.)
2089    

Legend:
Removed from v.967  
changed lines
  Added in v.1392

  ViewVC Help
Powered by ViewVC 1.1.5