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

Diff of /code/trunk/ChangeLog

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

revision 118 by ph10, Fri Mar 9 16:17:46 2007 UTC revision 432 by ph10, Wed Sep 2 16:02:56 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.1 05-Mar-07  Version 8.00 ??-???-??
5    ----------------------
6    
7    1.  The table for translating pcre_compile() error codes into POSIX error codes
8        was out-of-date, and there was no check on the pcre_compile() error code
9        being within the table. This could lead to an OK return being given in
10        error.
11    
12    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
13        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
14        in a Windows environment.
15    
16    3.  The pcregrep --count option prints the count for each file even when it is
17        zero, as does GNU grep. However, pcregrep was also printing all files when
18        --files-with-matches was added. Now, when both options are given, it prints
19        counts only for those files that have at least one match. (GNU grep just
20        prints the file name in this circumstance, but including the count seems
21        more useful - otherwise, why use --count?) Also ensured that the
22        combination -clh just lists non-zero counts, with no names.
23    
24    4.  The long form of the pcregrep -F option was incorrectly implemented as
25        --fixed_strings instead of --fixed-strings. This is an incompatible change,
26        but it seems right to fix it, and I didn't think it was worth preserving
27        the old behaviour.
28    
29    5.  The command line items --regex=pattern and --regexp=pattern were not
30        recognized by pcregrep, which required --regex pattern or --regexp pattern
31        (with a space rather than an '='). The man page documented the '=' forms,
32        which are compatible with GNU grep; these now work.
33    
34    6.  No libpcreposix.pc file was created for pkg-config; there was just
35        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
36    
37    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
38        when UCP support is not needed, by modifying the Python script that
39        generates it from Unicode data files. This should not matter if the module
40        is correctly used as a library, but I received one complaint about 50K of
41        unwanted data. My guess is that the person linked everything into his
42        program rather than using a library. Anyway, it does no harm.
43    
44    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
45        was a minimum greater than 1 for a wide character in a possessive
46        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
47        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
48        character. Chaos in the form of incorrect output or a compiling loop could
49        result.
50    
51    9.  The restrictions on what a pattern can contain when partial matching is
52        requested for pcre_exec() have been removed. All patterns can now be
53        partially matched by this function. In addition, if there are at least two
54        slots in the offset vector, the offsets of the first-encountered partial
55        match are set in them when PCRE_ERROR_PARTIAL is returned.
56    
57    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
58        synonymous with PCRE_PARTIAL, for backwards compatibility, and
59        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
60        and may be more useful for multi-segment matching, especially with
61        pcre_exec().
62    
63    11. Partial matching with pcre_exec() is now more intuitive. A partial match
64        used to be given if ever the end of the subject was reached; now it is
65        given only if matching could not proceed because another character was
66        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
67        string "Z", which now yields "no match" instead of "partial match". In the
68        case of pcre_dfa_exec(), "no match" is given if every matching path for the
69        final character ended with (*FAIL).
70    
71    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
72        if the pattern had a "must contain" character that was already found in the
73        earlier partial match, unless partial matching was again requested. For
74        example, with the pattern /dog.(body)?/, the "must contain" character is
75        "g". If the first part-match was for the string "dog", restarting with
76        "sbody" failed.
77    
78    13. Added a pcredemo man page, created automatically from the pcredemo.c file,
79        so that the demonstration program is easily available in environments where
80        PCRE has not been installed from source.
81    
82    14. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
83        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
84        library.
85    
86    15. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
87        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
88        is not the first non-POSIX option to be added. Clearly some people find
89        these options useful.
90    
91    
92    Version 7.9 11-Apr-09
93    ---------------------
94    
95    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
96        (pcretest), all targets were linked against these libraries. This included
97        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
98        libraries. This caused unwanted dependencies to be created. This problem
99        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
100        pcretest is linked with readline.
101    
102    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
103        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
104        moved outside it again, because FALSE and TRUE are already defined in AIX,
105        but BOOL is not.
106    
107    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
108        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
109    
110    4.  The pcregrep documentation said spaces were inserted as well as colons (or
111        hyphens) following file names and line numbers when outputting matching
112        lines. This is not true; no spaces are inserted. I have also clarified the
113        wording for the --colour (or --color) option.
114    
115    5.  In pcregrep, when --colour was used with -o, the list of matching strings
116        was not coloured; this is different to GNU grep, so I have changed it to be
117        the same.
118    
119    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
120        each matching line was coloured. Now it goes on to look for further matches
121        of any of the test patterns, which is the same behaviour as GNU grep.
122    
123    7.  A pattern that could match an empty string could cause pcregrep to loop; it
124        doesn't make sense to accept an empty string match in pcregrep, so I have
125        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
126        seems to be how GNU grep behaves.
127    
128    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
129        start or after a newline", because the conditional assertion was not being
130        correctly handled. The rule now is that both the assertion and what follows
131        in the first alternative must satisfy the test.
132    
133    9.  If auto-callout was enabled in a pattern with a conditional group whose
134        condition was an assertion, PCRE could crash during matching, both with
135        pcre_exec() and pcre_dfa_exec().
136    
137    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
138        used for matching.
139    
140    11. Unicode property support in character classes was not working for
141        characters (bytes) greater than 127 when not in UTF-8 mode.
142    
143    12. Added the -M command line option to pcretest.
144    
145    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
146    
147    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
148    
149    16. Added comments and documentation about mis-use of no_arg in the C++
150        wrapper.
151    
152    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
153        from Martin Jerabek that uses macro names for all relevant character and
154        string constants.
155    
156    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
157        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
158        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
159        these, but not everybody uses configure.
160    
161    19. A conditional group that had only one branch was not being correctly
162        recognized as an item that could match an empty string. This meant that an
163        enclosing group might also not be so recognized, causing infinite looping
164        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
165        with the subject "ab", where knowledge that the repeated group can match
166        nothing is needed in order to break the loop.
167    
168    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
169        exec(), but without supplying a callout function, matching went wrong.
170    
171    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
172        leak if the size of the offset vector was greater than 30. When the vector
173        is smaller, the saved offsets during recursion go onto a local stack
174        vector, but for larger vectors malloc() is used. It was failing to free
175        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
176        error, in fact).
177    
178    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
179        heapframe that is used only when UTF-8 support is enabled. This caused no
180        problem, but was untidy.
181    
182    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
183        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
184        included within another project.
185    
186    24. Steven Van Ingelgem's patches to add more options to the CMake support,
187        slightly modified by me:
188    
189          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
190              not building pcregrep.
191    
192          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
193              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
194    
195    25. Forward references, both numeric and by name, in patterns that made use of
196        duplicate group numbers, could behave incorrectly or give incorrect errors,
197        because when scanning forward to find the reference group, PCRE was not
198        taking into account the duplicate group numbers. A pattern such as
199        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
200    
201    26. Changed a few more instances of "const unsigned char *" to USPTR, making
202        the feature of a custom pointer more persuasive (as requested by a user).
203    
204    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
205        pcretest.c, inside #ifndefs, because it seems they are sometimes already
206        pre-defined.
207    
208    28. Added support for (*UTF8) at the start of a pattern.
209    
210    29. Arrange for flags added by the "release type" setting in CMake to be shown
211        in the configuration summary.
212    
213    
214    Version 7.8 05-Sep-08
215    ---------------------
216    
217    1.  Replaced UCP searching code with optimized version as implemented for Ad
218        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
219        stage table and inline lookup instead of a function, giving speed ups of 2
220        to 5 times on some simple patterns that I tested. Permission was given to
221        distribute the MultiStage2.py script that generates the tables (it's not in
222        the tarball, but is in the Subversion repository).
223    
224    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
225        scripts.
226    
227    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
228        a group with a zero qualifier. The result of the study could be incorrect,
229        or the function might crash, depending on the pattern.
230    
231    4.  Caseless matching was not working for non-ASCII characters in back
232        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
233        It now works when Unicode Property Support is available.
234    
235    5.  In pcretest, an escape such as \x{de} in the data was always generating
236        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
237        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
238        truncation.
239    
240    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
241    
242    7.  Added two (int) casts to pcregrep when printing the difference of two
243        pointers, in case they are 64-bit values.
244    
245    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
246        test 2 if it fails.
247    
248    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
249        and a #define of that name to empty if it is not externally set. This is to
250        allow users of MSVC to set it if necessary.
251    
252    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
253        the convenience functions in the pcre_get.c source file.
254    
255    11. An option change at the start of a pattern that had top-level alternatives
256        could cause overwriting and/or a crash. This command provoked a crash in
257        some environments:
258    
259          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
260    
261        This potential security problem was recorded as CVE-2008-2371.
262    
263    12. For a pattern where the match had to start at the beginning or immediately
264        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
265        pcre_dfa_exec() could read past the end of the passed subject if there was
266        no match. To help with detecting such bugs (e.g. with valgrind), I modified
267        pcretest so that it places the subject at the end of its malloc-ed buffer.
268    
269    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
270        exec() might read past the end of the data buffer in UTF-8 mode.
271    
272    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
273        the data contained the byte 0x85 as part of a UTF-8 character within its
274        first line. This applied both to normal and DFA matching.
275    
276    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
277        /^[^d]*?$/8 failed to match "abc".
278    
279    16. Added a missing copyright notice to pcrecpp_internal.h.
280    
281    17. Make it more clear in the documentation that values returned from
282        pcre_exec() in ovector are byte offsets, not character counts.
283    
284    18. Tidied a few places to stop certain compilers from issuing warnings.
285    
286    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
287        supplied by Stefan Weber. I made a further small update for 7.8 because
288        there is a change of source arrangements: the pcre_searchfuncs.c module is
289        replaced by pcre_ucd.c.
290    
291    
292    Version 7.7 07-May-08
293    ---------------------
294    
295    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
296        a string to a long long, pretend we don't even have a long long." This is
297        done by checking for the strtoq, strtoll, and _strtoi64 functions.
298    
299    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
300        pre-7.6 versions, which defined a global no_arg variable instead of putting
301        it in the RE class. (See also #8 below.)
302    
303    3.  Remove a line of dead code, identified by coverity and reported by Nuno
304        Lopes.
305    
306    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
307    
308        (1) The include/exclude patterns were being applied to the whole pathnames
309            of files, instead of just to the final components.
310    
311        (2) If there was more than one level of directory, the subdirectories were
312            skipped unless they satisfied the include/exclude conditions. This is
313            inconsistent with GNU grep (and could even be seen as contrary to the
314            pcregrep specification - which I improved to make it absolutely clear).
315            The action now is always to scan all levels of directory, and just
316            apply the include/exclude patterns to regular files.
317    
318    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
319        --exclude_dir in the tests to avoid scanning .svn directories.
320    
321    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
322        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
323        doesn't support NULs in patterns.
324    
325    7.  Added some missing "const"s to declarations of static tables in
326        pcre_compile.c and pcre_dfa_exec.c.
327    
328    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
329        caused by fix #2  above. (Subsequently also a second patch to fix the
330        first patch. And a third patch - this was a messy problem.)
331    
332    9.  Applied Craig's patch to remove the use of push_back().
333    
334    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
335        matching function regexec().
336    
337    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
338        which, however, unlike Perl's \g{...}, are subroutine calls, not back
339        references. PCRE supports relative numbers with this syntax (I don't think
340        Oniguruma does).
341    
342    12. Previously, a group with a zero repeat such as (...){0} was completely
343        omitted from the compiled regex. However, this means that if the group
344        was called as a subroutine from elsewhere in the pattern, things went wrong
345        (an internal error was given). Such groups are now left in the compiled
346        pattern, with a new opcode that causes them to be skipped at execution
347        time.
348    
349    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
350        to the way PCRE behaves:
351    
352        (a) A lone ] character is dis-allowed (Perl treats it as data).
353    
354        (b) A back reference to an unmatched subpattern matches an empty string
355            (Perl fails the current match path).
356    
357        (c) A data ] in a character class must be notated as \] because if the
358            first data character in a class is ], it defines an empty class. (In
359            Perl it is not possible to have an empty class.) The empty class []
360            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
361            The negative empty class [^] matches any one character, independently
362            of the DOTALL setting.
363    
364    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
365        non-existent subpattern following a character class starting with ']' and
366        containing () gave an internal compiling error instead of "reference to
367        non-existent subpattern". Fortunately, when the pattern did exist, the
368        compiled code was correct. (When scanning forwards to check for the
369        existencd of the subpattern, it was treating the data ']' as terminating
370        the class, so got the count wrong. When actually compiling, the reference
371        was subsequently set up correctly.)
372    
373    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
374        it was being rejected as not supported by pcre_dfa_exec(), even though
375        other assertions are supported. I have made pcre_dfa_exec() support
376        (*FAIL).
377    
378    16. The implementation of 13c above involved the invention of a new opcode,
379        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
380        cannot be changed at match time, I realized I could make a small
381        improvement to matching performance by compiling OP_ALLANY instead of
382        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
383        on the OP_ANY path.
384    
385    17. Compiling pcretest on Windows with readline support failed without the
386        following two fixes: (1) Make the unistd.h include conditional on
387        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
388    
389    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
390        ncurses library to be included for pcretest when ReadLine support is
391        requested, but also to allow for it to be overridden. This patch came from
392        Daniel Bergström.
393    
394    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
395        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
396        any errors with the current Unicode tables. Thanks to Peter Kankowski for
397        spotting this.
398    
399    
400    Version 7.6 28-Jan-08
401    ---------------------
402    
403    1.  A character class containing a very large number of characters with
404        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
405        overflow.
406    
407    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
408        HAVE_LONG_LONG is not defined.
409    
410    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
411        bring them up to date and include new features. This patch includes:
412    
413        - Fixed PH's badly added libz and libbz2 support.
414        - Fixed a problem with static linking.
415        - Added pcredemo. [But later removed - see 7 below.]
416        - Fixed dftables problem and added an option.
417        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
418            HAVE_LONG_LONG.
419        - Added readline support for pcretest.
420        - Added an listing of the option settings after cmake has run.
421    
422    4.  A user submitted a patch to Makefile that makes it easy to create
423        "pcre.dll" under mingw when using Configure/Make. I added stuff to
424        Makefile.am that cause it to include this special target, without
425        affecting anything else. Note that the same mingw target plus all
426        the other distribution libraries and programs are now supported
427        when configuring with CMake (see 6 below) instead of with
428        Configure/Make.
429    
430    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
431        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
432        exported in the Windows port". It has not yet been confirmed that the patch
433        solves the problem, but it does no harm.
434    
435    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
436        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
437        with CMake, and also correct the comment about stack recursion.
438    
439    7.  Remove the automatic building of pcredemo from the ./configure system and
440        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
441        of a program that users should build themselves after PCRE is installed, so
442        building it automatically is not really right. What is more, it gave
443        trouble in some build environments.
444    
445    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
446    
447    
448    Version 7.5 10-Jan-08
449    ---------------------
450    
451    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
452        values in parens when parsing an RE using the C++ wrapper."
453    
454    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
455        Characters greater than 255 were excluded from the class instead of being
456        included.
457    
458    3.  The same bug as (2) above applied to negated POSIX classes such as
459        [:^space:].
460    
461    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
462        defined or documented. It seems to have been a typo for PCRE_STATIC, so
463        I have changed it.
464    
465    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
466        first named subpattern) and a construct such as (?&a) would reference the
467        first named subpattern whose name started with "a" (in other words, the
468        length check was missing). Both these problems are fixed. "Subpattern name
469        expected" is now given for (?&) (a zero-length name), and this patch also
470        makes it give the same error for \k'' (previously it complained that that
471        was a reference to a non-existent subpattern).
472    
473    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
474        this is right because (?- can be followed by option settings as well as by
475        digits. I have, however, made the messages clearer.
476    
477    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
478        than the number used in the conditional) now cause a compile-time error.
479        This is actually not compatible with Perl, which accepts such patterns, but
480        treats the conditional as always being FALSE (as PCRE used to), but it
481        seems to me that giving a diagnostic is better.
482    
483    8.  Change "alphameric" to the more common word "alphanumeric" in comments
484        and messages.
485    
486    9.  Fix two occurrences of "backslash" in comments that should have been
487        "backspace".
488    
489    10. Remove two redundant lines of code that can never be obeyed (their function
490        was moved elsewhere).
491    
492    11. The program that makes PCRE's Unicode character property table had a bug
493        which caused it to generate incorrect table entries for sequences of
494        characters that have the same character type, but are in different scripts.
495        It amalgamated them into a single range, with the script of the first of
496        them. In other words, some characters were in the wrong script. There were
497        thirteen such cases, affecting characters in the following ranges:
498    
499          U+002b0 - U+002c1
500          U+0060c - U+0060d
501          U+0061e - U+00612
502          U+0064b - U+0065e
503          U+0074d - U+0076d
504          U+01800 - U+01805
505          U+01d00 - U+01d77
506          U+01d9b - U+01dbf
507          U+0200b - U+0200f
508          U+030fc - U+030fe
509          U+03260 - U+0327f
510          U+0fb46 - U+0fbb1
511          U+10450 - U+1049d
512    
513    12. The -o option (show only the matching part of a line) for pcregrep was not
514        compatible with GNU grep in that, if there was more than one match in a
515        line, it showed only the first of them. It now behaves in the same way as
516        GNU grep.
517    
518    13. If the -o and -v options were combined for pcregrep, it printed a blank
519        line for every non-matching line. GNU grep prints nothing, and pcregrep now
520        does the same. The return code can be used to tell if there were any
521        non-matching lines.
522    
523    14. Added --file-offsets and --line-offsets to pcregrep.
524    
525    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
526        infinitely looping recursion. The bug was that positive lookaheads were not
527        being skipped when checking for a possible empty match (negative lookaheads
528        and both kinds of lookbehind were skipped).
529    
530    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
531        inclusion of <windows.h> to before rather than after the definition of
532        INVALID_FILE_ATTRIBUTES (patch from David Byron).
533    
534    17. Specifying a possessive quantifier with a specific limit for a Unicode
535        character property caused pcre_compile() to compile bad code, which led at
536        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
537        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
538        caused the error; without that there was no problem.
539    
540    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
541    
542    19. Added --enable-pcretest-libreadline.
543    
544    20. In pcrecpp.cc, the variable 'count' was incremented twice in
545        RE::GlobalReplace(). As a result, the number of replacements returned was
546        double what it should be. I removed one of the increments, but Craig sent a
547        later patch that removed the other one (the right fix) and added unit tests
548        that check the return values (which was not done before).
549    
550    21. Several CMake things:
551    
552        (1) Arranged that, when cmake is used on Unix, the libraries end up with
553            the names libpcre and libpcreposix, not just pcre and pcreposix.
554    
555        (2) The above change means that pcretest and pcregrep are now correctly
556            linked with the newly-built libraries, not previously installed ones.
557    
558        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
559    
560    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
561        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
562        UTF-8 newline character). The key issue is that the pattern starts .*;
563        this means that the match must be either at the beginning, or after a
564        newline. The bug was in the code for advancing after a failed match and
565        checking that the new position followed a newline. It was not taking
566        account of UTF-8 characters correctly.
567    
568    23. PCRE was behaving differently from Perl in the way it recognized POSIX
569        character classes. PCRE was not treating the sequence [:...:] as a
570        character class unless the ... were all letters. Perl, however, seems to
571        allow any characters between [: and :], though of course it rejects as
572        unknown any "names" that contain non-letters, because all the known class
573        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
574        for example, whereas PCRE did not - it did not recognize a POSIX character
575        class. This seemed a bit dangerous, so the code has been changed to be
576        closer to Perl. The behaviour is not identical to Perl, because PCRE will
577        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
578        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
579        Perl does, and where it didn't before.
580    
581    24. Rewrite so as to remove the single use of %n from pcregrep because in some
582        Windows environments %n is disabled by default.
583    
584    
585    Version 7.4 21-Sep-07
586    ---------------------
587    
588    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
589        means that a class such as [\s] counted as "explicit reference to CR or
590        LF". That isn't really right - the whole point of the change was to try to
591        help when there was an actual mention of one of the two characters. So now
592        the change happens only if \r or \n (or a literal CR or LF) character is
593        encountered.
594    
595    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
596        of both had grown to the point where there were only 3 bits left.
597        Fortunately, there was spare space in the data structure, and so I have
598        moved the internal flags into a new 16-bit field to free up more option
599        bits.
600    
601    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
602        but did not set the internal JCHANGED flag - either of these is enough to
603        control the way the "get" function works - but the PCRE_INFO_JCHANGED
604        facility is supposed to tell if (?J) was ever used, so now (?J) at the
605        start sets both bits.
606    
607    4.  Added options (at build time, compile time, exec time) to change \R from
608        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
609    
610    5.  doc/pcresyntax.html was missing from the distribution.
611    
612    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
613        compatibility, even though it is no longer used.
614    
615    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
616        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
617        windows.h file is present (where different names are used). [This was
618        reversed later after testing - see 16 below.]
619    
620    8.  Changed all #include <config.h> to #include "config.h". There were also
621        some further <pcre.h> cases that I changed to "pcre.h".
622    
623    9.  When pcregrep was used with the --colour option, it missed the line ending
624        sequence off the lines that it output.
625    
626    10. It was pointed out to me that arrays of string pointers cause lots of
627        relocations when a shared library is dynamically loaded. A technique of
628        using a single long string with a table of offsets can drastically reduce
629        these. I have refactored PCRE in four places to do this. The result is
630        dramatic:
631    
632          Originally:                          290
633          After changing UCP table:            187
634          After changing error message table:   43
635          After changing table of "verbs"       36
636          After changing table of Posix names   22
637    
638        Thanks to the folks working on Gregex for glib for this insight.
639    
640    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
641        unicode-properties was also set.
642    
643    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
644    
645    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
646        checked only for CRLF.
647    
648    14. Added casts to pcretest.c to avoid compiler warnings.
649    
650    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
651    
652    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
653        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
654        entirely. This removes changes made in 7 above.
655    
656    17. The CMake files have been updated, and there is now more information about
657        building with CMake in the NON-UNIX-USE document.
658    
659    
660    Version 7.3 28-Aug-07
661    ---------------------
662    
663     1. In the rejigging of the build system that eventually resulted in 7.1, the
664        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
665        brackets there is not right, since it causes compilers to look for an
666        installed pcre.h, not the version that is in the source that is being
667        compiled (which of course may be different). I have changed it back to:
668    
669          #include "pcre.h"
670    
671        I have a vague recollection that the change was concerned with compiling in
672        different directories, but in the new build system, that is taken care of
673        by the VPATH setting the Makefile.
674    
675     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
676        when the subject happened to end in the byte 0x85 (e.g. if the last
677        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
678        characters but of course it shouldn't be taken as a newline when it is part
679        of another character. The bug was that, for an unlimited repeat of . in
680        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
681        characters when looking for a newline.
682    
683     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
684    
685     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
686        in debug output.
687    
688     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
689        long printing in the pcrecpp unittest when running under MinGW.
690    
691     6. ESC_K was left out of the EBCDIC table.
692    
693     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
694        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
695        limit also applies to "virtual nesting" when a pattern is recursive, and in
696        this case 1000 isn't so big. I have been able to remove this limit at the
697        expense of backing off one optimization in certain circumstances. Normally,
698        when pcre_exec() would call its internal match() function recursively and
699        immediately return the result unconditionally, it uses a "tail recursion"
700        feature to save stack. However, when a subpattern that can match an empty
701        string has an unlimited repetition quantifier, it no longer makes this
702        optimization. That gives it a stack frame in which to save the data for
703        checking that an empty string has been matched. Previously this was taken
704        from the 1000-entry workspace that had been reserved. So now there is no
705        explicit limit, but more stack is used.
706    
707     8. Applied Daniel's patches to solve problems with the import/export magic
708        syntax that is required for Windows, and which was going wrong for the
709        pcreposix and pcrecpp parts of the library. These were overlooked when this
710        problem was solved for the main library.
711    
712     9. There were some crude static tests to avoid integer overflow when computing
713        the size of patterns that contain repeated groups with explicit upper
714        limits. As the maximum quantifier is 65535, the maximum group length was
715        set at 30,000 so that the product of these two numbers did not overflow a
716        32-bit integer. However, it turns out that people want to use groups that
717        are longer than 30,000 bytes (though not repeat them that many times).
718        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
719        made it possible to implement the integer overflow checks in a much more
720        dynamic way, which I have now done. The artificial limitation on group
721        length has been removed - we now have only the limit on the total length of
722        the compiled pattern, which depends on the LINK_SIZE setting.
723    
724    10. Fixed a bug in the documentation for get/copy named substring when
725        duplicate names are permitted. If none of the named substrings are set, the
726        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
727        empty string.
728    
729    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
730        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
731        because the ] is interpreted as the first data character and the
732        terminating ] is not found. PCRE has been made compatible with Perl in this
733        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
734        cause memory overwriting.
735    
736    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
737        string has been matched (to stop an infinite loop). It was not recognizing
738        a conditional subpattern that could match an empty string if that
739        subpattern was within another subpattern. For example, it looped when
740        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
741        condition was not nested. This bug has been fixed.
742    
743    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
744        past the start of the subject in the presence of bytes with the top bit
745        set, for example "\x8aBCD".
746    
747    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
748        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
749    
750    14. Optimized (?!) to (*FAIL).
751    
752    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
753        This restricts code points to be within the range 0 to 0x10FFFF, excluding
754        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
755        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
756        does: it's just the validity check that is more restrictive.
757    
758    16. Inserted checks for integer overflows during escape sequence (backslash)
759        processing, and also fixed erroneous offset values for syntax errors during
760        backslash processing.
761    
762    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
763        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
764    
765    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
766        caused an overrun.
767    
768    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
769        something other than just ASCII characters) inside a group that had an
770        unlimited repeat caused a loop at compile time (while checking to see
771        whether the group could match an empty string).
772    
773    20. Debugging a pattern containing \p or \P could cause a crash. For example,
774        [\P{Any}] did so. (Error in the code for printing property names.)
775    
776    21. An orphan \E inside a character class could cause a crash.
777    
778    22. A repeated capturing bracket such as (A)? could cause a wild memory
779        reference during compilation.
780    
781    23. There are several functions in pcre_compile() that scan along a compiled
782        expression for various reasons (e.g. to see if it's fixed length for look
783        behind). There were bugs in these functions when a repeated \p or \P was
784        present in the pattern. These operators have additional parameters compared
785        with \d, etc, and these were not being taken into account when moving along
786        the compiled data. Specifically:
787    
788        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
789            length.
790    
791        (b) An item such as \pL+ within a repeated group could cause crashes or
792            loops.
793    
794        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
795            "reference to non-existent subpattern" error.
796    
797        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
798    
799    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
800        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
801    
802    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
803    
804    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
805        character were causing crashes (broken optimization).
806    
807    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
808        \p or \P) caused a compile-time loop.
809    
810    28. More problems have arisen in unanchored patterns when CRLF is a valid line
811        break. For example, the unstudied pattern [\r\n]A does not match the string
812        "\r\nA" because change 7.0/46 below moves the current point on by two
813        characters after failing to match at the start. However, the pattern \nA
814        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
815        the same is true. There doesn't seem any very clean way out of this, but
816        what I have chosen to do makes the common cases work: PCRE now takes note
817        of whether there can be an explicit match for \r or \n anywhere in the
818        pattern, and if so, 7.0/46 no longer applies. As part of this change,
819        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
820        pattern has explicit CR or LF references.
821    
822    29. Added (*CR) etc for changing newline setting at start of pattern.
823    
824    
825    Version 7.2 19-Jun-07
826    ---------------------
827    
828     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
829        which is apparently normally available under Windows.
830    
831     2. Re-jig the pcregrep tests with different newline settings in an attempt
832        to make them independent of the local environment's newline setting.
833    
834     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
835    
836     4. Some of the "internals" tests were previously cut out when the link size
837        was not 2, because the output contained actual offsets. The recent new
838        "Z" feature of pcretest means that these can be cut out, making the tests
839        usable with all link sizes.
840    
841     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
842        stack recursion. This gives a massive performance boost under BSD, but just
843        a small improvement under Linux. However, it saves one field in the frame
844        in all cases.
845    
846     6. Added more features from the forthcoming Perl 5.10:
847    
848        (a) (?-n) (where n is a string of digits) is a relative subroutine or
849            recursion call. It refers to the nth most recently opened parentheses.
850    
851        (b) (?+n) is also a relative subroutine call; it refers to the nth next
852            to be opened parentheses.
853    
854        (c) Conditions that refer to capturing parentheses can be specified
855            relatively, for example, (?(-2)... or (?(+3)...
856    
857        (d) \K resets the start of the current match so that everything before
858            is not part of it.
859    
860        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
861    
862        (f) \g{name} is another synonym - part of Perl 5.10's unification of
863            reference syntax.
864    
865        (g) (?| introduces a group in which the numbering of parentheses in each
866            alternative starts with the same number.
867    
868        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
869    
870     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
871        PCRE_INFO_JCHANGED.
872    
873     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
874        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
875        for detecting groups that can match an empty string.
876    
877     9. A pattern with a very large number of alternatives (more than several
878        hundred) was running out of internal workspace during the pre-compile
879        phase, where pcre_compile() figures out how much memory will be needed. A
880        bit of new cunning has reduced the workspace needed for groups with
881        alternatives. The 1000-alternative test pattern now uses 12 bytes of
882        workspace instead of running out of the 4096 that are available.
883    
884    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
885    
886    11. Applied patch from Google to remove an optimization that didn't quite work.
887        The report of the bug said:
888    
889          pcrecpp::RE("a*").FullMatch("aaa") matches, while
890          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
891          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
892    
893    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
894        it matched the wrong number of bytes.
895    
896    
897    Version 7.1 24-Apr-07
898  ---------------------  ---------------------
899    
900   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
901      that is more "standard", making use of automake and other autotools. There      that is more "standard", making use of automake and other Autotools. There
902      is some re-arrangement of the files and adjustment of comments consequent      is some re-arrangement of the files and adjustment of comments consequent
903      on this.      on this.
904    
# Line 26  Version 7.1 05-Mar-07 Line 919  Version 7.1 05-Mar-07
919      .br or .in.      .br or .in.
920    
921   4. Updated comments in configure.ac that get placed in config.h.in and also   4. Updated comments in configure.ac that get placed in config.h.in and also
922      arranged for config.h to be included in the distribution, with the name      arranged for config.h to be included in the distribution, with the name
923      config.h.generic, for the benefit of those who have to compile without      config.h.generic, for the benefit of those who have to compile without
924      Autotools (compare pcre.h, which is now distributed as pcre.h.generic).      Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
925    
926   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
927      Weber: (1) pcre_internal.h was missing some function renames; (2) updated      Weber: (1) pcre_internal.h was missing some function renames; (2) updated
928      makevp.bat for the current PCRE, using the additional files !compile.txt,      makevp.bat for the current PCRE, using the additional files
929      !linklib.txt, and pcregexp.pas.      makevp_c.txt, makevp_l.txt, and pcregexp.pas.
930    
931   6. A Windows user reported a minor discrepancy with test 2, which turned out   6. A Windows user reported a minor discrepancy with test 2, which turned out
932      to be caused by a trailing space on an input line that had got lost in his      to be caused by a trailing space on an input line that had got lost in his
# Line 63  Version 7.1 05-Mar-07 Line 956  Version 7.1 05-Mar-07
956  10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:  10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
957    
958      (a) It was defining its arguments as char * instead of void *.      (a) It was defining its arguments as char * instead of void *.
959    
960      (b) It was assuming that all moves were upwards in memory; this was true      (b) It was assuming that all moves were upwards in memory; this was true
961          a long time ago when I wrote it, but is no longer the case.          a long time ago when I wrote it, but is no longer the case.
962    
963      The emulated memove() is provided for those environments that have neither      The emulated memove() is provided for those environments that have neither
964      memmove() nor bcopy(). I didn't think anyone used it these days, but that      memmove() nor bcopy(). I didn't think anyone used it these days, but that
965      is clearly not the case, as these two bugs were recently reported.      is clearly not the case, as these two bugs were recently reported.
966    
967  11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,  11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
968      and Detrail to create the HTML documentation, the .txt form of the man      and Detrail to create the HTML documentation, the .txt form of the man
969      pages, and it removes trailing spaces from listed files. It also creates      pages, and it removes trailing spaces from listed files. It also creates
970      pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter      pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
971      case, it wraps all the #defines with #ifndefs. This script should be run      case, it wraps all the #defines with #ifndefs. This script should be run
972      before "make dist".      before "make dist".
973    
974  12. Fixed two fairly obscure bugs concerned with quantified caseless matching  12. Fixed two fairly obscure bugs concerned with quantified caseless matching
975      with Unicode property support.      with Unicode property support.
976    
977      (a) For a maximizing quantifier, if the two different cases of the      (a) For a maximizing quantifier, if the two different cases of the
978          character were of different lengths in their UTF-8 codings (there are          character were of different lengths in their UTF-8 codings (there are
979          some cases like this - I found 11), and the matching function had to          some cases like this - I found 11), and the matching function had to
980          back up over a mixture of the two cases, it incorrectly assumed they          back up over a mixture of the two cases, it incorrectly assumed they
981          were both the same length.          were both the same length.
982    
983      (b) When PCRE was configured to use the heap rather than the stack for      (b) When PCRE was configured to use the heap rather than the stack for
984          recursion during matching, it was not correctly preserving the data for          recursion during matching, it was not correctly preserving the data for
985          the other case of a UTF-8 character when checking ahead for a match          the other case of a UTF-8 character when checking ahead for a match
986          while processing a minimizing repeat. If the check also involved          while processing a minimizing repeat. If the check also involved
987          matching a wide character, but failed, corruption could cause an          matching a wide character, but failed, corruption could cause an
988          erroneous result when trying to check for a repeat of the original          erroneous result when trying to check for a repeat of the original
989          character.          character.
990    
991  13. Some tidying changes to the testing mechanism:  13. Some tidying changes to the testing mechanism:
992    
993      (a) The RunTest script now detects the internal link size and whether there      (a) The RunTest script now detects the internal link size and whether there
994          is UTF-8 and UCP support by running ./pcretest -C instead of relying on          is UTF-8 and UCP support by running ./pcretest -C instead of relying on
995          values substituted by "configure". (The RunGrepTest script already did          values substituted by "configure". (The RunGrepTest script already did
996          this for UTF-8.) The configure.ac script no longer substitutes the          this for UTF-8.) The configure.ac script no longer substitutes the
997          relevant variables.          relevant variables.
998    
999      (b) The debugging options /B and /D in pcretest show the compiled bytecode      (b) The debugging options /B and /D in pcretest show the compiled bytecode
1000          with length and offset values. This means that the output is different          with length and offset values. This means that the output is different
1001          for different internal link sizes. Test 2 is skipped for link sizes          for different internal link sizes. Test 2 is skipped for link sizes
1002          other than 2 because of this, bypassing the problem. Unfortunately,          other than 2 because of this, bypassing the problem. Unfortunately,
1003          there was also a test in test 3 (the locale tests) that used /B and          there was also a test in test 3 (the locale tests) that used /B and
1004          failed for link sizes other than 2. Rather than cut the whole test out,          failed for link sizes other than 2. Rather than cut the whole test out,
1005          I have added a new /Z option to pcretest that replaces the length and          I have added a new /Z option to pcretest that replaces the length and
1006          offset values with spaces. This is now used to make test 3 independent          offset values with spaces. This is now used to make test 3 independent
1007          of link size.          of link size. (Test 2 will be tidied up later.)
1008    
1009    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
1010        segmentation fault instead of returning the appropriate error message.
1011    
1012    15. In multiline mode when the newline sequence was set to "any", the pattern
1013        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
1014        This doesn't seem right; it now treats the CRLF combination as the line
1015        ending, and so does not match in that case. It's only a pattern such as ^$
1016        that would hit this one: something like ^ABC$ would have failed after \r
1017        and then tried again after \r\n.
1018    
1019    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
1020        in an attempt to make files that differ only in their line terminators
1021        compare equal. This works on Linux.
1022    
1023    17. Under certain error circumstances pcregrep might try to free random memory
1024        as it exited. This is now fixed, thanks to valgrind.
1025    
1026    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
1027        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
1028        was because its rules for how to advance for /g after matching an empty
1029        string at the end of a line did not allow for this case. They now check for
1030        it specially.
1031    
1032    20. pcretest is supposed to handle patterns and data of any length, by
1033        extending its buffers when necessary. It was getting this wrong when the
1034        buffer for a data line had to be extended.
1035    
1036    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1037        CRLF as a newline sequence.
1038    
1039    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1040        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1041        I have nevertheless tidied it up.
1042    
1043    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1044    
1045    24. Added a man page for pcre-config.
1046    
1047    
1048  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
1049  ---------------------  ---------------------

Legend:
Removed from v.118  
changed lines
  Added in v.432

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12