/[pcre]/code/branches/pcre16/ChangeLog

Diff of /code/branches/pcre16/ChangeLog

Parent Directory | Revision Log | View Patch Patch

-revision 307 by ph10,
Sun Jan 20 20:36:45 2008 UTC
+revision 497 by ph10,
Wed Mar  3 12:01:00 2010 UTC
 Line 1
  ChangeLog for PCRE
  ------------------
- Version 7.6 19-Jan-08
+ Version 8.02 01-Mar-2010
+ ------------------------
+.  The Unicode data tables have been updated to Unicode 5.2.0.
+.  Added the option --libs-cpp to pcre-config, but only when C++ support is
+     configured.
+.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
+     original author of that file, following a query about its status.
+.  On systems that do not have stdint.h (e.g. Solaris), check for and include
+     inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
+.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
+     quantifier applied to a forward-referencing subroutine call, could compile
+     incorrect code or give the error "internal error: previously-checked
+     referenced subpattern not found".
+.  Both MS Visual Studio and Symbian OS have problems with initializing
+     variables to point to external functions. For these systems, therefore,
+     pcre_malloc etc. are now initialized to local functions that call the
+     relevant global functions.
+ Version 8.01 19-Jan-2010
+ ------------------------
+.  If a pattern contained a conditional subpattern with only one branch (in
+     particular, this includes all (*DEFINE) patterns), a call to pcre_study()
+     computed the wrong minimum data length (which is of course zero for such
+     subpatterns). This could cause incorrect "no match" results.
+.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
+     the pattern is reset in the first branch, pcre_compile() failed with
+     "internal error: code overflow at offset...". This happened only when
+     the reset was to the original external option setting. (An optimization
+     abstracts leading options settings into an external setting, which was the
+     cause of this.)
+.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
+     of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
+     assertion pattern did not match (meaning that the assertion was true), it
+     was incorrectly treated as false if the SKIP had been reached during the
+     matching. This also applied to assertions used as conditions.
+.  If an item that is not supported by pcre_dfa_exec() was encountered in an
+     assertion subpattern, including such a pattern used as a condition,
+     unpredictable results occurred, instead of the error return
+     PCRE_ERROR_DFA_UITEM.
+.  The C++ GlobalReplace function was not working like Perl for the special
+     situation when an empty string is matched. It now does the fancy magic
+     stuff that is necessary.
+.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
+     removed. (These were left over from very, very early versions of PCRE.)
+.  Some cosmetic changes to the code to make life easier when compiling it
+     as part of something else:
+     (a) Change DEBUG to PCRE_DEBUG.
+     (b) In pcre_compile(), rename the member of the "branch_chain" structure
+         called "current" as "current_branch", to prevent a collision with the
+         Linux macro when compiled as a kernel module.
+     (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
+         prevent a collision with the Linux macro when compiled as a kernel
+         module.
+.  In pcre_compile() there are some checks for integer overflows that used to
+     cast potentially large values to (double). This has been changed to that
+     when building, a check for int64_t is made, and if it is found, it is used
+     instead, thus avoiding the use of floating point arithmetic. (There is no
+     other use of FP in PCRE.) If int64_t is not found, the fallback is to
+     double.
+.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
+(difference between two addresses compared to an unsigned value).
+. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
+     custom one, because of the following reported problem in Windows:
+       - libbz2 uses the Pascal calling convention (WINAPI) for the functions
+           under Win32.
+       - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
+           therefore missing the function definition.
+       - The compiler thus generates a "C" signature for the test function.
+       - The linker fails to find the "C" function.
+       - PCRE fails to configure if asked to do so against libbz2.
+. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
+     messages were output:
+       Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
+       rerunning libtoolize, to keep the correct libtool macros in-tree.
+       Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
+     I have done both of these things.
+. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
+     most of the time, it *can* run out if it is given a pattern that contains a
+     runaway infinite recursion. I updated the discussion in the pcrestack man
+     page.
+. Now that we have gone to the x.xx style of version numbers, the minor
+     version may start with zero. Using 08 or 09 is a bad idea because users
+     might check the value of PCRE_MINOR in their code, and 08 or 09 may be
+     interpreted as invalid octal numbers. I've updated the previous comment in
+     configure.ac, and also added a check that gives an error if 08 or 09 are
+     used.
+. Change 8.00/11 was not quite complete: code had been accidentally omitted,
+     causing partial matching to fail when the end of the subject matched \W
+     in a UTF-8 pattern where \W was quantified with a minimum of 3.
+. There were some discrepancies between the declarations in pcre_internal.h
+     of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
+     their definitions. The declarations used "const uschar *" and the
+     definitions used USPTR. Even though USPTR is normally defined as "const
+     unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
+     reported that: "This difference in casting confuses some C++ compilers, for
+     example, SunCC recognizes above declarations as different functions and
+     generates broken code for hbpcre." I have changed the declarations to use
+     USPTR.
+. GNU libtool is named differently on some systems. The autogen.sh script now
+     tries several variants such as glibtoolize (MacOSX) and libtoolize1x
+     (FreeBSD).
+. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
+     (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
+     comment: "Figure out how to create a longlong from a string: strtoll and
+     equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
+     instance, but it only takes 2 args instead of 3!"
+. A subtle bug concerned with back references has been fixed by a change of
+     specification, with a corresponding code fix. A pattern such as
+     ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
+     refers, was giving matches when it shouldn't. For example, xa=xaaa would
+     match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
+     same bug. Such groups have to be quantified to be useful, or contained
+     inside another quantified group. (If there's no repetition, the reference
+     can never match.) The problem arises because, having left the group and
+     moved on to the rest of the pattern, a later failure that backtracks into
+     the group uses the captured value from the final iteration of the group
+     rather than the correct earlier one. I have fixed this in PCRE by forcing
+     any group that contains a reference to itself to be an atomic group; that
+     is, there cannot be any backtracking into it once it has completed. This is
+     similar to recursive and subroutine calls.
+ Version 8.00 19-Oct-09
+ ----------------------
+.  The table for translating pcre_compile() error codes into POSIX error codes
+     was out-of-date, and there was no check on the pcre_compile() error code
+     being within the table. This could lead to an OK return being given in
+     error.
+.  Changed the call to open a subject file in pcregrep from fopen(pathname,
+     "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
+     in a Windows environment.
+.  The pcregrep --count option prints the count for each file even when it is
+     zero, as does GNU grep. However, pcregrep was also printing all files when
+     --files-with-matches was added. Now, when both options are given, it prints
+     counts only for those files that have at least one match. (GNU grep just
+     prints the file name in this circumstance, but including the count seems
+     more useful - otherwise, why use --count?) Also ensured that the
+     combination -clh just lists non-zero counts, with no names.
+.  The long form of the pcregrep -F option was incorrectly implemented as
+     --fixed_strings instead of --fixed-strings. This is an incompatible change,
+     but it seems right to fix it, and I didn't think it was worth preserving
+     the old behaviour.
+.  The command line items --regex=pattern and --regexp=pattern were not
+     recognized by pcregrep, which required --regex pattern or --regexp pattern
+     (with a space rather than an '='). The man page documented the '=' forms,
+     which are compatible with GNU grep; these now work.
+.  No libpcreposix.pc file was created for pkg-config; there was just
+     libpcre.pc and libpcrecpp.pc. The omission has been rectified.
+.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
+     when UCP support is not needed, by modifying the Python script that
+     generates it from Unicode data files. This should not matter if the module
+     is correctly used as a library, but I received one complaint about 50K of
+     unwanted data. My guess is that the person linked everything into his
+     program rather than using a library. Anyway, it does no harm.
+.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
+     was a minimum greater than 1 for a wide character in a possessive
+     repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
+     which had an unlimited repeat of a nested, fixed maximum repeat of a wide
+     character. Chaos in the form of incorrect output or a compiling loop could
+     result.
+.  The restrictions on what a pattern can contain when partial matching is
+     requested for pcre_exec() have been removed. All patterns can now be
+     partially matched by this function. In addition, if there are at least two
+     slots in the offset vector, the offset of the earliest inspected character
+     for the match and the offset of the end of the subject are set in them when
+     PCRE_ERROR_PARTIAL is returned.
+. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
+     synonymous with PCRE_PARTIAL, for backwards compatibility, and
+     PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
+     and may be more useful for multi-segment matching.
+. Partial matching with pcre_exec() is now more intuitive. A partial match
+     used to be given if ever the end of the subject was reached; now it is
+     given only if matching could not proceed because another character was
+     needed. This makes a difference in some odd cases such as Z(*FAIL) with the
+     string "Z", which now yields "no match" instead of "partial match". In the
+     case of pcre_dfa_exec(), "no match" is given if every matching path for the
+     final character ended with (*FAIL).
+. Restarting a match using pcre_dfa_exec() after a partial match did not work
+     if the pattern had a "must contain" character that was already found in the
+     earlier partial match, unless partial matching was again requested. For
+     example, with the pattern /dog.(body)?/, the "must contain" character is
+     "g". If the first part-match was for the string "dog", restarting with
+     "sbody" failed. This bug has been fixed.
+. The string returned by pcre_dfa_exec() after a partial match has been
+     changed so that it starts at the first inspected character rather than the
+     first character of the match. This makes a difference only if the pattern
+     starts with a lookbehind assertion or \b or \B (\K is not supported by
+     pcre_dfa_exec()). It's an incompatible change, but it makes the two
+     matching functions compatible, and I think it's the right thing to do.
+. Added a pcredemo man page, created automatically from the pcredemo.c file,
+     so that the demonstration program is easily available in environments where
+     PCRE has not been installed from source.
+. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
+     libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
+     library.
+. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
+     It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
+     is not the first non-POSIX option to be added. Clearly some people find
+     these options useful.
+. If a caller to the POSIX matching function regexec() passes a non-zero
+     value for nmatch with a NULL value for pmatch, the value of
+     nmatch is forced to zero.
+. RunGrepTest did not have a test for the availability of the -u option of
+     the diff command, as RunTest does. It now checks in the same way as
+     RunTest, and also checks for the -b option.
+. If an odd number of negated classes containing just a single character
+     interposed, within parentheses, between a forward reference to a named
+     subpattern and the definition of the subpattern, compilation crashed with
+     an internal error, complaining that it could not find the referenced
+     subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
+     [The bug was that it was starting one character too far in when skipping
+     over the character class, thus treating the ] as data rather than
+     terminating the class. This meant it could skip too much.]
+. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
+     /g option in pcretest when the pattern contains \K, which makes it possible
+     to have an empty string match not at the start, even when the pattern is
+     anchored. Updated pcretest and pcredemo to use this option.
+. If the maximum number of capturing subpatterns in a recursion was greater
+     than the maximum at the outer level, the higher number was returned, but
+     with unset values at the outer level. The correct (outer level) value is
+     now given.
+. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
+     PCRE did not set those parentheses (unlike Perl). I have now found a way to
+     make it do so. The string so far is captured, making this feature
+     compatible with Perl.
+. The tests have been re-organized, adding tests 11 and 12, to make it
+     possible to check the Perl 5.10 features against Perl 5.10.
+. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
+     pattern matches a fixed length string. PCRE did not allow this; now it
+     does. Neither allows recursion.
+. I finally figured out how to implement a request to provide the minimum
+     length of subject string that was needed in order to match a given pattern.
+     (It was back references and recursion that I had previously got hung up
+     on.) This code has now been added to pcre_study(); it finds a lower bound
+     to the length of subject needed. It is not necessarily the greatest lower
+     bound, but using it to avoid searching strings that are too short does give
+     some useful speed-ups. The value is available to calling programs via
+     pcre_fullinfo().
+. While implementing 25, I discovered to my embarrassment that pcretest had
+     not been passing the result of pcre_study() to pcre_dfa_exec(), so the
+     study optimizations had never been tested with that matching function.
+     Oops. What is worse, even when it was passed study data, there was a bug in
+     pcre_dfa_exec() that meant it never actually used it. Double oops. There
+     were also very few tests of studied patterns with pcre_dfa_exec().
+. If (?| is used to create subpatterns with duplicate numbers, they are now
+     allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
+     on the other side of the coin, they are no longer allowed to have different
+     names, because these cannot be distinguished in PCRE, and this has caused
+     confusion. (This is a difference from Perl.)
+. When duplicate subpattern names are present (necessarily with different
+     numbers, as required by 27 above), and a test is made by name in a
+     conditional pattern, either for a subpattern having been matched, or for
+     recursion in such a pattern, all the associated numbered subpatterns are
+     tested, and the overall condition is true if the condition is true for any
+     one of them. This is the way Perl works, and is also more like the way
+     testing by number works.
+ Version 7.9 11-Apr-09
+ ---------------------
+.  When building with support for bzlib/zlib (pcregrep) and/or readline
+     (pcretest), all targets were linked against these libraries. This included
+     libpcre, libpcreposix, and libpcrecpp, even though they do not use these
+     libraries. This caused unwanted dependencies to be created. This problem
+     has been fixed, and now only pcregrep is linked with bzlib/zlib and only
+     pcretest is linked with readline.
+.  The "typedef int BOOL" in pcre_internal.h that was included inside the
+     "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
+     moved outside it again, because FALSE and TRUE are already defined in AIX,
+     but BOOL is not.
+.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
+     PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
+.  The pcregrep documentation said spaces were inserted as well as colons (or
+     hyphens) following file names and line numbers when outputting matching
+     lines. This is not true; no spaces are inserted. I have also clarified the
+     wording for the --colour (or --color) option.
+.  In pcregrep, when --colour was used with -o, the list of matching strings
+     was not coloured; this is different to GNU grep, so I have changed it to be
+     the same.
+.  When --colo(u)r was used in pcregrep, only the first matching substring in
+     each matching line was coloured. Now it goes on to look for further matches
+     of any of the test patterns, which is the same behaviour as GNU grep.
+.  A pattern that could match an empty string could cause pcregrep to loop; it
+     doesn't make sense to accept an empty string match in pcregrep, so I have
+     locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
+     seems to be how GNU grep behaves.
+.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
+     start or after a newline", because the conditional assertion was not being
+     correctly handled. The rule now is that both the assertion and what follows
+     in the first alternative must satisfy the test.
+.  If auto-callout was enabled in a pattern with a conditional group whose
+     condition was an assertion, PCRE could crash during matching, both with
+     pcre_exec() and pcre_dfa_exec().
+. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
+     used for matching.
+. Unicode property support in character classes was not working for
+     characters (bytes) greater than 127 when not in UTF-8 mode.
+. Added the -M command line option to pcretest.
+. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
+. Added the PCRE_NO_START_OPTIMIZE match-time option.
+. Added comments and documentation about mis-use of no_arg in the C++
+     wrapper.
+. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
+     from Martin Jerabek that uses macro names for all relevant character and
+     string constants.
+. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
+     SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
+     SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
+     these, but not everybody uses configure.
+. A conditional group that had only one branch was not being correctly
+     recognized as an item that could match an empty string. This meant that an
+     enclosing group might also not be so recognized, causing infinite looping
+     (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
+     with the subject "ab", where knowledge that the repeated group can match
+     nothing is needed in order to break the loop.
+. If a pattern that was compiled with callouts was matched using pcre_dfa_
+     exec(), but without supplying a callout function, matching went wrong.
+. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
+     leak if the size of the offset vector was greater than 30. When the vector
+     is smaller, the saved offsets during recursion go onto a local stack
+     vector, but for larger vectors malloc() is used. It was failing to free
+     when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
+     error, in fact).
+. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
+     heapframe that is used only when UTF-8 support is enabled. This caused no
+     problem, but was untidy.
+. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
+     CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
+     included within another project.
+. Steven Van Ingelgem's patches to add more options to the CMake support,
+     slightly modified by me:
+       (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
+           not building pcregrep.
+       (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
+           if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
+. Forward references, both numeric and by name, in patterns that made use of
+     duplicate group numbers, could behave incorrectly or give incorrect errors,
+     because when scanning forward to find the reference group, PCRE was not
+     taking into account the duplicate group numbers. A pattern such as
+     ^X(?3)(a)(?|(b)|(q))(Y) is an example.
+. Changed a few more instances of "const unsigned char *" to USPTR, making
+     the feature of a custom pointer more persuasive (as requested by a user).
+. Wrapped the definitions of fileno and isatty for Windows, which appear in
+     pcretest.c, inside #ifndefs, because it seems they are sometimes already
+     pre-defined.
+. Added support for (*UTF8) at the start of a pattern.
+. Arrange for flags added by the "release type" setting in CMake to be shown
+     in the configuration summary.
+ Version 7.8 05-Sep-08
+ ---------------------
+.  Replaced UCP searching code with optimized version as implemented for Ad
+     Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
+     stage table and inline lookup instead of a function, giving speed ups of 2
+     to 5 times on some simple patterns that I tested. Permission was given to
+     distribute the MultiStage2.py script that generates the tables (it's not in
+     the tarball, but is in the Subversion repository).
+.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
+     scripts.
+.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
+     a group with a zero qualifier. The result of the study could be incorrect,
+     or the function might crash, depending on the pattern.
+.  Caseless matching was not working for non-ASCII characters in back
+     references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
+     It now works when Unicode Property Support is available.
+.  In pcretest, an escape such as \x{de} in the data was always generating
+     a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
+     non-UTF-8 mode. If the value is greater than 255, it gives a warning about
+     truncation.
+.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
+.  Added two (int) casts to pcregrep when printing the difference of two
+     pointers, in case they are 64-bit values.
+.  Added comments about Mac OS X stack usage to the pcrestack man page and to
+     test 2 if it fails.
+.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
+     and a #define of that name to empty if it is not externally set. This is to
+     allow users of MSVC to set it if necessary.
+. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
+     the convenience functions in the pcre_get.c source file.
+. An option change at the start of a pattern that had top-level alternatives
+     could cause overwriting and/or a crash. This command provoked a crash in
+     some environments:
+       printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
+     This potential security problem was recorded as CVE-2008-2371.
+. For a pattern where the match had to start at the beginning or immediately
+     after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
+     pcre_dfa_exec() could read past the end of the passed subject if there was
+     no match. To help with detecting such bugs (e.g. with valgrind), I modified
+     pcretest so that it places the subject at the end of its malloc-ed buffer.
+. The change to pcretest in 12 above threw up a couple more cases when pcre_
+     exec() might read past the end of the data buffer in UTF-8 mode.
+. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
+     the data contained the byte 0x85 as part of a UTF-8 character within its
+     first line. This applied both to normal and DFA matching.
+. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
+     /^[^d]*?$/8 failed to match "abc".
+. Added a missing copyright notice to pcrecpp_internal.h.
+. Make it more clear in the documentation that values returned from
+     pcre_exec() in ovector are byte offsets, not character counts.
+. Tidied a few places to stop certain compilers from issuing warnings.
+. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
+     supplied by Stefan Weber. I made a further small update for 7.8 because
+     there is a change of source arrangements: the pcre_searchfuncs.c module is
+     replaced by pcre_ucd.c.
+ Version 7.7 07-May-08
+ ---------------------
+.  Applied Craig's patch to sort out a long long problem: "If we can't convert
+     a string to a long long, pretend we don't even have a long long." This is
+     done by checking for the strtoq, strtoll, and _strtoi64 functions.
+.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
+     pre-7.6 versions, which defined a global no_arg variable instead of putting
+     it in the RE class. (See also #8 below.)
+.  Remove a line of dead code, identified by coverity and reported by Nuno
+     Lopes.
+.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
+     (1) The include/exclude patterns were being applied to the whole pathnames
+         of files, instead of just to the final components.
+     (2) If there was more than one level of directory, the subdirectories were
+         skipped unless they satisfied the include/exclude conditions. This is
+         inconsistent with GNU grep (and could even be seen as contrary to the
+         pcregrep specification - which I improved to make it absolutely clear).
+         The action now is always to scan all levels of directory, and just
+         apply the include/exclude patterns to regular files.
+.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
+     --exclude_dir in the tests to avoid scanning .svn directories.
+.  Applied Craig's patch to the QuoteMeta function so that it escapes the
+     NUL character as backslash + 0 rather than backslash + NUL, because PCRE
+     doesn't support NULs in patterns.
+.  Added some missing "const"s to declarations of static tables in
+     pcre_compile.c and pcre_dfa_exec.c.
+.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
+     caused by fix #2  above. (Subsequently also a second patch to fix the
+     first patch. And a third patch - this was a messy problem.)
+.  Applied Craig's patch to remove the use of push_back().
+. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
+     matching function regexec().
+. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
+     which, however, unlike Perl's \g{...}, are subroutine calls, not back
+     references. PCRE supports relative numbers with this syntax (I don't think
+     Oniguruma does).
+. Previously, a group with a zero repeat such as (...){0} was completely
+     omitted from the compiled regex. However, this means that if the group
+     was called as a subroutine from elsewhere in the pattern, things went wrong
+     (an internal error was given). Such groups are now left in the compiled
+     pattern, with a new opcode that causes them to be skipped at execution
+     time.
+. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
+     to the way PCRE behaves:
+     (a) A lone ] character is dis-allowed (Perl treats it as data).
+     (b) A back reference to an unmatched subpattern matches an empty string
+         (Perl fails the current match path).
+     (c) A data ] in a character class must be notated as \] because if the
+         first data character in a class is ], it defines an empty class. (In
+         Perl it is not possible to have an empty class.) The empty class []
+         never matches; it forces failure and is equivalent to (*FAIL) or (?!).
+         The negative empty class [^] matches any one character, independently
+         of the DOTALL setting.
+. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
+     non-existent subpattern following a character class starting with ']' and
+     containing () gave an internal compiling error instead of "reference to
+     non-existent subpattern". Fortunately, when the pattern did exist, the
+     compiled code was correct. (When scanning forwards to check for the
+     existencd of the subpattern, it was treating the data ']' as terminating
+     the class, so got the count wrong. When actually compiling, the reference
+     was subsequently set up correctly.)
+. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
+     it was being rejected as not supported by pcre_dfa_exec(), even though
+     other assertions are supported. I have made pcre_dfa_exec() support
+     (*FAIL).
+. The implementation of 13c above involved the invention of a new opcode,
+     OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
+     cannot be changed at match time, I realized I could make a small
+     improvement to matching performance by compiling OP_ALLANY instead of
+     OP_ANY for "." when DOTALL was set, and then removing the runtime tests
+     on the OP_ANY path.
+. Compiling pcretest on Windows with readline support failed without the
+     following two fixes: (1) Make the unistd.h include conditional on
+     HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
+. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
+     ncurses library to be included for pcretest when ReadLine support is
+     requested, but also to allow for it to be overridden. This patch came from
+     Daniel Bergstr�m.
+. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
+     as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
+     any errors with the current Unicode tables. Thanks to Peter Kankowski for
+     spotting this.
+ Version 7.6 28-Jan-08
  ---------------------
 .  A character class containing a very large number of characters with
      codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
      overflow.
 .  Patch to cut out the "long long" test in pcrecpp_unittest when
      HAVE_LONG_LONG is not defined.
 .  Applied Christian Ehrlicher's patch to update the CMake build files to
      bring them up to date and include new features. This patch includes:
      - Fixed PH's badly added libz and libbz2 support.
      - Fixed a problem with static linking.
-     - Added pcredemo.
+     - Added pcredemo. [But later removed - see 7 below.]
      - Fixed dftables problem and added an option.
      - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
          HAVE_LONG_LONG.
      - Added readline support for pcretest.
      - Added an listing of the option settings after cmake has run.
-.  A user submitted a patch to Makefile that makes it easy to created a dll
+.  A user submitted a patch to Makefile that makes it easy to create
-     under mingw. I added stuff to Makefile.am that cause it to include this
+     "pcre.dll" under mingw when using Configure/Make. I added stuff to
-     special target, without affecting anything else.
+     Makefile.am that cause it to include this special target, without
+     affecting anything else. Note that the same mingw target plus all
+     the other distribution libraries and programs are now supported
+     when configuring with CMake (see 6 below) instead of with
+     Configure/Make.
+.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
+     This is an attempt to solve the reported problem "pcrecpp::no_arg is not
+     exported in the Windows port". It has not yet been confirmed that the patch
+     solves the problem, but it does no harm.
+.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
+     NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
+     with CMake, and also correct the comment about stack recursion.
+.  Remove the automatic building of pcredemo from the ./configure system and
+     from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
+     of a program that users should build themselves after PCRE is installed, so
+     building it automatically is not really right. What is more, it gave
+     trouble in some build environments.
+.  Further tidies to CMakeLists.txt from Sheri and Christian.
  Version 7.5 10-Jan-08
  ---------------------

 Legend:



Removed from v.307
 


changed lines


 
Added in v.497
 Legend:



Removed from v.307
 


changed lines


 
Added in v.497
-Removed from v.307
+Added in v.497

	ViewVC Help
Powered by ViewVC 1.1.5