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

Diff of /code/trunk/ChangeLog

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

revision 589 by ph10, Sat Jan 15 11:31:39 2011 UTC revision 888 by ph10, Tue Jan 17 14:43:23 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.15 12-Jan-2011  Version 8.30
5    ------------
6    
7    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
8        name is defined in ctype.h.
9    
10    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
11        only in quite long subpatterns.
12    
13    3.  Removed the function pcre_info(), which has been obsolete and deprecated
14        since it was replaced by pcre_fullinfo() in February 2000.
15    
16    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
17        match a (*MARK), and the match failed at the start of the subject, a
18        reference to memory before the start of the subject could occur. This bug
19        was introduced by fix 17 of release 8.21.
20    
21    5.  A reference to an unset group with zero minimum repetition was giving
22        totally wrong answers (in non-JavaScript-compatibility mode). For example,
23        /(another)?(\1?)test/ matched against "hello world test". This bug was
24        introduced in release 8.13.
25    
26    6.  Add support for 16-bit character strings (a large amount of work involving
27        many changes and refactorings).
28    
29    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
30        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
31        from a file.
32    
33    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
34        rounding is not applied in this particular case).
35    
36    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
37        if they appear, or are escaped, in patterns.
38    
39    10. Get rid of a number of -Wunused-but-set-variable warnings.
40    
41    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
42        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
43        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
44        also returns the mark "x". This bug applied to capturing parentheses,
45        non-capturing parentheses, and atomic parentheses. It also applied to some
46        assertions.
47    
48    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
49        information out of configure.ac instead of relying on pcre.h.generic, which
50        is not stored in the repository.
51    
52    
53    Version 8.21 12-Dec-2011
54    ------------------------
55    
56    1.  Updating the JIT compiler.
57    
58    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
59        are added as well.
60    
61    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
62        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
63        calling _pcre_jit_exec. Some extra comments are added.
64    
65    4.  (*MARK) settings inside atomic groups that do not contain any capturing
66        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
67        was introduced by change 18 for 8.20.
68    
69    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
70        ECMA-262 standard.
71    
72    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
73        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
74        This bug was probably introduced by change 9 of 8.13.
75    
76    7.  While fixing 6 above, I noticed that a number of other items were being
77        incorrectly rejected as "not fixed length". This arose partly because newer
78        opcodes had not been added to the fixed-length checking code. I have (a)
79        corrected the bug and added tests for these items, and (b) arranged for an
80        error to occur if an unknown opcode is encountered while checking for fixed
81        length instead of just assuming "not fixed length". The items that were
82        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
83        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
84        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
85    
86    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
87        being incorrectly compiled and would have given unpredicatble results.
88    
89    9.  A possessively repeated subpattern with minimum repeat count greater than
90        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
91        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
92        the first (A) could occur when it should not.
93    
94    10. Add a cast and remove a redundant test from the code.
95    
96    11. JIT should use pcre_malloc/pcre_free for allocation.
97    
98    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
99        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
100        is anything other than /usr, -L is still shown).
101    
102    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
103    
104    14. Perl does not support \N without a following name in a [] class; PCRE now
105        also gives an error.
106    
107    15. If a forward reference was repeated with an upper limit of around 2000,
108        it caused the error "internal error: overran compiling workspace". The
109        maximum number of forward references (including repeats) was limited by the
110        internal workspace, and dependent on the LINK_SIZE. The code has been
111        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
112        the default depends on LINK_SIZE. There is a new upper limit (for safety)
113        of around 200,000 forward references. While doing this, I also speeded up
114        the filling in of repeated forward references.
115    
116    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
117        incorrectly expecting the subject to contain another "a" after the start.
118    
119    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
120        in the match, the SKIP should be ignored. This was not happening; instead
121        the SKIP was being treated as NOMATCH. For patterns such as
122        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
123        tested.
124    
125    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
126        now much more compatible with Perl, in particular in cases where the result
127        is a non-match for a non-anchored pattern. For example, if
128        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
129        "m", where previously it did not return a name. A side effect of this
130        change is that for partial matches, the last encountered mark name is
131        returned, as for non matches. A number of tests that were previously not
132        Perl-compatible have been moved into the Perl-compatible test files. The
133        refactoring has had the pleasing side effect of removing one argument from
134        the match() function, thus reducing its stack requirements.
135    
136    19. If the /S+ option was used in pcretest to study a pattern using JIT,
137        subsequent uses of /S (without +) incorrectly behaved like /S+.
138    
139    21. Retrieve executable code size support for the JIT compiler and fixing
140        some warnings.
141    
142    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
143        not work when the shorter character appeared right at the end of the
144        subject string.
145    
146    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
147        systems.
148    
149    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
150        output it when the /M option is used in pcretest.
151    
152    25. The CheckMan script was not being included in the distribution. Also, added
153        an explicit "perl" to run Perl scripts from the PrepareRelease script
154        because this is reportedly needed in Windows.
155    
156    26. If study data was being save in a file and studying had not found a set of
157        "starts with" bytes for the pattern, the data written to the file (though
158        never used) was taken from uninitialized memory and so caused valgrind to
159        complain.
160    
161    27. Updated RunTest.bat as provided by Sheri Pierce.
162    
163    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
164    
165    29. Computation of memory usage for the table of capturing group names was
166        giving an unnecessarily large value.
167    
168    
169    Version 8.20 21-Oct-2011
170    ------------------------
171    
172    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
173        a POSIX class. After further experiments with Perl, which convinced me that
174        Perl has bugs and confusions, a closing square bracket is no longer allowed
175        in a POSIX name. This bug also affected patterns with classes that started
176        with full stops.
177    
178    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
179        captured substring, but while checking the failing first alternative,
180        substring 1 is temporarily captured. If the output vector supplied to
181        pcre_exec() was not big enough for this capture, the yield of the function
182        was still zero ("insufficient space for captured substrings"). This cannot
183        be totally fixed without adding another stack variable, which seems a lot
184        of expense for a edge case. However, I have improved the situation in cases
185        such as /(a)(b)x|abc/ matched against "abc", where the return code
186        indicates that fewer than the maximum number of slots in the ovector have
187        been set.
188    
189    3.  Related to (2) above: when there are more back references in a pattern than
190        slots in the output vector, pcre_exec() uses temporary memory during
191        matching, and copies in the captures as far as possible afterwards. It was
192        using the entire output vector, but this conflicts with the specification
193        that only 2/3 is used for passing back captured substrings. Now it uses
194        only the first 2/3, for compatibility. This is, of course, another edge
195        case.
196    
197    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
198        main code base, and can be used by building with --enable-jit. When this is
199        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
200        runtime --no-jit option is given.
201    
202    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
203        ovector, the return from the function was zero, implying that there were
204        other matches that did not fit. The correct "exactly full" value is now
205        returned.
206    
207    6.  If a subpattern that was called recursively or as a subroutine contained
208        (*PRUNE) or any other control that caused it to give a non-standard return,
209        invalid errors such as "Error -26 (nested recursion at the same subject
210        position)" or even infinite loops could occur.
211    
212    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
213        computing the minimum length on reaching *ACCEPT, and so ended up with the
214        wrong value of 1 rather than 0. Further investigation indicates that
215        computing a minimum subject length in the presence of *ACCEPT is difficult
216        (think back references, subroutine calls), and so I have changed the code
217        so that no minimum is registered for a pattern that contains *ACCEPT.
218    
219    8.  If (*THEN) was present in the first (true) branch of a conditional group,
220        it was not handled as intended. [But see 16 below.]
221    
222    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
223        Sheri Pierce.
224    
225    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
226        the first byte in a match must be "a".
227    
228    11. Change 17 for 8.13 increased the recursion depth for patterns like
229        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
230        pattern contains any instances of (*THEN). If it does not, the old
231        optimizations are restored. It would be nice to do this on a per-group
232        basis, but at the moment that is not feasible.
233    
234    12. In some environments, the output of pcretest -C is CRLF terminated. This
235        broke RunTest's code that checks for the link size. A single white space
236        character after the value is now allowed for.
237    
238    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
239        For "fr", it uses the Windows-specific input and output files.
240    
241    14. If (*THEN) appeared in a group that was called recursively or as a
242        subroutine, it did not work as intended. [But see next item.]
243    
244    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
245        pattern fragments (but not containing any | characters). If A and B are
246        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
247        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
248        D. In other words, Perl considers parentheses that do not contain any |
249        characters to be part of a surrounding alternative, whereas PCRE was
250        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
251        differently. PCRE now behaves in the same way as Perl, except in the case
252        of subroutine/recursion calls such as (?1) which have in any case always
253        been different (but PCRE had them first :-).
254    
255    16. Related to 15 above: Perl does not treat the | in a conditional group as
256        creating alternatives. Such a group is treated in the same way as an
257        ordinary group without any | characters when processing (*THEN). PCRE has
258        been changed to match Perl's behaviour.
259    
260    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
261        RunGrepTest script failed.
262    
263    18. Change 22 for version 13 caused atomic groups to use more stack. This is
264        inevitable for groups that contain captures, but it can lead to a lot of
265        stack use in large patterns. The old behaviour has been restored for atomic
266        groups that do not contain any capturing parentheses.
267    
268    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
269        suppress the check for a minimum subject length at run time. (If it was
270        given to pcre_exec() or pcre_dfa_exec() it did work.)
271    
272    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
273        fail to work when decoding hex characters in data strings in EBCDIC
274        environments.
275    
276    21. It appears that in at least one Mac OS environment, the isxdigit() function
277        is implemented as a macro that evaluates to its argument more than once,
278        contravening the C 90 Standard (I haven't checked a later standard). There
279        was an instance in pcretest which caused it to go wrong when processing
280        \x{...} escapes in subject strings. The has been rewritten to avoid using
281        things like p++ in the argument of isxdigit().
282    
283    
284    Version 8.13 16-Aug-2011
285    ------------------------
286    
287    1.  The Unicode data tables have been updated to Unicode 6.0.0.
288    
289    2.  Two minor typos in pcre_internal.h have been fixed.
290    
291    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
292        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
293        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
294    
295    4.  There were a number of related bugs in the code for matching backrefences
296        caselessly in UTF-8 mode when codes for the characters concerned were
297        different numbers of bytes. For example, U+023A and U+2C65 are an upper
298        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
299        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
300        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
301        2-byte code at the end of the subject (it thought there wasn't enough data
302        left).
303    
304    5.  Comprehensive information about what went wrong is now returned by
305        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
306        as the output vector has at least 2 elements. The offset of the start of
307        the failing character and a reason code are placed in the vector.
308    
309    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
310        now returned is for the first byte of the failing character, instead of the
311        last byte inspected. This is an incompatible change, but I hope it is small
312        enough not to be a problem. It makes the returned offset consistent with
313        pcre_exec() and pcre_dfa_exec().
314    
315    7.  pcretest now gives a text phrase as well as the error number when
316        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
317        failure, the offset and reason code are output.
318    
319    8.  When \R was used with a maximizing quantifier it failed to skip backwards
320        over a \r\n pair if the subsequent match failed. Instead, it just skipped
321        back over a single character (\n). This seems wrong (because it treated the
322        two characters as a single entity when going forwards), conflicts with the
323        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
324        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
325        has been changed.
326    
327    9.  Some internal refactoring has changed the processing so that the handling
328        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
329        time (the PCRE_DOTALL option was changed this way some time ago: version
330        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
331        which was always a bit of a fudge. It also means that there is one less
332        argument for the match() function, which reduces its stack requirements
333        slightly. This change also fixes an incompatibility with Perl: the pattern
334        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
335    
336    10. More internal refactoring has drastically reduced the number of recursive
337        calls to match() for possessively repeated groups such as (abc)++ when
338        using pcre_exec().
339    
340    11. While implementing 10, a number of bugs in the handling of groups were
341        discovered and fixed:
342    
343        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
344        (a|)*(?1) gave a compile-time internal error.
345        ((a|)+)+  did not notice that the outer group could match an empty string.
346        (^a|^)+   was not marked as anchored.
347        (.*a|.*)+ was not marked as matching at start or after a newline.
348    
349    12. Yet more internal refactoring has removed another argument from the match()
350        function. Special calls to this function are now indicated by setting a
351        value in a variable in the "match data" data block.
352    
353    13. Be more explicit in pcre_study() instead of relying on "default" for
354        opcodes that mean there is no starting character; this means that when new
355        ones are added and accidentally left out of pcre_study(), testing should
356        pick them up.
357    
358    14. The -s option of pcretest has been documented for ages as being an old
359        synonym of -m (show memory usage). I have changed it to mean "force study
360        for every regex", that is, assume /S for every regex. This is similar to -i
361        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
362        using it. It makes it easier to run collections of tests with and without
363        study enabled, and thereby test pcre_study() more easily. All the standard
364        tests are now run with and without -s (but some patterns can be marked as
365        "never study" - see 20 below).
366    
367    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
368        restoration of the capturing data to the outer values was not happening
369        correctly.
370    
371    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
372        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
373        pattern had matched an empty string, and so incorrectly returned a no
374        match.
375    
376    17. There was optimizing code for the last branch of non-capturing parentheses,
377        and also for the obeyed branch of a conditional subexpression, which used
378        tail recursion to cut down on stack usage. Unfortunately, now that there is
379        the possibility of (*THEN) occurring in these branches, tail recursion is
380        no longer possible because the return has to be checked for (*THEN). These
381        two optimizations have therefore been removed. [But see 8.20/11 above.]
382    
383    18. If a pattern containing \R was studied, it was assumed that \R always
384        matched two bytes, thus causing the minimum subject length to be
385        incorrectly computed because \R can also match just one byte.
386    
387    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
388        was incorrectly computed.
389    
390    20. If /S is present twice on a test pattern in pcretest input, it now
391        *disables* studying, thereby overriding the use of -s on the command line
392        (see 14 above). This is necessary for one or two tests to keep the output
393        identical in both cases.
394    
395    21. When (*ACCEPT) was used in an assertion that matched an empty string and
396        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
397    
398    22. When an atomic group that contained a capturing parenthesis was
399        successfully matched, but the branch in which it appeared failed, the
400        capturing was not being forgotten if a higher numbered group was later
401        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
402        group 1 to "a", when in fact it should be unset. This applied to multi-
403        branched capturing and non-capturing groups, repeated or not, and also to
404        positive assertions (capturing in negative assertions does not happen
405        in PCRE) and also to nested atomic groups.
406    
407    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
408        subject after a captured substring, to make it easier to tell which of a
409        number of identical substrings has been captured.
410    
411    24. The way atomic groups are processed by pcre_exec() has been changed so that
412        if they are repeated, backtracking one repetition now resets captured
413        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
414        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
415        "aaa". Previously, it would have been "a". As part of this code
416        refactoring, the way recursive calls are handled has also been changed.
417    
418    25. If an assertion condition captured any substrings, they were not passed
419        back unless some other capturing happened later. For example, if
420        (?(?=(a))a) was matched against "a", no capturing was returned.
421    
422    26. When studying a pattern that contained subroutine calls or assertions,
423        the code for finding the minimum length of a possible match was handling
424        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
425        group 1 called group 2 while simultaneously a separate group 2 called group
426        1). A stack overflow occurred in this case. I have fixed this by limiting
427        the recursion depth to 10.
428    
429    27. Updated RunTest.bat in the distribution to the version supplied by Tom
430        Fortmann. This supports explicit test numbers on the command line, and has
431        argument validation and error reporting.
432    
433    28. An instance of \X with an unlimited repeat could fail if at any point the
434        first character it looked at was a mark character.
435    
436    29. Some minor code refactoring concerning Unicode properties and scripts
437        should reduce the stack requirement of match() slightly.
438    
439    30. Added the '=' option to pcretest to check the setting of unused capturing
440        slots at the end of the pattern, which are documented as being -1, but are
441        not included in the return count.
442    
443    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
444        compiled something random. Now it gives a compile-time error (as does
445        Perl).
446    
447    32. A *MARK encountered during the processing of a positive assertion is now
448        recorded and passed back (compatible with Perl).
449    
450    33. If --only-matching or --colour was set on a pcregrep call whose pattern
451        had alternative anchored branches, the search for a second match in a line
452        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
453        matched the line "0102" twice. The same bug affected patterns that started
454        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
455        twice.
456    
457    34. Previously, PCRE did not allow quantification of assertions. However, Perl
458        does, and because of capturing effects, quantifying parenthesized
459        assertions may at times be useful. Quantifiers are now allowed for
460        parenthesized assertions.
461    
462    35. A minor code tidy in pcre_compile() when checking options for \R usage.
463    
464    36. \g was being checked for fancy things in a character class, when it should
465        just be a literal "g".
466    
467    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
468        appearance of a nested POSIX class supersedes an apparent external class.
469        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
470        unescaped square brackets may also appear as part of class names. For
471        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
472        more like Perl. (But see 8.20/1 above.)
473    
474    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
475        was because it thought it was \N{name}, which is not supported).
476    
477    39. Add minix to OS list not supporting the -S option in pcretest.
478    
479    40. PCRE tries to detect cases of infinite recursion at compile time, but it
480        cannot analyze patterns in sufficient detail to catch mutual recursions
481        such as ((?1))((?2)). There is now a runtime test that gives an error if a
482        subgroup is called recursively as a subpattern for a second time at the
483        same position in the subject string. In previous releases this might have
484        been caught by the recursion limit, or it might have run out of stack.
485    
486    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
487        happen only once. PCRE was, however incorrectly giving a compile time error
488        "recursive call could loop indefinitely" because it cannot analyze the
489        pattern in sufficient detail. The compile time test no longer happens when
490        PCRE is compiling a conditional subpattern, but actual runaway loops are
491        now caught at runtime (see 40 above).
492    
493    42. It seems that Perl allows any characters other than a closing parenthesis
494        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
495        has been changed to be the same.
496    
497    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
498        as not to get warnings when autogen.sh is called. Also changed
499        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
500    
501    44. To help people who use pcregrep to scan files containing exceedingly long
502        lines, the following changes have been made:
503    
504        (a) The default value of the buffer size parameter has been increased from
505            8K to 20K. (The actual buffer used is three times this size.)
506    
507        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
508            PCRE is built.
509    
510        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
511            to be set at run time.
512    
513        (d) Numerical values in pcregrep options can be followed by K or M, for
514            example --buffer-size=50K.
515    
516        (e) If a line being scanned overflows pcregrep's buffer, an error is now
517            given and the return code is set to 2.
518    
519    45. Add a pointer to the latest mark to the callout data block.
520    
521    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
522        partial match of an empty string instead of no match. This was specific to
523        the use of ".".
524    
525    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
526        complete match instead of a partial match. This bug was dependent on both
527        the PCRE_UTF8 and PCRE_DOTALL options being set.
528    
529    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
530        starting byte set, because \b was not being ignored.
531    
532    
533    Version 8.12 15-Jan-2011
534  ------------------------  ------------------------
535    
536  1.  Fixed some typos in the markup of the man pages, and wrote a script that  1.  Fixed some typos in the markup of the man pages, and wrote a script that

Legend:
Removed from v.589  
changed lines
  Added in v.888

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12