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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.368  
changed lines
  Added in v.494

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12