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

Diff of /code/trunk/ChangeLog

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

revision 388 by ph10, Wed Mar 11 17:03:17 2009 UTC revision 600 by ph10, Mon May 9 08:54:11 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.9 xx-xxx-09  Version 8.13 30-Apr-2011
5    ------------------------
6    
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
8    
9    2.  Two minor typos in pcre_internal.h have been fixed.
10    
11    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
12        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
13        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
14    
15    4.  There were a number of related bugs in the code for matching backrefences
16        caselessly in UTF-8 mode when codes for the characters concerned were
17        different numbers of bytes. For example, U+023A and U+2C65 are an upper
18        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
19        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
20        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
21        2-byte code at the end of the subject (it thought there wasn't enough data
22        left).
23    
24    5.  Comprehensive information about what went wrong is now returned by
25        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
26        as the output vector has at least 2 elements. The offset of the start of
27        the failing character and a reason code are placed in the vector.
28    
29    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
30        now returned is for the first byte of the failing character, instead of the
31        last byte inspected. This is an incompatible change, but I hope it is small
32        enough not to be a problem. It makes the returned offset consistent with
33        pcre_exec() and pcre_dfa_exec().
34    
35    7.  pcretest now gives a text phrase as well as the error number when
36        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
37        failure, the offset and reason code are output.
38    
39    8.  When \R was used with a maximizing quantifier it failed to skip backwards
40        over a \r\n pair if the subsequent match failed. Instead, it just skipped
41        back over a single character (\n). This seems wrong (because it treated the
42        two characters as a single entity when going forwards), conflicts with the
43        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
44        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
45        has been changed.
46    
47    
48    Version 8.12 15-Jan-2011
49    ------------------------
50    
51    1.  Fixed some typos in the markup of the man pages, and wrote a script that
52        checks for such things as part of the documentation building process.
53    
54    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
55        --match-limit and --recursion-limit options (added for 8.11). In
56        particular, this made one of the standard tests fail. (The integer value
57        went into the wrong half of a long int.)
58    
59    3.  If the --colour option was given to pcregrep with -v (invert match), it
60        did strange things, either producing crazy output, or crashing. It should,
61        of course, ignore a request for colour when reporting lines that do not
62        match.
63    
64    4.  Another pcregrep bug caused similar problems if --colour was specified with
65        -M (multiline) and the pattern match finished with a line ending.
66    
67    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
68        matched in multiline mode, the following line was shown as part of the
69        match. This seems wrong, so I have changed it.
70    
71    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
72        the check for further matches in the same line (so they could be coloured)
73        to overrun the end of the current line. If another match was found, it was
74        incorrectly shown (and then shown again when found in the next line).
75    
76    7.  If pcregrep was compiled under Windows, there was a reference to the
77        function pcregrep_exit() before it was defined. I am assuming this was
78        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
79        reported by a user. I've moved the definition above the reference.
80    
81    
82    Version 8.11 10-Dec-2010
83    ------------------------
84    
85    1.  (*THEN) was not working properly if there were untried alternatives prior
86        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
87        backtracked to try for "b" instead of moving to the next alternative branch
88        at the same level (in this case, to look for "c"). The Perl documentation
89        is clear that when (*THEN) is backtracked onto, it goes to the "next
90        alternative in the innermost enclosing group".
91    
92    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
93        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
94        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
95        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
96        (*THEN).
97    
98    3.  If \s appeared in a character class, it removed the VT character from
99        the class, even if it had been included by some previous item, for example
100        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
101        of \s, but is part of the POSIX "space" class.)
102    
103    4.  A partial match never returns an empty string (because you can always
104        match an empty string at the end of the subject); however the checking for
105        an empty string was starting at the "start of match" point. This has been
106        changed to the "earliest inspected character" point, because the returned
107        data for a partial match starts at this character. This means that, for
108        example, /(?<=abc)def/ gives a partial match for the subject "abc"
109        (previously it gave "no match").
110    
111    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
112        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
113        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
114        has an implication that the given string is incomplete (because a partial
115        match is preferred over a full match). For this reason, these items now
116        give a partial match in this situation. [Aside: previously, the one case
117        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
118        match rather than a full match, which was wrong by the old rules, but is
119        now correct.]
120    
121    6.  There was a bug in the handling of #-introduced comments, recognized when
122        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
123        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
124        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
125        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
126        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
127        places in pcre_compile().
128    
129    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
130        comments when looking ahead for named forward references to subpatterns,
131        the only newline sequence it recognized was NL. It now handles newlines
132        according to the set newline convention.
133    
134    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
135        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
136        cater for a lack of strerror(). These oversights have been fixed.
137    
138    9.  Added --match-limit and --recursion-limit to pcregrep.
139    
140    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
141    
142    11. When the -o option was used, pcregrep was setting a return code of 1, even
143        when matches were found, and --line-buffered was not being honoured.
144    
145    12. Added an optional parentheses number to the -o and --only-matching options
146        of pcregrep.
147    
148    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
149        can match an empty string. The code to do it in pcretest and pcredemo
150        needed fixing:
151    
152        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
153            only one byte after an empty string match just before CRLF (this case
154            just got forgotten; "any" and "anycrlf" were OK).
155    
156        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
157            mode when an empty string match preceded an ASCII character followed by
158            a non-ASCII character. (The code for advancing by one character rather
159            than one byte was nonsense.)
160    
161        (c) The pcredemo.c sample program did not have any code at all to handle
162            the cases when CRLF is a valid newline sequence.
163    
164    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
165        as a starting offset was within the subject string. There is now a new
166        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
167        negative or greater than the length of the string. In order to test this,
168        pcretest is extended to allow the setting of negative starting offsets.
169    
170    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
171        starting offset points to the beginning of a UTF-8 character was
172        unnecessarily clumsy. I tidied it up.
173    
174    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
175        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
176    
177    17. Nobody had reported that the --include_dir option, which was added in
178        release 7.7 should have been called --include-dir (hyphen, not underscore)
179        for compatibility with GNU grep. I have changed it to --include-dir, but
180        left --include_dir as an undocumented synonym, and the same for
181        --exclude-dir, though that is not available in GNU grep, at least as of
182        release 2.5.4.
183    
184    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
185        characters from a string of bytes) have been redefined so as not to use
186        loops, in order to improve performance in some environments. At the same
187        time, I abstracted some of the common code into auxiliary macros to save
188        repetition (this should not affect the compiled code).
189    
190    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
191        compile-time error is now given if \c is not followed by an ASCII
192        character, that is, a byte less than 128. (In EBCDIC mode, the code is
193        different, and any byte value is allowed.)
194    
195    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
196        START_OPTIMIZE option, which is now allowed at compile time - but just
197        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
198        to pcregrep and other applications that have no direct access to PCRE
199        options. The new /Y option in pcretest sets this option when calling
200        pcre_compile().
201    
202    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
203        back references. Groups containing recursive back references were forced to
204        be atomic by that change, but in the case of named groups, the amount of
205        memory required was incorrectly computed, leading to "Failed: internal
206        error: code overflow". This has been fixed.
207    
208    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
209        pcretest.c, to avoid build problems in some Borland environments.
210    
211    
212    Version 8.10 25-Jun-2010
213    ------------------------
214    
215    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
216        THEN.
217    
218    2.  (*ACCEPT) was not working when inside an atomic group.
219    
220    3.  Inside a character class, \B is treated as a literal by default, but
221        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
222        causes the error). The code is unchanged, but I tidied the documentation.
223    
224    4.  Inside a character class, PCRE always treated \R and \X as literals,
225        whereas Perl faults them if its -w option is set. I have changed PCRE so
226        that it faults them when PCRE_EXTRA is set.
227    
228    5.  Added support for \N, which always matches any character other than
229        newline. (It is the same as "." when PCRE_DOTALL is not set.)
230    
231    6.  When compiling pcregrep with newer versions of gcc which may have
232        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
233        declared with attribute warn_unused_result" were given. Just casting the
234        result to (void) does not stop the warnings; a more elaborate fudge is
235        needed. I've used a macro to implement this.
236    
237    7.  Minor change to pcretest.c to avoid a compiler warning.
238    
239    8.  Added four artifical Unicode properties to help with an option to make
240        \s etc use properties (see next item). The new properties are: Xan
241        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
242    
243    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
244        use Unicode properties. (*UCP) at the start of a pattern can be used to set
245        this option. Modified pcretest to add /W to test this facility. Added
246        REG_UCP to make it available via the POSIX interface.
247    
248    10. Added --line-buffered to pcregrep.
249    
250    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
251        studied, and the match started with a letter with a code point greater than
252        127 whose first byte was different to the first byte of the other case of
253        the letter, the other case of this starting letter was not recognized
254        (#976).
255    
256    12. If a pattern that was studied started with a repeated Unicode property
257        test, for example, \p{Nd}+, there was the theoretical possibility of
258        setting up an incorrect bitmap of starting bytes, but fortunately it could
259        not have actually happened in practice until change 8 above was made (it
260        added property types that matched character-matching opcodes).
261    
262    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
263        possible starting bytes for non-anchored patterns.
264    
265    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
266        \R, and also a number of cases that involve Unicode properties, both
267        explicit and implicit when PCRE_UCP is set.
268    
269    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
270        input, it could crash or give wrong results if characters with values
271        greater than 0xc0 were present in the subject string. (Detail: it assumed
272        UTF-8 input when processing these items.)
273    
274    16. Added a lot of (int) casts to avoid compiler warnings in systems where
275        size_t is 64-bit (#991).
276    
277    17. Added a check for running out of memory when PCRE is compiled with
278        --disable-stack-for-recursion (#990).
279    
280    18. If the last data line in a file for pcretest does not have a newline on
281        the end, a newline was missing in the output.
282    
283    19. The default pcre_chartables.c file recognizes only ASCII characters (values
284        less than 128) in its various bitmaps. However, there is a facility for
285        generating tables according to the current locale when PCRE is compiled. It
286        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
287        characters, are recognized by isspace() and therefore were getting set in
288        these tables, and indeed these tables seem to approximate to ISO 8859. This
289        caused a problem in UTF-8 mode when pcre_study() was used to create a list
290        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
291        which of course cannot start UTF-8 characters. I have changed the code so
292        that only real ASCII characters (less than 128) and the correct starting
293        bytes for UTF-8 encodings are set for characters greater than 127 when in
294        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
295        altogether.)
296    
297    20. Added the /T option to pcretest so as to be able to run tests with non-
298        standard character tables, thus making it possible to include the tests
299        used for 19 above in the standard set of tests.
300    
301    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
302        reference to a subpattern the other side of a comment that contains an
303        opening parenthesis caused either an internal compiling error, or a
304        reference to the wrong subpattern.
305    
306    
307    Version 8.02 19-Mar-2010
308    ------------------------
309    
310    1.  The Unicode data tables have been updated to Unicode 5.2.0.
311    
312    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
313        configured.
314    
315    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
316        original author of that file, following a query about its status.
317    
318    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
319        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
320    
321    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
322        quantifier applied to a forward-referencing subroutine call, could compile
323        incorrect code or give the error "internal error: previously-checked
324        referenced subpattern not found".
325    
326    6.  Both MS Visual Studio and Symbian OS have problems with initializing
327        variables to point to external functions. For these systems, therefore,
328        pcre_malloc etc. are now initialized to local functions that call the
329        relevant global functions.
330    
331    7.  There were two entries missing in the vectors called coptable and poptable
332        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
333        I've fixed the data, and added a kludgy way of testing at compile time that
334        the lengths are correct (equal to the number of opcodes).
335    
336    8.  Following on from 7, I added a similar kludge to check the length of the
337        eint vector in pcreposix.c.
338    
339    9.  Error texts for pcre_compile() are held as one long string to avoid too
340        much relocation at load time. To find a text, the string is searched,
341        counting zeros. There was no check for running off the end of the string,
342        which could happen if a new error number was added without updating the
343        string.
344    
345    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
346    
347    11. \K was not working if it appeared in an atomic group or in a group that
348        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
349        \K is "not well defined" if used in an assertion. PCRE now accepts it if
350        the assertion is positive, but not if it is negative.
351    
352    12. Change 11 fortuitously reduced the size of the stack frame used in the
353        "match()" function of pcre_exec.c by one pointer. Forthcoming
354        implementation of support for (*MARK) will need an extra pointer on the
355        stack; I have reserved it now, so that the stack frame size does not
356        decrease.
357    
358    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
359        item in branch that calls a recursion is a subroutine call - as in the
360        second branch in the above example - was incorrectly given the compile-
361        time error "recursive call could loop indefinitely" because pcre_compile()
362        was not correctly checking the subroutine for matching a non-empty string.
363    
364    14. The checks for overrunning compiling workspace could trigger after an
365        overrun had occurred. This is a "should never occur" error, but it can be
366        triggered by pathological patterns such as hundreds of nested parentheses.
367        The checks now trigger 100 bytes before the end of the workspace.
368    
369    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
370    
371    
372    Version 8.01 19-Jan-2010
373    ------------------------
374    
375    1.  If a pattern contained a conditional subpattern with only one branch (in
376        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
377        computed the wrong minimum data length (which is of course zero for such
378        subpatterns). This could cause incorrect "no match" results.
379    
380    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
381        the pattern is reset in the first branch, pcre_compile() failed with
382        "internal error: code overflow at offset...". This happened only when
383        the reset was to the original external option setting. (An optimization
384        abstracts leading options settings into an external setting, which was the
385        cause of this.)
386    
387    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
388        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
389        assertion pattern did not match (meaning that the assertion was true), it
390        was incorrectly treated as false if the SKIP had been reached during the
391        matching. This also applied to assertions used as conditions.
392    
393    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
394        assertion subpattern, including such a pattern used as a condition,
395        unpredictable results occurred, instead of the error return
396        PCRE_ERROR_DFA_UITEM.
397    
398    5.  The C++ GlobalReplace function was not working like Perl for the special
399        situation when an empty string is matched. It now does the fancy magic
400        stuff that is necessary.
401    
402    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
403        removed. (These were left over from very, very early versions of PCRE.)
404    
405    7.  Some cosmetic changes to the code to make life easier when compiling it
406        as part of something else:
407    
408        (a) Change DEBUG to PCRE_DEBUG.
409    
410        (b) In pcre_compile(), rename the member of the "branch_chain" structure
411            called "current" as "current_branch", to prevent a collision with the
412            Linux macro when compiled as a kernel module.
413    
414        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
415            prevent a collision with the Linux macro when compiled as a kernel
416            module.
417    
418    8.  In pcre_compile() there are some checks for integer overflows that used to
419        cast potentially large values to (double). This has been changed to that
420        when building, a check for int64_t is made, and if it is found, it is used
421        instead, thus avoiding the use of floating point arithmetic. (There is no
422        other use of FP in PCRE.) If int64_t is not found, the fallback is to
423        double.
424    
425    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
426        2005 (difference between two addresses compared to an unsigned value).
427    
428    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
429        custom one, because of the following reported problem in Windows:
430    
431          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
432              under Win32.
433          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
434              therefore missing the function definition.
435          - The compiler thus generates a "C" signature for the test function.
436          - The linker fails to find the "C" function.
437          - PCRE fails to configure if asked to do so against libbz2.
438    
439    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
440        messages were output:
441    
442          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
443          rerunning libtoolize, to keep the correct libtool macros in-tree.
444          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
445    
446        I have done both of these things.
447    
448    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
449        most of the time, it *can* run out if it is given a pattern that contains a
450        runaway infinite recursion. I updated the discussion in the pcrestack man
451        page.
452    
453    13. Now that we have gone to the x.xx style of version numbers, the minor
454        version may start with zero. Using 08 or 09 is a bad idea because users
455        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
456        interpreted as invalid octal numbers. I've updated the previous comment in
457        configure.ac, and also added a check that gives an error if 08 or 09 are
458        used.
459    
460    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
461        causing partial matching to fail when the end of the subject matched \W
462        in a UTF-8 pattern where \W was quantified with a minimum of 3.
463    
464    15. There were some discrepancies between the declarations in pcre_internal.h
465        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
466        their definitions. The declarations used "const uschar *" and the
467        definitions used USPTR. Even though USPTR is normally defined as "const
468        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
469        reported that: "This difference in casting confuses some C++ compilers, for
470        example, SunCC recognizes above declarations as different functions and
471        generates broken code for hbpcre." I have changed the declarations to use
472        USPTR.
473    
474    16. GNU libtool is named differently on some systems. The autogen.sh script now
475        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
476        (FreeBSD).
477    
478    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
479        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
480        comment: "Figure out how to create a longlong from a string: strtoll and
481        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
482        instance, but it only takes 2 args instead of 3!"
483    
484    18. A subtle bug concerned with back references has been fixed by a change of
485        specification, with a corresponding code fix. A pattern such as
486        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
487        refers, was giving matches when it shouldn't. For example, xa=xaaa would
488        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
489        same bug. Such groups have to be quantified to be useful, or contained
490        inside another quantified group. (If there's no repetition, the reference
491        can never match.) The problem arises because, having left the group and
492        moved on to the rest of the pattern, a later failure that backtracks into
493        the group uses the captured value from the final iteration of the group
494        rather than the correct earlier one. I have fixed this in PCRE by forcing
495        any group that contains a reference to itself to be an atomic group; that
496        is, there cannot be any backtracking into it once it has completed. This is
497        similar to recursive and subroutine calls.
498    
499    
500    Version 8.00 19-Oct-09
501    ----------------------
502    
503    1.  The table for translating pcre_compile() error codes into POSIX error codes
504        was out-of-date, and there was no check on the pcre_compile() error code
505        being within the table. This could lead to an OK return being given in
506        error.
507    
508    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
509        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
510        in a Windows environment.
511    
512    3.  The pcregrep --count option prints the count for each file even when it is
513        zero, as does GNU grep. However, pcregrep was also printing all files when
514        --files-with-matches was added. Now, when both options are given, it prints
515        counts only for those files that have at least one match. (GNU grep just
516        prints the file name in this circumstance, but including the count seems
517        more useful - otherwise, why use --count?) Also ensured that the
518        combination -clh just lists non-zero counts, with no names.
519    
520    4.  The long form of the pcregrep -F option was incorrectly implemented as
521        --fixed_strings instead of --fixed-strings. This is an incompatible change,
522        but it seems right to fix it, and I didn't think it was worth preserving
523        the old behaviour.
524    
525    5.  The command line items --regex=pattern and --regexp=pattern were not
526        recognized by pcregrep, which required --regex pattern or --regexp pattern
527        (with a space rather than an '='). The man page documented the '=' forms,
528        which are compatible with GNU grep; these now work.
529    
530    6.  No libpcreposix.pc file was created for pkg-config; there was just
531        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
532    
533    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
534        when UCP support is not needed, by modifying the Python script that
535        generates it from Unicode data files. This should not matter if the module
536        is correctly used as a library, but I received one complaint about 50K of
537        unwanted data. My guess is that the person linked everything into his
538        program rather than using a library. Anyway, it does no harm.
539    
540    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
541        was a minimum greater than 1 for a wide character in a possessive
542        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
543        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
544        character. Chaos in the form of incorrect output or a compiling loop could
545        result.
546    
547    9.  The restrictions on what a pattern can contain when partial matching is
548        requested for pcre_exec() have been removed. All patterns can now be
549        partially matched by this function. In addition, if there are at least two
550        slots in the offset vector, the offset of the earliest inspected character
551        for the match and the offset of the end of the subject are set in them when
552        PCRE_ERROR_PARTIAL is returned.
553    
554    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
555        synonymous with PCRE_PARTIAL, for backwards compatibility, and
556        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
557        and may be more useful for multi-segment matching.
558    
559    11. Partial matching with pcre_exec() is now more intuitive. A partial match
560        used to be given if ever the end of the subject was reached; now it is
561        given only if matching could not proceed because another character was
562        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
563        string "Z", which now yields "no match" instead of "partial match". In the
564        case of pcre_dfa_exec(), "no match" is given if every matching path for the
565        final character ended with (*FAIL).
566    
567    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
568        if the pattern had a "must contain" character that was already found in the
569        earlier partial match, unless partial matching was again requested. For
570        example, with the pattern /dog.(body)?/, the "must contain" character is
571        "g". If the first part-match was for the string "dog", restarting with
572        "sbody" failed. This bug has been fixed.
573    
574    13. The string returned by pcre_dfa_exec() after a partial match has been
575        changed so that it starts at the first inspected character rather than the
576        first character of the match. This makes a difference only if the pattern
577        starts with a lookbehind assertion or \b or \B (\K is not supported by
578        pcre_dfa_exec()). It's an incompatible change, but it makes the two
579        matching functions compatible, and I think it's the right thing to do.
580    
581    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
582        so that the demonstration program is easily available in environments where
583        PCRE has not been installed from source.
584    
585    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
586        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
587        library.
588    
589    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
590        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
591        is not the first non-POSIX option to be added. Clearly some people find
592        these options useful.
593    
594    17. If a caller to the POSIX matching function regexec() passes a non-zero
595        value for nmatch with a NULL value for pmatch, the value of
596        nmatch is forced to zero.
597    
598    18. RunGrepTest did not have a test for the availability of the -u option of
599        the diff command, as RunTest does. It now checks in the same way as
600        RunTest, and also checks for the -b option.
601    
602    19. If an odd number of negated classes containing just a single character
603        interposed, within parentheses, between a forward reference to a named
604        subpattern and the definition of the subpattern, compilation crashed with
605        an internal error, complaining that it could not find the referenced
606        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
607        [The bug was that it was starting one character too far in when skipping
608        over the character class, thus treating the ] as data rather than
609        terminating the class. This meant it could skip too much.]
610    
611    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
612        /g option in pcretest when the pattern contains \K, which makes it possible
613        to have an empty string match not at the start, even when the pattern is
614        anchored. Updated pcretest and pcredemo to use this option.
615    
616    21. If the maximum number of capturing subpatterns in a recursion was greater
617        than the maximum at the outer level, the higher number was returned, but
618        with unset values at the outer level. The correct (outer level) value is
619        now given.
620    
621    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
622        PCRE did not set those parentheses (unlike Perl). I have now found a way to
623        make it do so. The string so far is captured, making this feature
624        compatible with Perl.
625    
626    23. The tests have been re-organized, adding tests 11 and 12, to make it
627        possible to check the Perl 5.10 features against Perl 5.10.
628    
629    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
630        pattern matches a fixed length string. PCRE did not allow this; now it
631        does. Neither allows recursion.
632    
633    25. I finally figured out how to implement a request to provide the minimum
634        length of subject string that was needed in order to match a given pattern.
635        (It was back references and recursion that I had previously got hung up
636        on.) This code has now been added to pcre_study(); it finds a lower bound
637        to the length of subject needed. It is not necessarily the greatest lower
638        bound, but using it to avoid searching strings that are too short does give
639        some useful speed-ups. The value is available to calling programs via
640        pcre_fullinfo().
641    
642    26. While implementing 25, I discovered to my embarrassment that pcretest had
643        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
644        study optimizations had never been tested with that matching function.
645        Oops. What is worse, even when it was passed study data, there was a bug in
646        pcre_dfa_exec() that meant it never actually used it. Double oops. There
647        were also very few tests of studied patterns with pcre_dfa_exec().
648    
649    27. If (?| is used to create subpatterns with duplicate numbers, they are now
650        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
651        on the other side of the coin, they are no longer allowed to have different
652        names, because these cannot be distinguished in PCRE, and this has caused
653        confusion. (This is a difference from Perl.)
654    
655    28. When duplicate subpattern names are present (necessarily with different
656        numbers, as required by 27 above), and a test is made by name in a
657        conditional pattern, either for a subpattern having been matched, or for
658        recursion in such a pattern, all the associated numbered subpatterns are
659        tested, and the overall condition is true if the condition is true for any
660        one of them. This is the way Perl works, and is also more like the way
661        testing by number works.
662    
663    
664    Version 7.9 11-Apr-09
665  ---------------------  ---------------------
666    
667  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
668      (pcretest), all targets were linked against these libraries. This included      (pcretest), all targets were linked against these libraries. This included
669      libpcre, libpcreposix, and libpcrecpp, even though they do not use these      libpcre, libpcreposix, and libpcrecpp, even though they do not use these
670      libraries. This caused unwanted dependencies to be created. This problem      libraries. This caused unwanted dependencies to be created. This problem
671      has been fixed, and now only pcregrep is linked with bzlib/zlib and only      has been fixed, and now only pcregrep is linked with bzlib/zlib and only
672      pcretest is linked with readline.      pcretest is linked with readline.
673    
674  2.  The "typedef int BOOL" in pcre_internal.h that was included inside the  2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
675      "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been      "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
676      moved outside it again, because FALSE and TRUE are already defined in AIX,      moved outside it again, because FALSE and TRUE are already defined in AIX,
677      but BOOL is not.      but BOOL is not.
678    
679  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
680      PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.      PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
681    
682  4.  The pcregrep documentation said spaces were inserted as well as colons (or  4.  The pcregrep documentation said spaces were inserted as well as colons (or
683      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
684      lines. This is not true; no spaces are inserted. I have also clarified the      lines. This is not true; no spaces are inserted. I have also clarified the
685      wording for the --colour (or --color) option.      wording for the --colour (or --color) option.
686    
687  5.  In pcregrep, when --colour was used with -o, the list of matching strings  5.  In pcregrep, when --colour was used with -o, the list of matching strings
688      was not coloured; this is different to GNU grep, so I have changed it to be      was not coloured; this is different to GNU grep, so I have changed it to be
689      the same.      the same.
690    
691  6.  When --colo(u)r was used in pcregrep, only the first matching substring in  6.  When --colo(u)r was used in pcregrep, only the first matching substring in
692      each matching line was coloured. Now it goes on to look for further matches      each matching line was coloured. Now it goes on to look for further matches
693      of any of the test patterns, which is the same behaviour as GNU grep.      of any of the test patterns, which is the same behaviour as GNU grep.
694    
695  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
696      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
697      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
698      seems to be how GNU grep behaves.      seems to be how GNU grep behaves.
699    
700  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
701      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
702      correctly handled. The rule now is that both the assertion and what follows      correctly handled. The rule now is that both the assertion and what follows
703      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
704    
705  9.  If auto-callout was enabled in a pattern with a conditional group, PCRE  9.  If auto-callout was enabled in a pattern with a conditional group whose
706      could crash during matching.      condition was an assertion, PCRE could crash during matching, both with
707        pcre_exec() and pcre_dfa_exec().
708  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was  
709      used for matching.  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
710        used for matching.
711  11. Unicode property support in character classes was not working for  
712    11. Unicode property support in character classes was not working for
713      characters (bytes) greater than 127 when not in UTF-8 mode.      characters (bytes) greater than 127 when not in UTF-8 mode.
714    
715  12. Added the -M command line option to pcretest.  12. Added the -M command line option to pcretest.
716    
717  14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.  14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
718    
719    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
720    
721    16. Added comments and documentation about mis-use of no_arg in the C++
722        wrapper.
723    
724    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
725        from Martin Jerabek that uses macro names for all relevant character and
726        string constants.
727    
728    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
729        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
730        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
731        these, but not everybody uses configure.
732    
733    19. A conditional group that had only one branch was not being correctly
734        recognized as an item that could match an empty string. This meant that an
735        enclosing group might also not be so recognized, causing infinite looping
736        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
737        with the subject "ab", where knowledge that the repeated group can match
738        nothing is needed in order to break the loop.
739    
740    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
741        exec(), but without supplying a callout function, matching went wrong.
742    
743    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
744        leak if the size of the offset vector was greater than 30. When the vector
745        is smaller, the saved offsets during recursion go onto a local stack
746        vector, but for larger vectors malloc() is used. It was failing to free
747        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
748        error, in fact).
749    
750    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
751        heapframe that is used only when UTF-8 support is enabled. This caused no
752        problem, but was untidy.
753    
754    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
755        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
756        included within another project.
757    
758    24. Steven Van Ingelgem's patches to add more options to the CMake support,
759        slightly modified by me:
760    
761          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
762              not building pcregrep.
763    
764          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
765              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
766    
767    25. Forward references, both numeric and by name, in patterns that made use of
768        duplicate group numbers, could behave incorrectly or give incorrect errors,
769        because when scanning forward to find the reference group, PCRE was not
770        taking into account the duplicate group numbers. A pattern such as
771        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
772    
773    26. Changed a few more instances of "const unsigned char *" to USPTR, making
774        the feature of a custom pointer more persuasive (as requested by a user).
775    
776    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
777        pcretest.c, inside #ifndefs, because it seems they are sometimes already
778        pre-defined.
779    
780    28. Added support for (*UTF8) at the start of a pattern.
781    
782    29. Arrange for flags added by the "release type" setting in CMake to be shown
783        in the configuration summary.
784    
785    
786  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08
787  ---------------------  ---------------------

Legend:
Removed from v.388  
changed lines
  Added in v.600

  ViewVC Help
Powered by ViewVC 1.1.5