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

Diff of /code/trunk/ChangeLog

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

revision 236 by ph10, Tue Sep 11 12:57:06 2007 UTC revision 743 by ph10, Tue Nov 8 09:59:38 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.4 10-Sep-07  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    
21    Version 8.20 21-Oct-2011
22    ------------------------
23    
24    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
25        a POSIX class. After further experiments with Perl, which convinced me that
26        Perl has bugs and confusions, a closing square bracket is no longer allowed
27        in a POSIX name. This bug also affected patterns with classes that started
28        with full stops.
29    
30    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
31        captured substring, but while checking the failing first alternative,
32        substring 1 is temporarily captured. If the output vector supplied to
33        pcre_exec() was not big enough for this capture, the yield of the function
34        was still zero ("insufficient space for captured substrings"). This cannot
35        be totally fixed without adding another stack variable, which seems a lot
36        of expense for a edge case. However, I have improved the situation in cases
37        such as /(a)(b)x|abc/ matched against "abc", where the return code
38        indicates that fewer than the maximum number of slots in the ovector have
39        been set.
40    
41    3.  Related to (2) above: when there are more back references in a pattern than
42        slots in the output vector, pcre_exec() uses temporary memory during
43        matching, and copies in the captures as far as possible afterwards. It was
44        using the entire output vector, but this conflicts with the specification
45        that only 2/3 is used for passing back captured substrings. Now it uses
46        only the first 2/3, for compatibility. This is, of course, another edge
47        case.
48    
49    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
50        main code base, and can be used by building with --enable-jit. When this is
51        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
52        runtime --no-jit option is given.
53    
54    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
55        ovector, the return from the function was zero, implying that there were
56        other matches that did not fit. The correct "exactly full" value is now
57        returned.
58    
59    6.  If a subpattern that was called recursively or as a subroutine contained
60        (*PRUNE) or any other control that caused it to give a non-standard return,
61        invalid errors such as "Error -26 (nested recursion at the same subject
62        position)" or even infinite loops could occur.
63    
64    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
65        computing the minimum length on reaching *ACCEPT, and so ended up with the
66        wrong value of 1 rather than 0. Further investigation indicates that
67        computing a minimum subject length in the presence of *ACCEPT is difficult
68        (think back references, subroutine calls), and so I have changed the code
69        so that no minimum is registered for a pattern that contains *ACCEPT.
70    
71    8.  If (*THEN) was present in the first (true) branch of a conditional group,
72        it was not handled as intended. [But see 16 below.]
73    
74    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
75        Sheri Pierce.
76    
77    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
78        the first byte in a match must be "a".
79    
80    11. Change 17 for 8.13 increased the recursion depth for patterns like
81        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
82        pattern contains any instances of (*THEN). If it does not, the old
83        optimizations are restored. It would be nice to do this on a per-group
84        basis, but at the moment that is not feasible.
85    
86    12. In some environments, the output of pcretest -C is CRLF terminated. This
87        broke RunTest's code that checks for the link size. A single white space
88        character after the value is now allowed for.
89    
90    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
91        For "fr", it uses the Windows-specific input and output files.
92    
93    14. If (*THEN) appeared in a group that was called recursively or as a
94        subroutine, it did not work as intended. [But see next item.]
95    
96    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
97        pattern fragments (but not containing any | characters). If A and B are
98        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
99        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
100        D. In other words, Perl considers parentheses that do not contain any |
101        characters to be part of a surrounding alternative, whereas PCRE was
102        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
103        differently. PCRE now behaves in the same way as Perl, except in the case
104        of subroutine/recursion calls such as (?1) which have in any case always
105        been different (but PCRE had them first :-).
106    
107    16. Related to 15 above: Perl does not treat the | in a conditional group as
108        creating alternatives. Such a group is treated in the same way as an
109        ordinary group without any | characters when processing (*THEN). PCRE has
110        been changed to match Perl's behaviour.
111    
112    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
113        RunGrepTest script failed.
114    
115    18. Change 22 for version 13 caused atomic groups to use more stack. This is
116        inevitable for groups that contain captures, but it can lead to a lot of
117        stack use in large patterns. The old behaviour has been restored for atomic
118        groups that do not contain any capturing parentheses.
119    
120    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
121        suppress the check for a minimum subject length at run time. (If it was
122        given to pcre_exec() or pcre_dfa_exec() it did work.)
123    
124    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
125        fail to work when decoding hex characters in data strings in EBCDIC
126        environments.
127    
128    21. It appears that in at least one Mac OS environment, the isxdigit() function
129        is implemented as a macro that evaluates to its argument more than once,
130        contravening the C 90 Standard (I haven't checked a later standard). There
131        was an instance in pcretest which caused it to go wrong when processing
132        \x{...} escapes in subject strings. The has been rewritten to avoid using
133        things like p++ in the argument of isxdigit().
134    
135    
136    Version 8.13 16-Aug-2011
137    ------------------------
138    
139    1.  The Unicode data tables have been updated to Unicode 6.0.0.
140    
141    2.  Two minor typos in pcre_internal.h have been fixed.
142    
143    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
144        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
145        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
146    
147    4.  There were a number of related bugs in the code for matching backrefences
148        caselessly in UTF-8 mode when codes for the characters concerned were
149        different numbers of bytes. For example, U+023A and U+2C65 are an upper
150        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
151        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
152        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
153        2-byte code at the end of the subject (it thought there wasn't enough data
154        left).
155    
156    5.  Comprehensive information about what went wrong is now returned by
157        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
158        as the output vector has at least 2 elements. The offset of the start of
159        the failing character and a reason code are placed in the vector.
160    
161    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
162        now returned is for the first byte of the failing character, instead of the
163        last byte inspected. This is an incompatible change, but I hope it is small
164        enough not to be a problem. It makes the returned offset consistent with
165        pcre_exec() and pcre_dfa_exec().
166    
167    7.  pcretest now gives a text phrase as well as the error number when
168        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
169        failure, the offset and reason code are output.
170    
171    8.  When \R was used with a maximizing quantifier it failed to skip backwards
172        over a \r\n pair if the subsequent match failed. Instead, it just skipped
173        back over a single character (\n). This seems wrong (because it treated the
174        two characters as a single entity when going forwards), conflicts with the
175        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
176        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
177        has been changed.
178    
179    9.  Some internal refactoring has changed the processing so that the handling
180        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
181        time (the PCRE_DOTALL option was changed this way some time ago: version
182        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
183        which was always a bit of a fudge. It also means that there is one less
184        argument for the match() function, which reduces its stack requirements
185        slightly. This change also fixes an incompatibility with Perl: the pattern
186        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
187    
188    10. More internal refactoring has drastically reduced the number of recursive
189        calls to match() for possessively repeated groups such as (abc)++ when
190        using pcre_exec().
191    
192    11. While implementing 10, a number of bugs in the handling of groups were
193        discovered and fixed:
194    
195        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
196        (a|)*(?1) gave a compile-time internal error.
197        ((a|)+)+  did not notice that the outer group could match an empty string.
198        (^a|^)+   was not marked as anchored.
199        (.*a|.*)+ was not marked as matching at start or after a newline.
200    
201    12. Yet more internal refactoring has removed another argument from the match()
202        function. Special calls to this function are now indicated by setting a
203        value in a variable in the "match data" data block.
204    
205    13. Be more explicit in pcre_study() instead of relying on "default" for
206        opcodes that mean there is no starting character; this means that when new
207        ones are added and accidentally left out of pcre_study(), testing should
208        pick them up.
209    
210    14. The -s option of pcretest has been documented for ages as being an old
211        synonym of -m (show memory usage). I have changed it to mean "force study
212        for every regex", that is, assume /S for every regex. This is similar to -i
213        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
214        using it. It makes it easier to run collections of tests with and without
215        study enabled, and thereby test pcre_study() more easily. All the standard
216        tests are now run with and without -s (but some patterns can be marked as
217        "never study" - see 20 below).
218    
219    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
220        restoration of the capturing data to the outer values was not happening
221        correctly.
222    
223    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
224        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
225        pattern had matched an empty string, and so incorrectly returned a no
226        match.
227    
228    17. There was optimizing code for the last branch of non-capturing parentheses,
229        and also for the obeyed branch of a conditional subexpression, which used
230        tail recursion to cut down on stack usage. Unfortunately, now that there is
231        the possibility of (*THEN) occurring in these branches, tail recursion is
232        no longer possible because the return has to be checked for (*THEN). These
233        two optimizations have therefore been removed. [But see 8.20/11 above.]
234    
235    18. If a pattern containing \R was studied, it was assumed that \R always
236        matched two bytes, thus causing the minimum subject length to be
237        incorrectly computed because \R can also match just one byte.
238    
239    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
240        was incorrectly computed.
241    
242    20. If /S is present twice on a test pattern in pcretest input, it now
243        *disables* studying, thereby overriding the use of -s on the command line
244        (see 14 above). This is necessary for one or two tests to keep the output
245        identical in both cases.
246    
247    21. When (*ACCEPT) was used in an assertion that matched an empty string and
248        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
249    
250    22. When an atomic group that contained a capturing parenthesis was
251        successfully matched, but the branch in which it appeared failed, the
252        capturing was not being forgotten if a higher numbered group was later
253        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
254        group 1 to "a", when in fact it should be unset. This applied to multi-
255        branched capturing and non-capturing groups, repeated or not, and also to
256        positive assertions (capturing in negative assertions does not happen
257        in PCRE) and also to nested atomic groups.
258    
259    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
260        subject after a captured substring, to make it easier to tell which of a
261        number of identical substrings has been captured.
262    
263    24. The way atomic groups are processed by pcre_exec() has been changed so that
264        if they are repeated, backtracking one repetition now resets captured
265        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
266        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
267        "aaa". Previously, it would have been "a". As part of this code
268        refactoring, the way recursive calls are handled has also been changed.
269    
270    25. If an assertion condition captured any substrings, they were not passed
271        back unless some other capturing happened later. For example, if
272        (?(?=(a))a) was matched against "a", no capturing was returned.
273    
274    26. When studying a pattern that contained subroutine calls or assertions,
275        the code for finding the minimum length of a possible match was handling
276        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
277        group 1 called group 2 while simultaneously a separate group 2 called group
278        1). A stack overflow occurred in this case. I have fixed this by limiting
279        the recursion depth to 10.
280    
281    27. Updated RunTest.bat in the distribution to the version supplied by Tom
282        Fortmann. This supports explicit test numbers on the command line, and has
283        argument validation and error reporting.
284    
285    28. An instance of \X with an unlimited repeat could fail if at any point the
286        first character it looked at was a mark character.
287    
288    29. Some minor code refactoring concerning Unicode properties and scripts
289        should reduce the stack requirement of match() slightly.
290    
291    30. Added the '=' option to pcretest to check the setting of unused capturing
292        slots at the end of the pattern, which are documented as being -1, but are
293        not included in the return count.
294    
295    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
296        compiled something random. Now it gives a compile-time error (as does
297        Perl).
298    
299    32. A *MARK encountered during the processing of a positive assertion is now
300        recorded and passed back (compatible with Perl).
301    
302    33. If --only-matching or --colour was set on a pcregrep call whose pattern
303        had alternative anchored branches, the search for a second match in a line
304        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
305        matched the line "0102" twice. The same bug affected patterns that started
306        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
307        twice.
308    
309    34. Previously, PCRE did not allow quantification of assertions. However, Perl
310        does, and because of capturing effects, quantifying parenthesized
311        assertions may at times be useful. Quantifiers are now allowed for
312        parenthesized assertions.
313    
314    35. A minor code tidy in pcre_compile() when checking options for \R usage.
315    
316    36. \g was being checked for fancy things in a character class, when it should
317        just be a literal "g".
318    
319    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
320        appearance of a nested POSIX class supersedes an apparent external class.
321        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
322        unescaped square brackets may also appear as part of class names. For
323        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
324        more like Perl. (But see 8.20/1 above.)
325    
326    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
327        was because it thought it was \N{name}, which is not supported).
328    
329    39. Add minix to OS list not supporting the -S option in pcretest.
330    
331    40. PCRE tries to detect cases of infinite recursion at compile time, but it
332        cannot analyze patterns in sufficient detail to catch mutual recursions
333        such as ((?1))((?2)). There is now a runtime test that gives an error if a
334        subgroup is called recursively as a subpattern for a second time at the
335        same position in the subject string. In previous releases this might have
336        been caught by the recursion limit, or it might have run out of stack.
337    
338    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
339        happen only once. PCRE was, however incorrectly giving a compile time error
340        "recursive call could loop indefinitely" because it cannot analyze the
341        pattern in sufficient detail. The compile time test no longer happens when
342        PCRE is compiling a conditional subpattern, but actual runaway loops are
343        now caught at runtime (see 40 above).
344    
345    42. It seems that Perl allows any characters other than a closing parenthesis
346        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
347        has been changed to be the same.
348    
349    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
350        as not to get warnings when autogen.sh is called. Also changed
351        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
352    
353    44. To help people who use pcregrep to scan files containing exceedingly long
354        lines, the following changes have been made:
355    
356        (a) The default value of the buffer size parameter has been increased from
357            8K to 20K. (The actual buffer used is three times this size.)
358    
359        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
360            PCRE is built.
361    
362        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
363            to be set at run time.
364    
365        (d) Numerical values in pcregrep options can be followed by K or M, for
366            example --buffer-size=50K.
367    
368        (e) If a line being scanned overflows pcregrep's buffer, an error is now
369            given and the return code is set to 2.
370    
371    45. Add a pointer to the latest mark to the callout data block.
372    
373    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
374        partial match of an empty string instead of no match. This was specific to
375        the use of ".".
376    
377    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
378        complete match instead of a partial match. This bug was dependent on both
379        the PCRE_UTF8 and PCRE_DOTALL options being set.
380    
381    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
382        starting byte set, because \b was not being ignored.
383    
384    
385    Version 8.12 15-Jan-2011
386    ------------------------
387    
388    1.  Fixed some typos in the markup of the man pages, and wrote a script that
389        checks for such things as part of the documentation building process.
390    
391    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
392        --match-limit and --recursion-limit options (added for 8.11). In
393        particular, this made one of the standard tests fail. (The integer value
394        went into the wrong half of a long int.)
395    
396    3.  If the --colour option was given to pcregrep with -v (invert match), it
397        did strange things, either producing crazy output, or crashing. It should,
398        of course, ignore a request for colour when reporting lines that do not
399        match.
400    
401    4.  Another pcregrep bug caused similar problems if --colour was specified with
402        -M (multiline) and the pattern match finished with a line ending.
403    
404    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
405        matched in multiline mode, the following line was shown as part of the
406        match. This seems wrong, so I have changed it.
407    
408    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
409        the check for further matches in the same line (so they could be coloured)
410        to overrun the end of the current line. If another match was found, it was
411        incorrectly shown (and then shown again when found in the next line).
412    
413    7.  If pcregrep was compiled under Windows, there was a reference to the
414        function pcregrep_exit() before it was defined. I am assuming this was
415        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
416        reported by a user. I've moved the definition above the reference.
417    
418    
419    Version 8.11 10-Dec-2010
420    ------------------------
421    
422    1.  (*THEN) was not working properly if there were untried alternatives prior
423        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
424        backtracked to try for "b" instead of moving to the next alternative branch
425        at the same level (in this case, to look for "c"). The Perl documentation
426        is clear that when (*THEN) is backtracked onto, it goes to the "next
427        alternative in the innermost enclosing group".
428    
429    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
430        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
431        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
432        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
433        (*THEN).
434    
435    3.  If \s appeared in a character class, it removed the VT character from
436        the class, even if it had been included by some previous item, for example
437        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
438        of \s, but is part of the POSIX "space" class.)
439    
440    4.  A partial match never returns an empty string (because you can always
441        match an empty string at the end of the subject); however the checking for
442        an empty string was starting at the "start of match" point. This has been
443        changed to the "earliest inspected character" point, because the returned
444        data for a partial match starts at this character. This means that, for
445        example, /(?<=abc)def/ gives a partial match for the subject "abc"
446        (previously it gave "no match").
447    
448    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
449        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
450        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
451        has an implication that the given string is incomplete (because a partial
452        match is preferred over a full match). For this reason, these items now
453        give a partial match in this situation. [Aside: previously, the one case
454        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
455        match rather than a full match, which was wrong by the old rules, but is
456        now correct.]
457    
458    6.  There was a bug in the handling of #-introduced comments, recognized when
459        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
460        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
461        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
462        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
463        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
464        places in pcre_compile().
465    
466    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
467        comments when looking ahead for named forward references to subpatterns,
468        the only newline sequence it recognized was NL. It now handles newlines
469        according to the set newline convention.
470    
471    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
472        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
473        cater for a lack of strerror(). These oversights have been fixed.
474    
475    9.  Added --match-limit and --recursion-limit to pcregrep.
476    
477    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
478    
479    11. When the -o option was used, pcregrep was setting a return code of 1, even
480        when matches were found, and --line-buffered was not being honoured.
481    
482    12. Added an optional parentheses number to the -o and --only-matching options
483        of pcregrep.
484    
485    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
486        can match an empty string. The code to do it in pcretest and pcredemo
487        needed fixing:
488    
489        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
490            only one byte after an empty string match just before CRLF (this case
491            just got forgotten; "any" and "anycrlf" were OK).
492    
493        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
494            mode when an empty string match preceded an ASCII character followed by
495            a non-ASCII character. (The code for advancing by one character rather
496            than one byte was nonsense.)
497    
498        (c) The pcredemo.c sample program did not have any code at all to handle
499            the cases when CRLF is a valid newline sequence.
500    
501    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
502        as a starting offset was within the subject string. There is now a new
503        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
504        negative or greater than the length of the string. In order to test this,
505        pcretest is extended to allow the setting of negative starting offsets.
506    
507    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
508        starting offset points to the beginning of a UTF-8 character was
509        unnecessarily clumsy. I tidied it up.
510    
511    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
512        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
513    
514    17. Nobody had reported that the --include_dir option, which was added in
515        release 7.7 should have been called --include-dir (hyphen, not underscore)
516        for compatibility with GNU grep. I have changed it to --include-dir, but
517        left --include_dir as an undocumented synonym, and the same for
518        --exclude-dir, though that is not available in GNU grep, at least as of
519        release 2.5.4.
520    
521    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
522        characters from a string of bytes) have been redefined so as not to use
523        loops, in order to improve performance in some environments. At the same
524        time, I abstracted some of the common code into auxiliary macros to save
525        repetition (this should not affect the compiled code).
526    
527    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
528        compile-time error is now given if \c is not followed by an ASCII
529        character, that is, a byte less than 128. (In EBCDIC mode, the code is
530        different, and any byte value is allowed.)
531    
532    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
533        START_OPTIMIZE option, which is now allowed at compile time - but just
534        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
535        to pcregrep and other applications that have no direct access to PCRE
536        options. The new /Y option in pcretest sets this option when calling
537        pcre_compile().
538    
539    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
540        back references. Groups containing recursive back references were forced to
541        be atomic by that change, but in the case of named groups, the amount of
542        memory required was incorrectly computed, leading to "Failed: internal
543        error: code overflow". This has been fixed.
544    
545    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
546        pcretest.c, to avoid build problems in some Borland environments.
547    
548    
549    Version 8.10 25-Jun-2010
550    ------------------------
551    
552    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
553        THEN.
554    
555    2.  (*ACCEPT) was not working when inside an atomic group.
556    
557    3.  Inside a character class, \B is treated as a literal by default, but
558        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
559        causes the error). The code is unchanged, but I tidied the documentation.
560    
561    4.  Inside a character class, PCRE always treated \R and \X as literals,
562        whereas Perl faults them if its -w option is set. I have changed PCRE so
563        that it faults them when PCRE_EXTRA is set.
564    
565    5.  Added support for \N, which always matches any character other than
566        newline. (It is the same as "." when PCRE_DOTALL is not set.)
567    
568    6.  When compiling pcregrep with newer versions of gcc which may have
569        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
570        declared with attribute warn_unused_result" were given. Just casting the
571        result to (void) does not stop the warnings; a more elaborate fudge is
572        needed. I've used a macro to implement this.
573    
574    7.  Minor change to pcretest.c to avoid a compiler warning.
575    
576    8.  Added four artifical Unicode properties to help with an option to make
577        \s etc use properties (see next item). The new properties are: Xan
578        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
579    
580    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
581        use Unicode properties. (*UCP) at the start of a pattern can be used to set
582        this option. Modified pcretest to add /W to test this facility. Added
583        REG_UCP to make it available via the POSIX interface.
584    
585    10. Added --line-buffered to pcregrep.
586    
587    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
588        studied, and the match started with a letter with a code point greater than
589        127 whose first byte was different to the first byte of the other case of
590        the letter, the other case of this starting letter was not recognized
591        (#976).
592    
593    12. If a pattern that was studied started with a repeated Unicode property
594        test, for example, \p{Nd}+, there was the theoretical possibility of
595        setting up an incorrect bitmap of starting bytes, but fortunately it could
596        not have actually happened in practice until change 8 above was made (it
597        added property types that matched character-matching opcodes).
598    
599    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
600        possible starting bytes for non-anchored patterns.
601    
602    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
603        \R, and also a number of cases that involve Unicode properties, both
604        explicit and implicit when PCRE_UCP is set.
605    
606    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
607        input, it could crash or give wrong results if characters with values
608        greater than 0xc0 were present in the subject string. (Detail: it assumed
609        UTF-8 input when processing these items.)
610    
611    16. Added a lot of (int) casts to avoid compiler warnings in systems where
612        size_t is 64-bit (#991).
613    
614    17. Added a check for running out of memory when PCRE is compiled with
615        --disable-stack-for-recursion (#990).
616    
617    18. If the last data line in a file for pcretest does not have a newline on
618        the end, a newline was missing in the output.
619    
620    19. The default pcre_chartables.c file recognizes only ASCII characters (values
621        less than 128) in its various bitmaps. However, there is a facility for
622        generating tables according to the current locale when PCRE is compiled. It
623        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
624        characters, are recognized by isspace() and therefore were getting set in
625        these tables, and indeed these tables seem to approximate to ISO 8859. This
626        caused a problem in UTF-8 mode when pcre_study() was used to create a list
627        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
628        which of course cannot start UTF-8 characters. I have changed the code so
629        that only real ASCII characters (less than 128) and the correct starting
630        bytes for UTF-8 encodings are set for characters greater than 127 when in
631        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
632        altogether.)
633    
634    20. Added the /T option to pcretest so as to be able to run tests with non-
635        standard character tables, thus making it possible to include the tests
636        used for 19 above in the standard set of tests.
637    
638    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
639        reference to a subpattern the other side of a comment that contains an
640        opening parenthesis caused either an internal compiling error, or a
641        reference to the wrong subpattern.
642    
643    
644    Version 8.02 19-Mar-2010
645    ------------------------
646    
647    1.  The Unicode data tables have been updated to Unicode 5.2.0.
648    
649    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
650        configured.
651    
652    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
653        original author of that file, following a query about its status.
654    
655    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
656        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
657    
658    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
659        quantifier applied to a forward-referencing subroutine call, could compile
660        incorrect code or give the error "internal error: previously-checked
661        referenced subpattern not found".
662    
663    6.  Both MS Visual Studio and Symbian OS have problems with initializing
664        variables to point to external functions. For these systems, therefore,
665        pcre_malloc etc. are now initialized to local functions that call the
666        relevant global functions.
667    
668    7.  There were two entries missing in the vectors called coptable and poptable
669        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
670        I've fixed the data, and added a kludgy way of testing at compile time that
671        the lengths are correct (equal to the number of opcodes).
672    
673    8.  Following on from 7, I added a similar kludge to check the length of the
674        eint vector in pcreposix.c.
675    
676    9.  Error texts for pcre_compile() are held as one long string to avoid too
677        much relocation at load time. To find a text, the string is searched,
678        counting zeros. There was no check for running off the end of the string,
679        which could happen if a new error number was added without updating the
680        string.
681    
682    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
683    
684    11. \K was not working if it appeared in an atomic group or in a group that
685        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
686        \K is "not well defined" if used in an assertion. PCRE now accepts it if
687        the assertion is positive, but not if it is negative.
688    
689    12. Change 11 fortuitously reduced the size of the stack frame used in the
690        "match()" function of pcre_exec.c by one pointer. Forthcoming
691        implementation of support for (*MARK) will need an extra pointer on the
692        stack; I have reserved it now, so that the stack frame size does not
693        decrease.
694    
695    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
696        item in branch that calls a recursion is a subroutine call - as in the
697        second branch in the above example - was incorrectly given the compile-
698        time error "recursive call could loop indefinitely" because pcre_compile()
699        was not correctly checking the subroutine for matching a non-empty string.
700    
701    14. The checks for overrunning compiling workspace could trigger after an
702        overrun had occurred. This is a "should never occur" error, but it can be
703        triggered by pathological patterns such as hundreds of nested parentheses.
704        The checks now trigger 100 bytes before the end of the workspace.
705    
706    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
707    
708    
709    Version 8.01 19-Jan-2010
710    ------------------------
711    
712    1.  If a pattern contained a conditional subpattern with only one branch (in
713        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
714        computed the wrong minimum data length (which is of course zero for such
715        subpatterns). This could cause incorrect "no match" results.
716    
717    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
718        the pattern is reset in the first branch, pcre_compile() failed with
719        "internal error: code overflow at offset...". This happened only when
720        the reset was to the original external option setting. (An optimization
721        abstracts leading options settings into an external setting, which was the
722        cause of this.)
723    
724    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
725        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
726        assertion pattern did not match (meaning that the assertion was true), it
727        was incorrectly treated as false if the SKIP had been reached during the
728        matching. This also applied to assertions used as conditions.
729    
730    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
731        assertion subpattern, including such a pattern used as a condition,
732        unpredictable results occurred, instead of the error return
733        PCRE_ERROR_DFA_UITEM.
734    
735    5.  The C++ GlobalReplace function was not working like Perl for the special
736        situation when an empty string is matched. It now does the fancy magic
737        stuff that is necessary.
738    
739    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
740        removed. (These were left over from very, very early versions of PCRE.)
741    
742    7.  Some cosmetic changes to the code to make life easier when compiling it
743        as part of something else:
744    
745        (a) Change DEBUG to PCRE_DEBUG.
746    
747        (b) In pcre_compile(), rename the member of the "branch_chain" structure
748            called "current" as "current_branch", to prevent a collision with the
749            Linux macro when compiled as a kernel module.
750    
751        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
752            prevent a collision with the Linux macro when compiled as a kernel
753            module.
754    
755    8.  In pcre_compile() there are some checks for integer overflows that used to
756        cast potentially large values to (double). This has been changed to that
757        when building, a check for int64_t is made, and if it is found, it is used
758        instead, thus avoiding the use of floating point arithmetic. (There is no
759        other use of FP in PCRE.) If int64_t is not found, the fallback is to
760        double.
761    
762    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
763        2005 (difference between two addresses compared to an unsigned value).
764    
765    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
766        custom one, because of the following reported problem in Windows:
767    
768          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
769              under Win32.
770          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
771              therefore missing the function definition.
772          - The compiler thus generates a "C" signature for the test function.
773          - The linker fails to find the "C" function.
774          - PCRE fails to configure if asked to do so against libbz2.
775    
776    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
777        messages were output:
778    
779          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
780          rerunning libtoolize, to keep the correct libtool macros in-tree.
781          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
782    
783        I have done both of these things.
784    
785    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
786        most of the time, it *can* run out if it is given a pattern that contains a
787        runaway infinite recursion. I updated the discussion in the pcrestack man
788        page.
789    
790    13. Now that we have gone to the x.xx style of version numbers, the minor
791        version may start with zero. Using 08 or 09 is a bad idea because users
792        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
793        interpreted as invalid octal numbers. I've updated the previous comment in
794        configure.ac, and also added a check that gives an error if 08 or 09 are
795        used.
796    
797    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
798        causing partial matching to fail when the end of the subject matched \W
799        in a UTF-8 pattern where \W was quantified with a minimum of 3.
800    
801    15. There were some discrepancies between the declarations in pcre_internal.h
802        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
803        their definitions. The declarations used "const uschar *" and the
804        definitions used USPTR. Even though USPTR is normally defined as "const
805        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
806        reported that: "This difference in casting confuses some C++ compilers, for
807        example, SunCC recognizes above declarations as different functions and
808        generates broken code for hbpcre." I have changed the declarations to use
809        USPTR.
810    
811    16. GNU libtool is named differently on some systems. The autogen.sh script now
812        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
813        (FreeBSD).
814    
815    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
816        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
817        comment: "Figure out how to create a longlong from a string: strtoll and
818        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
819        instance, but it only takes 2 args instead of 3!"
820    
821    18. A subtle bug concerned with back references has been fixed by a change of
822        specification, with a corresponding code fix. A pattern such as
823        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
824        refers, was giving matches when it shouldn't. For example, xa=xaaa would
825        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
826        same bug. Such groups have to be quantified to be useful, or contained
827        inside another quantified group. (If there's no repetition, the reference
828        can never match.) The problem arises because, having left the group and
829        moved on to the rest of the pattern, a later failure that backtracks into
830        the group uses the captured value from the final iteration of the group
831        rather than the correct earlier one. I have fixed this in PCRE by forcing
832        any group that contains a reference to itself to be an atomic group; that
833        is, there cannot be any backtracking into it once it has completed. This is
834        similar to recursive and subroutine calls.
835    
836    
837    Version 8.00 19-Oct-09
838    ----------------------
839    
840    1.  The table for translating pcre_compile() error codes into POSIX error codes
841        was out-of-date, and there was no check on the pcre_compile() error code
842        being within the table. This could lead to an OK return being given in
843        error.
844    
845    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
846        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
847        in a Windows environment.
848    
849    3.  The pcregrep --count option prints the count for each file even when it is
850        zero, as does GNU grep. However, pcregrep was also printing all files when
851        --files-with-matches was added. Now, when both options are given, it prints
852        counts only for those files that have at least one match. (GNU grep just
853        prints the file name in this circumstance, but including the count seems
854        more useful - otherwise, why use --count?) Also ensured that the
855        combination -clh just lists non-zero counts, with no names.
856    
857    4.  The long form of the pcregrep -F option was incorrectly implemented as
858        --fixed_strings instead of --fixed-strings. This is an incompatible change,
859        but it seems right to fix it, and I didn't think it was worth preserving
860        the old behaviour.
861    
862    5.  The command line items --regex=pattern and --regexp=pattern were not
863        recognized by pcregrep, which required --regex pattern or --regexp pattern
864        (with a space rather than an '='). The man page documented the '=' forms,
865        which are compatible with GNU grep; these now work.
866    
867    6.  No libpcreposix.pc file was created for pkg-config; there was just
868        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
869    
870    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
871        when UCP support is not needed, by modifying the Python script that
872        generates it from Unicode data files. This should not matter if the module
873        is correctly used as a library, but I received one complaint about 50K of
874        unwanted data. My guess is that the person linked everything into his
875        program rather than using a library. Anyway, it does no harm.
876    
877    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
878        was a minimum greater than 1 for a wide character in a possessive
879        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
880        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
881        character. Chaos in the form of incorrect output or a compiling loop could
882        result.
883    
884    9.  The restrictions on what a pattern can contain when partial matching is
885        requested for pcre_exec() have been removed. All patterns can now be
886        partially matched by this function. In addition, if there are at least two
887        slots in the offset vector, the offset of the earliest inspected character
888        for the match and the offset of the end of the subject are set in them when
889        PCRE_ERROR_PARTIAL is returned.
890    
891    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
892        synonymous with PCRE_PARTIAL, for backwards compatibility, and
893        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
894        and may be more useful for multi-segment matching.
895    
896    11. Partial matching with pcre_exec() is now more intuitive. A partial match
897        used to be given if ever the end of the subject was reached; now it is
898        given only if matching could not proceed because another character was
899        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
900        string "Z", which now yields "no match" instead of "partial match". In the
901        case of pcre_dfa_exec(), "no match" is given if every matching path for the
902        final character ended with (*FAIL).
903    
904    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
905        if the pattern had a "must contain" character that was already found in the
906        earlier partial match, unless partial matching was again requested. For
907        example, with the pattern /dog.(body)?/, the "must contain" character is
908        "g". If the first part-match was for the string "dog", restarting with
909        "sbody" failed. This bug has been fixed.
910    
911    13. The string returned by pcre_dfa_exec() after a partial match has been
912        changed so that it starts at the first inspected character rather than the
913        first character of the match. This makes a difference only if the pattern
914        starts with a lookbehind assertion or \b or \B (\K is not supported by
915        pcre_dfa_exec()). It's an incompatible change, but it makes the two
916        matching functions compatible, and I think it's the right thing to do.
917    
918    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
919        so that the demonstration program is easily available in environments where
920        PCRE has not been installed from source.
921    
922    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
923        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
924        library.
925    
926    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
927        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
928        is not the first non-POSIX option to be added. Clearly some people find
929        these options useful.
930    
931    17. If a caller to the POSIX matching function regexec() passes a non-zero
932        value for nmatch with a NULL value for pmatch, the value of
933        nmatch is forced to zero.
934    
935    18. RunGrepTest did not have a test for the availability of the -u option of
936        the diff command, as RunTest does. It now checks in the same way as
937        RunTest, and also checks for the -b option.
938    
939    19. If an odd number of negated classes containing just a single character
940        interposed, within parentheses, between a forward reference to a named
941        subpattern and the definition of the subpattern, compilation crashed with
942        an internal error, complaining that it could not find the referenced
943        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
944        [The bug was that it was starting one character too far in when skipping
945        over the character class, thus treating the ] as data rather than
946        terminating the class. This meant it could skip too much.]
947    
948    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
949        /g option in pcretest when the pattern contains \K, which makes it possible
950        to have an empty string match not at the start, even when the pattern is
951        anchored. Updated pcretest and pcredemo to use this option.
952    
953    21. If the maximum number of capturing subpatterns in a recursion was greater
954        than the maximum at the outer level, the higher number was returned, but
955        with unset values at the outer level. The correct (outer level) value is
956        now given.
957    
958    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
959        PCRE did not set those parentheses (unlike Perl). I have now found a way to
960        make it do so. The string so far is captured, making this feature
961        compatible with Perl.
962    
963    23. The tests have been re-organized, adding tests 11 and 12, to make it
964        possible to check the Perl 5.10 features against Perl 5.10.
965    
966    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
967        pattern matches a fixed length string. PCRE did not allow this; now it
968        does. Neither allows recursion.
969    
970    25. I finally figured out how to implement a request to provide the minimum
971        length of subject string that was needed in order to match a given pattern.
972        (It was back references and recursion that I had previously got hung up
973        on.) This code has now been added to pcre_study(); it finds a lower bound
974        to the length of subject needed. It is not necessarily the greatest lower
975        bound, but using it to avoid searching strings that are too short does give
976        some useful speed-ups. The value is available to calling programs via
977        pcre_fullinfo().
978    
979    26. While implementing 25, I discovered to my embarrassment that pcretest had
980        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
981        study optimizations had never been tested with that matching function.
982        Oops. What is worse, even when it was passed study data, there was a bug in
983        pcre_dfa_exec() that meant it never actually used it. Double oops. There
984        were also very few tests of studied patterns with pcre_dfa_exec().
985    
986    27. If (?| is used to create subpatterns with duplicate numbers, they are now
987        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
988        on the other side of the coin, they are no longer allowed to have different
989        names, because these cannot be distinguished in PCRE, and this has caused
990        confusion. (This is a difference from Perl.)
991    
992    28. When duplicate subpattern names are present (necessarily with different
993        numbers, as required by 27 above), and a test is made by name in a
994        conditional pattern, either for a subpattern having been matched, or for
995        recursion in such a pattern, all the associated numbered subpatterns are
996        tested, and the overall condition is true if the condition is true for any
997        one of them. This is the way Perl works, and is also more like the way
998        testing by number works.
999    
1000    
1001    Version 7.9 11-Apr-09
1002    ---------------------
1003    
1004    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
1005        (pcretest), all targets were linked against these libraries. This included
1006        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1007        libraries. This caused unwanted dependencies to be created. This problem
1008        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1009        pcretest is linked with readline.
1010    
1011    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
1012        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1013        moved outside it again, because FALSE and TRUE are already defined in AIX,
1014        but BOOL is not.
1015    
1016    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1017        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1018    
1019    4.  The pcregrep documentation said spaces were inserted as well as colons (or
1020        hyphens) following file names and line numbers when outputting matching
1021        lines. This is not true; no spaces are inserted. I have also clarified the
1022        wording for the --colour (or --color) option.
1023    
1024    5.  In pcregrep, when --colour was used with -o, the list of matching strings
1025        was not coloured; this is different to GNU grep, so I have changed it to be
1026        the same.
1027    
1028    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
1029        each matching line was coloured. Now it goes on to look for further matches
1030        of any of the test patterns, which is the same behaviour as GNU grep.
1031    
1032    7.  A pattern that could match an empty string could cause pcregrep to loop; it
1033        doesn't make sense to accept an empty string match in pcregrep, so I have
1034        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1035        seems to be how GNU grep behaves.
1036    
1037    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1038        start or after a newline", because the conditional assertion was not being
1039        correctly handled. The rule now is that both the assertion and what follows
1040        in the first alternative must satisfy the test.
1041    
1042    9.  If auto-callout was enabled in a pattern with a conditional group whose
1043        condition was an assertion, PCRE could crash during matching, both with
1044        pcre_exec() and pcre_dfa_exec().
1045    
1046    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1047        used for matching.
1048    
1049    11. Unicode property support in character classes was not working for
1050        characters (bytes) greater than 127 when not in UTF-8 mode.
1051    
1052    12. Added the -M command line option to pcretest.
1053    
1054    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1055    
1056    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1057    
1058    16. Added comments and documentation about mis-use of no_arg in the C++
1059        wrapper.
1060    
1061    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1062        from Martin Jerabek that uses macro names for all relevant character and
1063        string constants.
1064    
1065    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1066        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1067        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1068        these, but not everybody uses configure.
1069    
1070    19. A conditional group that had only one branch was not being correctly
1071        recognized as an item that could match an empty string. This meant that an
1072        enclosing group might also not be so recognized, causing infinite looping
1073        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1074        with the subject "ab", where knowledge that the repeated group can match
1075        nothing is needed in order to break the loop.
1076    
1077    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1078        exec(), but without supplying a callout function, matching went wrong.
1079    
1080    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1081        leak if the size of the offset vector was greater than 30. When the vector
1082        is smaller, the saved offsets during recursion go onto a local stack
1083        vector, but for larger vectors malloc() is used. It was failing to free
1084        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1085        error, in fact).
1086    
1087    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1088        heapframe that is used only when UTF-8 support is enabled. This caused no
1089        problem, but was untidy.
1090    
1091    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1092        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1093        included within another project.
1094    
1095    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1096        slightly modified by me:
1097    
1098          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1099              not building pcregrep.
1100    
1101          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1102              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1103    
1104    25. Forward references, both numeric and by name, in patterns that made use of
1105        duplicate group numbers, could behave incorrectly or give incorrect errors,
1106        because when scanning forward to find the reference group, PCRE was not
1107        taking into account the duplicate group numbers. A pattern such as
1108        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1109    
1110    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1111        the feature of a custom pointer more persuasive (as requested by a user).
1112    
1113    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1114        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1115        pre-defined.
1116    
1117    28. Added support for (*UTF8) at the start of a pattern.
1118    
1119    29. Arrange for flags added by the "release type" setting in CMake to be shown
1120        in the configuration summary.
1121    
1122    
1123    Version 7.8 05-Sep-08
1124    ---------------------
1125    
1126    1.  Replaced UCP searching code with optimized version as implemented for Ad
1127        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1128        stage table and inline lookup instead of a function, giving speed ups of 2
1129        to 5 times on some simple patterns that I tested. Permission was given to
1130        distribute the MultiStage2.py script that generates the tables (it's not in
1131        the tarball, but is in the Subversion repository).
1132    
1133    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1134        scripts.
1135    
1136    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1137        a group with a zero qualifier. The result of the study could be incorrect,
1138        or the function might crash, depending on the pattern.
1139    
1140    4.  Caseless matching was not working for non-ASCII characters in back
1141        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1142        It now works when Unicode Property Support is available.
1143    
1144    5.  In pcretest, an escape such as \x{de} in the data was always generating
1145        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1146        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1147        truncation.
1148    
1149    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1150    
1151    7.  Added two (int) casts to pcregrep when printing the difference of two
1152        pointers, in case they are 64-bit values.
1153    
1154    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
1155        test 2 if it fails.
1156    
1157    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1158        and a #define of that name to empty if it is not externally set. This is to
1159        allow users of MSVC to set it if necessary.
1160    
1161    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1162        the convenience functions in the pcre_get.c source file.
1163    
1164    11. An option change at the start of a pattern that had top-level alternatives
1165        could cause overwriting and/or a crash. This command provoked a crash in
1166        some environments:
1167    
1168          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1169    
1170        This potential security problem was recorded as CVE-2008-2371.
1171    
1172    12. For a pattern where the match had to start at the beginning or immediately
1173        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1174        pcre_dfa_exec() could read past the end of the passed subject if there was
1175        no match. To help with detecting such bugs (e.g. with valgrind), I modified
1176        pcretest so that it places the subject at the end of its malloc-ed buffer.
1177    
1178    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1179        exec() might read past the end of the data buffer in UTF-8 mode.
1180    
1181    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1182        the data contained the byte 0x85 as part of a UTF-8 character within its
1183        first line. This applied both to normal and DFA matching.
1184    
1185    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1186        /^[^d]*?$/8 failed to match "abc".
1187    
1188    16. Added a missing copyright notice to pcrecpp_internal.h.
1189    
1190    17. Make it more clear in the documentation that values returned from
1191        pcre_exec() in ovector are byte offsets, not character counts.
1192    
1193    18. Tidied a few places to stop certain compilers from issuing warnings.
1194    
1195    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1196        supplied by Stefan Weber. I made a further small update for 7.8 because
1197        there is a change of source arrangements: the pcre_searchfuncs.c module is
1198        replaced by pcre_ucd.c.
1199    
1200    
1201    Version 7.7 07-May-08
1202    ---------------------
1203    
1204    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
1205        a string to a long long, pretend we don't even have a long long." This is
1206        done by checking for the strtoq, strtoll, and _strtoi64 functions.
1207    
1208    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1209        pre-7.6 versions, which defined a global no_arg variable instead of putting
1210        it in the RE class. (See also #8 below.)
1211    
1212    3.  Remove a line of dead code, identified by coverity and reported by Nuno
1213        Lopes.
1214    
1215    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
1216    
1217        (1) The include/exclude patterns were being applied to the whole pathnames
1218            of files, instead of just to the final components.
1219    
1220        (2) If there was more than one level of directory, the subdirectories were
1221            skipped unless they satisfied the include/exclude conditions. This is
1222            inconsistent with GNU grep (and could even be seen as contrary to the
1223            pcregrep specification - which I improved to make it absolutely clear).
1224            The action now is always to scan all levels of directory, and just
1225            apply the include/exclude patterns to regular files.
1226    
1227    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1228        --exclude_dir in the tests to avoid scanning .svn directories.
1229    
1230    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
1231        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1232        doesn't support NULs in patterns.
1233    
1234    7.  Added some missing "const"s to declarations of static tables in
1235        pcre_compile.c and pcre_dfa_exec.c.
1236    
1237    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1238        caused by fix #2  above. (Subsequently also a second patch to fix the
1239        first patch. And a third patch - this was a messy problem.)
1240    
1241    9.  Applied Craig's patch to remove the use of push_back().
1242    
1243    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1244        matching function regexec().
1245    
1246    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1247        which, however, unlike Perl's \g{...}, are subroutine calls, not back
1248        references. PCRE supports relative numbers with this syntax (I don't think
1249        Oniguruma does).
1250    
1251    12. Previously, a group with a zero repeat such as (...){0} was completely
1252        omitted from the compiled regex. However, this means that if the group
1253        was called as a subroutine from elsewhere in the pattern, things went wrong
1254        (an internal error was given). Such groups are now left in the compiled
1255        pattern, with a new opcode that causes them to be skipped at execution
1256        time.
1257    
1258    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1259        to the way PCRE behaves:
1260    
1261        (a) A lone ] character is dis-allowed (Perl treats it as data).
1262    
1263        (b) A back reference to an unmatched subpattern matches an empty string
1264            (Perl fails the current match path).
1265    
1266        (c) A data ] in a character class must be notated as \] because if the
1267            first data character in a class is ], it defines an empty class. (In
1268            Perl it is not possible to have an empty class.) The empty class []
1269            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1270            The negative empty class [^] matches any one character, independently
1271            of the DOTALL setting.
1272    
1273    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1274        non-existent subpattern following a character class starting with ']' and
1275        containing () gave an internal compiling error instead of "reference to
1276        non-existent subpattern". Fortunately, when the pattern did exist, the
1277        compiled code was correct. (When scanning forwards to check for the
1278        existencd of the subpattern, it was treating the data ']' as terminating
1279        the class, so got the count wrong. When actually compiling, the reference
1280        was subsequently set up correctly.)
1281    
1282    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1283        it was being rejected as not supported by pcre_dfa_exec(), even though
1284        other assertions are supported. I have made pcre_dfa_exec() support
1285        (*FAIL).
1286    
1287    16. The implementation of 13c above involved the invention of a new opcode,
1288        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1289        cannot be changed at match time, I realized I could make a small
1290        improvement to matching performance by compiling OP_ALLANY instead of
1291        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1292        on the OP_ANY path.
1293    
1294    17. Compiling pcretest on Windows with readline support failed without the
1295        following two fixes: (1) Make the unistd.h include conditional on
1296        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1297    
1298    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1299        ncurses library to be included for pcretest when ReadLine support is
1300        requested, but also to allow for it to be overridden. This patch came from
1301        Daniel Bergström.
1302    
1303    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1304        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1305        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1306        spotting this.
1307    
1308    
1309    Version 7.6 28-Jan-08
1310    ---------------------
1311    
1312    1.  A character class containing a very large number of characters with
1313        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
1314        overflow.
1315    
1316    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
1317        HAVE_LONG_LONG is not defined.
1318    
1319    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
1320        bring them up to date and include new features. This patch includes:
1321    
1322        - Fixed PH's badly added libz and libbz2 support.
1323        - Fixed a problem with static linking.
1324        - Added pcredemo. [But later removed - see 7 below.]
1325        - Fixed dftables problem and added an option.
1326        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
1327            HAVE_LONG_LONG.
1328        - Added readline support for pcretest.
1329        - Added an listing of the option settings after cmake has run.
1330    
1331    4.  A user submitted a patch to Makefile that makes it easy to create
1332        "pcre.dll" under mingw when using Configure/Make. I added stuff to
1333        Makefile.am that cause it to include this special target, without
1334        affecting anything else. Note that the same mingw target plus all
1335        the other distribution libraries and programs are now supported
1336        when configuring with CMake (see 6 below) instead of with
1337        Configure/Make.
1338    
1339    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
1340        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
1341        exported in the Windows port". It has not yet been confirmed that the patch
1342        solves the problem, but it does no harm.
1343    
1344    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
1345        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
1346        with CMake, and also correct the comment about stack recursion.
1347    
1348    7.  Remove the automatic building of pcredemo from the ./configure system and
1349        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
1350        of a program that users should build themselves after PCRE is installed, so
1351        building it automatically is not really right. What is more, it gave
1352        trouble in some build environments.
1353    
1354    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
1355    
1356    
1357    Version 7.5 10-Jan-08
1358    ---------------------
1359    
1360    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
1361        values in parens when parsing an RE using the C++ wrapper."
1362    
1363    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
1364        Characters greater than 255 were excluded from the class instead of being
1365        included.
1366    
1367    3.  The same bug as (2) above applied to negated POSIX classes such as
1368        [:^space:].
1369    
1370    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
1371        defined or documented. It seems to have been a typo for PCRE_STATIC, so
1372        I have changed it.
1373    
1374    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
1375        first named subpattern) and a construct such as (?&a) would reference the
1376        first named subpattern whose name started with "a" (in other words, the
1377        length check was missing). Both these problems are fixed. "Subpattern name
1378        expected" is now given for (?&) (a zero-length name), and this patch also
1379        makes it give the same error for \k'' (previously it complained that that
1380        was a reference to a non-existent subpattern).
1381    
1382    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
1383        this is right because (?- can be followed by option settings as well as by
1384        digits. I have, however, made the messages clearer.
1385    
1386    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1387        than the number used in the conditional) now cause a compile-time error.
1388        This is actually not compatible with Perl, which accepts such patterns, but
1389        treats the conditional as always being FALSE (as PCRE used to), but it
1390        seems to me that giving a diagnostic is better.
1391    
1392    8.  Change "alphameric" to the more common word "alphanumeric" in comments
1393        and messages.
1394    
1395    9.  Fix two occurrences of "backslash" in comments that should have been
1396        "backspace".
1397    
1398    10. Remove two redundant lines of code that can never be obeyed (their function
1399        was moved elsewhere).
1400    
1401    11. The program that makes PCRE's Unicode character property table had a bug
1402        which caused it to generate incorrect table entries for sequences of
1403        characters that have the same character type, but are in different scripts.
1404        It amalgamated them into a single range, with the script of the first of
1405        them. In other words, some characters were in the wrong script. There were
1406        thirteen such cases, affecting characters in the following ranges:
1407    
1408          U+002b0 - U+002c1
1409          U+0060c - U+0060d
1410          U+0061e - U+00612
1411          U+0064b - U+0065e
1412          U+0074d - U+0076d
1413          U+01800 - U+01805
1414          U+01d00 - U+01d77
1415          U+01d9b - U+01dbf
1416          U+0200b - U+0200f
1417          U+030fc - U+030fe
1418          U+03260 - U+0327f
1419          U+0fb46 - U+0fbb1
1420          U+10450 - U+1049d
1421    
1422    12. The -o option (show only the matching part of a line) for pcregrep was not
1423        compatible with GNU grep in that, if there was more than one match in a
1424        line, it showed only the first of them. It now behaves in the same way as
1425        GNU grep.
1426    
1427    13. If the -o and -v options were combined for pcregrep, it printed a blank
1428        line for every non-matching line. GNU grep prints nothing, and pcregrep now
1429        does the same. The return code can be used to tell if there were any
1430        non-matching lines.
1431    
1432    14. Added --file-offsets and --line-offsets to pcregrep.
1433    
1434    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1435        infinitely looping recursion. The bug was that positive lookaheads were not
1436        being skipped when checking for a possible empty match (negative lookaheads
1437        and both kinds of lookbehind were skipped).
1438    
1439    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1440        inclusion of <windows.h> to before rather than after the definition of
1441        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1442    
1443    17. Specifying a possessive quantifier with a specific limit for a Unicode
1444        character property caused pcre_compile() to compile bad code, which led at
1445        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1446        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1447        caused the error; without that there was no problem.
1448    
1449    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1450    
1451    19. Added --enable-pcretest-libreadline.
1452    
1453    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1454        RE::GlobalReplace(). As a result, the number of replacements returned was
1455        double what it should be. I removed one of the increments, but Craig sent a
1456        later patch that removed the other one (the right fix) and added unit tests
1457        that check the return values (which was not done before).
1458    
1459    21. Several CMake things:
1460    
1461        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1462            the names libpcre and libpcreposix, not just pcre and pcreposix.
1463    
1464        (2) The above change means that pcretest and pcregrep are now correctly
1465            linked with the newly-built libraries, not previously installed ones.
1466    
1467        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
1468    
1469    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1470        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1471        UTF-8 newline character). The key issue is that the pattern starts .*;
1472        this means that the match must be either at the beginning, or after a
1473        newline. The bug was in the code for advancing after a failed match and
1474        checking that the new position followed a newline. It was not taking
1475        account of UTF-8 characters correctly.
1476    
1477    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1478        character classes. PCRE was not treating the sequence [:...:] as a
1479        character class unless the ... were all letters. Perl, however, seems to
1480        allow any characters between [: and :], though of course it rejects as
1481        unknown any "names" that contain non-letters, because all the known class
1482        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1483        for example, whereas PCRE did not - it did not recognize a POSIX character
1484        class. This seemed a bit dangerous, so the code has been changed to be
1485        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1486        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1487        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1488        Perl does, and where it didn't before.
1489    
1490    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1491        Windows environments %n is disabled by default.
1492    
1493    
1494    Version 7.4 21-Sep-07
1495  ---------------------  ---------------------
1496    
1497  1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This  1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
# Line 25  Version 7.4 10-Sep-07 Line 1515  Version 7.4 10-Sep-07
1515    
1516  4.  Added options (at build time, compile time, exec time) to change \R from  4.  Added options (at build time, compile time, exec time) to change \R from
1517      matching any Unicode line ending sequence to just matching CR, LF, or CRLF.      matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
   
 5.  doc/pcresyntax.html was missing from the distribution.  
