ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 77 by nigel, Sat Feb 24 21:40:45 2007 UTC revision 427 by ph10, Fri Aug 28 09:55:54 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. Chaos could result.
48    9.  The restrictions on what a pattern can contain when partial matching is
49        requested for pcre_exec() have been removed. All patterns can now be
50        partially matched by this function. In addition, if there are at least two
51        slots in the offset vector, the offsets of the first-encountered partial
52        match are set in them when PCRE_ERROR_PARTIAL is returned.
54    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
55        synonymous with PCRE_PARTIAL, for backwards compatibility, and
56        PCRE_PARTIAL_HARD, which causes a longer partial match to supersede a
57        shorter full match, and may be more useful for multi-segment matching,
58        especially with pcre_exec().
61    Version 7.9 11-Apr-09
62    ---------------------
64    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
65        (pcretest), all targets were linked against these libraries. This included
66        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
67        libraries. This caused unwanted dependencies to be created. This problem
68        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
69        pcretest is linked with readline.
71    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
72        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
73        moved outside it again, because FALSE and TRUE are already defined in AIX,
74        but BOOL is not.
76    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
77        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
79    4.  The pcregrep documentation said spaces were inserted as well as colons (or
80        hyphens) following file names and line numbers when outputting matching
81        lines. This is not true; no spaces are inserted. I have also clarified the
82        wording for the --colour (or --color) option.
84    5.  In pcregrep, when --colour was used with -o, the list of matching strings
85        was not coloured; this is different to GNU grep, so I have changed it to be
86        the same.
88    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
89        each matching line was coloured. Now it goes on to look for further matches
90        of any of the test patterns, which is the same behaviour as GNU grep.
92    7.  A pattern that could match an empty string could cause pcregrep to loop; it
93        doesn't make sense to accept an empty string match in pcregrep, so I have
94        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
95        seems to be how GNU grep behaves.
97    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
98        start or after a newline", because the conditional assertion was not being
99        correctly handled. The rule now is that both the assertion and what follows
100        in the first alternative must satisfy the test.
102    9.  If auto-callout was enabled in a pattern with a conditional group whose
103        condition was an assertion, PCRE could crash during matching, both with
104        pcre_exec() and pcre_dfa_exec().
106    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
107        used for matching.
109    11. Unicode property support in character classes was not working for
110        characters (bytes) greater than 127 when not in UTF-8 mode.
112    12. Added the -M command line option to pcretest.
114    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
116    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
118    16. Added comments and documentation about mis-use of no_arg in the C++
119        wrapper.
121    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
122        from Martin Jerabek that uses macro names for all relevant character and
123        string constants.
125    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
126        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
127        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
128        these, but not everybody uses configure.
130    19. A conditional group that had only one branch was not being correctly
131        recognized as an item that could match an empty string. This meant that an
132        enclosing group might also not be so recognized, causing infinite looping
133        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
134        with the subject "ab", where knowledge that the repeated group can match
135        nothing is needed in order to break the loop.
137    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
138        exec(), but without supplying a callout function, matching went wrong.
140    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
141        leak if the size of the offset vector was greater than 30. When the vector
142        is smaller, the saved offsets during recursion go onto a local stack
143        vector, but for larger vectors malloc() is used. It was failing to free
144        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
145        error, in fact).
147    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
148        heapframe that is used only when UTF-8 support is enabled. This caused no
149        problem, but was untidy.
151    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
152        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
153        included within another project.
155    24. Steven Van Ingelgem's patches to add more options to the CMake support,
156        slightly modified by me:
158          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
159              not building pcregrep.
161          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
162              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
164    25. Forward references, both numeric and by name, in patterns that made use of
165        duplicate group numbers, could behave incorrectly or give incorrect errors,
166        because when scanning forward to find the reference group, PCRE was not
167        taking into account the duplicate group numbers. A pattern such as
168        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
170    26. Changed a few more instances of "const unsigned char *" to USPTR, making
171        the feature of a custom pointer more persuasive (as requested by a user).
173    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
174        pcretest.c, inside #ifndefs, because it seems they are sometimes already
175        pre-defined.
177    28. Added support for (*UTF8) at the start of a pattern.
179    29. Arrange for flags added by the "release type" setting in CMake to be shown
180        in the configuration summary.
183    Version 7.8 05-Sep-08
184    ---------------------
186    1.  Replaced UCP searching code with optimized version as implemented for Ad
187        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
188        stage table and inline lookup instead of a function, giving speed ups of 2
189        to 5 times on some simple patterns that I tested. Permission was given to
190        distribute the MultiStage2.py script that generates the tables (it's not in
191        the tarball, but is in the Subversion repository).
193    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
194        scripts.
196    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
197        a group with a zero qualifier. The result of the study could be incorrect,
198        or the function might crash, depending on the pattern.
200    4.  Caseless matching was not working for non-ASCII characters in back
201        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
202        It now works when Unicode Property Support is available.
204    5.  In pcretest, an escape such as \x{de} in the data was always generating
205        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
206        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
207        truncation.
209    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
211    7.  Added two (int) casts to pcregrep when printing the difference of two
212        pointers, in case they are 64-bit values.
214    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
215        test 2 if it fails.
217    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
218        and a #define of that name to empty if it is not externally set. This is to
219        allow users of MSVC to set it if necessary.
221    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
222        the convenience functions in the pcre_get.c source file.
224    11. An option change at the start of a pattern that had top-level alternatives
225        could cause overwriting and/or a crash. This command provoked a crash in
226        some environments:
228          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
230        This potential security problem was recorded as CVE-2008-2371.
232    12. For a pattern where the match had to start at the beginning or immediately
233        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
234        pcre_dfa_exec() could read past the end of the passed subject if there was
235        no match. To help with detecting such bugs (e.g. with valgrind), I modified
236        pcretest so that it places the subject at the end of its malloc-ed buffer.
238    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
239        exec() might read past the end of the data buffer in UTF-8 mode.
241    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
242        the data contained the byte 0x85 as part of a UTF-8 character within its
243        first line. This applied both to normal and DFA matching.
245    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
246        /^[^d]*?$/8 failed to match "abc".
248    16. Added a missing copyright notice to pcrecpp_internal.h.
250    17. Make it more clear in the documentation that values returned from
251        pcre_exec() in ovector are byte offsets, not character counts.
253    18. Tidied a few places to stop certain compilers from issuing warnings.
255    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
256        supplied by Stefan Weber. I made a further small update for 7.8 because
257        there is a change of source arrangements: the pcre_searchfuncs.c module is
258        replaced by pcre_ucd.c.
261    Version 7.7 07-May-08
262    ---------------------
264    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
265        a string to a long long, pretend we don't even have a long long." This is
266        done by checking for the strtoq, strtoll, and _strtoi64 functions.
268    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
269        pre-7.6 versions, which defined a global no_arg variable instead of putting
270        it in the RE class. (See also #8 below.)
272    3.  Remove a line of dead code, identified by coverity and reported by Nuno
273        Lopes.
275    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
277        (1) The include/exclude patterns were being applied to the whole pathnames
278            of files, instead of just to the final components.
280        (2) If there was more than one level of directory, the subdirectories were
281            skipped unless they satisfied the include/exclude conditions. This is
282            inconsistent with GNU grep (and could even be seen as contrary to the
283            pcregrep specification - which I improved to make it absolutely clear).
284            The action now is always to scan all levels of directory, and just
285            apply the include/exclude patterns to regular files.
287    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
288        --exclude_dir in the tests to avoid scanning .svn directories.
290    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
291        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
292        doesn't support NULs in patterns.
294    7.  Added some missing "const"s to declarations of static tables in
295        pcre_compile.c and pcre_dfa_exec.c.
297    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
298        caused by fix #2  above. (Subsequently also a second patch to fix the
299        first patch. And a third patch - this was a messy problem.)
301    9.  Applied Craig's patch to remove the use of push_back().
303    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
304        matching function regexec().
306    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
307        which, however, unlike Perl's \g{...}, are subroutine calls, not back
308        references. PCRE supports relative numbers with this syntax (I don't think
309        Oniguruma does).
311    12. Previously, a group with a zero repeat such as (...){0} was completely
312        omitted from the compiled regex. However, this means that if the group
313        was called as a subroutine from elsewhere in the pattern, things went wrong
314        (an internal error was given). Such groups are now left in the compiled
315        pattern, with a new opcode that causes them to be skipped at execution
316        time.
318    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
319        to the way PCRE behaves:
321        (a) A lone ] character is dis-allowed (Perl treats it as data).
323        (b) A back reference to an unmatched subpattern matches an empty string
324            (Perl fails the current match path).
326        (c) A data ] in a character class must be notated as \] because if the
327            first data character in a class is ], it defines an empty class. (In
328            Perl it is not possible to have an empty class.) The empty class []
329            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
330            The negative empty class [^] matches any one character, independently
331            of the DOTALL setting.
333    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
334        non-existent subpattern following a character class starting with ']' and
335        containing () gave an internal compiling error instead of "reference to
336        non-existent subpattern". Fortunately, when the pattern did exist, the
337        compiled code was correct. (When scanning forwards to check for the
338        existencd of the subpattern, it was treating the data ']' as terminating
339        the class, so got the count wrong. When actually compiling, the reference
340        was subsequently set up correctly.)
342    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
343        it was being rejected as not supported by pcre_dfa_exec(), even though
344        other assertions are supported. I have made pcre_dfa_exec() support
345        (*FAIL).
347    16. The implementation of 13c above involved the invention of a new opcode,
348        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
349        cannot be changed at match time, I realized I could make a small
350        improvement to matching performance by compiling OP_ALLANY instead of
351        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
352        on the OP_ANY path.
354    17. Compiling pcretest on Windows with readline support failed without the
355        following two fixes: (1) Make the unistd.h include conditional on
356        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
358    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
359        ncurses library to be included for pcretest when ReadLine support is
360        requested, but also to allow for it to be overridden. This patch came from
361        Daniel Bergström.
363    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
364        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
365        any errors with the current Unicode tables. Thanks to Peter Kankowski for
366        spotting this.
369    Version 7.6 28-Jan-08
370    ---------------------
372    1.  A character class containing a very large number of characters with
373        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
374        overflow.
376    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
377        HAVE_LONG_LONG is not defined.
379    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
380        bring them up to date and include new features. This patch includes:
382        - Fixed PH's badly added libz and libbz2 support.
383        - Fixed a problem with static linking.
384        - Added pcredemo. [But later removed - see 7 below.]
385        - Fixed dftables problem and added an option.
386        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
387            HAVE_LONG_LONG.
388        - Added readline support for pcretest.
389        - Added an listing of the option settings after cmake has run.
391    4.  A user submitted a patch to Makefile that makes it easy to create
392        "pcre.dll" under mingw when using Configure/Make. I added stuff to
393        Makefile.am that cause it to include this special target, without
394        affecting anything else. Note that the same mingw target plus all
395        the other distribution libraries and programs are now supported
396        when configuring with CMake (see 6 below) instead of with
397        Configure/Make.
399    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
400        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
401        exported in the Windows port". It has not yet been confirmed that the patch
402        solves the problem, but it does no harm.
404    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
405        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
406        with CMake, and also correct the comment about stack recursion.
408    7.  Remove the automatic building of pcredemo from the ./configure system and
409        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
410        of a program that users should build themselves after PCRE is installed, so
411        building it automatically is not really right. What is more, it gave
412        trouble in some build environments.
414    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
417    Version 7.5 10-Jan-08
418    ---------------------
420    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
421        values in parens when parsing an RE using the C++ wrapper."
423    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
424        Characters greater than 255 were excluded from the class instead of being
425        included.
427    3.  The same bug as (2) above applied to negated POSIX classes such as
428        [:^space:].
430    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
431        defined or documented. It seems to have been a typo for PCRE_STATIC, so
432        I have changed it.
434    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
435        first named subpattern) and a construct such as (?&a) would reference the
436        first named subpattern whose name started with "a" (in other words, the
437        length check was missing). Both these problems are fixed. "Subpattern name
438        expected" is now given for (?&) (a zero-length name), and this patch also
439        makes it give the same error for \k'' (previously it complained that that
440        was a reference to a non-existent subpattern).
442    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
443        this is right because (?- can be followed by option settings as well as by
444        digits. I have, however, made the messages clearer.
446    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
447        than the number used in the conditional) now cause a compile-time error.
448        This is actually not compatible with Perl, which accepts such patterns, but
449        treats the conditional as always being FALSE (as PCRE used to), but it
450        seems to me that giving a diagnostic is better.
452    8.  Change "alphameric" to the more common word "alphanumeric" in comments
453        and messages.
455    9.  Fix two occurrences of "backslash" in comments that should have been
456        "backspace".
458    10. Remove two redundant lines of code that can never be obeyed (their function
459        was moved elsewhere).
461    11. The program that makes PCRE's Unicode character property table had a bug
462        which caused it to generate incorrect table entries for sequences of
463        characters that have the same character type, but are in different scripts.
464        It amalgamated them into a single range, with the script of the first of
465        them. In other words, some characters were in the wrong script. There were
466        thirteen such cases, affecting characters in the following ranges:
468          U+002b0 - U+002c1
469          U+0060c - U+0060d
470          U+0061e - U+00612
471          U+0064b - U+0065e
472          U+0074d - U+0076d
473          U+01800 - U+01805
474          U+01d00 - U+01d77
475          U+01d9b - U+01dbf
476          U+0200b - U+0200f
477          U+030fc - U+030fe
478          U+03260 - U+0327f
479          U+0fb46 - U+0fbb1
480          U+10450 - U+1049d
482    12. The -o option (show only the matching part of a line) for pcregrep was not
483        compatible with GNU grep in that, if there was more than one match in a
484        line, it showed only the first of them. It now behaves in the same way as
485        GNU grep.
487    13. If the -o and -v options were combined for pcregrep, it printed a blank
488        line for every non-matching line. GNU grep prints nothing, and pcregrep now
489        does the same. The return code can be used to tell if there were any
490        non-matching lines.
492    14. Added --file-offsets and --line-offsets to pcregrep.
494    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
495        infinitely looping recursion. The bug was that positive lookaheads were not
496        being skipped when checking for a possible empty match (negative lookaheads
497        and both kinds of lookbehind were skipped).
499    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
500        inclusion of <windows.h> to before rather than after the definition of
501        INVALID_FILE_ATTRIBUTES (patch from David Byron).
503    17. Specifying a possessive quantifier with a specific limit for a Unicode
504        character property caused pcre_compile() to compile bad code, which led at
505        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
506        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
507        caused the error; without that there was no problem.
509    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
511    19. Added --enable-pcretest-libreadline.
513    20. In pcrecpp.cc, the variable 'count' was incremented twice in
514        RE::GlobalReplace(). As a result, the number of replacements returned was
515        double what it should be. I removed one of the increments, but Craig sent a
516        later patch that removed the other one (the right fix) and added unit tests
517        that check the return values (which was not done before).
519    21. Several CMake things:
521        (1) Arranged that, when cmake is used on Unix, the libraries end up with
522            the names libpcre and libpcreposix, not just pcre and pcreposix.
524        (2) The above change means that pcretest and pcregrep are now correctly
525            linked with the newly-built libraries, not previously installed ones.
529    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
530        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
531        UTF-8 newline character). The key issue is that the pattern starts .*;
532        this means that the match must be either at the beginning, or after a
533        newline. The bug was in the code for advancing after a failed match and
534        checking that the new position followed a newline. It was not taking
535        account of UTF-8 characters correctly.
537    23. PCRE was behaving differently from Perl in the way it recognized POSIX
538        character classes. PCRE was not treating the sequence [:...:] as a
539        character class unless the ... were all letters. Perl, however, seems to
540        allow any characters between [: and :], though of course it rejects as
541        unknown any "names" that contain non-letters, because all the known class
542        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
543        for example, whereas PCRE did not - it did not recognize a POSIX character
544        class. This seemed a bit dangerous, so the code has been changed to be
545        closer to Perl. The behaviour is not identical to Perl, because PCRE will
546        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
547        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
548        Perl does, and where it didn't before.
550    24. Rewrite so as to remove the single use of %n from pcregrep because in some
551        Windows environments %n is disabled by default.
554    Version 7.4 21-Sep-07
555    ---------------------
557    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
558        means that a class such as [\s] counted as "explicit reference to CR or
559        LF". That isn't really right - the whole point of the change was to try to
560        help when there was an actual mention of one of the two characters. So now
561        the change happens only if \r or \n (or a literal CR or LF) character is
562        encountered.
564    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
565        of both had grown to the point where there were only 3 bits left.
566        Fortunately, there was spare space in the data structure, and so I have
567        moved the internal flags into a new 16-bit field to free up more option
568        bits.
570    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
571        but did not set the internal JCHANGED flag - either of these is enough to
572        control the way the "get" function works - but the PCRE_INFO_JCHANGED
573        facility is supposed to tell if (?J) was ever used, so now (?J) at the
574        start sets both bits.
576    4.  Added options (at build time, compile time, exec time) to change \R from
577        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
579    5.  doc/pcresyntax.html was missing from the distribution.
581    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
582        compatibility, even though it is no longer used.
584    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
585        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
586        windows.h file is present (where different names are used). [This was
587        reversed later after testing - see 16 below.]
589    8.  Changed all #include <config.h> to #include "config.h". There were also
590        some further <pcre.h> cases that I changed to "pcre.h".
592    9.  When pcregrep was used with the --colour option, it missed the line ending
593        sequence off the lines that it output.
595    10. It was pointed out to me that arrays of string pointers cause lots of
596        relocations when a shared library is dynamically loaded. A technique of
597        using a single long string with a table of offsets can drastically reduce
598        these. I have refactored PCRE in four places to do this. The result is
599        dramatic:
601          Originally:                          290
602          After changing UCP table:            187
603          After changing error message table:   43
604          After changing table of "verbs"       36
605          After changing table of Posix names   22
607        Thanks to the folks working on Gregex for glib for this insight.
609    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
610        unicode-properties was also set.
612    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
614    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
615        checked only for CRLF.
617    14. Added casts to pcretest.c to avoid compiler warnings.
619    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
621    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
622        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
623        entirely. This removes changes made in 7 above.
625    17. The CMake files have been updated, and there is now more information about
626        building with CMake in the NON-UNIX-USE document.
629    Version 7.3 28-Aug-07
630    ---------------------
632     1. In the rejigging of the build system that eventually resulted in 7.1, the
633        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
634        brackets there is not right, since it causes compilers to look for an
635        installed pcre.h, not the version that is in the source that is being
636        compiled (which of course may be different). I have changed it back to:
638          #include "pcre.h"
640        I have a vague recollection that the change was concerned with compiling in
641        different directories, but in the new build system, that is taken care of
642        by the VPATH setting the Makefile.
644     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
645        when the subject happened to end in the byte 0x85 (e.g. if the last
646        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
647        characters but of course it shouldn't be taken as a newline when it is part
648        of another character. The bug was that, for an unlimited repeat of . in
649        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
650        characters when looking for a newline.
652     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
654     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
655        in debug output.
657     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
658        long printing in the pcrecpp unittest when running under MinGW.
660     6. ESC_K was left out of the EBCDIC table.
662     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
663        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
664        limit also applies to "virtual nesting" when a pattern is recursive, and in
665        this case 1000 isn't so big. I have been able to remove this limit at the
666        expense of backing off one optimization in certain circumstances. Normally,
667        when pcre_exec() would call its internal match() function recursively and
668        immediately return the result unconditionally, it uses a "tail recursion"
669        feature to save stack. However, when a subpattern that can match an empty
670        string has an unlimited repetition quantifier, it no longer makes this
671        optimization. That gives it a stack frame in which to save the data for
672        checking that an empty string has been matched. Previously this was taken
673        from the 1000-entry workspace that had been reserved. So now there is no
674        explicit limit, but more stack is used.
676     8. Applied Daniel's patches to solve problems with the import/export magic
677        syntax that is required for Windows, and which was going wrong for the
678        pcreposix and pcrecpp parts of the library. These were overlooked when this
679        problem was solved for the main library.
681     9. There were some crude static tests to avoid integer overflow when computing
682        the size of patterns that contain repeated groups with explicit upper
683        limits. As the maximum quantifier is 65535, the maximum group length was
684        set at 30,000 so that the product of these two numbers did not overflow a
685        32-bit integer. However, it turns out that people want to use groups that
686        are longer than 30,000 bytes (though not repeat them that many times).
687        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
688        made it possible to implement the integer overflow checks in a much more
689        dynamic way, which I have now done. The artificial limitation on group
690        length has been removed - we now have only the limit on the total length of
691        the compiled pattern, which depends on the LINK_SIZE setting.
693    10. Fixed a bug in the documentation for get/copy named substring when
694        duplicate names are permitted. If none of the named substrings are set, the
695        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
696        empty string.
698    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
699        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
700        because the ] is interpreted as the first data character and the
701        terminating ] is not found. PCRE has been made compatible with Perl in this
702        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
703        cause memory overwriting.
705    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
706        string has been matched (to stop an infinite loop). It was not recognizing
707        a conditional subpattern that could match an empty string if that
708        subpattern was within another subpattern. For example, it looped when
709        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
710        condition was not nested. This bug has been fixed.
712    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
713        past the start of the subject in the presence of bytes with the top bit
714        set, for example "\x8aBCD".
716    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
717        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
719    14. Optimized (?!) to (*FAIL).
721    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
722        This restricts code points to be within the range 0 to 0x10FFFF, excluding
723        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
724        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
725        does: it's just the validity check that is more restrictive.
727    16. Inserted checks for integer overflows during escape sequence (backslash)
728        processing, and also fixed erroneous offset values for syntax errors during
729        backslash processing.
731    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
732        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
734    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
735        caused an overrun.
737    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
738        something other than just ASCII characters) inside a group that had an
739        unlimited repeat caused a loop at compile time (while checking to see
740        whether the group could match an empty string).
742    20. Debugging a pattern containing \p or \P could cause a crash. For example,
743        [\P{Any}] did so. (Error in the code for printing property names.)
745    21. An orphan \E inside a character class could cause a crash.
747    22. A repeated capturing bracket such as (A)? could cause a wild memory
748        reference during compilation.
750    23. There are several functions in pcre_compile() that scan along a compiled
751        expression for various reasons (e.g. to see if it's fixed length for look
752        behind). There were bugs in these functions when a repeated \p or \P was
753        present in the pattern. These operators have additional parameters compared
754        with \d, etc, and these were not being taken into account when moving along
755        the compiled data. Specifically:
757        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
758            length.
760        (b) An item such as \pL+ within a repeated group could cause crashes or
761            loops.
763        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
764            "reference to non-existent subpattern" error.
766        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
768    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
769        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
771    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
773    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
774        character were causing crashes (broken optimization).
776    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
777        \p or \P) caused a compile-time loop.
779    28. More problems have arisen in unanchored patterns when CRLF is a valid line
780        break. For example, the unstudied pattern [\r\n]A does not match the string
781        "\r\nA" because change 7.0/46 below moves the current point on by two
782        characters after failing to match at the start. However, the pattern \nA
783        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
784        the same is true. There doesn't seem any very clean way out of this, but
785        what I have chosen to do makes the common cases work: PCRE now takes note
786        of whether there can be an explicit match for \r or \n anywhere in the
787        pattern, and if so, 7.0/46 no longer applies. As part of this change,
788        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
789        pattern has explicit CR or LF references.
791    29. Added (*CR) etc for changing newline setting at start of pattern.
794    Version 7.2 19-Jun-07
795    ---------------------
797     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
798        which is apparently normally available under Windows.
800     2. Re-jig the pcregrep tests with different newline settings in an attempt
801        to make them independent of the local environment's newline setting.
803     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
805     4. Some of the "internals" tests were previously cut out when the link size
806        was not 2, because the output contained actual offsets. The recent new
807        "Z" feature of pcretest means that these can be cut out, making the tests
808        usable with all link sizes.
810     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
811        stack recursion. This gives a massive performance boost under BSD, but just
812        a small improvement under Linux. However, it saves one field in the frame
813        in all cases.
815     6. Added more features from the forthcoming Perl 5.10:
817        (a) (?-n) (where n is a string of digits) is a relative subroutine or
818            recursion call. It refers to the nth most recently opened parentheses.
820        (b) (?+n) is also a relative subroutine call; it refers to the nth next
821            to be opened parentheses.
823        (c) Conditions that refer to capturing parentheses can be specified
824            relatively, for example, (?(-2)... or (?(+3)...
826        (d) \K resets the start of the current match so that everything before
827            is not part of it.
829        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
831        (f) \g{name} is another synonym - part of Perl 5.10's unification of
832            reference syntax.
834        (g) (?| introduces a group in which the numbering of parentheses in each
835            alternative starts with the same number.
837        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
839     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
842     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
843        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
844        for detecting groups that can match an empty string.
846     9. A pattern with a very large number of alternatives (more than several
847        hundred) was running out of internal workspace during the pre-compile
848        phase, where pcre_compile() figures out how much memory will be needed. A
849        bit of new cunning has reduced the workspace needed for groups with
850        alternatives. The 1000-alternative test pattern now uses 12 bytes of
851        workspace instead of running out of the 4096 that are available.
853    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
855    11. Applied patch from Google to remove an optimization that didn't quite work.
856        The report of the bug said:
858          pcrecpp::RE("a*").FullMatch("aaa") matches, while
859          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
860          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
862    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
863        it matched the wrong number of bytes.
866    Version 7.1 24-Apr-07
867    ---------------------
869     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
870        that is more "standard", making use of automake and other Autotools. There
871        is some re-arrangement of the files and adjustment of comments consequent
872        on this.
874     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
875        for recursive directory scanning broke on some systems because the files
876        are not scanned in any specific order and on different systems the order
877        was different. A call to "sort" has been inserted into RunGrepTest for the
878        approprate test as a short-term fix. In the longer term there may be an
879        alternative.
881     3. I had an email from Eric Raymond about problems translating some of PCRE's
882        man pages to HTML (despite the fact that I distribute HTML pages, some
883        people do their own conversions for various reasons). The problems
884        concerned the use of low-level troff macros .br and .in. I have therefore
885        removed all such uses from the man pages (some were redundant, some could
886        be replaced by .nf/.fi pairs). The 132html script that I use to generate
887        HTML has been updated to handle .nf/.fi and to complain if it encounters
888        .br or .in.
890     4. Updated comments in configure.ac that get placed in config.h.in and also
891        arranged for config.h to be included in the distribution, with the name
892        config.h.generic, for the benefit of those who have to compile without
893        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
895     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
896        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
897        makevp.bat for the current PCRE, using the additional files
898        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
900     6. A Windows user reported a minor discrepancy with test 2, which turned out
901        to be caused by a trailing space on an input line that had got lost in his
902        copy. The trailing space was an accident, so I've just removed it.
904     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
905        that is needed.
907     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
908        as "const" (a) because they are and (b) because it helps the PHP
909        maintainers who have recently made a script to detect big data structures
910        in the php code that should be moved to the .rodata section. I remembered
911        to update Builducptable as well, so it won't revert if ucptable.h is ever
912        re-created.
914     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
915        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
916        order to be able to cut out the UTF-8 tables in the latter when UTF-8
917        support is not required. This saves 1.5-2K of code, which is important in
918        some applications.
920        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
921        so as not to refer to the tables, even though these functions will never be
922        called when UTF-8 support is disabled. Otherwise there are problems with a
923        shared library.
925    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
927        (a) It was defining its arguments as char * instead of void *.
929        (b) It was assuming that all moves were upwards in memory; this was true
930            a long time ago when I wrote it, but is no longer the case.
932        The emulated memove() is provided for those environments that have neither
933        memmove() nor bcopy(). I didn't think anyone used it these days, but that
934        is clearly not the case, as these two bugs were recently reported.
936    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
937        and Detrail to create the HTML documentation, the .txt form of the man
938        pages, and it removes trailing spaces from listed files. It also creates
939        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
940        case, it wraps all the #defines with #ifndefs. This script should be run
941        before "make dist".
943    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
944        with Unicode property support.
946        (a) For a maximizing quantifier, if the two different cases of the
947            character were of different lengths in their UTF-8 codings (there are
948            some cases like this - I found 11), and the matching function had to
949            back up over a mixture of the two cases, it incorrectly assumed they
950            were both the same length.
952        (b) When PCRE was configured to use the heap rather than the stack for
953            recursion during matching, it was not correctly preserving the data for
954            the other case of a UTF-8 character when checking ahead for a match
955            while processing a minimizing repeat. If the check also involved
956            matching a wide character, but failed, corruption could cause an
957            erroneous result when trying to check for a repeat of the original
958            character.
960    13. Some tidying changes to the testing mechanism:
962        (a) The RunTest script now detects the internal link size and whether there
963            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
964            values substituted by "configure". (The RunGrepTest script already did
965            this for UTF-8.) The configure.ac script no longer substitutes the
966            relevant variables.
968        (b) The debugging options /B and /D in pcretest show the compiled bytecode
969            with length and offset values. This means that the output is different
970            for different internal link sizes. Test 2 is skipped for link sizes
971            other than 2 because of this, bypassing the problem. Unfortunately,
972            there was also a test in test 3 (the locale tests) that used /B and
973            failed for link sizes other than 2. Rather than cut the whole test out,
974            I have added a new /Z option to pcretest that replaces the length and
975            offset values with spaces. This is now used to make test 3 independent
976            of link size. (Test 2 will be tidied up later.)
978    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
979        segmentation fault instead of returning the appropriate error message.
981    15. In multiline mode when the newline sequence was set to "any", the pattern
982        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
983        This doesn't seem right; it now treats the CRLF combination as the line
984        ending, and so does not match in that case. It's only a pattern such as ^$
985        that would hit this one: something like ^ABC$ would have failed after \r
986        and then tried again after \r\n.
988    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
989        in an attempt to make files that differ only in their line terminators
990        compare equal. This works on Linux.
992    17. Under certain error circumstances pcregrep might try to free random memory
993        as it exited. This is now fixed, thanks to valgrind.
995    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
996        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
997        was because its rules for how to advance for /g after matching an empty
998        string at the end of a line did not allow for this case. They now check for
999        it specially.
1001    20. pcretest is supposed to handle patterns and data of any length, by
1002        extending its buffers when necessary. It was getting this wrong when the
1003        buffer for a data line had to be extended.
1005    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1006        CRLF as a newline sequence.
1008    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1009        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1010        I have nevertheless tidied it up.
1012    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1014    24. Added a man page for pcre-config.
1017    Version 7.0 19-Dec-06
1018    ---------------------
1020     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
1021        moving to gcc 4.1.1.
1023     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
1024        sys/time.h, which is documented as needed for this function. It doesn't
1025        seem to matter on Linux, but it showed up on some releases of OS X.
1027     3. It seems that there are systems where bytes whose values are greater than
1028        127 match isprint() in the "C" locale. The "C" locale should be the
1029        default when a C program starts up. In most systems, only ASCII printing
1030        characters match isprint(). This difference caused the output from pcretest
1031        to vary, making some of the tests fail. I have changed pcretest so that:
1033        (a) When it is outputting text in the compiled version of a pattern, bytes
1034            other than 32-126 are always shown as hex escapes.
1036        (b) When it is outputting text that is a matched part of a subject string,
1037            it does the same, unless a different locale has been set for the match
1038            (using the /L modifier). In this case, it uses isprint() to decide.
1040     4. Fixed a major bug that caused incorrect computation of the amount of memory
1041        required for a compiled pattern when options that changed within the
1042        pattern affected the logic of the preliminary scan that determines the
1043        length. The relevant options are -x, and -i in UTF-8 mode. The result was
1044        that the computed length was too small. The symptoms of this bug were
1045        either the PCRE error "internal error: code overflow" from pcre_compile(),
1046        or a glibc crash with a message such as "pcretest: free(): invalid next
1047        size (fast)". Examples of patterns that provoked this bug (shown in
1048        pcretest format) are:
1050          /(?-x: )/x
1051          /(?x)(?-x: \s*#\s*)/
1052          /((?i)[\x{c0}])/8
1053          /(?i:[\x{c0}])/8
1055        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
1056        is now done differently.
1058     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
1059        wrapper classes; (b) implement a new function in the C++ scanner that is
1060        more efficient than the old way of doing things because it avoids levels of
1061        recursion in the regex matching; (c) add a paragraph to the documentation
1062        for the FullMatch() function.
1064     6. The escape sequence \n was being treated as whatever was defined as
1065        "newline". Not only was this contrary to the documentation, which states
1066        that \n is character 10 (hex 0A), but it also went horribly wrong when
1067        "newline" was defined as CRLF. This has been fixed.
1069     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
1070        was being set to -1 for the "end of line" case (supposedly a value that no
1071        character can have). Though this value is never used (the check for end of
1072        line is "zero bytes in current character"), it caused compiler complaints.
1073        I've changed it to 0xffffffff.
1075     8. In pcre_version.c, the version string was being built by a sequence of
1076        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
1077        string (as it is for production releases) called a macro with an empty
1078        argument. The C standard says the result of this is undefined. The gcc
1079        compiler treats it as an empty string (which was what was wanted) but it is
1080        reported that Visual C gives an error. The source has been hacked around to
1081        avoid this problem.
1083     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
1084        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
1085        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
1086        of them did).
1088    10. Originally, pcretest opened its input and output without "b"; then I was
1089        told that "b" was needed in some environments, so it was added for release
1090        5.0 to both the input and output. (It makes no difference on Unix-like
1091        systems.) Later I was told that it is wrong for the input on Windows. I've
1092        now abstracted the modes into two macros, to make it easier to fiddle with
1093        them, and removed "b" from the input mode under Windows.
1095    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
1097    12. Added -help and --help to pcretest as an official way of being reminded
1098        of the options.
1100    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
1101        and pcrecpp.cc because they annoy compilers at high warning levels.
1103    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
1105    15. Fixed an occurrence of == in configure.ac that should have been = (shell
1106        scripts are not C programs :-) and which was not noticed because it works
1107        on Linux.
1109    16. pcretest is supposed to handle any length of pattern and data line (as one
1110        line or as a continued sequence of lines) by extending its input buffer if
1111        necessary. This feature was broken for very long pattern lines, leading to
1112        a string of junk being passed to pcre_compile() if the pattern was longer
1113        than about 50K.
1115    17. I have done a major re-factoring of the way pcre_compile() computes the
1116        amount of memory needed for a compiled pattern. Previously, there was code
1117        that made a preliminary scan of the pattern in order to do this. That was
1118        OK when PCRE was new, but as the facilities have expanded, it has become
1119        harder and harder to keep it in step with the real compile phase, and there
1120        have been a number of bugs (see for example, 4 above). I have now found a
1121        cunning way of running the real compile function in a "fake" mode that
1122        enables it to compute how much memory it would need, while actually only
1123        ever using a few hundred bytes of working memory and without too many
1124        tests of the mode. This should make future maintenance and development
1125        easier. A side effect of this work is that the limit of 200 on the nesting
1126        depth of parentheses has been removed (though this was never a serious
1127        limitation, I suspect). However, there is a downside: pcre_compile() now
1128        runs more slowly than before (30% or more, depending on the pattern). I
1129        hope this isn't a big issue. There is no effect on runtime performance.
1131    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
1132        newline (only possible for the last line of a file) and it was a
1133        pattern that set a locale (followed by /Lsomething), pcretest crashed.
1135    19. Added additional timing features to pcretest. (1) The -tm option now times
1136        matching only, not compiling. (2) Both -t and -tm can be followed, as a
1137        separate command line item, by a number that specifies the number of
1138        repeats to use when timing. The default is 50000; this gives better
1139        precision, but takes uncomfortably long for very large patterns.
1141    20. Extended pcre_study() to be more clever in cases where a branch of a
1142        subpattern has no definite first character. For example, (a*|b*)[cd] would
1143        previously give no result from pcre_study(). Now it recognizes that the
1144        first character must be a, b, c, or d.
1146    21. There was an incorrect error "recursive call could loop indefinitely" if
1147        a subpattern (or the entire pattern) that was being tested for matching an
1148        empty string contained only one non-empty item after a nested subpattern.
1149        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
1150        incorrectly, because the \d was being skipped in the check.
1152    22. The pcretest program now has a new pattern option /B and a command line
1153        option -b, which is equivalent to adding /B to every pattern. This causes
1154        it to show the compiled bytecode, without the additional information that
1155        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
1156        is the same as /B/I).
1158    23. A new optimization is now able automatically to treat some sequences such
1159        as a*b as a*+b. More specifically, if something simple (such as a character
1160        or a simple class like \d) has an unlimited quantifier, and is followed by
1161        something that cannot possibly match the quantified thing, the quantifier
1162        is automatically "possessified".
1164    24. A recursive reference to a subpattern whose number was greater than 39
1165        went wrong under certain circumstances in UTF-8 mode. This bug could also
1166        have affected the operation of pcre_study().
1168    25. Realized that a little bit of performance could be had by replacing
1169        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
1171    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
1173    27. Possessive quantifiers such as a++ were previously implemented by turning
1174        them into atomic groups such as ($>a+). Now they have their own opcodes,
1175        which improves performance. This includes the automatically created ones
1176        from 23 above.
1178    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
1179        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
1180        the first matched character to be a colon. This applied both to named and
1181        numbered groups.
1183    29. The ucpinternal.h header file was missing its idempotency #ifdef.
1185    30. I was sent a "project" file called libpcre.a.dev which I understand makes
1186        building PCRE on Windows easier, so I have included it in the distribution.
1188    31. There is now a check in pcretest against a ridiculously large number being
1189        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
1190        loop, the loop is abandoned.
1192    32. Forward references to subpatterns in conditions such as (?(2)...) where
1193        subpattern 2 is defined later cause pcre_compile() to search forwards in
1194        the pattern for the relevant set of parentheses. This search went wrong
1195        when there were unescaped parentheses in a character class, parentheses
1196        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
1198    33. "Subroutine" calls and backreferences were previously restricted to
1199        referencing subpatterns earlier in the regex. This restriction has now
1200        been removed.
1202    34. Added a number of extra features that are going to be in Perl 5.10. On the
1203        whole, these are just syntactic alternatives for features that PCRE had
1204        previously implemented using the Python syntax or my own invention. The
1205        other formats are all retained for compatibility.
1207        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
1208            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
1209            also .NET compatible.
1211        (b) A recursion or subroutine call to a named group can now be defined as
1212            (?&name) as well as (?P>name).
1214        (c) A backreference to a named group can now be defined as \k<name> or
1215            \k'name' as well as (?P=name). The new forms, as well as being in Perl
1216            5.10, are also .NET compatible.
1218        (d) A conditional reference to a named group can now use the syntax
1219            (?(<name>) or (?('name') as well as (?(name).
1221        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
1222            groups (named and numbered) that are never evaluated inline, but can be
1223            called as "subroutines" from elsewhere. In effect, the DEFINE condition
1224            is always false. There may be only one alternative in such a group.
1226        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
1227            as the simple (?(R). The condition is true only if the most recent
1228            recursion is that of the given number or name. It does not search out
1229            through the entire recursion stack.
1231        (g) The escape \gN or \g{N} has been added, where N is a positive or
1232            negative number, specifying an absolute or relative reference.
1234    35. Tidied to get rid of some further signed/unsigned compiler warnings and
1235        some "unreachable code" warnings.
1237    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
1238        things, this adds five new scripts.
1240    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
1241        There were also incompatibilities regarding the handling of \Q..\E inside
1242        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
1243        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
1245    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
1246        matches an empty string, and forcibly breaks the loop. There were bugs in
1247        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
1248        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
1249        separate and independent bugs (that affected different cases) have been
1250        fixed.
1252    39. Refactored the code to abolish the use of different opcodes for small
1253        capturing bracket numbers. This is a tidy that I avoided doing when I
1254        removed the limit on the number of capturing brackets for 3.5 back in 2001.
1255        The new approach is not only tidier, it makes it possible to reduce the
1256        memory needed to fix the previous bug (38).
1258    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
1259        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
1260        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
1261        mode.
1263    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
1264        report.
1266    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
1267        copy construction and assignment in the C++ wrapper.
1269    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
1270        couple of bugs that could have given wrong results in the "--newline=crlf"
1271        case.
1273    44. Added a number of casts and did some reorganization of signed/unsigned int
1274        variables following suggestions from Dair Grant. Also renamed the variable
1275        "this" as "item" because it is a C++ keyword.
1277    45. Arranged for dftables to add
1279          #include "pcre_internal.h"
1281        to pcre_chartables.c because without it, gcc 4.x may remove the array
1282        definition from the final binary if PCRE is built into a static library and
1283        dead code stripping is activated.
1285    46. For an unanchored pattern, if a match attempt fails at the start of a
1286        newline sequence, and the newline setting is CRLF or ANY, and the next two
1287        characters are CRLF, advance by two characters instead of one.
1290    Version 6.7 04-Jul-06
1291    ---------------------
1293     1. In order to handle tests when input lines are enormously long, pcretest has
1294        been re-factored so that it automatically extends its buffers when
1295        necessary. The code is crude, but this _is_ just a test program. The
1296        default size has been increased from 32K to 50K.
1298     2. The code in pcre_study() was using the value of the re argument before
1299        testing it for NULL. (Of course, in any sensible call of the function, it
1300        won't be NULL.)
1302     3. The memmove() emulation function in pcre_internal.h, which is used on
1303        systems that lack both memmove() and bcopy() - that is, hardly ever -
1304        was missing a "static" storage class specifier.
1306     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
1307        containing an extended class (one that cannot be represented by a bitmap
1308        because it contains high-valued characters or Unicode property items, e.g.
1309        [\pZ]). Almost always one would set UTF-8 mode when processing such a
1310        pattern, but PCRE should not loop if you do not (it no longer does).
1311        [Detail: two cases were found: (a) a repeated subpattern containing an
1312        extended class; (b) a recursive reference to a subpattern that followed a
1313        previous extended class. It wasn't skipping over the extended class
1314        correctly when UTF-8 mode was not set.]
1316     5. A negated single-character class was not being recognized as fixed-length
1317        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
1318        compile error "lookbehind assertion is not fixed length".
1320     6. The RunPerlTest auxiliary script was showing an unexpected difference
1321        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
1322        write a Perl script that can interpret lines of an input file either as
1323        byte characters or as UTF-8, which is what "perltest" was being required to
1324        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
1325        can't do is switch easily at run time between having the "use utf8;" pragma
1326        or not. In the end, I fudged it by using the RunPerlTest script to insert
1327        "use utf8;" explicitly for the UTF-8 tests.
1329     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
1330        the end of the subject string, contrary to the documentation and to what
1331        Perl does. This was true of both matching functions. Now it matches only at
1332        the start of the subject and immediately after *internal* newlines.
1334     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
1335        a pointer to an int instead of a pointer to an unsigned long int. This
1336        caused problems on 64-bit systems.
1338     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
1339        instance of the 'standard' template library not being so standard".
1341    10. There was no check on the number of named subpatterns nor the maximum
1342        length of a subpattern name. The product of these values is used to compute
1343        the size of the memory block for a compiled pattern. By supplying a very
1344        long subpattern name and a large number of named subpatterns, the size
1345        computation could be caused to overflow. This is now prevented by limiting
1346        the length of names to 32 characters, and the number of named subpatterns
1347        to 10,000.
1349    11. Subpatterns that are repeated with specific counts have to be replicated in
1350        the compiled pattern. The size of memory for this was computed from the
1351        length of the subpattern and the repeat count. The latter is limited to
1352        65535, but there was no limit on the former, meaning that integer overflow
1353        could in principle occur. The compiled length of a repeated subpattern is
1354        now limited to 30,000 bytes in order to prevent this.
1356    12. Added the optional facility to have named substrings with the same name.
1358    13. Added the ability to use a named substring as a condition, using the
1359        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
1360        are numbers (not recommended). Forward references are permitted.
1362    14. Added forward references in named backreferences (if you see what I mean).
1364    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
1365        pattern could run off the end of the subject. For example, the pattern
1366        "(?s)(.{1,5})"8 did this with the subject "ab".
1368    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
1369        PCRE_CASELESS was set when matching characters that were quantified with ?
1370        or *.
1372    17. A character class other than a single negated character that had a minimum
1373        but no maximum quantifier - for example [ab]{6,} - was not handled
1374        correctly by pce_dfa_exec(). It would match only one character.
1376    18. A valid (though odd) pattern that looked like a POSIX character
1377        class but used an invalid character after [ (for example [[,abc,]]) caused
1378        pcre_compile() to give the error "Failed: internal error: code overflow" or
1379        in some cases to crash with a glibc free() error. This could even happen if
1380        the pattern terminated after [[ but there just happened to be a sequence of
1381        letters, a binary zero, and a closing ] in the memory that followed.
1383    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
1384        over the years. Originally (before any Unicode support), just the bottom 8
1385        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
1386        output from "man perlunicode" includes this:
1388          The regular expression compiler produces polymorphic opcodes.  That
1389          is, the pattern adapts to the data and automatically switches to
1390          the Unicode character scheme when presented with Unicode data--or
1391          instead uses a traditional byte scheme when presented with byte
1392          data.
1394        Sadly, a wide octal escape does not cause a switch, and in a string with
1395        no other multibyte characters, these octal escapes are treated as before.
1396        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
1397        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
1398        Unicode string.
1400        I have not perpetrated such confusion in PCRE. Up till now, it took just
1401        the bottom 8 bits, as in old Perl. I have now made octal escapes with
1402        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
1403        translate to the appropriate multibyte character.
1405    29. Applied some refactoring to reduce the number of warnings from Microsoft
1406        and Borland compilers. This has included removing the fudge introduced
1407        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
1408        a warning about an unused variable.
1410    21. PCRE has not included VT (character 0x0b) in the set of whitespace
1411        characters since release 4.0, because Perl (from release 5.004) does not.
1412        [Or at least, is documented not to: some releases seem to be in conflict
1413        with the documentation.] However, when a pattern was studied with
1414        pcre_study() and all its branches started with \s, PCRE still included VT
1415        as a possible starting character. Of course, this did no harm; it just
1416        caused an unnecessary match attempt.
1418    22. Removed a now-redundant internal flag bit that recorded the fact that case
1419        dependency changed within the pattern. This was once needed for "required
1420        byte" processing, but is no longer used. This recovers a now-scarce options
1421        bit. Also moved the least significant internal flag bit to the most-
1422        significant bit of the word, which was not previously used (hangover from
1423        the days when it was an int rather than a uint) to free up another bit for
1424        the future.
1426    23. Added support for CRLF line endings as well as CR and LF. As well as the
1427        default being selectable at build time, it can now be changed at runtime
1428        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1429        specify that it is scanning data with non-default line endings.
1431    24. Changed the definition of CXXLINK to make it agree with the definition of
1432        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1434    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1435        recursions. This makes a big different to stack usage for some patterns.
1437    26. If a subpattern containing a named recursion or subroutine reference such
1438        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1439        the space required for the compiled pattern went wrong and gave too small a
1440        value. Depending on the environment, this could lead to "Failed: internal
1441        error: code overflow at offset 49" or "glibc detected double free or
1442        corruption" errors.
1444    27. Applied patches from Google (a) to support the new newline modes and (b) to
1445        advance over multibyte UTF-8 characters in GlobalReplace.
1447    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1448        difference for some implementation of PCRE in some Windows version.
1450    29. Added some extra testing facilities to pcretest:
1452        \q<number>   in a data line sets the "match limit" value
1453        \Q<number>   in a data line sets the "match recursion limt" value
1454        -S <number>  sets the stack size, where <number> is in megabytes
1456        The -S option isn't available for Windows.
1459    Version 6.6 06-Feb-06
1460    ---------------------
1462     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1463        in pcreposix.h. I have copied the definition from pcre.h.
1465     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1466        because pcre.h is no longer a built file.
1468     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1469        not normally included in the compiled code.
1472    Version 6.5 01-Feb-06
1473    ---------------------
1475     1. When using the partial match feature with pcre_dfa_exec(), it was not
1476        anchoring the second and subsequent partial matches at the new starting
1477        point. This could lead to incorrect results. For example, with the pattern
1478        /1234/, partially matching against "123" and then "a4" gave a match.
1480     2. Changes to pcregrep:
1482        (a) All non-match returns from pcre_exec() were being treated as failures
1483            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
1484            error message is output. Some extra information is given for the
1485            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
1486            probably the only errors that are likely to be caused by users (by
1487            specifying a regex that has nested indefinite repeats, for instance).
1488            If there are more than 20 of these errors, pcregrep is abandoned.
1490        (b) A binary zero was treated as data while matching, but terminated the
1491            output line if it was written out. This has been fixed: binary zeroes
1492            are now no different to any other data bytes.
1494        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
1495            used to set a locale for matching. The --locale=xxxx long option has
1496            been added (no short equivalent) to specify a locale explicitly on the
1497            pcregrep command, overriding the environment variables.
1499        (d) When -B was used with -n, some line numbers in the output were one less
1500            than they should have been.
1502        (e) Added the -o (--only-matching) option.
1504        (f) If -A or -C was used with -c (count only), some lines of context were
1505            accidentally printed for the final match.
1507        (g) Added the -H (--with-filename) option.
1509        (h) The combination of options -rh failed to suppress file names for files
1510            that were found from directory arguments.
1512        (i) Added the -D (--devices) and -d (--directories) options.
1514        (j) Added the -F (--fixed-strings) option.
1516        (k) Allow "-" to be used as a file name for -f as well as for a data file.
1518        (l) Added the --colo(u)r option.
1520        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
1521            is not present by default.
1523     3. A nasty bug was discovered in the handling of recursive patterns, that is,
1524        items such as (?R) or (?1), when the recursion could match a number of
1525        alternatives. If it matched one of the alternatives, but subsequently,
1526        outside the recursion, there was a failure, the code tried to back up into
1527        the recursion. However, because of the way PCRE is implemented, this is not
1528        possible, and the result was an incorrect result from the match.
1530        In order to prevent this happening, the specification of recursion has
1531        been changed so that all such subpatterns are automatically treated as
1532        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1534     4. I had overlooked the fact that, in some locales, there are characters for
1535        which isalpha() is true but neither isupper() nor islower() are true. In
1536        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1537        and ordfeminine) are like this. This affected the treatment of \w and \W
1538        when they appeared in character classes, but not when they appeared outside
1539        a character class. The bit map for "word" characters is now created
1540        separately from the results of isalnum() instead of just taking it from the
1541        upper, lower, and digit maps. (Plus the underscore character, of course.)
1543     5. The above bug also affected the handling of POSIX character classes such as
1544        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
1545        permanent tables. Instead, the bit maps for such a class were previously
1546        created as the appropriate unions of the upper, lower, and digit bitmaps.
1547        Now they are created by subtraction from the [[:word:]] class, which has
1548        its own bitmap.
1550     6. The [[:blank:]] character class matches horizontal, but not vertical space.
1551        It is created by subtracting the vertical space characters (\x09, \x0a,
1552        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
1553        subtraction was done in the overall bitmap for a character class, meaning
1554        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
1555        be recognized. This bug has been fixed.
1557     7. Patches from the folks at Google:
1559          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
1560          real life, but is still worth protecting against".
1562          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
1563          regular expressions".
1565          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
1566          have it.
1568          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
1569          "configure" and the latter not, in order to fix a problem somebody had
1570          with compiling the Arg class on HP-UX.
1572          (e) Improve the error-handling of the C++ wrapper a little bit.
1574          (f) New tests for checking recursion limiting.
1576     8. The pcre_memmove() function, which is used only if the environment does not
1577        have a standard memmove() function (and is therefore rarely compiled),
1578        contained two bugs: (a) use of int instead of size_t, and (b) it was not
1579        returning a result (though PCRE never actually uses the result).
1581     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
1582        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
1583        returned instead of calling malloc() with an overflowing number that would
1584        most likely cause subsequent chaos.
1586    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
1588    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
1589        with this option is matched, the nmatch and pmatch options of regexec() are
1590        ignored.
1592    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
1593        provided in case anyone wants to the the POSIX interface with UTF-8
1594        strings.
1596    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1597        C++ linking (needed for some HP-UX environments).
1599    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1600        (unused parameter) and in the pcre_printint() function (omitted "default"
1601        switch label when the default is to do nothing).
1603    15. Added some code to make it possible, when PCRE is compiled as a C++
1604        library, to replace subject pointers for pcre_exec() with a smart pointer
1605        class, thus making it possible to process discontinuous strings.
1607    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1608        much the same function. They were added by different people who were trying
1609        to make PCRE easy to compile on non-Unix systems. It has been suggested
1610        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1611        for compiling on Windows systems. I have therefore replaced it with
1612        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1613        defaults to "extern" for C or "extern C" for C++, which works fine on
1614        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1615        SCOPE with something explicit in config.h. In addition:
1617        (a) pcreposix.h still had just "extern" instead of either of these macros;
1618            I have replaced it with PCRE_DATA_SCOPE.
1620        (b) Functions such as _pcre_xclass(), which are internal to the library,
1621            but external in the C sense, all had PCRE_EXPORT in their definitions.
1622            This is apparently wrong for the Windows case, so I have removed it.
1623            (It makes no difference on Unix-like systems.)
1625    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1626        of recursive calls to match(). This is different to MATCH_LIMIT because
1627        that limits the total number of calls to match(), not all of which increase
1628        the depth of recursion. Limiting the recursion depth limits the amount of
1629        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1630        when PCRE is compiled, and changed at run time. A patch from Google adds
1631        this functionality to the C++ interface.
1633    18. Changes to the handling of Unicode character properties:
1635        (a) Updated the table to Unicode 4.1.0.
1637        (b) Recognize characters that are not in the table as "Cn" (undefined).
1639        (c) I revised the way the table is implemented to a much improved format
1640            which includes recognition of ranges. It now supports the ranges that
1641            are defined in UnicodeData.txt, and it also amalgamates other
1642            characters into ranges. This has reduced the number of entries in the
1643            table from around 16,000 to around 3,000, thus reducing its size
1644            considerably. I realized I did not need to use a tree structure after
1645            all - a binary chop search is just as efficient. Having reduced the
1646            number of entries, I extended their size from 6 bytes to 8 bytes to
1647            allow for more data.
1649        (d) Added support for Unicode script names via properties such as \p{Han}.
1651    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1652        matching that character.
1654    20. When matching a repeated Unicode property with a minimum greater than zero,
1655        (for example \pL{2,}), PCRE could look past the end of the subject if it
1656        reached it while seeking the minimum number of characters. This could
1657        happen only if some of the characters were more than one byte long, because
1658        there is a check for at least the minimum number of bytes.
1660    21. Refactored the implementation of \p and \P so as to be more general, to
1661        allow for more different types of property in future. This has changed the
1662        compiled form incompatibly. Anybody with saved compiled patterns that use
1663        \p or \P will have to recompile them.
1665    22. Added "Any" and "L&" to the supported property types.
1667    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1668        but give a compile time error if the value is greater than 0xff.
1670    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1671        accidentally not being installed or uninstalled.
1673    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1674        made were to insert the current release number. This seemed silly, because
1675        it made things harder for people building PCRE on systems that don't run
1676        "configure". I have turned pcre.h into a distributed file, no longer built
1677        by "configure", with the version identification directly included. There is
1678        no longer a pcre.h.in file.
1680        However, this change necessitated a change to the pcre-config script as
1681        well. It is built from pcre-config.in, and one of the substitutions was the
1682        release number. I have updated configure.ac so that ./configure now finds
1683        the release number by grepping pcre.h.
1685    26. Added the ability to run the tests under valgrind.
1688    Version 6.4 05-Sep-05
1689    ---------------------
1691     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1692        "--" to be printed when multiple files were scanned, even when none of the
1693        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1694        consider it to be a bug, and have restored the previous behaviour.
1696     2. A couple of code tidies to get rid of compiler warnings.
1698     3. The pcretest program used to cheat by referring to symbols in the library
1699        whose names begin with _pcre_. These are internal symbols that are not
1700        really supposed to be visible externally, and in some environments it is
1701        possible to suppress them. The cheating is now confined to including
1702        certain files from the library's source, which is a bit cleaner.
1704     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1705        file's purpose clearer.
1707     5. Reorganized pcre_ucp_findchar().
1710    Version 6.3 15-Aug-05
1711    ---------------------
1713     1. The file libpcre.pc.in did not have general read permission in the tarball.
1715     2. There were some problems when building without C++ support:
1717        (a) If C++ support was not built, "make install" and "make test" still
1718            tried to test it.
1720        (b) There were problems when the value of CXX was explicitly set. Some
1721            changes have been made to try to fix these, and ...
1723        (c) --disable-cpp can now be used to explicitly disable C++ support.
1725        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
1726            backslash in a target when C++ was disabled. This confuses some
1727            versions of "make", apparently. Using an intermediate variable solves
1728            this. (Same for CPP_LOBJ.)
1730     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
1731        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
1732        necessary on certain architectures.
1734     4. Added a setting of -export-symbols-regex to the link command to remove
1735        those symbols that are exported in the C sense, but actually are local
1736        within the library, and not documented. Their names all begin with
1737        "_pcre_". This is not a perfect job, because (a) we have to except some
1738        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
1739        available (and never for static libraries). I have made a note to try to
1740        find a way round (a) in the future.
1743    Version 6.2 01-Aug-05
1744    ---------------------
1746     1. There was no test for integer overflow of quantifier values. A construction
1747        such as {1111111111111111} would give undefined results. What is worse, if
1748        a minimum quantifier for a parenthesized subpattern overflowed and became
1749        negative, the calculation of the memory size went wrong. This could have
1750        led to memory overwriting.
1752     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
1754     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
1755        operating environments where this matters.
1757     4. Applied Giuseppe Maxia's patch to add additional features for controlling
1758        PCRE options from within the C++ wrapper.
1760     5. Named capturing subpatterns were not being correctly counted when a pattern
1761        was compiled. This caused two problems: (a) If there were more than 100
1762        such subpatterns, the calculation of the memory needed for the whole
1763        compiled pattern went wrong, leading to an overflow error. (b) Numerical
1764        back references of the form \12, where the number was greater than 9, were
1765        not recognized as back references, even though there were sufficient
1766        previous subpatterns.
1768     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
1769        versions of gcc, e.g. 2.95.4.
1772    Version 6.1 21-Jun-05
1773    ---------------------
1775     1. There was one reference to the variable "posix" in pcretest.c that was not
1776        surrounded by "#if !defined NOPOSIX".
1778     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
1779        the cross-check on the old pcre_info() function, for the benefit of the
1780        cut-down version of PCRE that is currently imported into Exim.
1782     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
1783        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
1784        patterns that start (?i) but I don't think that matters. The use of (?i) is
1785        just an example; this all applies to the other options as well.
1787     4. Since libtool seems to echo the compile commands it is issuing, the output
1788        from "make" can be reduced a bit by putting "@" in front of each libtool
1789        compile command.
1791     5. Patch from the folks at Google for configure.in to be a bit more thorough
1792        in checking for a suitable C++ installation before trying to compile the
1793        C++ stuff. This should fix a reported problem when a compiler was present,
1794        but no suitable headers.
1796     6. The man pages all had just "PCRE" as their title. I have changed them to
1797        be the relevant file name. I have also arranged that these names are
1798        retained in the file doc/pcre.txt, which is a concatenation in text format
1799        of all the man pages except the little individual ones for each function.
1801     7. The NON-UNIX-USE file had not been updated for the different set of source
1802        files that come with release 6. I also added a few comments about the C++
1803        wrapper.
1806  Version 6.0 07-Jun-05  Version 6.0 07-Jun-05
1807  ---------------------  ---------------------

Removed from v.77  
changed lines
  Added in v.427

  ViewVC Help
Powered by ViewVC 1.1.5