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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.836  
changed lines
  Added in v.1335

  ViewVC Help
Powered by ViewVC 1.1.5