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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.553  
changed lines
  Added in v.746

  ViewVC Help
Powered by ViewVC 1.1.5