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

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

  ViewVC Help
Powered by ViewVC 1.1.5