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

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

  ViewVC Help
Powered by ViewVC 1.1.5