ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 81 by nigel, Sat Feb 24 21:40:59 2007 UTC revision 409 by ph10, Sat Mar 28 17:10:56 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 7.9 xx-xxx-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).
118    Version 7.8 05-Sep-08
119    ---------------------
121    1.  Replaced UCP searching code with optimized version as implemented for Ad
122        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
123        stage table and inline lookup instead of a function, giving speed ups of 2
124        to 5 times on some simple patterns that I tested. Permission was given to
125        distribute the MultiStage2.py script that generates the tables (it's not in
126        the tarball, but is in the Subversion repository).
128    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
129        scripts.
131    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
132        a group with a zero qualifier. The result of the study could be incorrect,
133        or the function might crash, depending on the pattern.
135    4.  Caseless matching was not working for non-ASCII characters in back
136        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
137        It now works when Unicode Property Support is available.
139    5.  In pcretest, an escape such as \x{de} in the data was always generating
140        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
141        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
142        truncation.
144    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
146    7.  Added two (int) casts to pcregrep when printing the difference of two
147        pointers, in case they are 64-bit values.
149    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
150        test 2 if it fails.
152    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
153        and a #define of that name to empty if it is not externally set. This is to
154        allow users of MSVC to set it if necessary.
156    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
157        the convenience functions in the pcre_get.c source file.
159    11. An option change at the start of a pattern that had top-level alternatives
160        could cause overwriting and/or a crash. This command provoked a crash in
161        some environments:
163          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
165        This potential security problem was recorded as CVE-2008-2371.
167    12. For a pattern where the match had to start at the beginning or immediately
168        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
169        pcre_dfa_exec() could read past the end of the passed subject if there was
170        no match. To help with detecting such bugs (e.g. with valgrind), I modified
171        pcretest so that it places the subject at the end of its malloc-ed buffer.
173    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
174        exec() might read past the end of the data buffer in UTF-8 mode.
176    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
177        the data contained the byte 0x85 as part of a UTF-8 character within its
178        first line. This applied both to normal and DFA matching.
180    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
181        /^[^d]*?$/8 failed to match "abc".
183    16. Added a missing copyright notice to pcrecpp_internal.h.
185    17. Make it more clear in the documentation that values returned from
186        pcre_exec() in ovector are byte offsets, not character counts.
188    18. Tidied a few places to stop certain compilers from issuing warnings.
190    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
191        supplied by Stefan Weber. I made a further small update for 7.8 because
192        there is a change of source arrangements: the pcre_searchfuncs.c module is
193        replaced by pcre_ucd.c.
196    Version 7.7 07-May-08
197    ---------------------
199    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
200        a string to a long long, pretend we don't even have a long long." This is
201        done by checking for the strtoq, strtoll, and _strtoi64 functions.
203    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
204        pre-7.6 versions, which defined a global no_arg variable instead of putting
205        it in the RE class. (See also #8 below.)
207    3.  Remove a line of dead code, identified by coverity and reported by Nuno
208        Lopes.
210    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
212        (1) The include/exclude patterns were being applied to the whole pathnames
213            of files, instead of just to the final components.
215        (2) If there was more than one level of directory, the subdirectories were
216            skipped unless they satisfied the include/exclude conditions. This is
217            inconsistent with GNU grep (and could even be seen as contrary to the
218            pcregrep specification - which I improved to make it absolutely clear).
219            The action now is always to scan all levels of directory, and just
220            apply the include/exclude patterns to regular files.
222    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
223        --exclude_dir in the tests to avoid scanning .svn directories.
225    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
226        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
227        doesn't support NULs in patterns.
229    7.  Added some missing "const"s to declarations of static tables in
230        pcre_compile.c and pcre_dfa_exec.c.
232    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
233        caused by fix #2  above. (Subsequently also a second patch to fix the
234        first patch. And a third patch - this was a messy problem.)
236    9.  Applied Craig's patch to remove the use of push_back().
238    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
239        matching function regexec().
241    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
242        which, however, unlike Perl's \g{...}, are subroutine calls, not back
243        references. PCRE supports relative numbers with this syntax (I don't think
244        Oniguruma does).
246    12. Previously, a group with a zero repeat such as (...){0} was completely
247        omitted from the compiled regex. However, this means that if the group
248        was called as a subroutine from elsewhere in the pattern, things went wrong
249        (an internal error was given). Such groups are now left in the compiled
250        pattern, with a new opcode that causes them to be skipped at execution
251        time.
253    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
254        to the way PCRE behaves:
256        (a) A lone ] character is dis-allowed (Perl treats it as data).
258        (b) A back reference to an unmatched subpattern matches an empty string
259            (Perl fails the current match path).
261        (c) A data ] in a character class must be notated as \] because if the
262            first data character in a class is ], it defines an empty class. (In
263            Perl it is not possible to have an empty class.) The empty class []
264            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
265            The negative empty class [^] matches any one character, independently
266            of the DOTALL setting.
268    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
269        non-existent subpattern following a character class starting with ']' and
270        containing () gave an internal compiling error instead of "reference to
271        non-existent subpattern". Fortunately, when the pattern did exist, the
272        compiled code was correct. (When scanning forwards to check for the
273        existencd of the subpattern, it was treating the data ']' as terminating
274        the class, so got the count wrong. When actually compiling, the reference
275        was subsequently set up correctly.)
277    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
278        it was being rejected as not supported by pcre_dfa_exec(), even though
279        other assertions are supported. I have made pcre_dfa_exec() support
280        (*FAIL).
282    16. The implementation of 13c above involved the invention of a new opcode,
283        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
284        cannot be changed at match time, I realized I could make a small
285        improvement to matching performance by compiling OP_ALLANY instead of
286        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
287        on the OP_ANY path.
289    17. Compiling pcretest on Windows with readline support failed without the
290        following two fixes: (1) Make the unistd.h include conditional on
291        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
293    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
294        ncurses library to be included for pcretest when ReadLine support is
295        requested, but also to allow for it to be overridden. This patch came from
296        Daniel Bergström.
298    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
299        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
300        any errors with the current Unicode tables. Thanks to Peter Kankowski for
301        spotting this.
304    Version 7.6 28-Jan-08
305    ---------------------
307    1.  A character class containing a very large number of characters with
308        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
309        overflow.
311    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
312        HAVE_LONG_LONG is not defined.
314    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
315        bring them up to date and include new features. This patch includes:
317        - Fixed PH's badly added libz and libbz2 support.
318        - Fixed a problem with static linking.
319        - Added pcredemo. [But later removed - see 7 below.]
320        - Fixed dftables problem and added an option.
321        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
322            HAVE_LONG_LONG.
323        - Added readline support for pcretest.
324        - Added an listing of the option settings after cmake has run.
326    4.  A user submitted a patch to Makefile that makes it easy to create
327        "pcre.dll" under mingw when using Configure/Make. I added stuff to
328        Makefile.am that cause it to include this special target, without
329        affecting anything else. Note that the same mingw target plus all
330        the other distribution libraries and programs are now supported
331        when configuring with CMake (see 6 below) instead of with
332        Configure/Make.
334    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
335        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
336        exported in the Windows port". It has not yet been confirmed that the patch
337        solves the problem, but it does no harm.
339    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
340        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
341        with CMake, and also correct the comment about stack recursion.
343    7.  Remove the automatic building of pcredemo from the ./configure system and
344        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
345        of a program that users should build themselves after PCRE is installed, so
346        building it automatically is not really right. What is more, it gave
347        trouble in some build environments.
349    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
352    Version 7.5 10-Jan-08
353    ---------------------
355    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
356        values in parens when parsing an RE using the C++ wrapper."
358    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
359        Characters greater than 255 were excluded from the class instead of being
360        included.
362    3.  The same bug as (2) above applied to negated POSIX classes such as
363        [:^space:].
365    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
366        defined or documented. It seems to have been a typo for PCRE_STATIC, so
367        I have changed it.
369    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
370        first named subpattern) and a construct such as (?&a) would reference the
371        first named subpattern whose name started with "a" (in other words, the
372        length check was missing). Both these problems are fixed. "Subpattern name
373        expected" is now given for (?&) (a zero-length name), and this patch also
374        makes it give the same error for \k'' (previously it complained that that
375        was a reference to a non-existent subpattern).
377    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
378        this is right because (?- can be followed by option settings as well as by
379        digits. I have, however, made the messages clearer.
381    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
382        than the number used in the conditional) now cause a compile-time error.
383        This is actually not compatible with Perl, which accepts such patterns, but
384        treats the conditional as always being FALSE (as PCRE used to), but it
385        seems to me that giving a diagnostic is better.
387    8.  Change "alphameric" to the more common word "alphanumeric" in comments
388        and messages.
390    9.  Fix two occurrences of "backslash" in comments that should have been
391        "backspace".
393    10. Remove two redundant lines of code that can never be obeyed (their function
394        was moved elsewhere).
396    11. The program that makes PCRE's Unicode character property table had a bug
397        which caused it to generate incorrect table entries for sequences of
398        characters that have the same character type, but are in different scripts.
399        It amalgamated them into a single range, with the script of the first of
400        them. In other words, some characters were in the wrong script. There were
401        thirteen such cases, affecting characters in the following ranges:
403          U+002b0 - U+002c1
404          U+0060c - U+0060d
405          U+0061e - U+00612
406          U+0064b - U+0065e
407          U+0074d - U+0076d
408          U+01800 - U+01805
409          U+01d00 - U+01d77
410          U+01d9b - U+01dbf
411          U+0200b - U+0200f
412          U+030fc - U+030fe
413          U+03260 - U+0327f
414          U+0fb46 - U+0fbb1
415          U+10450 - U+1049d
417    12. The -o option (show only the matching part of a line) for pcregrep was not
418        compatible with GNU grep in that, if there was more than one match in a
419        line, it showed only the first of them. It now behaves in the same way as
420        GNU grep.
422    13. If the -o and -v options were combined for pcregrep, it printed a blank
423        line for every non-matching line. GNU grep prints nothing, and pcregrep now
424        does the same. The return code can be used to tell if there were any
425        non-matching lines.
427    14. Added --file-offsets and --line-offsets to pcregrep.
429    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
430        infinitely looping recursion. The bug was that positive lookaheads were not
431        being skipped when checking for a possible empty match (negative lookaheads
432        and both kinds of lookbehind were skipped).
434    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
435        inclusion of <windows.h> to before rather than after the definition of
436        INVALID_FILE_ATTRIBUTES (patch from David Byron).
438    17. Specifying a possessive quantifier with a specific limit for a Unicode
439        character property caused pcre_compile() to compile bad code, which led at
440        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
441        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
442        caused the error; without that there was no problem.
444    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
446    19. Added --enable-pcretest-libreadline.
448    20. In pcrecpp.cc, the variable 'count' was incremented twice in
449        RE::GlobalReplace(). As a result, the number of replacements returned was
450        double what it should be. I removed one of the increments, but Craig sent a
451        later patch that removed the other one (the right fix) and added unit tests
452        that check the return values (which was not done before).
454    21. Several CMake things:
456        (1) Arranged that, when cmake is used on Unix, the libraries end up with
457            the names libpcre and libpcreposix, not just pcre and pcreposix.
459        (2) The above change means that pcretest and pcregrep are now correctly
460            linked with the newly-built libraries, not previously installed ones.
464    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
465        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
466        UTF-8 newline character). The key issue is that the pattern starts .*;
467        this means that the match must be either at the beginning, or after a
468        newline. The bug was in the code for advancing after a failed match and
469        checking that the new position followed a newline. It was not taking
470        account of UTF-8 characters correctly.
472    23. PCRE was behaving differently from Perl in the way it recognized POSIX
473        character classes. PCRE was not treating the sequence [:...:] as a
474        character class unless the ... were all letters. Perl, however, seems to
475        allow any characters between [: and :], though of course it rejects as
476        unknown any "names" that contain non-letters, because all the known class
477        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
478        for example, whereas PCRE did not - it did not recognize a POSIX character
479        class. This seemed a bit dangerous, so the code has been changed to be
480        closer to Perl. The behaviour is not identical to Perl, because PCRE will
481        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
482        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
483        Perl does, and where it didn't before.
485    24. Rewrite so as to remove the single use of %n from pcregrep because in some
486        Windows environments %n is disabled by default.
489    Version 7.4 21-Sep-07
490    ---------------------
492    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
493        means that a class such as [\s] counted as "explicit reference to CR or
494        LF". That isn't really right - the whole point of the change was to try to
495        help when there was an actual mention of one of the two characters. So now
496        the change happens only if \r or \n (or a literal CR or LF) character is
497        encountered.
499    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
500        of both had grown to the point where there were only 3 bits left.
501        Fortunately, there was spare space in the data structure, and so I have
502        moved the internal flags into a new 16-bit field to free up more option
503        bits.
505    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
506        but did not set the internal JCHANGED flag - either of these is enough to
507        control the way the "get" function works - but the PCRE_INFO_JCHANGED
508        facility is supposed to tell if (?J) was ever used, so now (?J) at the
509        start sets both bits.
511    4.  Added options (at build time, compile time, exec time) to change \R from
512        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
514    5.  doc/pcresyntax.html was missing from the distribution.
516    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
517        compatibility, even though it is no longer used.
519    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
520        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
521        windows.h file is present (where different names are used). [This was
522        reversed later after testing - see 16 below.]
524    8.  Changed all #include <config.h> to #include "config.h". There were also
525        some further <pcre.h> cases that I changed to "pcre.h".
527    9.  When pcregrep was used with the --colour option, it missed the line ending
528        sequence off the lines that it output.
530    10. It was pointed out to me that arrays of string pointers cause lots of
531        relocations when a shared library is dynamically loaded. A technique of
532        using a single long string with a table of offsets can drastically reduce
533        these. I have refactored PCRE in four places to do this. The result is
534        dramatic:
536          Originally:                          290
537          After changing UCP table:            187
538          After changing error message table:   43
539          After changing table of "verbs"       36
540          After changing table of Posix names   22
542        Thanks to the folks working on Gregex for glib for this insight.
544    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
545        unicode-properties was also set.
547    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
549    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
550        checked only for CRLF.
552    14. Added casts to pcretest.c to avoid compiler warnings.
554    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
556    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
557        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
558        entirely. This removes changes made in 7 above.
560    17. The CMake files have been updated, and there is now more information about
561        building with CMake in the NON-UNIX-USE document.
564    Version 7.3 28-Aug-07
565    ---------------------
567     1. In the rejigging of the build system that eventually resulted in 7.1, the
568        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
569        brackets there is not right, since it causes compilers to look for an
570        installed pcre.h, not the version that is in the source that is being
571        compiled (which of course may be different). I have changed it back to:
573          #include "pcre.h"
575        I have a vague recollection that the change was concerned with compiling in
576        different directories, but in the new build system, that is taken care of
577        by the VPATH setting the Makefile.
579     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
580        when the subject happened to end in the byte 0x85 (e.g. if the last
581        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
582        characters but of course it shouldn't be taken as a newline when it is part
583        of another character. The bug was that, for an unlimited repeat of . in
584        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
585        characters when looking for a newline.
587     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
589     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
590        in debug output.
592     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
593        long printing in the pcrecpp unittest when running under MinGW.
595     6. ESC_K was left out of the EBCDIC table.
597     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
598        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
599        limit also applies to "virtual nesting" when a pattern is recursive, and in
600        this case 1000 isn't so big. I have been able to remove this limit at the
601        expense of backing off one optimization in certain circumstances. Normally,
602        when pcre_exec() would call its internal match() function recursively and
603        immediately return the result unconditionally, it uses a "tail recursion"
604        feature to save stack. However, when a subpattern that can match an empty
605        string has an unlimited repetition quantifier, it no longer makes this
606        optimization. That gives it a stack frame in which to save the data for
607        checking that an empty string has been matched. Previously this was taken
608        from the 1000-entry workspace that had been reserved. So now there is no
609        explicit limit, but more stack is used.
611     8. Applied Daniel's patches to solve problems with the import/export magic
612        syntax that is required for Windows, and which was going wrong for the
613        pcreposix and pcrecpp parts of the library. These were overlooked when this
614        problem was solved for the main library.
616     9. There were some crude static tests to avoid integer overflow when computing
617        the size of patterns that contain repeated groups with explicit upper
618        limits. As the maximum quantifier is 65535, the maximum group length was
619        set at 30,000 so that the product of these two numbers did not overflow a
620        32-bit integer. However, it turns out that people want to use groups that
621        are longer than 30,000 bytes (though not repeat them that many times).
622        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
623        made it possible to implement the integer overflow checks in a much more
624        dynamic way, which I have now done. The artificial limitation on group
625        length has been removed - we now have only the limit on the total length of
626        the compiled pattern, which depends on the LINK_SIZE setting.
628    10. Fixed a bug in the documentation for get/copy named substring when
629        duplicate names are permitted. If none of the named substrings are set, the
630        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
631        empty string.
633    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
634        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
635        because the ] is interpreted as the first data character and the
636        terminating ] is not found. PCRE has been made compatible with Perl in this
637        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
638        cause memory overwriting.
640    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
641        string has been matched (to stop an infinite loop). It was not recognizing
642        a conditional subpattern that could match an empty string if that
643        subpattern was within another subpattern. For example, it looped when
644        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
645        condition was not nested. This bug has been fixed.
647    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
648        past the start of the subject in the presence of bytes with the top bit
649        set, for example "\x8aBCD".
651    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
652        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
654    14. Optimized (?!) to (*FAIL).
656    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
657        This restricts code points to be within the range 0 to 0x10FFFF, excluding
658        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
659        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
660        does: it's just the validity check that is more restrictive.
662    16. Inserted checks for integer overflows during escape sequence (backslash)
663        processing, and also fixed erroneous offset values for syntax errors during
664        backslash processing.
666    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
667        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
669    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
670        caused an overrun.
672    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
673        something other than just ASCII characters) inside a group that had an
674        unlimited repeat caused a loop at compile time (while checking to see
675        whether the group could match an empty string).
677    20. Debugging a pattern containing \p or \P could cause a crash. For example,
678        [\P{Any}] did so. (Error in the code for printing property names.)
680    21. An orphan \E inside a character class could cause a crash.
682    22. A repeated capturing bracket such as (A)? could cause a wild memory
683        reference during compilation.
685    23. There are several functions in pcre_compile() that scan along a compiled
686        expression for various reasons (e.g. to see if it's fixed length for look
687        behind). There were bugs in these functions when a repeated \p or \P was
688        present in the pattern. These operators have additional parameters compared
689        with \d, etc, and these were not being taken into account when moving along
690        the compiled data. Specifically:
692        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
693            length.
695        (b) An item such as \pL+ within a repeated group could cause crashes or
696            loops.
698        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
699            "reference to non-existent subpattern" error.
701        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
703    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
704        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
706    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
708    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
709        character were causing crashes (broken optimization).
711    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
712        \p or \P) caused a compile-time loop.
714    28. More problems have arisen in unanchored patterns when CRLF is a valid line
715        break. For example, the unstudied pattern [\r\n]A does not match the string
716        "\r\nA" because change 7.0/46 below moves the current point on by two
717        characters after failing to match at the start. However, the pattern \nA
718        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
719        the same is true. There doesn't seem any very clean way out of this, but
720        what I have chosen to do makes the common cases work: PCRE now takes note
721        of whether there can be an explicit match for \r or \n anywhere in the
722        pattern, and if so, 7.0/46 no longer applies. As part of this change,
723        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
724        pattern has explicit CR or LF references.
726    29. Added (*CR) etc for changing newline setting at start of pattern.
729    Version 7.2 19-Jun-07
730    ---------------------
732     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
733        which is apparently normally available under Windows.
735     2. Re-jig the pcregrep tests with different newline settings in an attempt
736        to make them independent of the local environment's newline setting.
738     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
740     4. Some of the "internals" tests were previously cut out when the link size
741        was not 2, because the output contained actual offsets. The recent new
742        "Z" feature of pcretest means that these can be cut out, making the tests
743        usable with all link sizes.
745     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
746        stack recursion. This gives a massive performance boost under BSD, but just
747        a small improvement under Linux. However, it saves one field in the frame
748        in all cases.
750     6. Added more features from the forthcoming Perl 5.10:
752        (a) (?-n) (where n is a string of digits) is a relative subroutine or
753            recursion call. It refers to the nth most recently opened parentheses.
755        (b) (?+n) is also a relative subroutine call; it refers to the nth next
756            to be opened parentheses.
758        (c) Conditions that refer to capturing parentheses can be specified
759            relatively, for example, (?(-2)... or (?(+3)...
761        (d) \K resets the start of the current match so that everything before
762            is not part of it.
764        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
766        (f) \g{name} is another synonym - part of Perl 5.10's unification of
767            reference syntax.
769        (g) (?| introduces a group in which the numbering of parentheses in each
770            alternative starts with the same number.
772        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
774     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
777     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
778        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
779        for detecting groups that can match an empty string.
781     9. A pattern with a very large number of alternatives (more than several
782        hundred) was running out of internal workspace during the pre-compile
783        phase, where pcre_compile() figures out how much memory will be needed. A
784        bit of new cunning has reduced the workspace needed for groups with
785        alternatives. The 1000-alternative test pattern now uses 12 bytes of
786        workspace instead of running out of the 4096 that are available.
788    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
790    11. Applied patch from Google to remove an optimization that didn't quite work.
791        The report of the bug said:
793          pcrecpp::RE("a*").FullMatch("aaa") matches, while
794          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
795          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
797    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
798        it matched the wrong number of bytes.
801    Version 7.1 24-Apr-07
802    ---------------------
804     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
805        that is more "standard", making use of automake and other Autotools. There
806        is some re-arrangement of the files and adjustment of comments consequent
807        on this.
809     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
810        for recursive directory scanning broke on some systems because the files
811        are not scanned in any specific order and on different systems the order
812        was different. A call to "sort" has been inserted into RunGrepTest for the
813        approprate test as a short-term fix. In the longer term there may be an
814        alternative.
816     3. I had an email from Eric Raymond about problems translating some of PCRE's
817        man pages to HTML (despite the fact that I distribute HTML pages, some
818        people do their own conversions for various reasons). The problems
819        concerned the use of low-level troff macros .br and .in. I have therefore
820        removed all such uses from the man pages (some were redundant, some could
821        be replaced by .nf/.fi pairs). The 132html script that I use to generate
822        HTML has been updated to handle .nf/.fi and to complain if it encounters
823        .br or .in.
825     4. Updated comments in configure.ac that get placed in config.h.in and also
826        arranged for config.h to be included in the distribution, with the name
827        config.h.generic, for the benefit of those who have to compile without
828        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
830     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
831        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
832        makevp.bat for the current PCRE, using the additional files
833        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
835     6. A Windows user reported a minor discrepancy with test 2, which turned out
836        to be caused by a trailing space on an input line that had got lost in his
837        copy. The trailing space was an accident, so I've just removed it.
839     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
840        that is needed.
842     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
843        as "const" (a) because they are and (b) because it helps the PHP
844        maintainers who have recently made a script to detect big data structures
845        in the php code that should be moved to the .rodata section. I remembered
846        to update Builducptable as well, so it won't revert if ucptable.h is ever
847        re-created.
849     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
850        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
851        order to be able to cut out the UTF-8 tables in the latter when UTF-8
852        support is not required. This saves 1.5-2K of code, which is important in
853        some applications.
855        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
856        so as not to refer to the tables, even though these functions will never be
857        called when UTF-8 support is disabled. Otherwise there are problems with a
858        shared library.
860    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
862        (a) It was defining its arguments as char * instead of void *.
864        (b) It was assuming that all moves were upwards in memory; this was true
865            a long time ago when I wrote it, but is no longer the case.
867        The emulated memove() is provided for those environments that have neither
868        memmove() nor bcopy(). I didn't think anyone used it these days, but that
869        is clearly not the case, as these two bugs were recently reported.
871    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
872        and Detrail to create the HTML documentation, the .txt form of the man
873        pages, and it removes trailing spaces from listed files. It also creates
874        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
875        case, it wraps all the #defines with #ifndefs. This script should be run
876        before "make dist".
878    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
879        with Unicode property support.
881        (a) For a maximizing quantifier, if the two different cases of the
882            character were of different lengths in their UTF-8 codings (there are
883            some cases like this - I found 11), and the matching function had to
884            back up over a mixture of the two cases, it incorrectly assumed they
885            were both the same length.
887        (b) When PCRE was configured to use the heap rather than the stack for
888            recursion during matching, it was not correctly preserving the data for
889            the other case of a UTF-8 character when checking ahead for a match
890            while processing a minimizing repeat. If the check also involved
891            matching a wide character, but failed, corruption could cause an
892            erroneous result when trying to check for a repeat of the original
893            character.
895    13. Some tidying changes to the testing mechanism:
897        (a) The RunTest script now detects the internal link size and whether there
898            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
899            values substituted by "configure". (The RunGrepTest script already did
900            this for UTF-8.) The configure.ac script no longer substitutes the
901            relevant variables.
903        (b) The debugging options /B and /D in pcretest show the compiled bytecode
904            with length and offset values. This means that the output is different
905            for different internal link sizes. Test 2 is skipped for link sizes
906            other than 2 because of this, bypassing the problem. Unfortunately,
907            there was also a test in test 3 (the locale tests) that used /B and
908            failed for link sizes other than 2. Rather than cut the whole test out,
909            I have added a new /Z option to pcretest that replaces the length and
910            offset values with spaces. This is now used to make test 3 independent
911            of link size. (Test 2 will be tidied up later.)
913    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
914        segmentation fault instead of returning the appropriate error message.
916    15. In multiline mode when the newline sequence was set to "any", the pattern
917        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
918        This doesn't seem right; it now treats the CRLF combination as the line
919        ending, and so does not match in that case. It's only a pattern such as ^$
920        that would hit this one: something like ^ABC$ would have failed after \r
921        and then tried again after \r\n.
923    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
924        in an attempt to make files that differ only in their line terminators
925        compare equal. This works on Linux.
927    17. Under certain error circumstances pcregrep might try to free random memory
928        as it exited. This is now fixed, thanks to valgrind.
930    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
931        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
932        was because its rules for how to advance for /g after matching an empty
933        string at the end of a line did not allow for this case. They now check for
934        it specially.
936    20. pcretest is supposed to handle patterns and data of any length, by
937        extending its buffers when necessary. It was getting this wrong when the
938        buffer for a data line had to be extended.
940    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
941        CRLF as a newline sequence.
943    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
944        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
945        I have nevertheless tidied it up.
947    23. Added some casts to kill warnings from HP-UX ia64 compiler.
949    24. Added a man page for pcre-config.
952    Version 7.0 19-Dec-06
953    ---------------------
955     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
956        moving to gcc 4.1.1.
958     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
959        sys/time.h, which is documented as needed for this function. It doesn't
960        seem to matter on Linux, but it showed up on some releases of OS X.
962     3. It seems that there are systems where bytes whose values are greater than
963        127 match isprint() in the "C" locale. The "C" locale should be the
964        default when a C program starts up. In most systems, only ASCII printing
965        characters match isprint(). This difference caused the output from pcretest
966        to vary, making some of the tests fail. I have changed pcretest so that:
968        (a) When it is outputting text in the compiled version of a pattern, bytes
969            other than 32-126 are always shown as hex escapes.
971        (b) When it is outputting text that is a matched part of a subject string,
972            it does the same, unless a different locale has been set for the match
973            (using the /L modifier). In this case, it uses isprint() to decide.
975     4. Fixed a major bug that caused incorrect computation of the amount of memory
976        required for a compiled pattern when options that changed within the
977        pattern affected the logic of the preliminary scan that determines the
978        length. The relevant options are -x, and -i in UTF-8 mode. The result was
979        that the computed length was too small. The symptoms of this bug were
980        either the PCRE error "internal error: code overflow" from pcre_compile(),
981        or a glibc crash with a message such as "pcretest: free(): invalid next
982        size (fast)". Examples of patterns that provoked this bug (shown in
983        pcretest format) are:
985          /(?-x: )/x
986          /(?x)(?-x: \s*#\s*)/
987          /((?i)[\x{c0}])/8
988          /(?i:[\x{c0}])/8
990        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
991        is now done differently.
993     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
994        wrapper classes; (b) implement a new function in the C++ scanner that is
995        more efficient than the old way of doing things because it avoids levels of
996        recursion in the regex matching; (c) add a paragraph to the documentation
997        for the FullMatch() function.
999     6. The escape sequence \n was being treated as whatever was defined as
1000        "newline". Not only was this contrary to the documentation, which states
1001        that \n is character 10 (hex 0A), but it also went horribly wrong when
1002        "newline" was defined as CRLF. This has been fixed.
1004     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
1005        was being set to -1 for the "end of line" case (supposedly a value that no
1006        character can have). Though this value is never used (the check for end of
1007        line is "zero bytes in current character"), it caused compiler complaints.
1008        I've changed it to 0xffffffff.
1010     8. In pcre_version.c, the version string was being built by a sequence of
1011        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
1012        string (as it is for production releases) called a macro with an empty
1013        argument. The C standard says the result of this is undefined. The gcc
1014        compiler treats it as an empty string (which was what was wanted) but it is
1015        reported that Visual C gives an error. The source has been hacked around to
1016        avoid this problem.
1018     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
1019        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
1020        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
1021        of them did).
1023    10. Originally, pcretest opened its input and output without "b"; then I was
1024        told that "b" was needed in some environments, so it was added for release
1025        5.0 to both the input and output. (It makes no difference on Unix-like
1026        systems.) Later I was told that it is wrong for the input on Windows. I've
1027        now abstracted the modes into two macros, to make it easier to fiddle with
1028        them, and removed "b" from the input mode under Windows.
1030    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
1032    12. Added -help and --help to pcretest as an official way of being reminded
1033        of the options.
1035    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
1036        and pcrecpp.cc because they annoy compilers at high warning levels.
1038    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
1040    15. Fixed an occurrence of == in configure.ac that should have been = (shell
1041        scripts are not C programs :-) and which was not noticed because it works
1042        on Linux.
1044    16. pcretest is supposed to handle any length of pattern and data line (as one
1045        line or as a continued sequence of lines) by extending its input buffer if
1046        necessary. This feature was broken for very long pattern lines, leading to
1047        a string of junk being passed to pcre_compile() if the pattern was longer
1048        than about 50K.
1050    17. I have done a major re-factoring of the way pcre_compile() computes the
1051        amount of memory needed for a compiled pattern. Previously, there was code
1052        that made a preliminary scan of the pattern in order to do this. That was
1053        OK when PCRE was new, but as the facilities have expanded, it has become
1054        harder and harder to keep it in step with the real compile phase, and there
1055        have been a number of bugs (see for example, 4 above). I have now found a
1056        cunning way of running the real compile function in a "fake" mode that
1057        enables it to compute how much memory it would need, while actually only
1058        ever using a few hundred bytes of working memory and without too many
1059        tests of the mode. This should make future maintenance and development
1060        easier. A side effect of this work is that the limit of 200 on the nesting
1061        depth of parentheses has been removed (though this was never a serious
1062        limitation, I suspect). However, there is a downside: pcre_compile() now
1063        runs more slowly than before (30% or more, depending on the pattern). I
1064        hope this isn't a big issue. There is no effect on runtime performance.
1066    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
1067        newline (only possible for the last line of a file) and it was a
1068        pattern that set a locale (followed by /Lsomething), pcretest crashed.
1070    19. Added additional timing features to pcretest. (1) The -tm option now times
1071        matching only, not compiling. (2) Both -t and -tm can be followed, as a
1072        separate command line item, by a number that specifies the number of
1073        repeats to use when timing. The default is 50000; this gives better
1074        precision, but takes uncomfortably long for very large patterns.
1076    20. Extended pcre_study() to be more clever in cases where a branch of a
1077        subpattern has no definite first character. For example, (a*|b*)[cd] would
1078        previously give no result from pcre_study(). Now it recognizes that the
1079        first character must be a, b, c, or d.
1081    21. There was an incorrect error "recursive call could loop indefinitely" if
1082        a subpattern (or the entire pattern) that was being tested for matching an
1083        empty string contained only one non-empty item after a nested subpattern.
1084        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
1085        incorrectly, because the \d was being skipped in the check.
1087    22. The pcretest program now has a new pattern option /B and a command line
1088        option -b, which is equivalent to adding /B to every pattern. This causes
1089        it to show the compiled bytecode, without the additional information that
1090        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
1091        is the same as /B/I).
1093    23. A new optimization is now able automatically to treat some sequences such
1094        as a*b as a*+b. More specifically, if something simple (such as a character
1095        or a simple class like \d) has an unlimited quantifier, and is followed by
1096        something that cannot possibly match the quantified thing, the quantifier
1097        is automatically "possessified".
1099    24. A recursive reference to a subpattern whose number was greater than 39
1100        went wrong under certain circumstances in UTF-8 mode. This bug could also
1101        have affected the operation of pcre_study().
1103    25. Realized that a little bit of performance could be had by replacing
1104        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
1106    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
1108    27. Possessive quantifiers such as a++ were previously implemented by turning
1109        them into atomic groups such as ($>a+). Now they have their own opcodes,
1110        which improves performance. This includes the automatically created ones
1111        from 23 above.
1113    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
1114        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
1115        the first matched character to be a colon. This applied both to named and
1116        numbered groups.
1118    29. The ucpinternal.h header file was missing its idempotency #ifdef.
1120    30. I was sent a "project" file called libpcre.a.dev which I understand makes
1121        building PCRE on Windows easier, so I have included it in the distribution.
1123    31. There is now a check in pcretest against a ridiculously large number being
1124        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
1125        loop, the loop is abandoned.
1127    32. Forward references to subpatterns in conditions such as (?(2)...) where
1128        subpattern 2 is defined later cause pcre_compile() to search forwards in
1129        the pattern for the relevant set of parentheses. This search went wrong
1130        when there were unescaped parentheses in a character class, parentheses
1131        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
1133    33. "Subroutine" calls and backreferences were previously restricted to
1134        referencing subpatterns earlier in the regex. This restriction has now
1135        been removed.
1137    34. Added a number of extra features that are going to be in Perl 5.10. On the
1138        whole, these are just syntactic alternatives for features that PCRE had
1139        previously implemented using the Python syntax or my own invention. The
1140        other formats are all retained for compatibility.
1142        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
1143            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
1144            also .NET compatible.
1146        (b) A recursion or subroutine call to a named group can now be defined as
1147            (?&name) as well as (?P>name).
1149        (c) A backreference to a named group can now be defined as \k<name> or
1150            \k'name' as well as (?P=name). The new forms, as well as being in Perl
1151            5.10, are also .NET compatible.
1153        (d) A conditional reference to a named group can now use the syntax
1154            (?(<name>) or (?('name') as well as (?(name).
1156        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
1157            groups (named and numbered) that are never evaluated inline, but can be
1158            called as "subroutines" from elsewhere. In effect, the DEFINE condition
1159            is always false. There may be only one alternative in such a group.
1161        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
1162            as the simple (?(R). The condition is true only if the most recent
1163            recursion is that of the given number or name. It does not search out
1164            through the entire recursion stack.
1166        (g) The escape \gN or \g{N} has been added, where N is a positive or
1167            negative number, specifying an absolute or relative reference.
1169    35. Tidied to get rid of some further signed/unsigned compiler warnings and
1170        some "unreachable code" warnings.
1172    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
1173        things, this adds five new scripts.
1175    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
1176        There were also incompatibilities regarding the handling of \Q..\E inside
1177        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
1178        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
1180    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
1181        matches an empty string, and forcibly breaks the loop. There were bugs in
1182        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
1183        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
1184        separate and independent bugs (that affected different cases) have been
1185        fixed.
1187    39. Refactored the code to abolish the use of different opcodes for small
1188        capturing bracket numbers. This is a tidy that I avoided doing when I
1189        removed the limit on the number of capturing brackets for 3.5 back in 2001.
1190        The new approach is not only tidier, it makes it possible to reduce the
1191        memory needed to fix the previous bug (38).
1193    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
1194        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
1195        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
1196        mode.
1198    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
1199        report.
1201    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
1202        copy construction and assignment in the C++ wrapper.
1204    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
1205        couple of bugs that could have given wrong results in the "--newline=crlf"
1206        case.
1208    44. Added a number of casts and did some reorganization of signed/unsigned int
1209        variables following suggestions from Dair Grant. Also renamed the variable
1210        "this" as "item" because it is a C++ keyword.
1212    45. Arranged for dftables to add
1214          #include "pcre_internal.h"
1216        to pcre_chartables.c because without it, gcc 4.x may remove the array
1217        definition from the final binary if PCRE is built into a static library and
1218        dead code stripping is activated.
1220    46. For an unanchored pattern, if a match attempt fails at the start of a
1221        newline sequence, and the newline setting is CRLF or ANY, and the next two
1222        characters are CRLF, advance by two characters instead of one.
1225    Version 6.7 04-Jul-06
1226    ---------------------
1228     1. In order to handle tests when input lines are enormously long, pcretest has
1229        been re-factored so that it automatically extends its buffers when
1230        necessary. The code is crude, but this _is_ just a test program. The
1231        default size has been increased from 32K to 50K.
1233     2. The code in pcre_study() was using the value of the re argument before
1234        testing it for NULL. (Of course, in any sensible call of the function, it
1235        won't be NULL.)
1237     3. The memmove() emulation function in pcre_internal.h, which is used on
1238        systems that lack both memmove() and bcopy() - that is, hardly ever -
1239        was missing a "static" storage class specifier.
1241     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
1242        containing an extended class (one that cannot be represented by a bitmap
1243        because it contains high-valued characters or Unicode property items, e.g.
1244        [\pZ]). Almost always one would set UTF-8 mode when processing such a
1245        pattern, but PCRE should not loop if you do not (it no longer does).
1246        [Detail: two cases were found: (a) a repeated subpattern containing an
1247        extended class; (b) a recursive reference to a subpattern that followed a
1248        previous extended class. It wasn't skipping over the extended class
1249        correctly when UTF-8 mode was not set.]
1251     5. A negated single-character class was not being recognized as fixed-length
1252        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
1253        compile error "lookbehind assertion is not fixed length".
1255     6. The RunPerlTest auxiliary script was showing an unexpected difference
1256        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
1257        write a Perl script that can interpret lines of an input file either as
1258        byte characters or as UTF-8, which is what "perltest" was being required to
1259        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
1260        can't do is switch easily at run time between having the "use utf8;" pragma
1261        or not. In the end, I fudged it by using the RunPerlTest script to insert
1262        "use utf8;" explicitly for the UTF-8 tests.
1264     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
1265        the end of the subject string, contrary to the documentation and to what
1266        Perl does. This was true of both matching functions. Now it matches only at
1267        the start of the subject and immediately after *internal* newlines.
1269     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
1270        a pointer to an int instead of a pointer to an unsigned long int. This
1271        caused problems on 64-bit systems.
1273     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
1274        instance of the 'standard' template library not being so standard".
1276    10. There was no check on the number of named subpatterns nor the maximum
1277        length of a subpattern name. The product of these values is used to compute
1278        the size of the memory block for a compiled pattern. By supplying a very
1279        long subpattern name and a large number of named subpatterns, the size
1280        computation could be caused to overflow. This is now prevented by limiting
1281        the length of names to 32 characters, and the number of named subpatterns
1282        to 10,000.
1284    11. Subpatterns that are repeated with specific counts have to be replicated in
1285        the compiled pattern. The size of memory for this was computed from the
1286        length of the subpattern and the repeat count. The latter is limited to
1287        65535, but there was no limit on the former, meaning that integer overflow
1288        could in principle occur. The compiled length of a repeated subpattern is
1289        now limited to 30,000 bytes in order to prevent this.
1291    12. Added the optional facility to have named substrings with the same name.
1293    13. Added the ability to use a named substring as a condition, using the
1294        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
1295        are numbers (not recommended). Forward references are permitted.
1297    14. Added forward references in named backreferences (if you see what I mean).
1299    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
1300        pattern could run off the end of the subject. For example, the pattern
1301        "(?s)(.{1,5})"8 did this with the subject "ab".
1303    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
1304        PCRE_CASELESS was set when matching characters that were quantified with ?
1305        or *.
1307    17. A character class other than a single negated character that had a minimum
1308        but no maximum quantifier - for example [ab]{6,} - was not handled
1309        correctly by pce_dfa_exec(). It would match only one character.
1311    18. A valid (though odd) pattern that looked like a POSIX character
1312        class but used an invalid character after [ (for example [[,abc,]]) caused
1313        pcre_compile() to give the error "Failed: internal error: code overflow" or
1314        in some cases to crash with a glibc free() error. This could even happen if
1315        the pattern terminated after [[ but there just happened to be a sequence of
1316        letters, a binary zero, and a closing ] in the memory that followed.
1318    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
1319        over the years. Originally (before any Unicode support), just the bottom 8
1320        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
1321        output from "man perlunicode" includes this:
1323          The regular expression compiler produces polymorphic opcodes.  That
1324          is, the pattern adapts to the data and automatically switches to
1325          the Unicode character scheme when presented with Unicode data--or
1326          instead uses a traditional byte scheme when presented with byte
1327          data.
1329        Sadly, a wide octal escape does not cause a switch, and in a string with
1330        no other multibyte characters, these octal escapes are treated as before.
1331        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
1332        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
1333        Unicode string.
1335        I have not perpetrated such confusion in PCRE. Up till now, it took just
1336        the bottom 8 bits, as in old Perl. I have now made octal escapes with
1337        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
1338        translate to the appropriate multibyte character.
1340    29. Applied some refactoring to reduce the number of warnings from Microsoft
1341        and Borland compilers. This has included removing the fudge introduced
1342        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
1343        a warning about an unused variable.
1345    21. PCRE has not included VT (character 0x0b) in the set of whitespace
1346        characters since release 4.0, because Perl (from release 5.004) does not.
1347        [Or at least, is documented not to: some releases seem to be in conflict
1348        with the documentation.] However, when a pattern was studied with
1349        pcre_study() and all its branches started with \s, PCRE still included VT
1350        as a possible starting character. Of course, this did no harm; it just
1351        caused an unnecessary match attempt.
1353    22. Removed a now-redundant internal flag bit that recorded the fact that case
1354        dependency changed within the pattern. This was once needed for "required
1355        byte" processing, but is no longer used. This recovers a now-scarce options
1356        bit. Also moved the least significant internal flag bit to the most-
1357        significant bit of the word, which was not previously used (hangover from
1358        the days when it was an int rather than a uint) to free up another bit for
1359        the future.
1361    23. Added support for CRLF line endings as well as CR and LF. As well as the
1362        default being selectable at build time, it can now be changed at runtime
1363        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1364        specify that it is scanning data with non-default line endings.
1366    24. Changed the definition of CXXLINK to make it agree with the definition of
1367        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1369    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1370        recursions. This makes a big different to stack usage for some patterns.
1372    26. If a subpattern containing a named recursion or subroutine reference such
1373        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1374        the space required for the compiled pattern went wrong and gave too small a
1375        value. Depending on the environment, this could lead to "Failed: internal
1376        error: code overflow at offset 49" or "glibc detected double free or
1377        corruption" errors.
1379    27. Applied patches from Google (a) to support the new newline modes and (b) to
1380        advance over multibyte UTF-8 characters in GlobalReplace.
1382    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1383        difference for some implementation of PCRE in some Windows version.
1385    29. Added some extra testing facilities to pcretest:
1387        \q<number>   in a data line sets the "match limit" value
1388        \Q<number>   in a data line sets the "match recursion limt" value
1389        -S <number>  sets the stack size, where <number> is in megabytes
1391        The -S option isn't available for Windows.
1394    Version 6.6 06-Feb-06
1395    ---------------------
1397     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1398        in pcreposix.h. I have copied the definition from pcre.h.
1400     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1401        because pcre.h is no longer a built file.
1403     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1404        not normally included in the compiled code.
1407    Version 6.5 01-Feb-06
1408    ---------------------
1410     1. When using the partial match feature with pcre_dfa_exec(), it was not
1411        anchoring the second and subsequent partial matches at the new starting
1412        point. This could lead to incorrect results. For example, with the pattern
1413        /1234/, partially matching against "123" and then "a4" gave a match.
1415     2. Changes to pcregrep:
1417        (a) All non-match returns from pcre_exec() were being treated as failures
1418            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
1419            error message is output. Some extra information is given for the
1420            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
1421            probably the only errors that are likely to be caused by users (by
1422            specifying a regex that has nested indefinite repeats, for instance).
1423            If there are more than 20 of these errors, pcregrep is abandoned.
1425        (b) A binary zero was treated as data while matching, but terminated the
1426            output line if it was written out. This has been fixed: binary zeroes
1427            are now no different to any other data bytes.
1429        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
1430            used to set a locale for matching. The --locale=xxxx long option has
1431            been added (no short equivalent) to specify a locale explicitly on the
1432            pcregrep command, overriding the environment variables.
1434        (d) When -B was used with -n, some line numbers in the output were one less
1435            than they should have been.
1437        (e) Added the -o (--only-matching) option.
1439        (f) If -A or -C was used with -c (count only), some lines of context were
1440            accidentally printed for the final match.
1442        (g) Added the -H (--with-filename) option.
1444        (h) The combination of options -rh failed to suppress file names for files
1445            that were found from directory arguments.
1447        (i) Added the -D (--devices) and -d (--directories) options.
1449        (j) Added the -F (--fixed-strings) option.
1451        (k) Allow "-" to be used as a file name for -f as well as for a data file.
1453        (l) Added the --colo(u)r option.
1455        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
1456            is not present by default.
1458     3. A nasty bug was discovered in the handling of recursive patterns, that is,
1459        items such as (?R) or (?1), when the recursion could match a number of
1460        alternatives. If it matched one of the alternatives, but subsequently,
1461        outside the recursion, there was a failure, the code tried to back up into
1462        the recursion. However, because of the way PCRE is implemented, this is not
1463        possible, and the result was an incorrect result from the match.
1465        In order to prevent this happening, the specification of recursion has
1466        been changed so that all such subpatterns are automatically treated as
1467        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1469     4. I had overlooked the fact that, in some locales, there are characters for
1470        which isalpha() is true but neither isupper() nor islower() are true. In
1471        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1472        and ordfeminine) are like this. This affected the treatment of \w and \W
1473        when they appeared in character classes, but not when they appeared outside
1474        a character class. The bit map for "word" characters is now created
1475        separately from the results of isalnum() instead of just taking it from the
1476        upper, lower, and digit maps. (Plus the underscore character, of course.)
1478     5. The above bug also affected the handling of POSIX character classes such as
1479        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
1480        permanent tables. Instead, the bit maps for such a class were previously
1481        created as the appropriate unions of the upper, lower, and digit bitmaps.
1482        Now they are created by subtraction from the [[:word:]] class, which has
1483        its own bitmap.
1485     6. The [[:blank:]] character class matches horizontal, but not vertical space.
1486        It is created by subtracting the vertical space characters (\x09, \x0a,
1487        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
1488        subtraction was done in the overall bitmap for a character class, meaning
1489        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
1490        be recognized. This bug has been fixed.
1492     7. Patches from the folks at Google:
1494          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
1495          real life, but is still worth protecting against".
1497          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
1498          regular expressions".
1500          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
1501          have it.
1503          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
1504          "configure" and the latter not, in order to fix a problem somebody had
1505          with compiling the Arg class on HP-UX.
1507          (e) Improve the error-handling of the C++ wrapper a little bit.
1509          (f) New tests for checking recursion limiting.
1511     8. The pcre_memmove() function, which is used only if the environment does not
1512        have a standard memmove() function (and is therefore rarely compiled),
1513        contained two bugs: (a) use of int instead of size_t, and (b) it was not
1514        returning a result (though PCRE never actually uses the result).
1516     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
1517        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
1518        returned instead of calling malloc() with an overflowing number that would
1519        most likely cause subsequent chaos.
1521    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
1523    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
1524        with this option is matched, the nmatch and pmatch options of regexec() are
1525        ignored.
1527    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
1528        provided in case anyone wants to the the POSIX interface with UTF-8
1529        strings.
1531    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1532        C++ linking (needed for some HP-UX environments).
1534    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1535        (unused parameter) and in the pcre_printint() function (omitted "default"
1536        switch label when the default is to do nothing).
1538    15. Added some code to make it possible, when PCRE is compiled as a C++
1539        library, to replace subject pointers for pcre_exec() with a smart pointer
1540        class, thus making it possible to process discontinuous strings.
1542    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1543        much the same function. They were added by different people who were trying
1544        to make PCRE easy to compile on non-Unix systems. It has been suggested
1545        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1546        for compiling on Windows systems. I have therefore replaced it with
1547        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1548        defaults to "extern" for C or "extern C" for C++, which works fine on
1549        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1550        SCOPE with something explicit in config.h. In addition:
1552        (a) pcreposix.h still had just "extern" instead of either of these macros;
1553            I have replaced it with PCRE_DATA_SCOPE.
1555        (b) Functions such as _pcre_xclass(), which are internal to the library,
1556            but external in the C sense, all had PCRE_EXPORT in their definitions.
1557            This is apparently wrong for the Windows case, so I have removed it.
1558            (It makes no difference on Unix-like systems.)
1560    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1561        of recursive calls to match(). This is different to MATCH_LIMIT because
1562        that limits the total number of calls to match(), not all of which increase
1563        the depth of recursion. Limiting the recursion depth limits the amount of
1564        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1565        when PCRE is compiled, and changed at run time. A patch from Google adds
1566        this functionality to the C++ interface.
1568    18. Changes to the handling of Unicode character properties:
1570        (a) Updated the table to Unicode 4.1.0.
1572        (b) Recognize characters that are not in the table as "Cn" (undefined).
1574        (c) I revised the way the table is implemented to a much improved format
1575            which includes recognition of ranges. It now supports the ranges that
1576            are defined in UnicodeData.txt, and it also amalgamates other
1577            characters into ranges. This has reduced the number of entries in the
1578            table from around 16,000 to around 3,000, thus reducing its size
1579            considerably. I realized I did not need to use a tree structure after
1580            all - a binary chop search is just as efficient. Having reduced the
1581            number of entries, I extended their size from 6 bytes to 8 bytes to
1582            allow for more data.
1584        (d) Added support for Unicode script names via properties such as \p{Han}.
1586    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1587        matching that character.
1589    20. When matching a repeated Unicode property with a minimum greater than zero,
1590        (for example \pL{2,}), PCRE could look past the end of the subject if it
1591        reached it while seeking the minimum number of characters. This could
1592        happen only if some of the characters were more than one byte long, because
1593        there is a check for at least the minimum number of bytes.
1595    21. Refactored the implementation of \p and \P so as to be more general, to
1596        allow for more different types of property in future. This has changed the
1597        compiled form incompatibly. Anybody with saved compiled patterns that use
1598        \p or \P will have to recompile them.
1600    22. Added "Any" and "L&" to the supported property types.
1602    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1603        but give a compile time error if the value is greater than 0xff.
1605    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1606        accidentally not being installed or uninstalled.
1608    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1609        made were to insert the current release number. This seemed silly, because
1610        it made things harder for people building PCRE on systems that don't run
1611        "configure". I have turned pcre.h into a distributed file, no longer built
1612        by "configure", with the version identification directly included. There is
1613        no longer a pcre.h.in file.
1615        However, this change necessitated a change to the pcre-config script as
1616        well. It is built from pcre-config.in, and one of the substitutions was the
1617        release number. I have updated configure.ac so that ./configure now finds
1618        the release number by grepping pcre.h.
1620    26. Added the ability to run the tests under valgrind.
1623    Version 6.4 05-Sep-05
1624    ---------------------
1626     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1627        "--" to be printed when multiple files were scanned, even when none of the
1628        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1629        consider it to be a bug, and have restored the previous behaviour.
1631     2. A couple of code tidies to get rid of compiler warnings.
1633     3. The pcretest program used to cheat by referring to symbols in the library
1634        whose names begin with _pcre_. These are internal symbols that are not
1635        really supposed to be visible externally, and in some environments it is
1636        possible to suppress them. The cheating is now confined to including
1637        certain files from the library's source, which is a bit cleaner.
1639     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1640        file's purpose clearer.
1642     5. Reorganized pcre_ucp_findchar().
1645    Version 6.3 15-Aug-05
1646    ---------------------
1648     1. The file libpcre.pc.in did not have general read permission in the tarball.
1650     2. There were some problems when building without C++ support:
1652        (a) If C++ support was not built, "make install" and "make test" still
1653            tried to test it.
1655        (b) There were problems when the value of CXX was explicitly set. Some
1656            changes have been made to try to fix these, and ...
1658        (c) --disable-cpp can now be used to explicitly disable C++ support.
1660        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
1661            backslash in a target when C++ was disabled. This confuses some
1662            versions of "make", apparently. Using an intermediate variable solves
1663            this. (Same for CPP_LOBJ.)
1665     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
1666        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
1667        necessary on certain architectures.
1669     4. Added a setting of -export-symbols-regex to the link command to remove
1670        those symbols that are exported in the C sense, but actually are local
1671        within the library, and not documented. Their names all begin with
1672        "_pcre_". This is not a perfect job, because (a) we have to except some
1673        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
1674        available (and never for static libraries). I have made a note to try to
1675        find a way round (a) in the future.
1678  Version 6.2 01-Aug-05  Version 6.2 01-Aug-05
1679  ---------------------  ---------------------

Removed from v.81  
changed lines
  Added in v.409

  ViewVC Help
Powered by ViewVC 1.1.5