ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 73 by nigel, Sat Feb 24 21:40:30 2007 UTC revision 454 by ph10, Tue Sep 22 09:42:11 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 8.00 ??-???-??
5    ----------------------
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.
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.
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.
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.
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.
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.
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.
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.
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 offset of the earliest inspected character
55        for the match and the offset of the end of the subject are set in them when
56        PCRE_ERROR_PARTIAL is returned.
58    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
59        synonymous with PCRE_PARTIAL, for backwards compatibility, and
60        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
61        and may be more useful for multi-segment matching, especially with
62        pcre_exec().
64    11. Partial matching with pcre_exec() is now more intuitive. A partial match
65        used to be given if ever the end of the subject was reached; now it is
66        given only if matching could not proceed because another character was
67        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
68        string "Z", which now yields "no match" instead of "partial match". In the
69        case of pcre_dfa_exec(), "no match" is given if every matching path for the
70        final character ended with (*FAIL).
72    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
73        if the pattern had a "must contain" character that was already found in the
74        earlier partial match, unless partial matching was again requested. For
75        example, with the pattern /dog.(body)?/, the "must contain" character is
76        "g". If the first part-match was for the string "dog", restarting with
77        "sbody" failed. This bug has been fixed.
79    13. The string returned by pcre_dfa_exec() after a partial match has been
80        changed so that it starts at the first inspected character rather than the
81        first character of the match. This makes a difference only if the pattern
82        starts with a lookbehind assertion or \b or \B (\K is not supported by
83        pcre_dfa_exec()). It's an incompatible change, but it makes the two
84        matching functions compatible, and I think it's the right thing to do.
86    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
87        so that the demonstration program is easily available in environments where
88        PCRE has not been installed from source.
90    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
91        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
92        library.
94    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
95        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
96        is not the first non-POSIX option to be added. Clearly some people find
97        these options useful.
99    17. If a caller to the POSIX matching function regexec() passes a non-zero
100        value for nmatch with a NULL value for pmatch, the value of
101        nmatch is forced to zero.
103    18. RunGrepTest did not have a test for the availability of the -u option of
104        the diff command, as RunTest does. It now checks in the same way as
105        RunTest, and also checks for the -b option.
107    19. If an odd number of negated classes containing just a single character
108        interposed, within parentheses, between a forward reference to a named
109        subpattern and the definition of the subpattern, compilation crashed with
110        an internal error, complaining that it could not find the referenced
111        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
112        [The bug was that it was starting one character too far in when skipping
113        over the character class, thus treating the ] as data rather than
114        terminating the class. This meant it could skip too much.]
116    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
117        /g option in pcretest when the pattern contains \K, which makes it possible
118        to have an empty string match not at the start, even when the pattern is
119        anchored. Updated pcretest and pcredemo to use this option.
121    21. If the maximum number of capturing subpatterns in a recursion was greater
122        than the maximum at the outer level, the higher number was returned, but
123        with unset values at the outer level. The correct (outer level) value is
124        now given.
126    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
127        PCRE did not set those parentheses (unlike Perl). I have now found a way to
128        make it do so. The string so far is captured, making this feature
129        compatible with Perl.
131    23. The tests have been re-organized, adding tests 11 and 12, to make it
132        possible to check the Perl 5.10 features against Perl 5.10.
134    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
135        pattern matches a fixed length string. PCRE did not allow this; now it
136        does. Neither allows recursion.
139    Version 7.9 11-Apr-09
140    ---------------------
142    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
143        (pcretest), all targets were linked against these libraries. This included
144        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
145        libraries. This caused unwanted dependencies to be created. This problem
146        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
147        pcretest is linked with readline.
149    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
150        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
151        moved outside it again, because FALSE and TRUE are already defined in AIX,
152        but BOOL is not.
154    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
155        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
157    4.  The pcregrep documentation said spaces were inserted as well as colons (or
158        hyphens) following file names and line numbers when outputting matching
159        lines. This is not true; no spaces are inserted. I have also clarified the
160        wording for the --colour (or --color) option.
162    5.  In pcregrep, when --colour was used with -o, the list of matching strings
163        was not coloured; this is different to GNU grep, so I have changed it to be
164        the same.
166    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
167        each matching line was coloured. Now it goes on to look for further matches
168        of any of the test patterns, which is the same behaviour as GNU grep.
170    7.  A pattern that could match an empty string could cause pcregrep to loop; it
171        doesn't make sense to accept an empty string match in pcregrep, so I have
172        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
173        seems to be how GNU grep behaves.
175    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
176        start or after a newline", because the conditional assertion was not being
177        correctly handled. The rule now is that both the assertion and what follows
178        in the first alternative must satisfy the test.
180    9.  If auto-callout was enabled in a pattern with a conditional group whose
181        condition was an assertion, PCRE could crash during matching, both with
182        pcre_exec() and pcre_dfa_exec().
184    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
185        used for matching.
187    11. Unicode property support in character classes was not working for
188        characters (bytes) greater than 127 when not in UTF-8 mode.
190    12. Added the -M command line option to pcretest.
192    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
194    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
196    16. Added comments and documentation about mis-use of no_arg in the C++
197        wrapper.
199    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
200        from Martin Jerabek that uses macro names for all relevant character and
201        string constants.
203    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
204        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
205        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
206        these, but not everybody uses configure.
208    19. A conditional group that had only one branch was not being correctly
209        recognized as an item that could match an empty string. This meant that an
210        enclosing group might also not be so recognized, causing infinite looping
211        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
212        with the subject "ab", where knowledge that the repeated group can match
213        nothing is needed in order to break the loop.
215    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
216        exec(), but without supplying a callout function, matching went wrong.
218    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
219        leak if the size of the offset vector was greater than 30. When the vector
220        is smaller, the saved offsets during recursion go onto a local stack
221        vector, but for larger vectors malloc() is used. It was failing to free
222        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
223        error, in fact).
225    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
226        heapframe that is used only when UTF-8 support is enabled. This caused no
227        problem, but was untidy.
229    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
230        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
231        included within another project.
233    24. Steven Van Ingelgem's patches to add more options to the CMake support,
234        slightly modified by me:
236          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
237              not building pcregrep.
239          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
240              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
242    25. Forward references, both numeric and by name, in patterns that made use of
243        duplicate group numbers, could behave incorrectly or give incorrect errors,
244        because when scanning forward to find the reference group, PCRE was not
245        taking into account the duplicate group numbers. A pattern such as
246        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
248    26. Changed a few more instances of "const unsigned char *" to USPTR, making
249        the feature of a custom pointer more persuasive (as requested by a user).
251    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
252        pcretest.c, inside #ifndefs, because it seems they are sometimes already
253        pre-defined.
255    28. Added support for (*UTF8) at the start of a pattern.
257    29. Arrange for flags added by the "release type" setting in CMake to be shown
258        in the configuration summary.
261    Version 7.8 05-Sep-08
262    ---------------------
264    1.  Replaced UCP searching code with optimized version as implemented for Ad
265        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
266        stage table and inline lookup instead of a function, giving speed ups of 2
267        to 5 times on some simple patterns that I tested. Permission was given to
268        distribute the MultiStage2.py script that generates the tables (it's not in
269        the tarball, but is in the Subversion repository).
271    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
272        scripts.
274    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
275        a group with a zero qualifier. The result of the study could be incorrect,
276        or the function might crash, depending on the pattern.
278    4.  Caseless matching was not working for non-ASCII characters in back
279        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
280        It now works when Unicode Property Support is available.
282    5.  In pcretest, an escape such as \x{de} in the data was always generating
283        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
284        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
285        truncation.
287    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
289    7.  Added two (int) casts to pcregrep when printing the difference of two
290        pointers, in case they are 64-bit values.
292    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
293        test 2 if it fails.
295    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
296        and a #define of that name to empty if it is not externally set. This is to
297        allow users of MSVC to set it if necessary.
299    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
300        the convenience functions in the pcre_get.c source file.
302    11. An option change at the start of a pattern that had top-level alternatives
303        could cause overwriting and/or a crash. This command provoked a crash in
304        some environments:
306          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
308        This potential security problem was recorded as CVE-2008-2371.
310    12. For a pattern where the match had to start at the beginning or immediately
311        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
312        pcre_dfa_exec() could read past the end of the passed subject if there was
313        no match. To help with detecting such bugs (e.g. with valgrind), I modified
314        pcretest so that it places the subject at the end of its malloc-ed buffer.
316    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
317        exec() might read past the end of the data buffer in UTF-8 mode.
319    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
320        the data contained the byte 0x85 as part of a UTF-8 character within its
321        first line. This applied both to normal and DFA matching.
323    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
324        /^[^d]*?$/8 failed to match "abc".
326    16. Added a missing copyright notice to pcrecpp_internal.h.
328    17. Make it more clear in the documentation that values returned from
329        pcre_exec() in ovector are byte offsets, not character counts.
331    18. Tidied a few places to stop certain compilers from issuing warnings.
333    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
334        supplied by Stefan Weber. I made a further small update for 7.8 because
335        there is a change of source arrangements: the pcre_searchfuncs.c module is
336        replaced by pcre_ucd.c.
339    Version 7.7 07-May-08
340    ---------------------
342    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
343        a string to a long long, pretend we don't even have a long long." This is
344        done by checking for the strtoq, strtoll, and _strtoi64 functions.
346    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
347        pre-7.6 versions, which defined a global no_arg variable instead of putting
348        it in the RE class. (See also #8 below.)
350    3.  Remove a line of dead code, identified by coverity and reported by Nuno
351        Lopes.
353    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
355        (1) The include/exclude patterns were being applied to the whole pathnames
356            of files, instead of just to the final components.
358        (2) If there was more than one level of directory, the subdirectories were
359            skipped unless they satisfied the include/exclude conditions. This is
360            inconsistent with GNU grep (and could even be seen as contrary to the
361            pcregrep specification - which I improved to make it absolutely clear).
362            The action now is always to scan all levels of directory, and just
363            apply the include/exclude patterns to regular files.
365    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
366        --exclude_dir in the tests to avoid scanning .svn directories.
368    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
369        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
370        doesn't support NULs in patterns.
372    7.  Added some missing "const"s to declarations of static tables in
373        pcre_compile.c and pcre_dfa_exec.c.
375    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
376        caused by fix #2  above. (Subsequently also a second patch to fix the
377        first patch. And a third patch - this was a messy problem.)
379    9.  Applied Craig's patch to remove the use of push_back().
381    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
382        matching function regexec().
384    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
385        which, however, unlike Perl's \g{...}, are subroutine calls, not back
386        references. PCRE supports relative numbers with this syntax (I don't think
387        Oniguruma does).
389    12. Previously, a group with a zero repeat such as (...){0} was completely
390        omitted from the compiled regex. However, this means that if the group
391        was called as a subroutine from elsewhere in the pattern, things went wrong
392        (an internal error was given). Such groups are now left in the compiled
393        pattern, with a new opcode that causes them to be skipped at execution
394        time.
396    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
397        to the way PCRE behaves:
399        (a) A lone ] character is dis-allowed (Perl treats it as data).
401        (b) A back reference to an unmatched subpattern matches an empty string
402            (Perl fails the current match path).
404        (c) A data ] in a character class must be notated as \] because if the
405            first data character in a class is ], it defines an empty class. (In
406            Perl it is not possible to have an empty class.) The empty class []
407            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
408            The negative empty class [^] matches any one character, independently
409            of the DOTALL setting.
411    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
412        non-existent subpattern following a character class starting with ']' and
413        containing () gave an internal compiling error instead of "reference to
414        non-existent subpattern". Fortunately, when the pattern did exist, the
415        compiled code was correct. (When scanning forwards to check for the
416        existencd of the subpattern, it was treating the data ']' as terminating
417        the class, so got the count wrong. When actually compiling, the reference
418        was subsequently set up correctly.)
420    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
421        it was being rejected as not supported by pcre_dfa_exec(), even though
422        other assertions are supported. I have made pcre_dfa_exec() support
423        (*FAIL).
425    16. The implementation of 13c above involved the invention of a new opcode,
426        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
427        cannot be changed at match time, I realized I could make a small
428        improvement to matching performance by compiling OP_ALLANY instead of
429        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
430        on the OP_ANY path.
432    17. Compiling pcretest on Windows with readline support failed without the
433        following two fixes: (1) Make the unistd.h include conditional on
434        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
436    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
437        ncurses library to be included for pcretest when ReadLine support is
438        requested, but also to allow for it to be overridden. This patch came from
439        Daniel Bergström.
441    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
442        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
443        any errors with the current Unicode tables. Thanks to Peter Kankowski for
444        spotting this.
447    Version 7.6 28-Jan-08
448    ---------------------
450    1.  A character class containing a very large number of characters with
451        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
452        overflow.
454    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
455        HAVE_LONG_LONG is not defined.
457    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
458        bring them up to date and include new features. This patch includes:
460        - Fixed PH's badly added libz and libbz2 support.
461        - Fixed a problem with static linking.
462        - Added pcredemo. [But later removed - see 7 below.]
463        - Fixed dftables problem and added an option.
464        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
465            HAVE_LONG_LONG.
466        - Added readline support for pcretest.
467        - Added an listing of the option settings after cmake has run.
469    4.  A user submitted a patch to Makefile that makes it easy to create
470        "pcre.dll" under mingw when using Configure/Make. I added stuff to
471        Makefile.am that cause it to include this special target, without
472        affecting anything else. Note that the same mingw target plus all
473        the other distribution libraries and programs are now supported
474        when configuring with CMake (see 6 below) instead of with
475        Configure/Make.
477    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
478        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
479        exported in the Windows port". It has not yet been confirmed that the patch
480        solves the problem, but it does no harm.
482    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
483        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
484        with CMake, and also correct the comment about stack recursion.
486    7.  Remove the automatic building of pcredemo from the ./configure system and
487        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
488        of a program that users should build themselves after PCRE is installed, so
489        building it automatically is not really right. What is more, it gave
490        trouble in some build environments.
492    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
495    Version 7.5 10-Jan-08
496    ---------------------
498    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
499        values in parens when parsing an RE using the C++ wrapper."
501    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
502        Characters greater than 255 were excluded from the class instead of being
503        included.
505    3.  The same bug as (2) above applied to negated POSIX classes such as
506        [:^space:].
508    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
509        defined or documented. It seems to have been a typo for PCRE_STATIC, so
510        I have changed it.
512    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
513        first named subpattern) and a construct such as (?&a) would reference the
514        first named subpattern whose name started with "a" (in other words, the
515        length check was missing). Both these problems are fixed. "Subpattern name
516        expected" is now given for (?&) (a zero-length name), and this patch also
517        makes it give the same error for \k'' (previously it complained that that
518        was a reference to a non-existent subpattern).
520    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
521        this is right because (?- can be followed by option settings as well as by
522        digits. I have, however, made the messages clearer.
524    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
525        than the number used in the conditional) now cause a compile-time error.
526        This is actually not compatible with Perl, which accepts such patterns, but
527        treats the conditional as always being FALSE (as PCRE used to), but it
528        seems to me that giving a diagnostic is better.
530    8.  Change "alphameric" to the more common word "alphanumeric" in comments
531        and messages.
533    9.  Fix two occurrences of "backslash" in comments that should have been
534        "backspace".
536    10. Remove two redundant lines of code that can never be obeyed (their function
537        was moved elsewhere).
539    11. The program that makes PCRE's Unicode character property table had a bug
540        which caused it to generate incorrect table entries for sequences of
541        characters that have the same character type, but are in different scripts.
542        It amalgamated them into a single range, with the script of the first of
543        them. In other words, some characters were in the wrong script. There were
544        thirteen such cases, affecting characters in the following ranges:
546          U+002b0 - U+002c1
547          U+0060c - U+0060d
548          U+0061e - U+00612
549          U+0064b - U+0065e
550          U+0074d - U+0076d
551          U+01800 - U+01805
552          U+01d00 - U+01d77
553          U+01d9b - U+01dbf
554          U+0200b - U+0200f
555          U+030fc - U+030fe
556          U+03260 - U+0327f
557          U+0fb46 - U+0fbb1
558          U+10450 - U+1049d
560    12. The -o option (show only the matching part of a line) for pcregrep was not
561        compatible with GNU grep in that, if there was more than one match in a
562        line, it showed only the first of them. It now behaves in the same way as
563        GNU grep.
565    13. If the -o and -v options were combined for pcregrep, it printed a blank
566        line for every non-matching line. GNU grep prints nothing, and pcregrep now
567        does the same. The return code can be used to tell if there were any
568        non-matching lines.
570    14. Added --file-offsets and --line-offsets to pcregrep.
572    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
573        infinitely looping recursion. The bug was that positive lookaheads were not
574        being skipped when checking for a possible empty match (negative lookaheads
575        and both kinds of lookbehind were skipped).
577    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
578        inclusion of <windows.h> to before rather than after the definition of
579        INVALID_FILE_ATTRIBUTES (patch from David Byron).
581    17. Specifying a possessive quantifier with a specific limit for a Unicode
582        character property caused pcre_compile() to compile bad code, which led at
583        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
584        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
585        caused the error; without that there was no problem.
587    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
589    19. Added --enable-pcretest-libreadline.
591    20. In pcrecpp.cc, the variable 'count' was incremented twice in
592        RE::GlobalReplace(). As a result, the number of replacements returned was
593        double what it should be. I removed one of the increments, but Craig sent a
594        later patch that removed the other one (the right fix) and added unit tests
595        that check the return values (which was not done before).
597    21. Several CMake things:
599        (1) Arranged that, when cmake is used on Unix, the libraries end up with
600            the names libpcre and libpcreposix, not just pcre and pcreposix.
602        (2) The above change means that pcretest and pcregrep are now correctly
603            linked with the newly-built libraries, not previously installed ones.
607    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
608        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
609        UTF-8 newline character). The key issue is that the pattern starts .*;
610        this means that the match must be either at the beginning, or after a
611        newline. The bug was in the code for advancing after a failed match and
612        checking that the new position followed a newline. It was not taking
613        account of UTF-8 characters correctly.
615    23. PCRE was behaving differently from Perl in the way it recognized POSIX
616        character classes. PCRE was not treating the sequence [:...:] as a
617        character class unless the ... were all letters. Perl, however, seems to
618        allow any characters between [: and :], though of course it rejects as
619        unknown any "names" that contain non-letters, because all the known class
620        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
621        for example, whereas PCRE did not - it did not recognize a POSIX character
622        class. This seemed a bit dangerous, so the code has been changed to be
623        closer to Perl. The behaviour is not identical to Perl, because PCRE will
624        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
625        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
626        Perl does, and where it didn't before.
628    24. Rewrite so as to remove the single use of %n from pcregrep because in some
629        Windows environments %n is disabled by default.
632    Version 7.4 21-Sep-07
633    ---------------------
635    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
636        means that a class such as [\s] counted as "explicit reference to CR or
637        LF". That isn't really right - the whole point of the change was to try to
638        help when there was an actual mention of one of the two characters. So now
639        the change happens only if \r or \n (or a literal CR or LF) character is
640        encountered.
642    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
643        of both had grown to the point where there were only 3 bits left.
644        Fortunately, there was spare space in the data structure, and so I have
645        moved the internal flags into a new 16-bit field to free up more option
646        bits.
648    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
649        but did not set the internal JCHANGED flag - either of these is enough to
650        control the way the "get" function works - but the PCRE_INFO_JCHANGED
651        facility is supposed to tell if (?J) was ever used, so now (?J) at the
652        start sets both bits.
654    4.  Added options (at build time, compile time, exec time) to change \R from
655        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
657    5.  doc/pcresyntax.html was missing from the distribution.
659    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
660        compatibility, even though it is no longer used.
662    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
663        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
664        windows.h file is present (where different names are used). [This was
665        reversed later after testing - see 16 below.]
667    8.  Changed all #include <config.h> to #include "config.h". There were also
668        some further <pcre.h> cases that I changed to "pcre.h".
670    9.  When pcregrep was used with the --colour option, it missed the line ending
671        sequence off the lines that it output.
673    10. It was pointed out to me that arrays of string pointers cause lots of
674        relocations when a shared library is dynamically loaded. A technique of
675        using a single long string with a table of offsets can drastically reduce
676        these. I have refactored PCRE in four places to do this. The result is
677        dramatic:
679          Originally:                          290
680          After changing UCP table:            187
681          After changing error message table:   43
682          After changing table of "verbs"       36
683          After changing table of Posix names   22
685        Thanks to the folks working on Gregex for glib for this insight.
687    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
688        unicode-properties was also set.
690    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
692    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
693        checked only for CRLF.
695    14. Added casts to pcretest.c to avoid compiler warnings.
697    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
699    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
700        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
701        entirely. This removes changes made in 7 above.
703    17. The CMake files have been updated, and there is now more information about
704        building with CMake in the NON-UNIX-USE document.
707    Version 7.3 28-Aug-07
708    ---------------------
710     1. In the rejigging of the build system that eventually resulted in 7.1, the
711        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
712        brackets there is not right, since it causes compilers to look for an
713        installed pcre.h, not the version that is in the source that is being
714        compiled (which of course may be different). I have changed it back to:
716          #include "pcre.h"
718        I have a vague recollection that the change was concerned with compiling in
719        different directories, but in the new build system, that is taken care of
720        by the VPATH setting the Makefile.
722     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
723        when the subject happened to end in the byte 0x85 (e.g. if the last
724        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
725        characters but of course it shouldn't be taken as a newline when it is part
726        of another character. The bug was that, for an unlimited repeat of . in
727        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
728        characters when looking for a newline.
730     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
732     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
733        in debug output.
735     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
736        long printing in the pcrecpp unittest when running under MinGW.
738     6. ESC_K was left out of the EBCDIC table.
740     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
741        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
742        limit also applies to "virtual nesting" when a pattern is recursive, and in
743        this case 1000 isn't so big. I have been able to remove this limit at the
744        expense of backing off one optimization in certain circumstances. Normally,
745        when pcre_exec() would call its internal match() function recursively and
746        immediately return the result unconditionally, it uses a "tail recursion"
747        feature to save stack. However, when a subpattern that can match an empty
748        string has an unlimited repetition quantifier, it no longer makes this
749        optimization. That gives it a stack frame in which to save the data for
750        checking that an empty string has been matched. Previously this was taken
751        from the 1000-entry workspace that had been reserved. So now there is no
752        explicit limit, but more stack is used.
754     8. Applied Daniel's patches to solve problems with the import/export magic
755        syntax that is required for Windows, and which was going wrong for the
756        pcreposix and pcrecpp parts of the library. These were overlooked when this
757        problem was solved for the main library.
759     9. There were some crude static tests to avoid integer overflow when computing
760        the size of patterns that contain repeated groups with explicit upper
761        limits. As the maximum quantifier is 65535, the maximum group length was
762        set at 30,000 so that the product of these two numbers did not overflow a
763        32-bit integer. However, it turns out that people want to use groups that
764        are longer than 30,000 bytes (though not repeat them that many times).
765        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
766        made it possible to implement the integer overflow checks in a much more
767        dynamic way, which I have now done. The artificial limitation on group
768        length has been removed - we now have only the limit on the total length of
769        the compiled pattern, which depends on the LINK_SIZE setting.
771    10. Fixed a bug in the documentation for get/copy named substring when
772        duplicate names are permitted. If none of the named substrings are set, the
773        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
774        empty string.
776    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
777        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
778        because the ] is interpreted as the first data character and the
779        terminating ] is not found. PCRE has been made compatible with Perl in this
780        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
781        cause memory overwriting.
783    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
784        string has been matched (to stop an infinite loop). It was not recognizing
785        a conditional subpattern that could match an empty string if that
786        subpattern was within another subpattern. For example, it looped when
787        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
788        condition was not nested. This bug has been fixed.
790    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
791        past the start of the subject in the presence of bytes with the top bit
792        set, for example "\x8aBCD".
794    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
795        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
797    14. Optimized (?!) to (*FAIL).
799    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
800        This restricts code points to be within the range 0 to 0x10FFFF, excluding
801        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
802        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
803        does: it's just the validity check that is more restrictive.
805    16. Inserted checks for integer overflows during escape sequence (backslash)
806        processing, and also fixed erroneous offset values for syntax errors during
807        backslash processing.
809    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
810        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
812    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
813        caused an overrun.
815    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
816        something other than just ASCII characters) inside a group that had an
817        unlimited repeat caused a loop at compile time (while checking to see
818        whether the group could match an empty string).
820    20. Debugging a pattern containing \p or \P could cause a crash. For example,
821        [\P{Any}] did so. (Error in the code for printing property names.)
823    21. An orphan \E inside a character class could cause a crash.
825    22. A repeated capturing bracket such as (A)? could cause a wild memory
826        reference during compilation.
828    23. There are several functions in pcre_compile() that scan along a compiled
829        expression for various reasons (e.g. to see if it's fixed length for look
830        behind). There were bugs in these functions when a repeated \p or \P was
831        present in the pattern. These operators have additional parameters compared
832        with \d, etc, and these were not being taken into account when moving along
833        the compiled data. Specifically:
835        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
836            length.
838        (b) An item such as \pL+ within a repeated group could cause crashes or
839            loops.
841        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
842            "reference to non-existent subpattern" error.
844        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
846    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
847        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
849    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
851    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
852        character were causing crashes (broken optimization).
854    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
855        \p or \P) caused a compile-time loop.
857    28. More problems have arisen in unanchored patterns when CRLF is a valid line
858        break. For example, the unstudied pattern [\r\n]A does not match the string
859        "\r\nA" because change 7.0/46 below moves the current point on by two
860        characters after failing to match at the start. However, the pattern \nA
861        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
862        the same is true. There doesn't seem any very clean way out of this, but
863        what I have chosen to do makes the common cases work: PCRE now takes note
864        of whether there can be an explicit match for \r or \n anywhere in the
865        pattern, and if so, 7.0/46 no longer applies. As part of this change,
866        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
867        pattern has explicit CR or LF references.
869    29. Added (*CR) etc for changing newline setting at start of pattern.
872    Version 7.2 19-Jun-07
873    ---------------------
875     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
876        which is apparently normally available under Windows.
878     2. Re-jig the pcregrep tests with different newline settings in an attempt
879        to make them independent of the local environment's newline setting.
881     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
883     4. Some of the "internals" tests were previously cut out when the link size
884        was not 2, because the output contained actual offsets. The recent new
885        "Z" feature of pcretest means that these can be cut out, making the tests
886        usable with all link sizes.
888     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
889        stack recursion. This gives a massive performance boost under BSD, but just
890        a small improvement under Linux. However, it saves one field in the frame
891        in all cases.
893     6. Added more features from the forthcoming Perl 5.10:
895        (a) (?-n) (where n is a string of digits) is a relative subroutine or
896            recursion call. It refers to the nth most recently opened parentheses.
898        (b) (?+n) is also a relative subroutine call; it refers to the nth next
899            to be opened parentheses.
901        (c) Conditions that refer to capturing parentheses can be specified
902            relatively, for example, (?(-2)... or (?(+3)...
904        (d) \K resets the start of the current match so that everything before
905            is not part of it.
907        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
909        (f) \g{name} is another synonym - part of Perl 5.10's unification of
910            reference syntax.
912        (g) (?| introduces a group in which the numbering of parentheses in each
913            alternative starts with the same number.
915        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
917     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
920     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
921        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
922        for detecting groups that can match an empty string.
924     9. A pattern with a very large number of alternatives (more than several
925        hundred) was running out of internal workspace during the pre-compile
926        phase, where pcre_compile() figures out how much memory will be needed. A
927        bit of new cunning has reduced the workspace needed for groups with
928        alternatives. The 1000-alternative test pattern now uses 12 bytes of
929        workspace instead of running out of the 4096 that are available.
931    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
933    11. Applied patch from Google to remove an optimization that didn't quite work.
934        The report of the bug said:
936          pcrecpp::RE("a*").FullMatch("aaa") matches, while
937          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
938          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
940    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
941        it matched the wrong number of bytes.
944    Version 7.1 24-Apr-07
945    ---------------------
947     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
948        that is more "standard", making use of automake and other Autotools. There
949        is some re-arrangement of the files and adjustment of comments consequent
950        on this.
952     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
953        for recursive directory scanning broke on some systems because the files
954        are not scanned in any specific order and on different systems the order
955        was different. A call to "sort" has been inserted into RunGrepTest for the
956        approprate test as a short-term fix. In the longer term there may be an
957        alternative.
959     3. I had an email from Eric Raymond about problems translating some of PCRE's
960        man pages to HTML (despite the fact that I distribute HTML pages, some
961        people do their own conversions for various reasons). The problems
962        concerned the use of low-level troff macros .br and .in. I have therefore
963        removed all such uses from the man pages (some were redundant, some could
964        be replaced by .nf/.fi pairs). The 132html script that I use to generate
965        HTML has been updated to handle .nf/.fi and to complain if it encounters
966        .br or .in.
968     4. Updated comments in configure.ac that get placed in config.h.in and also
969        arranged for config.h to be included in the distribution, with the name
970        config.h.generic, for the benefit of those who have to compile without
971        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
973     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
974        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
975        makevp.bat for the current PCRE, using the additional files
976        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
978     6. A Windows user reported a minor discrepancy with test 2, which turned out
979        to be caused by a trailing space on an input line that had got lost in his
980        copy. The trailing space was an accident, so I've just removed it.
982     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
983        that is needed.
985     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
986        as "const" (a) because they are and (b) because it helps the PHP
987        maintainers who have recently made a script to detect big data structures
988        in the php code that should be moved to the .rodata section. I remembered
989        to update Builducptable as well, so it won't revert if ucptable.h is ever
990        re-created.
992     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
993        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
994        order to be able to cut out the UTF-8 tables in the latter when UTF-8
995        support is not required. This saves 1.5-2K of code, which is important in
996        some applications.
998        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
999        so as not to refer to the tables, even though these functions will never be
1000        called when UTF-8 support is disabled. Otherwise there are problems with a
1001        shared library.
1003    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
1005        (a) It was defining its arguments as char * instead of void *.
1007        (b) It was assuming that all moves were upwards in memory; this was true
1008            a long time ago when I wrote it, but is no longer the case.
1010        The emulated memove() is provided for those environments that have neither
1011        memmove() nor bcopy(). I didn't think anyone used it these days, but that
1012        is clearly not the case, as these two bugs were recently reported.
1014    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
1015        and Detrail to create the HTML documentation, the .txt form of the man
1016        pages, and it removes trailing spaces from listed files. It also creates
1017        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
1018        case, it wraps all the #defines with #ifndefs. This script should be run
1019        before "make dist".
1021    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
1022        with Unicode property support.
1024        (a) For a maximizing quantifier, if the two different cases of the
1025            character were of different lengths in their UTF-8 codings (there are
1026            some cases like this - I found 11), and the matching function had to
1027            back up over a mixture of the two cases, it incorrectly assumed they
1028            were both the same length.
1030        (b) When PCRE was configured to use the heap rather than the stack for
1031            recursion during matching, it was not correctly preserving the data for
1032            the other case of a UTF-8 character when checking ahead for a match
1033            while processing a minimizing repeat. If the check also involved
1034            matching a wide character, but failed, corruption could cause an
1035            erroneous result when trying to check for a repeat of the original
1036            character.
1038    13. Some tidying changes to the testing mechanism:
1040        (a) The RunTest script now detects the internal link size and whether there
1041            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
1042            values substituted by "configure". (The RunGrepTest script already did
1043            this for UTF-8.) The configure.ac script no longer substitutes the
1044            relevant variables.
1046        (b) The debugging options /B and /D in pcretest show the compiled bytecode
1047            with length and offset values. This means that the output is different
1048            for different internal link sizes. Test 2 is skipped for link sizes
1049            other than 2 because of this, bypassing the problem. Unfortunately,
1050            there was also a test in test 3 (the locale tests) that used /B and
1051            failed for link sizes other than 2. Rather than cut the whole test out,
1052            I have added a new /Z option to pcretest that replaces the length and
1053            offset values with spaces. This is now used to make test 3 independent
1054            of link size. (Test 2 will be tidied up later.)
1056    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
1057        segmentation fault instead of returning the appropriate error message.
1059    15. In multiline mode when the newline sequence was set to "any", the pattern
1060        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
1061        This doesn't seem right; it now treats the CRLF combination as the line
1062        ending, and so does not match in that case. It's only a pattern such as ^$
1063        that would hit this one: something like ^ABC$ would have failed after \r
1064        and then tried again after \r\n.
1066    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
1067        in an attempt to make files that differ only in their line terminators
1068        compare equal. This works on Linux.
1070    17. Under certain error circumstances pcregrep might try to free random memory
1071        as it exited. This is now fixed, thanks to valgrind.
1073    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
1074        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
1075        was because its rules for how to advance for /g after matching an empty
1076        string at the end of a line did not allow for this case. They now check for
1077        it specially.
1079    20. pcretest is supposed to handle patterns and data of any length, by
1080        extending its buffers when necessary. It was getting this wrong when the
1081        buffer for a data line had to be extended.
1083    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1084        CRLF as a newline sequence.
1086    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1087        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1088        I have nevertheless tidied it up.
1090    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1092    24. Added a man page for pcre-config.
1095    Version 7.0 19-Dec-06
1096    ---------------------
1098     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
1099        moving to gcc 4.1.1.
1101     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
1102        sys/time.h, which is documented as needed for this function. It doesn't
1103        seem to matter on Linux, but it showed up on some releases of OS X.
1105     3. It seems that there are systems where bytes whose values are greater than
1106        127 match isprint() in the "C" locale. The "C" locale should be the
1107        default when a C program starts up. In most systems, only ASCII printing
1108        characters match isprint(). This difference caused the output from pcretest
1109        to vary, making some of the tests fail. I have changed pcretest so that:
1111        (a) When it is outputting text in the compiled version of a pattern, bytes
1112            other than 32-126 are always shown as hex escapes.
1114        (b) When it is outputting text that is a matched part of a subject string,
1115            it does the same, unless a different locale has been set for the match
1116            (using the /L modifier). In this case, it uses isprint() to decide.
1118     4. Fixed a major bug that caused incorrect computation of the amount of memory
1119        required for a compiled pattern when options that changed within the
1120        pattern affected the logic of the preliminary scan that determines the
1121        length. The relevant options are -x, and -i in UTF-8 mode. The result was
1122        that the computed length was too small. The symptoms of this bug were
1123        either the PCRE error "internal error: code overflow" from pcre_compile(),
1124        or a glibc crash with a message such as "pcretest: free(): invalid next
1125        size (fast)". Examples of patterns that provoked this bug (shown in
1126        pcretest format) are:
1128          /(?-x: )/x
1129          /(?x)(?-x: \s*#\s*)/
1130          /((?i)[\x{c0}])/8
1131          /(?i:[\x{c0}])/8
1133        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
1134        is now done differently.
1136     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
1137        wrapper classes; (b) implement a new function in the C++ scanner that is
1138        more efficient than the old way of doing things because it avoids levels of
1139        recursion in the regex matching; (c) add a paragraph to the documentation
1140        for the FullMatch() function.
1142     6. The escape sequence \n was being treated as whatever was defined as
1143        "newline". Not only was this contrary to the documentation, which states
1144        that \n is character 10 (hex 0A), but it also went horribly wrong when
1145        "newline" was defined as CRLF. This has been fixed.
1147     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
1148        was being set to -1 for the "end of line" case (supposedly a value that no
1149        character can have). Though this value is never used (the check for end of
1150        line is "zero bytes in current character"), it caused compiler complaints.
1151        I've changed it to 0xffffffff.
1153     8. In pcre_version.c, the version string was being built by a sequence of
1154        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
1155        string (as it is for production releases) called a macro with an empty
1156        argument. The C standard says the result of this is undefined. The gcc
1157        compiler treats it as an empty string (which was what was wanted) but it is
1158        reported that Visual C gives an error. The source has been hacked around to
1159        avoid this problem.
1161     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
1162        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
1163        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
1164        of them did).
1166    10. Originally, pcretest opened its input and output without "b"; then I was
1167        told that "b" was needed in some environments, so it was added for release
1168        5.0 to both the input and output. (It makes no difference on Unix-like
1169        systems.) Later I was told that it is wrong for the input on Windows. I've
1170        now abstracted the modes into two macros, to make it easier to fiddle with
1171        them, and removed "b" from the input mode under Windows.
1173    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
1175    12. Added -help and --help to pcretest as an official way of being reminded
1176        of the options.
1178    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
1179        and pcrecpp.cc because they annoy compilers at high warning levels.
1181    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
1183    15. Fixed an occurrence of == in configure.ac that should have been = (shell
1184        scripts are not C programs :-) and which was not noticed because it works
1185        on Linux.
1187    16. pcretest is supposed to handle any length of pattern and data line (as one
1188        line or as a continued sequence of lines) by extending its input buffer if
1189        necessary. This feature was broken for very long pattern lines, leading to
1190        a string of junk being passed to pcre_compile() if the pattern was longer
1191        than about 50K.
1193    17. I have done a major re-factoring of the way pcre_compile() computes the
1194        amount of memory needed for a compiled pattern. Previously, there was code
1195        that made a preliminary scan of the pattern in order to do this. That was
1196        OK when PCRE was new, but as the facilities have expanded, it has become
1197        harder and harder to keep it in step with the real compile phase, and there
1198        have been a number of bugs (see for example, 4 above). I have now found a
1199        cunning way of running the real compile function in a "fake" mode that
1200        enables it to compute how much memory it would need, while actually only
1201        ever using a few hundred bytes of working memory and without too many
1202        tests of the mode. This should make future maintenance and development
1203        easier. A side effect of this work is that the limit of 200 on the nesting
1204        depth of parentheses has been removed (though this was never a serious
1205        limitation, I suspect). However, there is a downside: pcre_compile() now
1206        runs more slowly than before (30% or more, depending on the pattern). I
1207        hope this isn't a big issue. There is no effect on runtime performance.
1209    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
1210        newline (only possible for the last line of a file) and it was a
1211        pattern that set a locale (followed by /Lsomething), pcretest crashed.
1213    19. Added additional timing features to pcretest. (1) The -tm option now times
1214        matching only, not compiling. (2) Both -t and -tm can be followed, as a
1215        separate command line item, by a number that specifies the number of
1216        repeats to use when timing. The default is 50000; this gives better
1217        precision, but takes uncomfortably long for very large patterns.
1219    20. Extended pcre_study() to be more clever in cases where a branch of a
1220        subpattern has no definite first character. For example, (a*|b*)[cd] would
1221        previously give no result from pcre_study(). Now it recognizes that the
1222        first character must be a, b, c, or d.
1224    21. There was an incorrect error "recursive call could loop indefinitely" if
1225        a subpattern (or the entire pattern) that was being tested for matching an
1226        empty string contained only one non-empty item after a nested subpattern.
1227        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
1228        incorrectly, because the \d was being skipped in the check.
1230    22. The pcretest program now has a new pattern option /B and a command line
1231        option -b, which is equivalent to adding /B to every pattern. This causes
1232        it to show the compiled bytecode, without the additional information that
1233        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
1234        is the same as /B/I).
1236    23. A new optimization is now able automatically to treat some sequences such
1237        as a*b as a*+b. More specifically, if something simple (such as a character
1238        or a simple class like \d) has an unlimited quantifier, and is followed by
1239        something that cannot possibly match the quantified thing, the quantifier
1240        is automatically "possessified".
1242    24. A recursive reference to a subpattern whose number was greater than 39
1243        went wrong under certain circumstances in UTF-8 mode. This bug could also
1244        have affected the operation of pcre_study().
1246    25. Realized that a little bit of performance could be had by replacing
1247        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
1249    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
1251    27. Possessive quantifiers such as a++ were previously implemented by turning
1252        them into atomic groups such as ($>a+). Now they have their own opcodes,
1253        which improves performance. This includes the automatically created ones
1254        from 23 above.
1256    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
1257        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
1258        the first matched character to be a colon. This applied both to named and
1259        numbered groups.
1261    29. The ucpinternal.h header file was missing its idempotency #ifdef.
1263    30. I was sent a "project" file called libpcre.a.dev which I understand makes
1264        building PCRE on Windows easier, so I have included it in the distribution.
1266    31. There is now a check in pcretest against a ridiculously large number being
1267        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
1268        loop, the loop is abandoned.
1270    32. Forward references to subpatterns in conditions such as (?(2)...) where
1271        subpattern 2 is defined later cause pcre_compile() to search forwards in
1272        the pattern for the relevant set of parentheses. This search went wrong
1273        when there were unescaped parentheses in a character class, parentheses
1274        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
1276    33. "Subroutine" calls and backreferences were previously restricted to
1277        referencing subpatterns earlier in the regex. This restriction has now
1278        been removed.
1280    34. Added a number of extra features that are going to be in Perl 5.10. On the
1281        whole, these are just syntactic alternatives for features that PCRE had
1282        previously implemented using the Python syntax or my own invention. The
1283        other formats are all retained for compatibility.
1285        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
1286            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
1287            also .NET compatible.
1289        (b) A recursion or subroutine call to a named group can now be defined as
1290            (?&name) as well as (?P>name).
1292        (c) A backreference to a named group can now be defined as \k<name> or
1293            \k'name' as well as (?P=name). The new forms, as well as being in Perl
1294            5.10, are also .NET compatible.
1296        (d) A conditional reference to a named group can now use the syntax
1297            (?(<name>) or (?('name') as well as (?(name).
1299        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
1300            groups (named and numbered) that are never evaluated inline, but can be
1301            called as "subroutines" from elsewhere. In effect, the DEFINE condition
1302            is always false. There may be only one alternative in such a group.
1304        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
1305            as the simple (?(R). The condition is true only if the most recent
1306            recursion is that of the given number or name. It does not search out
1307            through the entire recursion stack.
1309        (g) The escape \gN or \g{N} has been added, where N is a positive or
1310            negative number, specifying an absolute or relative reference.
1312    35. Tidied to get rid of some further signed/unsigned compiler warnings and
1313        some "unreachable code" warnings.
1315    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
1316        things, this adds five new scripts.
1318    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
1319        There were also incompatibilities regarding the handling of \Q..\E inside
1320        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
1321        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
1323    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
1324        matches an empty string, and forcibly breaks the loop. There were bugs in
1325        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
1326        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
1327        separate and independent bugs (that affected different cases) have been
1328        fixed.
1330    39. Refactored the code to abolish the use of different opcodes for small
1331        capturing bracket numbers. This is a tidy that I avoided doing when I
1332        removed the limit on the number of capturing brackets for 3.5 back in 2001.
1333        The new approach is not only tidier, it makes it possible to reduce the
1334        memory needed to fix the previous bug (38).
1336    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
1337        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
1338        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
1339        mode.
1341    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
1342        report.
1344    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
1345        copy construction and assignment in the C++ wrapper.
1347    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
1348        couple of bugs that could have given wrong results in the "--newline=crlf"
1349        case.
1351    44. Added a number of casts and did some reorganization of signed/unsigned int
1352        variables following suggestions from Dair Grant. Also renamed the variable
1353        "this" as "item" because it is a C++ keyword.
1355    45. Arranged for dftables to add
1357          #include "pcre_internal.h"
1359        to pcre_chartables.c because without it, gcc 4.x may remove the array
1360        definition from the final binary if PCRE is built into a static library and
1361        dead code stripping is activated.
1363    46. For an unanchored pattern, if a match attempt fails at the start of a
1364        newline sequence, and the newline setting is CRLF or ANY, and the next two
1365        characters are CRLF, advance by two characters instead of one.
1368    Version 6.7 04-Jul-06
1369    ---------------------
1371     1. In order to handle tests when input lines are enormously long, pcretest has
1372        been re-factored so that it automatically extends its buffers when
1373        necessary. The code is crude, but this _is_ just a test program. The
1374        default size has been increased from 32K to 50K.
1376     2. The code in pcre_study() was using the value of the re argument before
1377        testing it for NULL. (Of course, in any sensible call of the function, it
1378        won't be NULL.)
1380     3. The memmove() emulation function in pcre_internal.h, which is used on
1381        systems that lack both memmove() and bcopy() - that is, hardly ever -
1382        was missing a "static" storage class specifier.
1384     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
1385        containing an extended class (one that cannot be represented by a bitmap
1386        because it contains high-valued characters or Unicode property items, e.g.
1387        [\pZ]). Almost always one would set UTF-8 mode when processing such a
1388        pattern, but PCRE should not loop if you do not (it no longer does).
1389        [Detail: two cases were found: (a) a repeated subpattern containing an
1390        extended class; (b) a recursive reference to a subpattern that followed a
1391        previous extended class. It wasn't skipping over the extended class
1392        correctly when UTF-8 mode was not set.]
1394     5. A negated single-character class was not being recognized as fixed-length
1395        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
1396        compile error "lookbehind assertion is not fixed length".
1398     6. The RunPerlTest auxiliary script was showing an unexpected difference
1399        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
1400        write a Perl script that can interpret lines of an input file either as
1401        byte characters or as UTF-8, which is what "perltest" was being required to
1402        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
1403        can't do is switch easily at run time between having the "use utf8;" pragma
1404        or not. In the end, I fudged it by using the RunPerlTest script to insert
1405        "use utf8;" explicitly for the UTF-8 tests.
1407     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
1408        the end of the subject string, contrary to the documentation and to what
1409        Perl does. This was true of both matching functions. Now it matches only at
1410        the start of the subject and immediately after *internal* newlines.
1412     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
1413        a pointer to an int instead of a pointer to an unsigned long int. This
1414        caused problems on 64-bit systems.
1416     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
1417        instance of the 'standard' template library not being so standard".
1419    10. There was no check on the number of named subpatterns nor the maximum
1420        length of a subpattern name. The product of these values is used to compute
1421        the size of the memory block for a compiled pattern. By supplying a very
1422        long subpattern name and a large number of named subpatterns, the size
1423        computation could be caused to overflow. This is now prevented by limiting
1424        the length of names to 32 characters, and the number of named subpatterns
1425        to 10,000.
1427    11. Subpatterns that are repeated with specific counts have to be replicated in
1428        the compiled pattern. The size of memory for this was computed from the
1429        length of the subpattern and the repeat count. The latter is limited to
1430        65535, but there was no limit on the former, meaning that integer overflow
1431        could in principle occur. The compiled length of a repeated subpattern is
1432        now limited to 30,000 bytes in order to prevent this.
1434    12. Added the optional facility to have named substrings with the same name.
1436    13. Added the ability to use a named substring as a condition, using the
1437        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
1438        are numbers (not recommended). Forward references are permitted.
1440    14. Added forward references in named backreferences (if you see what I mean).
1442    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
1443        pattern could run off the end of the subject. For example, the pattern
1444        "(?s)(.{1,5})"8 did this with the subject "ab".
1446    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
1447        PCRE_CASELESS was set when matching characters that were quantified with ?
1448        or *.
1450    17. A character class other than a single negated character that had a minimum
1451        but no maximum quantifier - for example [ab]{6,} - was not handled
1452        correctly by pce_dfa_exec(). It would match only one character.
1454    18. A valid (though odd) pattern that looked like a POSIX character
1455        class but used an invalid character after [ (for example [[,abc,]]) caused
1456        pcre_compile() to give the error "Failed: internal error: code overflow" or
1457        in some cases to crash with a glibc free() error. This could even happen if
1458        the pattern terminated after [[ but there just happened to be a sequence of
1459        letters, a binary zero, and a closing ] in the memory that followed.
1461    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
1462        over the years. Originally (before any Unicode support), just the bottom 8
1463        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
1464        output from "man perlunicode" includes this:
1466          The regular expression compiler produces polymorphic opcodes.  That
1467          is, the pattern adapts to the data and automatically switches to
1468          the Unicode character scheme when presented with Unicode data--or
1469          instead uses a traditional byte scheme when presented with byte
1470          data.
1472        Sadly, a wide octal escape does not cause a switch, and in a string with
1473        no other multibyte characters, these octal escapes are treated as before.
1474        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
1475        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
1476        Unicode string.
1478        I have not perpetrated such confusion in PCRE. Up till now, it took just
1479        the bottom 8 bits, as in old Perl. I have now made octal escapes with
1480        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
1481        translate to the appropriate multibyte character.
1483    29. Applied some refactoring to reduce the number of warnings from Microsoft
1484        and Borland compilers. This has included removing the fudge introduced
1485        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
1486        a warning about an unused variable.
1488    21. PCRE has not included VT (character 0x0b) in the set of whitespace
1489        characters since release 4.0, because Perl (from release 5.004) does not.
1490        [Or at least, is documented not to: some releases seem to be in conflict
1491        with the documentation.] However, when a pattern was studied with
1492        pcre_study() and all its branches started with \s, PCRE still included VT
1493        as a possible starting character. Of course, this did no harm; it just
1494        caused an unnecessary match attempt.
1496    22. Removed a now-redundant internal flag bit that recorded the fact that case
1497        dependency changed within the pattern. This was once needed for "required
1498        byte" processing, but is no longer used. This recovers a now-scarce options
1499        bit. Also moved the least significant internal flag bit to the most-
1500        significant bit of the word, which was not previously used (hangover from
1501        the days when it was an int rather than a uint) to free up another bit for
1502        the future.
1504    23. Added support for CRLF line endings as well as CR and LF. As well as the
1505        default being selectable at build time, it can now be changed at runtime
1506        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1507        specify that it is scanning data with non-default line endings.
1509    24. Changed the definition of CXXLINK to make it agree with the definition of
1510        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1512    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1513        recursions. This makes a big different to stack usage for some patterns.
1515    26. If a subpattern containing a named recursion or subroutine reference such
1516        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1517        the space required for the compiled pattern went wrong and gave too small a
1518        value. Depending on the environment, this could lead to "Failed: internal
1519        error: code overflow at offset 49" or "glibc detected double free or
1520        corruption" errors.
1522    27. Applied patches from Google (a) to support the new newline modes and (b) to
1523        advance over multibyte UTF-8 characters in GlobalReplace.
1525    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1526        difference for some implementation of PCRE in some Windows version.
1528    29. Added some extra testing facilities to pcretest:
1530        \q<number>   in a data line sets the "match limit" value
1531        \Q<number>   in a data line sets the "match recursion limt" value
1532        -S <number>  sets the stack size, where <number> is in megabytes
1534        The -S option isn't available for Windows.
1537    Version 6.6 06-Feb-06
1538    ---------------------
1540     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1541        in pcreposix.h. I have copied the definition from pcre.h.
1543     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1544        because pcre.h is no longer a built file.
1546     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1547        not normally included in the compiled code.
1550    Version 6.5 01-Feb-06
1551    ---------------------
1553     1. When using the partial match feature with pcre_dfa_exec(), it was not
1554        anchoring the second and subsequent partial matches at the new starting
1555        point. This could lead to incorrect results. For example, with the pattern
1556        /1234/, partially matching against "123" and then "a4" gave a match.
1558     2. Changes to pcregrep:
1560        (a) All non-match returns from pcre_exec() were being treated as failures
1561            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
1562            error message is output. Some extra information is given for the
1563            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
1564            probably the only errors that are likely to be caused by users (by
1565            specifying a regex that has nested indefinite repeats, for instance).
1566            If there are more than 20 of these errors, pcregrep is abandoned.
1568        (b) A binary zero was treated as data while matching, but terminated the
1569            output line if it was written out. This has been fixed: binary zeroes
1570            are now no different to any other data bytes.
1572        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
1573            used to set a locale for matching. The --locale=xxxx long option has
1574            been added (no short equivalent) to specify a locale explicitly on the
1575            pcregrep command, overriding the environment variables.
1577        (d) When -B was used with -n, some line numbers in the output were one less
1578            than they should have been.
1580        (e) Added the -o (--only-matching) option.
1582        (f) If -A or -C was used with -c (count only), some lines of context were
1583            accidentally printed for the final match.
1585        (g) Added the -H (--with-filename) option.
1587        (h) The combination of options -rh failed to suppress file names for files
1588            that were found from directory arguments.
1590        (i) Added the -D (--devices) and -d (--directories) options.
1592        (j) Added the -F (--fixed-strings) option.
1594        (k) Allow "-" to be used as a file name for -f as well as for a data file.
1596        (l) Added the --colo(u)r option.
1598        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
1599            is not present by default.
1601     3. A nasty bug was discovered in the handling of recursive patterns, that is,
1602        items such as (?R) or (?1), when the recursion could match a number of
1603        alternatives. If it matched one of the alternatives, but subsequently,
1604        outside the recursion, there was a failure, the code tried to back up into
1605        the recursion. However, because of the way PCRE is implemented, this is not
1606        possible, and the result was an incorrect result from the match.
1608        In order to prevent this happening, the specification of recursion has
1609        been changed so that all such subpatterns are automatically treated as
1610        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1612     4. I had overlooked the fact that, in some locales, there are characters for
1613        which isalpha() is true but neither isupper() nor islower() are true. In
1614        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1615        and ordfeminine) are like this. This affected the treatment of \w and \W
1616        when they appeared in character classes, but not when they appeared outside
1617        a character class. The bit map for "word" characters is now created
1618        separately from the results of isalnum() instead of just taking it from the
1619        upper, lower, and digit maps. (Plus the underscore character, of course.)
1621     5. The above bug also affected the handling of POSIX character classes such as
1622        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
1623        permanent tables. Instead, the bit maps for such a class were previously
1624        created as the appropriate unions of the upper, lower, and digit bitmaps.
1625        Now they are created by subtraction from the [[:word:]] class, which has
1626        its own bitmap.
1628     6. The [[:blank:]] character class matches horizontal, but not vertical space.
1629        It is created by subtracting the vertical space characters (\x09, \x0a,
1630        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
1631        subtraction was done in the overall bitmap for a character class, meaning
1632        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
1633        be recognized. This bug has been fixed.
1635     7. Patches from the folks at Google:
1637          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
1638          real life, but is still worth protecting against".
1640          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
1641          regular expressions".
1643          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
1644          have it.
1646          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
1647          "configure" and the latter not, in order to fix a problem somebody had
1648          with compiling the Arg class on HP-UX.
1650          (e) Improve the error-handling of the C++ wrapper a little bit.
1652          (f) New tests for checking recursion limiting.
1654     8. The pcre_memmove() function, which is used only if the environment does not
1655        have a standard memmove() function (and is therefore rarely compiled),
1656        contained two bugs: (a) use of int instead of size_t, and (b) it was not
1657        returning a result (though PCRE never actually uses the result).
1659     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
1660        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
1661        returned instead of calling malloc() with an overflowing number that would
1662        most likely cause subsequent chaos.
1664    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
1666    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
1667        with this option is matched, the nmatch and pmatch options of regexec() are
1668        ignored.
1670    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
1671        provided in case anyone wants to the the POSIX interface with UTF-8
1672        strings.
1674    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1675        C++ linking (needed for some HP-UX environments).
1677    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1678        (unused parameter) and in the pcre_printint() function (omitted "default"
1679        switch label when the default is to do nothing).
1681    15. Added some code to make it possible, when PCRE is compiled as a C++
1682        library, to replace subject pointers for pcre_exec() with a smart pointer
1683        class, thus making it possible to process discontinuous strings.
1685    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1686        much the same function. They were added by different people who were trying
1687        to make PCRE easy to compile on non-Unix systems. It has been suggested
1688        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1689        for compiling on Windows systems. I have therefore replaced it with
1690        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1691        defaults to "extern" for C or "extern C" for C++, which works fine on
1692        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1693        SCOPE with something explicit in config.h. In addition:
1695        (a) pcreposix.h still had just "extern" instead of either of these macros;
1696            I have replaced it with PCRE_DATA_SCOPE.
1698        (b) Functions such as _pcre_xclass(), which are internal to the library,
1699            but external in the C sense, all had PCRE_EXPORT in their definitions.
1700            This is apparently wrong for the Windows case, so I have removed it.
1701            (It makes no difference on Unix-like systems.)
1703    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1704        of recursive calls to match(). This is different to MATCH_LIMIT because
1705        that limits the total number of calls to match(), not all of which increase
1706        the depth of recursion. Limiting the recursion depth limits the amount of
1707        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1708        when PCRE is compiled, and changed at run time. A patch from Google adds
1709        this functionality to the C++ interface.
1711    18. Changes to the handling of Unicode character properties:
1713        (a) Updated the table to Unicode 4.1.0.
1715        (b) Recognize characters that are not in the table as "Cn" (undefined).
1717        (c) I revised the way the table is implemented to a much improved format
1718            which includes recognition of ranges. It now supports the ranges that
1719            are defined in UnicodeData.txt, and it also amalgamates other
1720            characters into ranges. This has reduced the number of entries in the
1721            table from around 16,000 to around 3,000, thus reducing its size
1722            considerably. I realized I did not need to use a tree structure after
1723            all - a binary chop search is just as efficient. Having reduced the
1724            number of entries, I extended their size from 6 bytes to 8 bytes to
1725            allow for more data.
1727        (d) Added support for Unicode script names via properties such as \p{Han}.
1729    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1730        matching that character.
1732    20. When matching a repeated Unicode property with a minimum greater than zero,
1733        (for example \pL{2,}), PCRE could look past the end of the subject if it
1734        reached it while seeking the minimum number of characters. This could
1735        happen only if some of the characters were more than one byte long, because
1736        there is a check for at least the minimum number of bytes.
1738    21. Refactored the implementation of \p and \P so as to be more general, to
1739        allow for more different types of property in future. This has changed the
1740        compiled form incompatibly. Anybody with saved compiled patterns that use
1741        \p or \P will have to recompile them.
1743    22. Added "Any" and "L&" to the supported property types.
1745    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1746        but give a compile time error if the value is greater than 0xff.
1748    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1749        accidentally not being installed or uninstalled.
1751    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1752        made were to insert the current release number. This seemed silly, because
1753        it made things harder for people building PCRE on systems that don't run
1754        "configure". I have turned pcre.h into a distributed file, no longer built
1755        by "configure", with the version identification directly included. There is
1756        no longer a pcre.h.in file.
1758        However, this change necessitated a change to the pcre-config script as
1759        well. It is built from pcre-config.in, and one of the substitutions was the
1760        release number. I have updated configure.ac so that ./configure now finds
1761        the release number by grepping pcre.h.
1763    26. Added the ability to run the tests under valgrind.
1766    Version 6.4 05-Sep-05
1767    ---------------------
1769     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1770        "--" to be printed when multiple files were scanned, even when none of the
1771        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1772        consider it to be a bug, and have restored the previous behaviour.
1774     2. A couple of code tidies to get rid of compiler warnings.
1776     3. The pcretest program used to cheat by referring to symbols in the library
1777        whose names begin with _pcre_. These are internal symbols that are not
1778        really supposed to be visible externally, and in some environments it is
1779        possible to suppress them. The cheating is now confined to including
1780        certain files from the library's source, which is a bit cleaner.
1782     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1783        file's purpose clearer.
1785     5. Reorganized pcre_ucp_findchar().
1788    Version 6.3 15-Aug-05
1789    ---------------------
1791     1. The file libpcre.pc.in did not have general read permission in the tarball.
1793     2. There were some problems when building without C++ support:
1795        (a) If C++ support was not built, "make install" and "make test" still
1796            tried to test it.
1798        (b) There were problems when the value of CXX was explicitly set. Some
1799            changes have been made to try to fix these, and ...
1801        (c) --disable-cpp can now be used to explicitly disable C++ support.
1803        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
1804            backslash in a target when C++ was disabled. This confuses some
1805            versions of "make", apparently. Using an intermediate variable solves
1806            this. (Same for CPP_LOBJ.)
1808     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
1809        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
1810        necessary on certain architectures.
1812     4. Added a setting of -export-symbols-regex to the link command to remove
1813        those symbols that are exported in the C sense, but actually are local
1814        within the library, and not documented. Their names all begin with
1815        "_pcre_". This is not a perfect job, because (a) we have to except some
1816        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
1817        available (and never for static libraries). I have made a note to try to
1818        find a way round (a) in the future.
1821    Version 6.2 01-Aug-05
1822    ---------------------
1824     1. There was no test for integer overflow of quantifier values. A construction
1825        such as {1111111111111111} would give undefined results. What is worse, if
1826        a minimum quantifier for a parenthesized subpattern overflowed and became
1827        negative, the calculation of the memory size went wrong. This could have
1828        led to memory overwriting.
1830     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
1832     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
1833        operating environments where this matters.
1835     4. Applied Giuseppe Maxia's patch to add additional features for controlling
1836        PCRE options from within the C++ wrapper.
1838     5. Named capturing subpatterns were not being correctly counted when a pattern
1839        was compiled. This caused two problems: (a) If there were more than 100
1840        such subpatterns, the calculation of the memory needed for the whole
1841        compiled pattern went wrong, leading to an overflow error. (b) Numerical
1842        back references of the form \12, where the number was greater than 9, were
1843        not recognized as back references, even though there were sufficient
1844        previous subpatterns.
1846     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
1847        versions of gcc, e.g. 2.95.4.
1850    Version 6.1 21-Jun-05
1851    ---------------------
1853     1. There was one reference to the variable "posix" in pcretest.c that was not
1854        surrounded by "#if !defined NOPOSIX".
1856     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
1857        the cross-check on the old pcre_info() function, for the benefit of the
1858        cut-down version of PCRE that is currently imported into Exim.
1860     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
1861        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
1862        patterns that start (?i) but I don't think that matters. The use of (?i) is
1863        just an example; this all applies to the other options as well.
1865     4. Since libtool seems to echo the compile commands it is issuing, the output
1866        from "make" can be reduced a bit by putting "@" in front of each libtool
1867        compile command.
1869     5. Patch from the folks at Google for configure.in to be a bit more thorough
1870        in checking for a suitable C++ installation before trying to compile the
1871        C++ stuff. This should fix a reported problem when a compiler was present,
1872        but no suitable headers.
1874     6. The man pages all had just "PCRE" as their title. I have changed them to
1875        be the relevant file name. I have also arranged that these names are
1876        retained in the file doc/pcre.txt, which is a concatenation in text format
1877        of all the man pages except the little individual ones for each function.
1879     7. The NON-UNIX-USE file had not been updated for the different set of source
1880        files that come with release 6. I also added a few comments about the C++
1881        wrapper.
1884    Version 6.0 07-Jun-05
1885    ---------------------
1887     1. Some minor internal re-organization to help with my DFA experiments.
1889     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
1890        didn't matter for the library itself when fully configured, but did matter
1891        when compiling without UCP support, or within Exim, where the ucp files are
1892        not imported.
1894     3. Refactoring of the library code to split up the various functions into
1895        different source modules. The addition of the new DFA matching code (see
1896        below) to a single monolithic source would have made it really too
1897        unwieldy, quite apart from causing all the code to be include in a
1898        statically linked application, when only some functions are used. This is
1899        relevant even without the DFA addition now that patterns can be compiled in
1900        one application and matched in another.
1902        The downside of splitting up is that there have to be some external
1903        functions and data tables that are used internally in different modules of
1904        the library but which are not part of the API. These have all had their
1905        names changed to start with "_pcre_" so that they are unlikely to clash
1906        with other external names.
1908     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
1909        a different (DFA) algorithm. Although it is slower than the original
1910        function, it does have some advantages for certain types of matching
1911        problem.
1913     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
1914        including restarting after a partial match.
1916     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
1917        defined when compiling for Windows was sent to me. I have put it into the
1918        code, though I have no means of testing or verifying it.
1920     7. Added the pcre_refcount() auxiliary function.
1922     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
1923        match before or at the first newline in the subject string. In pcretest,
1924        the /f option on a pattern can be used to set this.
1926     9. A repeated \w when used in UTF-8 mode with characters greater than 256
1927        would behave wrongly. This has been present in PCRE since release 4.0.
1929    10. A number of changes to the pcregrep command:
1931        (a) Refactored how -x works; insert ^(...)$ instead of setting
1932            PCRE_ANCHORED and checking the length, in preparation for adding
1933            something similar for -w.
1935        (b) Added the -w (match as a word) option.
1937        (c) Refactored the way lines are read and buffered so as to have more
1938            than one at a time available.
1940        (d) Implemented a pcregrep test script.
1942        (e) Added the -M (multiline match) option. This allows patterns to match
1943            over several lines of the subject. The buffering ensures that at least
1944            8K, or the rest of the document (whichever is the shorter) is available
1945            for matching (and similarly the previous 8K for lookbehind assertions).
1947        (f) Changed the --help output so that it now says
1949              -w, --word-regex(p)
1951            instead of two lines, one with "regex" and the other with "regexp"
1952            because that confused at least one person since the short forms are the
1953            same. (This required a bit of code, as the output is generated
1954            automatically from a table. It wasn't just a text change.)
1956        (g) -- can be used to terminate pcregrep options if the next thing isn't an
1957            option but starts with a hyphen. Could be a pattern or a path name
1958            starting with a hyphen, for instance.
1960        (h) "-" can be given as a file name to represent stdin.
1962        (i) When file names are being printed, "(standard input)" is used for
1963            the standard input, for compatibility with GNU grep. Previously
1964            "<stdin>" was used.
1966        (j) The option --label=xxx can be used to supply a name to be used for
1967            stdin when file names are being printed. There is no short form.
1969        (k) Re-factored the options decoding logic because we are going to add
1970            two more options that take data. Such options can now be given in four
1971            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
1973        (l) Added the -A, -B, and -C options for requesting that lines of context
1974            around matches be printed.
1976        (m) Added the -L option to print the names of files that do not contain
1977            any matching lines, that is, the complement of -l.
1979        (n) The return code is 2 if any file cannot be opened, but pcregrep does
1980            continue to scan other files.
1982        (o) The -s option was incorrectly implemented. For compatibility with other
1983            greps, it now suppresses the error message for a non-existent or non-
1984            accessible file (but not the return code). There is a new option called
1985            -q that suppresses the output of matching lines, which was what -s was
1986            previously doing.
1988        (p) Added --include and --exclude options to specify files for inclusion
1989            and exclusion when recursing.
1991    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
1992        Hopefully, it now does.
1994    12. Missing cast in pcre_study().
1996    13. Added an "uninstall" target to the makefile.
1998    14. Replaced "extern" in the function prototypes in Makefile.in with
1999        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
2000        world, but is set differently for Windows.
2002    15. Added a second compiling function called pcre_compile2(). The only
2003        difference is that it has an extra argument, which is a pointer to an
2004        integer error code. When there is a compile-time failure, this is set
2005        non-zero, in addition to the error test pointer being set to point to an
2006        error message. The new argument may be NULL if no error number is required
2007        (but then you may as well call pcre_compile(), which is now just a
2008        wrapper). This facility is provided because some applications need a
2009        numeric error indication, but it has also enabled me to tidy up the way
2010        compile-time errors are handled in the POSIX wrapper.
2012    16. Added VPATH=.libs to the makefile; this should help when building with one
2013        prefix path and installing with another. (Or so I'm told by someone who
2014        knows more about this stuff than I do.)
2016    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
2017        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
2018        match everything, including newlines. This is not POSIX-compatible, but
2019        somebody wanted the feature. From pcretest it can be activated by using
2020        both the P and the s flags.
2022    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
2024    19. libpcre.pc was being incorrectly installed as executable.
2026    20. A couple of places in pcretest check for end-of-line by looking for '\n';
2027        it now also looks for '\r' so that it will work unmodified on Windows.
2029    21. Added Google's contributed C++ wrapper to the distribution.
2031    22. Added some untidy missing memory free() calls in pcretest, to keep
2032        Electric Fence happy when testing.
2036    Version 5.0 13-Sep-04
2037    ---------------------
2039     1. Internal change: literal characters are no longer packed up into items
2040        containing multiple characters in a single byte-string. Each character
2041        is now matched using a separate opcode. However, there may be more than one
2042        byte in the character in UTF-8 mode.
2044     2. The pcre_callout_block structure has two new fields: pattern_position and
2045        next_item_length. These contain the offset in the pattern to the next match
2046        item, and its length, respectively.
2048     3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
2049        insertion of callouts before each pattern item. Added the /C option to
2050        pcretest to make use of this.
2052     4. On the advice of a Windows user, the lines
2054          #if defined(_WIN32) || defined(WIN32)
2055          _setmode( _fileno( stdout ), 0x8000 );
2056          #endif  /* defined(_WIN32) || defined(WIN32) */
2058        have been added to the source of pcretest. This apparently does useful
2059        magic in relation to line terminators.
2061     5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
2062        for the benefit of those environments where the "b" makes a difference.
2064     6. The icc compiler has the same options as gcc, but "configure" doesn't seem
2065        to know about it. I have put a hack into configure.in that adds in code
2066        to set GCC=yes if CC=icc. This seems to end up at a point in the
2067        generated configure script that is early enough to affect the setting of
2068        compiler options, which is what is needed, but I have no means of testing
2069        whether it really works. (The user who reported this had patched the
2070        generated configure script, which of course I cannot do.)
2072        LATER: After change 22 below (new libtool files), the configure script
2073        seems to know about icc (and also ecc). Therefore, I have commented out
2074        this hack in configure.in.
2076     7. Added support for pkg-config (2 patches were sent in).
2078     8. Negated POSIX character classes that used a combination of internal tables
2079        were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
2080        [[:^ascii]]. Typically, they would match almost any characters. The other
2081        POSIX classes were not broken in this way.
2083     9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
2084        to find the match, as PCRE was deluded into thinking that the match had to
2085        start at the start point or following a newline. The same bug applied to
2086        patterns with negative forward assertions or any backward assertions
2087        preceding ".*" at the start, unless the pattern required a fixed first
2088        character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
2090    10. In UTF-8 mode, when moving forwards in the subject after a failed match
2091        starting at the last subject character, bytes beyond the end of the subject
2092        string were read.
2094    11. Renamed the variable "class" as "classbits" to make life easier for C++
2095        users. (Previously there was a macro definition, but it apparently wasn't
2096        enough.)
2098    12. Added the new field "tables" to the extra data so that tables can be passed
2099        in at exec time, or the internal tables can be re-selected. This allows
2100        a compiled regex to be saved and re-used at a later time by a different
2101        program that might have everything at different addresses.
2103    13. Modified the pcre-config script so that, when run on Solaris, it shows a
2104        -R library as well as a -L library.
2106    14. The debugging options of pcretest (-d on the command line or D on a
2107        pattern) showed incorrect output for anything following an extended class
2108        that contained multibyte characters and which was followed by a quantifier.
2110    15. Added optional support for general category Unicode character properties
2111        via the \p, \P, and \X escapes. Unicode property support implies UTF-8
2112        support. It adds about 90K to the size of the library. The meanings of the
2113        inbuilt class escapes such as \d and \s have NOT been changed.
2115    16. Updated pcredemo.c to include calls to free() to release the memory for the
2116        compiled pattern.
2118    17. The generated file chartables.c was being created in the source directory
2119        instead of in the building directory. This caused the build to fail if the
2120        source directory was different from the building directory, and was
2121        read-only.
2123    18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
2124        file. No doubt somebody will tell me if they don't make sense... Also added
2125        Dan Mooney's comments about building on OpenVMS.
2127    19. Added support for partial matching via the PCRE_PARTIAL option for
2128        pcre_exec() and the \P data escape in pcretest.
2130    20. Extended pcretest with 3 new pattern features:
2132        (i)   A pattern option of the form ">rest-of-line" causes pcretest to
2133              write the compiled pattern to the file whose name is "rest-of-line".
2134              This is a straight binary dump of the data, with the saved pointer to
2135              the character tables forced to be NULL. The study data, if any, is
2136              written too. After writing, pcretest reads a new pattern.
2138        (ii)  If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
2139              compiled pattern from the given file. There must not be any
2140              occurrences of "<" in the file name (pretty unlikely); if there are,
2141              pcretest will instead treat the initial "<" as a pattern delimiter.
2142              After reading in the pattern, pcretest goes on to read data lines as
2143              usual.
2145        (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
2146              and 16-bit fields in a compiled pattern, to simulate a pattern that
2147              was compiled on a host of opposite endianness.
2149    21. The pcre-exec() function can now cope with patterns that were compiled on
2150        hosts of opposite endianness, with this restriction:
2152          As for any compiled expression that is saved and used later, the tables
2153          pointer field cannot be preserved; the extra_data field in the arguments
2154          to pcre_exec() should be used to pass in a tables address if a value
2155          other than the default internal tables were used at compile time.
2157    22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
2158        now diagnosed as an error. Previously, most of the time, a negative number
2159        would have been treated as zero, but if in addition "ovector" was passed as
2160        NULL, a crash could occur.
2162    23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
2163        new versions from the libtool 1.5 distribution (the last one is a copy of
2164        a file called libtool.m4). This seems to have fixed the need to patch
2165        "configure" to support Darwin 1.3 (which I used to do). However, I still
2166        had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
2167        workstation).
2169    24. Changed the PCRE licence to be the more standard "BSD" licence.
2172  Version 4.5 01-Dec-03  Version 4.5 01-Dec-03
2173  ---------------------  ---------------------

Removed from v.73  
changed lines
  Added in v.454

  ViewVC Help
Powered by ViewVC 1.1.5