/[pcre]/code/branches/pcre16/ChangeLog
ViewVC logotype

Diff of /code/branches/pcre16/ChangeLog

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

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

Legend:
Removed from v.511  
changed lines
  Added in v.734

  ViewVC Help
Powered by ViewVC 1.1.5