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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.980  
changed lines
  Added in v.1414

  ViewVC Help
Powered by ViewVC 1.1.5