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

Diff of /code/trunk/ChangeLog

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

revision 335 by ph10, Sat Apr 12 14:36:14 2008 UTC revision 488 by ph10, Mon Jan 11 15:29:42 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 05-Mar-08  Version 8.01 01-Jan-10
5    ----------------------
6    
7    1.  If a pattern contained a conditional subpattern with only one branch (in
8        particular, this includes all (DEFINE) patterns), a call to pcre_study()
9        computed the wrong minimum data length (which is of course zero for such
10        subpatterns).
11    
12    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
13        the pattern is reset in the first branch, pcre_compile() failed with
14        "internal error: code overflow at offset...". This happened only when
15        the reset was to the original external option setting. (An optimization
16        abstracts leading options settings into an external setting, which was the
17        cause of this.)
18    
19    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
20        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
21        assertion pattern did not match (meaning that the assertion was true), it
22        was incorrectly treated as false if the SKIP had been reached during the
23        matching. This also applied to assertions used as conditions.
24    
25    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
26        assertion subpattern, including such a pattern used as a condition,
27        unpredictable results occurred, instead of the error return
28        PCRE_ERROR_DFA_UITEM.
29    
30    5.  The C++ GlobalReplace function was not working like Perl for the special
31        situation when an empty string is matched. It now does the fancy magic
32        stuff that is necessary.
33    
34    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
35        removed. (These were left over from very, very early versions of PCRE.)
36    
37    7.  Some cosmetic changes to the code to make life easier when compiling it
38        as part of something else:
39    
40        (a) Change DEBUG to PCRE_DEBUG.
41    
42        (b) In pcre_compile(), rename the member of the "branch_chain" structure
43            called "current" as "current_branch", to prevent a collision with the
44            Linux macro when compiled as a kernel module.
45    
46        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
47            prevent a collision with the Linux macro when compiled as a kernel
48            module.
49    
50    8.  In pcre_compile() there are some checks for integer overflows that used to
51        cast potentially large values to (double). This has been changed to that
52        when building, a check for int64_t is made, and if it is found, it is used
53        instead, thus avoiding the use of floating point arithmetic. (There is no
54        other use of FP in PCRE.) If int64_t is not found, the fallback is to
55        double.
56    
57    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
58        2005 (difference between two addresses compared to an unsigned value).
59    
60    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
61        custom one, because of the following reported problem in Windows:
62    
63          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
64            under Win32.
65          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
66            therefore missing the function definition.
67          - The compiler thus generates a "C" signature for the test function.
68          - The linker fails to find the "C" function.
69          - PCRE fails to configure if asked to do so against libbz2.
70    
71    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
72        messages were output:
73    
74          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
75          rerunning libtoolize, to keep the correct libtool macros in-tree.
76          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
77    
78        I have done both of these things.
79    
80    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
81        most of the time, it *can* run out if it is given a pattern that contains a
82        runaway infinite recursion. I updated the discussion in the pcrestack man
83        page.
84    
85    13. Now that we have gone to the x.xx style of version numbers, the minor
86        version may start with zero. Using 08 or 09 is a bad idea because users
87        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
88        interpreted as invalid octal numbers. I've updated the previous comment in
89        configure.ac, and also added a check that gives an error if 08 or 09 are
90        used.
91    
92    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
93        causing partial matching to fail when the end of the subject matched \W
94        in a UTF-8 pattern where \W was quantified with a minimum of 3.
95    
96    15. There were some discrepancies between the declarations in pcre_internal.h
97        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
98        their definitions. The declarations used "const uschar *" and the
99        definitions used USPTR. Even though USPTR is normally defined as "const
100        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
101        reported that: "This difference in casting confuses some C++ compilers, for
102        example, SunCC recognizes above declarations as different functions and
103        generates broken code for hbpcre." I have changed the declarations to use
104        USPTR.
105    
106    16. GNU libtool is named differently on some systems. The autogen.sh script now
107        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
108        (FreeBSD).
109    
110    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
111        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
112        comment: "Figure out how to create a longlong from a string: strtoll and
113        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
114        instance, but it only takes 2 args instead of 3!"
115    
116    18. A subtle bug concerned with back references has been fixed by a change of
117        specification, with a corresponding code fix. A pattern such as
118        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
119        refers, was giving matches when it shouldn't. For example, xa=xaaa would
120        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
121        same bug. Such groups have to be quantified to be useful, or contained
122        inside another quantified group. (If there's no repetition, the reference
123        can never match.) The problem arises because, having left the group and
124        moved on to the rest of the pattern, a later failure that backtracks into
125        the group uses the captured value from the final iteration of the group
126        rather than the correct earlier one. I have fixed this in PCRE by forcing
127        any group that contains a reference to itself to be an atomic group; that
128        is, there cannot be any backtracking into it once it has completed. This is
129        similar to recursive and subroutine calls.
130    
131    
132    Version 8.00 19-Oct-09
133    ----------------------
134    
135    1.  The table for translating pcre_compile() error codes into POSIX error codes
136        was out-of-date, and there was no check on the pcre_compile() error code
137        being within the table. This could lead to an OK return being given in
138        error.
139    
140    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
141        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
142        in a Windows environment.
143    
144    3.  The pcregrep --count option prints the count for each file even when it is
145        zero, as does GNU grep. However, pcregrep was also printing all files when
146        --files-with-matches was added. Now, when both options are given, it prints
147        counts only for those files that have at least one match. (GNU grep just
148        prints the file name in this circumstance, but including the count seems
149        more useful - otherwise, why use --count?) Also ensured that the
150        combination -clh just lists non-zero counts, with no names.
151    
152    4.  The long form of the pcregrep -F option was incorrectly implemented as
153        --fixed_strings instead of --fixed-strings. This is an incompatible change,
154        but it seems right to fix it, and I didn't think it was worth preserving
155        the old behaviour.
156    
157    5.  The command line items --regex=pattern and --regexp=pattern were not
158        recognized by pcregrep, which required --regex pattern or --regexp pattern
159        (with a space rather than an '='). The man page documented the '=' forms,
160        which are compatible with GNU grep; these now work.
161    
162    6.  No libpcreposix.pc file was created for pkg-config; there was just
163        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
164    
165    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
166        when UCP support is not needed, by modifying the Python script that
167        generates it from Unicode data files. This should not matter if the module
168        is correctly used as a library, but I received one complaint about 50K of
169        unwanted data. My guess is that the person linked everything into his
170        program rather than using a library. Anyway, it does no harm.
171    
172    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
173        was a minimum greater than 1 for a wide character in a possessive
174        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
175        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
176        character. Chaos in the form of incorrect output or a compiling loop could
177        result.
178    
179    9.  The restrictions on what a pattern can contain when partial matching is
180        requested for pcre_exec() have been removed. All patterns can now be
181        partially matched by this function. In addition, if there are at least two
182        slots in the offset vector, the offset of the earliest inspected character
183        for the match and the offset of the end of the subject are set in them when
184        PCRE_ERROR_PARTIAL is returned.
185    
186    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
187        synonymous with PCRE_PARTIAL, for backwards compatibility, and
188        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
189        and may be more useful for multi-segment matching.
190    
191    11. Partial matching with pcre_exec() is now more intuitive. A partial match
192        used to be given if ever the end of the subject was reached; now it is
193        given only if matching could not proceed because another character was
194        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
195        string "Z", which now yields "no match" instead of "partial match". In the
196        case of pcre_dfa_exec(), "no match" is given if every matching path for the
197        final character ended with (*FAIL).
198    
199    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
200        if the pattern had a "must contain" character that was already found in the
201        earlier partial match, unless partial matching was again requested. For
202        example, with the pattern /dog.(body)?/, the "must contain" character is
203        "g". If the first part-match was for the string "dog", restarting with
204        "sbody" failed. This bug has been fixed.
205    
206    13. The string returned by pcre_dfa_exec() after a partial match has been
207        changed so that it starts at the first inspected character rather than the
208        first character of the match. This makes a difference only if the pattern
209        starts with a lookbehind assertion or \b or \B (\K is not supported by
210        pcre_dfa_exec()). It's an incompatible change, but it makes the two
211        matching functions compatible, and I think it's the right thing to do.
212    
213    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
214        so that the demonstration program is easily available in environments where
215        PCRE has not been installed from source.
216    
217    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
218        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
219        library.
220    
221    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
222        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
223        is not the first non-POSIX option to be added. Clearly some people find
224        these options useful.
225    
226    17. If a caller to the POSIX matching function regexec() passes a non-zero
227        value for nmatch with a NULL value for pmatch, the value of
228        nmatch is forced to zero.
229    
230    18. RunGrepTest did not have a test for the availability of the -u option of
231        the diff command, as RunTest does. It now checks in the same way as
232        RunTest, and also checks for the -b option.
233    
234    19. If an odd number of negated classes containing just a single character
235        interposed, within parentheses, between a forward reference to a named
236        subpattern and the definition of the subpattern, compilation crashed with
237        an internal error, complaining that it could not find the referenced
238        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
239        [The bug was that it was starting one character too far in when skipping
240        over the character class, thus treating the ] as data rather than
241        terminating the class. This meant it could skip too much.]
242    
243    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
244        /g option in pcretest when the pattern contains \K, which makes it possible
245        to have an empty string match not at the start, even when the pattern is
246        anchored. Updated pcretest and pcredemo to use this option.
247    
248    21. If the maximum number of capturing subpatterns in a recursion was greater
249        than the maximum at the outer level, the higher number was returned, but
250        with unset values at the outer level. The correct (outer level) value is
251        now given.
252    
253    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
254        PCRE did not set those parentheses (unlike Perl). I have now found a way to
255        make it do so. The string so far is captured, making this feature
256        compatible with Perl.
257    
258    23. The tests have been re-organized, adding tests 11 and 12, to make it
259        possible to check the Perl 5.10 features against Perl 5.10.
260    
261    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
262        pattern matches a fixed length string. PCRE did not allow this; now it
263        does. Neither allows recursion.
264    
265    25. I finally figured out how to implement a request to provide the minimum
266        length of subject string that was needed in order to match a given pattern.
267        (It was back references and recursion that I had previously got hung up
268        on.) This code has now been added to pcre_study(); it finds a lower bound
269        to the length of subject needed. It is not necessarily the greatest lower
270        bound, but using it to avoid searching strings that are too short does give
271        some useful speed-ups. The value is available to calling programs via
272        pcre_fullinfo().
273    
274    26. While implementing 25, I discovered to my embarrassment that pcretest had
275        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
276        study optimizations had never been tested with that matching function.
277        Oops. What is worse, even when it was passed study data, there was a bug in
278        pcre_dfa_exec() that meant it never actually used it. Double oops. There
279        were also very few tests of studied patterns with pcre_dfa_exec().
280    
281    27. If (?| is used to create subpatterns with duplicate numbers, they are now
282        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
283        on the other side of the coin, they are no longer allowed to have different
284        names, because these cannot be distinguished in PCRE, and this has caused
285        confusion. (This is a difference from Perl.)
286    
287    28. When duplicate subpattern names are present (necessarily with different
288        numbers, as required by 27 above), and a test is made by name in a
289        conditional pattern, either for a subpattern having been matched, or for
290        recursion in such a pattern, all the associated numbered subpatterns are
291        tested, and the overall condition is true if the condition is true for any
292        one of them. This is the way Perl works, and is also more like the way
293        testing by number works.
294    
295    
296    Version 7.9 11-Apr-09
297    ---------------------
298    
299    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
300        (pcretest), all targets were linked against these libraries. This included
301        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
302        libraries. This caused unwanted dependencies to be created. This problem
303        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
304        pcretest is linked with readline.
305    
306    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
307        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
308        moved outside it again, because FALSE and TRUE are already defined in AIX,
309        but BOOL is not.
310    
311    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
312        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
313    
314    4.  The pcregrep documentation said spaces were inserted as well as colons (or
315        hyphens) following file names and line numbers when outputting matching
316        lines. This is not true; no spaces are inserted. I have also clarified the
317        wording for the --colour (or --color) option.
318    
319    5.  In pcregrep, when --colour was used with -o, the list of matching strings
320        was not coloured; this is different to GNU grep, so I have changed it to be
321        the same.
322    
323    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
324        each matching line was coloured. Now it goes on to look for further matches
325        of any of the test patterns, which is the same behaviour as GNU grep.
326    
327    7.  A pattern that could match an empty string could cause pcregrep to loop; it
328        doesn't make sense to accept an empty string match in pcregrep, so I have
329        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
330        seems to be how GNU grep behaves.
331    
332    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
333        start or after a newline", because the conditional assertion was not being
334        correctly handled. The rule now is that both the assertion and what follows
335        in the first alternative must satisfy the test.
336    
337    9.  If auto-callout was enabled in a pattern with a conditional group whose
338        condition was an assertion, PCRE could crash during matching, both with
339        pcre_exec() and pcre_dfa_exec().
340    
341    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
342        used for matching.
343    
344    11. Unicode property support in character classes was not working for
345        characters (bytes) greater than 127 when not in UTF-8 mode.
346    
347    12. Added the -M command line option to pcretest.
348    
349    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
350    
351    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
352    
353    16. Added comments and documentation about mis-use of no_arg in the C++
354        wrapper.
355    
356    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
357        from Martin Jerabek that uses macro names for all relevant character and
358        string constants.
359    
360    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
361        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
362        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
363        these, but not everybody uses configure.
364    
365    19. A conditional group that had only one branch was not being correctly
366        recognized as an item that could match an empty string. This meant that an
367        enclosing group might also not be so recognized, causing infinite looping
368        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
369        with the subject "ab", where knowledge that the repeated group can match
370        nothing is needed in order to break the loop.
371    
372    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
373        exec(), but without supplying a callout function, matching went wrong.
374    
375    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
376        leak if the size of the offset vector was greater than 30. When the vector
377        is smaller, the saved offsets during recursion go onto a local stack
378        vector, but for larger vectors malloc() is used. It was failing to free
379        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
380        error, in fact).
381    
382    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
383        heapframe that is used only when UTF-8 support is enabled. This caused no
384        problem, but was untidy.
385    
386    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
387        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
388        included within another project.
389    
390    24. Steven Van Ingelgem's patches to add more options to the CMake support,
391        slightly modified by me:
392    
393          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
394              not building pcregrep.
395    
396          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
397              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
398    
399    25. Forward references, both numeric and by name, in patterns that made use of
400        duplicate group numbers, could behave incorrectly or give incorrect errors,
401        because when scanning forward to find the reference group, PCRE was not
402        taking into account the duplicate group numbers. A pattern such as
403        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
404    
405    26. Changed a few more instances of "const unsigned char *" to USPTR, making
406        the feature of a custom pointer more persuasive (as requested by a user).
407    
408    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
409        pcretest.c, inside #ifndefs, because it seems they are sometimes already
410        pre-defined.
411    
412    28. Added support for (*UTF8) at the start of a pattern.
413    
414    29. Arrange for flags added by the "release type" setting in CMake to be shown
415        in the configuration summary.
416    
417    
418    Version 7.8 05-Sep-08
419    ---------------------
420    
421    1.  Replaced UCP searching code with optimized version as implemented for Ad
422        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
423        stage table and inline lookup instead of a function, giving speed ups of 2
424        to 5 times on some simple patterns that I tested. Permission was given to
425        distribute the MultiStage2.py script that generates the tables (it's not in
426        the tarball, but is in the Subversion repository).
427    
428    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
429        scripts.
430    
431    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
432        a group with a zero qualifier. The result of the study could be incorrect,
433        or the function might crash, depending on the pattern.
434    
435    4.  Caseless matching was not working for non-ASCII characters in back
436        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
437        It now works when Unicode Property Support is available.
438    
439    5.  In pcretest, an escape such as \x{de} in the data was always generating
440        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
441        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
442        truncation.
443    
444    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
445    
446    7.  Added two (int) casts to pcregrep when printing the difference of two
447        pointers, in case they are 64-bit values.
448    
449    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
450        test 2 if it fails.
451    
452    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
453        and a #define of that name to empty if it is not externally set. This is to
454        allow users of MSVC to set it if necessary.
455    
456    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
457        the convenience functions in the pcre_get.c source file.
458    
459    11. An option change at the start of a pattern that had top-level alternatives
460        could cause overwriting and/or a crash. This command provoked a crash in
461        some environments:
462    
463          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
464    
465        This potential security problem was recorded as CVE-2008-2371.
466    
467    12. For a pattern where the match had to start at the beginning or immediately
468        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
469        pcre_dfa_exec() could read past the end of the passed subject if there was
470        no match. To help with detecting such bugs (e.g. with valgrind), I modified
471        pcretest so that it places the subject at the end of its malloc-ed buffer.
472    
473    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
474        exec() might read past the end of the data buffer in UTF-8 mode.
475    
476    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
477        the data contained the byte 0x85 as part of a UTF-8 character within its
478        first line. This applied both to normal and DFA matching.
479    
480    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
481        /^[^d]*?$/8 failed to match "abc".
482    
483    16. Added a missing copyright notice to pcrecpp_internal.h.
484    
485    17. Make it more clear in the documentation that values returned from
486        pcre_exec() in ovector are byte offsets, not character counts.
487    
488    18. Tidied a few places to stop certain compilers from issuing warnings.
489    
490    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
491        supplied by Stefan Weber. I made a further small update for 7.8 because
492        there is a change of source arrangements: the pcre_searchfuncs.c module is
493        replaced by pcre_ucd.c.
494    
495    
496    Version 7.7 07-May-08
497  ---------------------  ---------------------
498    
499  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
500      a string to a long long, pretend we don't even have a long long." This is      a string to a long long, pretend we don't even have a long long." This is
501      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
502    
503  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
504      pre-7.6 versions, which defined a global no_arg variable instead of putting      pre-7.6 versions, which defined a global no_arg variable instead of putting
505      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
506    
507  3.  Remove a line of dead code, identified by coverity and reported by Nuno  3.  Remove a line of dead code, identified by coverity and reported by Nuno
508      Lopes.      Lopes.
509    
510  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
511    
512      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
513          of files, instead of just to the final components.          of files, instead of just to the final components.
514    
515      (2) If there was more than one level of directory, the subdirectories were      (2) If there was more than one level of directory, the subdirectories were
516          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
517          inconsistent with GNU grep (and could even be seen as contrary to the          inconsistent with GNU grep (and could even be seen as contrary to the
518          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
519          The action now is always to scan all levels of directory, and just          The action now is always to scan all levels of directory, and just
520          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
521    
522  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
523      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
524    
525  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
526      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
527      doesn't support NULs in patterns.      doesn't support NULs in patterns.
528    
529  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
530      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
531    
532  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
533      caused by fix #2  above. (Subsequently also a second patch to fix the      caused by fix #2  above. (Subsequently also a second patch to fix the
534      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
535    
536  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
537    
538  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
539      matching function regexec().      matching function regexec().
540    
541  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
542      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
543      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
544      Oniguruma does).      Oniguruma does).
545    
546  12. Previously, a group with a zero repeat such as (...){0} was completely  12. Previously, a group with a zero repeat such as (...){0} was completely
547      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
548      was called as a subroutine from elsewhere in the pattern, things went wrong      was called as a subroutine from elsewhere in the pattern, things went wrong
549      (an internal error was given). Such groups are now left in the compiled      (an internal error was given). Such groups are now left in the compiled
550      pattern, with a new opcode that causes them to be skipped at execution      pattern, with a new opcode that causes them to be skipped at execution
551      time.      time.
552    
553    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
554        to the way PCRE behaves:
555    
556        (a) A lone ] character is dis-allowed (Perl treats it as data).
557    
558        (b) A back reference to an unmatched subpattern matches an empty string
559            (Perl fails the current match path).
560    
561        (c) A data ] in a character class must be notated as \] because if the
562            first data character in a class is ], it defines an empty class. (In
563            Perl it is not possible to have an empty class.) The empty class []
564            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
565            The negative empty class [^] matches any one character, independently
566            of the DOTALL setting.
567    
568    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
569        non-existent subpattern following a character class starting with ']' and
570        containing () gave an internal compiling error instead of "reference to
571        non-existent subpattern". Fortunately, when the pattern did exist, the
572        compiled code was correct. (When scanning forwards to check for the
573        existencd of the subpattern, it was treating the data ']' as terminating
574        the class, so got the count wrong. When actually compiling, the reference
575        was subsequently set up correctly.)
576    
577    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
578        it was being rejected as not supported by pcre_dfa_exec(), even though
579        other assertions are supported. I have made pcre_dfa_exec() support
580        (*FAIL).
581    
582    16. The implementation of 13c above involved the invention of a new opcode,
583        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
584        cannot be changed at match time, I realized I could make a small
585        improvement to matching performance by compiling OP_ALLANY instead of
586        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
587        on the OP_ANY path.
588    
589    17. Compiling pcretest on Windows with readline support failed without the
590        following two fixes: (1) Make the unistd.h include conditional on
591        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
592    
593    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
594        ncurses library to be included for pcretest when ReadLine support is
595        requested, but also to allow for it to be overridden. This patch came from
596        Daniel Bergström.
597    
598    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
599        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
600        any errors with the current Unicode tables. Thanks to Peter Kankowski for
601        spotting this.
602    
603    
604  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
605  ---------------------  ---------------------

Legend:
Removed from v.335  
changed lines
  Added in v.488

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12