1518    
1519  6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward  5.  doc/pcresyntax.html was missing from the distribution.
1520    
1521    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1522      compatibility, even though it is no longer used.      compatibility, even though it is no longer used.
1523    
1524  7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and  7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1525      strtoull to pcrecpp.cc to select the available functions in WIN32 (where      strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1526      different names are used).      windows.h file is present (where different names are used). [This was
1527        reversed later after testing - see 16 below.]
1528  8.  Changed all #include <config.h> to #include "config.h". There were also  
1529    8.  Changed all #include <config.h> to #include "config.h". There were also
1530      some further <pcre.h> cases that I changed to "pcre.h".      some further <pcre.h> cases that I changed to "pcre.h".
1531    
1532    9.  When pcregrep was used with the --colour option, it missed the line ending
1533        sequence off the lines that it output.
1534    
1535    10. It was pointed out to me that arrays of string pointers cause lots of
1536        relocations when a shared library is dynamically loaded. A technique of
1537        using a single long string with a table of offsets can drastically reduce
1538        these. I have refactored PCRE in four places to do this. The result is
1539        dramatic:
1540    
1541          Originally:                          290
1542          After changing UCP table:            187
1543          After changing error message table:   43
1544          After changing table of "verbs"       36
1545          After changing table of Posix names   22
1546    
1547        Thanks to the folks working on Gregex for glib for this insight.
1548    
1549    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1550        unicode-properties was also set.
1551    
1552    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1553    
1554    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1555        checked only for CRLF.
1556    
1557    14. Added casts to pcretest.c to avoid compiler warnings.
1558    
1559    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1560    
1561    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1562        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1563        entirely. This removes changes made in 7 above.
1564    
1565    17. The CMake files have been updated, and there is now more information about
1566        building with CMake in the NON-UNIX-USE document.
1567    
1568    
1569  Version 7.3 28-Aug-07  Version 7.3 28-Aug-07
1570  ---------------------  ---------------------

Legend:
Removed from v.236  
changed lines
  Added in v.743

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12