/[pcre]/code/trunk/ChangeLog

Diff of /code/trunk/ChangeLog

Parent Directory | Revision Log | View Patch Patch

-revision 69 by nigel,
Sat Feb 24 21:40:18 2007 UTC
+revision 79 by nigel,
Sat Feb 24 21:40:52 2007 UTC
 Line 1
  ChangeLog for PCRE
  ------------------
+ Version 6.1 21-Jun-05
+ ---------------------
+. There was one reference to the variable "posix" in pcretest.c that was not
+     surrounded by "#if !defined NOPOSIX".
+. Make it possible to compile pcretest without DFA support, UTF8 support, or
+     the cross-check on the old pcre_info() function, for the benefit of the
+     cut-down version of PCRE that is currently imported into Exim.
+. A (silly) pattern starting with (?i)(?-i) caused an internal space
+     allocation error. I've done the easy fix, which wastes 2 bytes for sensible
+     patterns that start (?i) but I don't think that matters. The use of (?i) is
+     just an example; this all applies to the other options as well.
+. Since libtool seems to echo the compile commands it is issuing, the output
+     from "make" can be reduced a bit by putting "@" in front of each libtool
+     compile command.
+. Patch from the folks at Google for configure.in to be a bit more thorough
+     in checking for a suitable C++ installation before trying to compile the
+     C++ stuff. This should fix a reported problem when a compiler was present,
+     but no suitable headers.
+. The man pages all had just "PCRE" as their title. I have changed them to
+     be the relevant file name. I have also arranged that these names are
+     retained in the file doc/pcre.txt, which is a concatenation in text format
+     of all the man pages except the little individual ones for each function.
+. The NON-UNIX-USE file had not been updated for the different set of source
+     files that come with release 6. I also added a few comments about the C++
+     wrapper.
+ Version 6.0 07-Jun-05
+ ---------------------
+. Some minor internal re-organization to help with my DFA experiments.
+. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
+     didn't matter for the library itself when fully configured, but did matter
+     when compiling without UCP support, or within Exim, where the ucp files are
+     not imported.
+. Refactoring of the library code to split up the various functions into
+     different source modules. The addition of the new DFA matching code (see
+     below) to a single monolithic source would have made it really too
+     unwieldy, quite apart from causing all the code to be include in a
+     statically linked application, when only some functions are used. This is
+     relevant even without the DFA addition now that patterns can be compiled in
+     one application and matched in another.
+     The downside of splitting up is that there have to be some external
+     functions and data tables that are used internally in different modules of
+     the library but which are not part of the API. These have all had their
+     names changed to start with "_pcre_" so that they are unlikely to clash
+     with other external names.
+. Added an alternate matching function, pcre_dfa_exec(), which matches using
+     a different (DFA) algorithm. Although it is slower than the original
+     function, it does have some advantages for certain types of matching
+     problem.
+. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
+     including restarting after a partial match.
+. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
+     defined when compiling for Windows was sent to me. I have put it into the
+     code, though I have no means of testing or verifying it.
+. Added the pcre_refcount() auxiliary function.
+. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
+     match before or at the first newline in the subject string. In pcretest,
+     the /f option on a pattern can be used to set this.
+. A repeated \w when used in UTF-8 mode with characters greater than 256
+     would behave wrongly. This has been present in PCRE since release 4.0.
+. A number of changes to the pcregrep command:
+     (a) Refactored how -x works; insert ^(...)$ instead of setting
+         PCRE_ANCHORED and checking the length, in preparation for adding
+         something similar for -w.
+     (b) Added the -w (match as a word) option.
+     (c) Refactored the way lines are read and buffered so as to have more
+         than one at a time available.
+     (d) Implemented a pcregrep test script.
+     (e) Added the -M (multiline match) option. This allows patterns to match
+         over several lines of the subject. The buffering ensures that at least
+K, or the rest of the document (whichever is the shorter) is available
+         for matching (and similarly the previous 8K for lookbehind assertions).
+     (f) Changed the --help output so that it now says
+           -w, --word-regex(p)
+         instead of two lines, one with "regex" and the other with "regexp"
+         because that confused at least one person since the short forms are the
+         same. (This required a bit of code, as the output is generated
+         automatically from a table. It wasn't just a text change.)
+     (g) -- can be used to terminate pcregrep options if the next thing isn't an
+         option but starts with a hyphen. Could be a pattern or a path name
+         starting with a hyphen, for instance.
+     (h) "-" can be given as a file name to represent stdin.
+     (i) When file names are being printed, "(standard input)" is used for
+         the standard input, for compatibility with GNU grep. Previously
+         "<stdin>" was used.
+     (j) The option --label=xxx can be used to supply a name to be used for
+         stdin when file names are being printed. There is no short form.
+     (k) Re-factored the options decoding logic because we are going to add
+         two more options that take data. Such options can now be given in four
+         different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
+     (l) Added the -A, -B, and -C options for requesting that lines of context
+         around matches be printed.
+     (m) Added the -L option to print the names of files that do not contain
+         any matching lines, that is, the complement of -l.
+     (n) The return code is 2 if any file cannot be opened, but pcregrep does
+         continue to scan other files.
+     (o) The -s option was incorrectly implemented. For compatibility with other
+         greps, it now suppresses the error message for a non-existent or non-
+         accessible file (but not the return code). There is a new option called
+         -q that suppresses the output of matching lines, which was what -s was
+         previously doing.
+     (p) Added --include and --exclude options to specify files for inclusion
+         and exclusion when recursing.
+. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
+     Hopefully, it now does.
+. Missing cast in pcre_study().
+. Added an "uninstall" target to the makefile.
+. Replaced "extern" in the function prototypes in Makefile.in with
+     "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
+     world, but is set differently for Windows.
+. Added a second compiling function called pcre_compile2(). The only
+     difference is that it has an extra argument, which is a pointer to an
+     integer error code. When there is a compile-time failure, this is set
+     non-zero, in addition to the error test pointer being set to point to an
+     error message. The new argument may be NULL if no error number is required
+     (but then you may as well call pcre_compile(), which is now just a
+     wrapper). This facility is provided because some applications need a
+     numeric error indication, but it has also enabled me to tidy up the way
+     compile-time errors are handled in the POSIX wrapper.
+. Added VPATH=.libs to the makefile; this should help when building with one
+     prefix path and installing with another. (Or so I'm told by someone who
+     knows more about this stuff than I do.)
+. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
+     passes PCRE_DOTALL to the pcre_compile() function, making the "." character
+     match everything, including newlines. This is not POSIX-compatible, but
+     somebody wanted the feature. From pcretest it can be activated by using
+     both the P and the s flags.
+. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
+. libpcre.pc was being incorrectly installed as executable.
+. A couple of places in pcretest check for end-of-line by looking for '\n';
+     it now also looks for '\r' so that it will work unmodified on Windows.
+. Added Google's contributed C++ wrapper to the distribution.
+. Added some untidy missing memory free() calls in pcretest, to keep
+     Electric Fence happy when testing.
+ Version 5.0 13-Sep-04
+ ---------------------
+. Internal change: literal characters are no longer packed up into items
+     containing multiple characters in a single byte-string. Each character
+     is now matched using a separate opcode. However, there may be more than one
+     byte in the character in UTF-8 mode.
+. The pcre_callout_block structure has two new fields: pattern_position and
+     next_item_length. These contain the offset in the pattern to the next match
+     item, and its length, respectively.
+. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
+     insertion of callouts before each pattern item. Added the /C option to
+     pcretest to make use of this.
+. On the advice of a Windows user, the lines
+       #if defined(_WIN32) || defined(WIN32)
+       _setmode( _fileno( stdout ), 0x8000 );
+       #endif  /* defined(_WIN32) || defined(WIN32) */
+     have been added to the source of pcretest. This apparently does useful
+     magic in relation to line terminators.
+. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
+     for the benefit of those environments where the "b" makes a difference.
+. The icc compiler has the same options as gcc, but "configure" doesn't seem
+     to know about it. I have put a hack into configure.in that adds in code
+     to set GCC=yes if CC=icc. This seems to end up at a point in the
+     generated configure script that is early enough to affect the setting of
+     compiler options, which is what is needed, but I have no means of testing
+     whether it really works. (The user who reported this had patched the
+     generated configure script, which of course I cannot do.)
+     LATER: After change 22 below (new libtool files), the configure script
+     seems to know about icc (and also ecc). Therefore, I have commented out
+     this hack in configure.in.
+. Added support for pkg-config (2 patches were sent in).
+. Negated POSIX character classes that used a combination of internal tables
+     were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
+     [[:^ascii]]. Typically, they would match almost any characters. The other
+     POSIX classes were not broken in this way.
+. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
+     to find the match, as PCRE was deluded into thinking that the match had to
+     start at the start point or following a newline. The same bug applied to
+     patterns with negative forward assertions or any backward assertions
+     preceding ".*" at the start, unless the pattern required a fixed first
+     character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
+. In UTF-8 mode, when moving forwards in the subject after a failed match
+     starting at the last subject character, bytes beyond the end of the subject
+     string were read.
+. Renamed the variable "class" as "classbits" to make life easier for C++
+     users. (Previously there was a macro definition, but it apparently wasn't
+     enough.)
+. Added the new field "tables" to the extra data so that tables can be passed
+     in at exec time, or the internal tables can be re-selected. This allows
+     a compiled regex to be saved and re-used at a later time by a different
+     program that might have everything at different addresses.
+. Modified the pcre-config script so that, when run on Solaris, it shows a
+     -R library as well as a -L library.
+. The debugging options of pcretest (-d on the command line or D on a
+     pattern) showed incorrect output for anything following an extended class
+     that contained multibyte characters and which was followed by a quantifier.
+. Added optional support for general category Unicode character properties
+     via the \p, \P, and \X escapes. Unicode property support implies UTF-8
+     support. It adds about 90K to the size of the library. The meanings of the
+     inbuilt class escapes such as \d and \s have NOT been changed.
+. Updated pcredemo.c to include calls to free() to release the memory for the
+     compiled pattern.
+. The generated file chartables.c was being created in the source directory
+     instead of in the building directory. This caused the build to fail if the
+     source directory was different from the building directory, and was
+     read-only.
+. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
+     file. No doubt somebody will tell me if they don't make sense... Also added
+     Dan Mooney's comments about building on OpenVMS.
+. Added support for partial matching via the PCRE_PARTIAL option for
+     pcre_exec() and the \P data escape in pcretest.
+. Extended pcretest with 3 new pattern features:
+     (i)   A pattern option of the form ">rest-of-line" causes pcretest to
+           write the compiled pattern to the file whose name is "rest-of-line".
+           This is a straight binary dump of the data, with the saved pointer to
+           the character tables forced to be NULL. The study data, if any, is
+           written too. After writing, pcretest reads a new pattern.
+     (ii)  If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
+           compiled pattern from the given file. There must not be any
+           occurrences of "<" in the file name (pretty unlikely); if there are,
+           pcretest will instead treat the initial "<" as a pattern delimiter.
+           After reading in the pattern, pcretest goes on to read data lines as
+           usual.
+     (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
+           and 16-bit fields in a compiled pattern, to simulate a pattern that
+           was compiled on a host of opposite endianness.
+. The pcre-exec() function can now cope with patterns that were compiled on
+     hosts of opposite endianness, with this restriction:
+       As for any compiled expression that is saved and used later, the tables
+       pointer field cannot be preserved; the extra_data field in the arguments
+       to pcre_exec() should be used to pass in a tables address if a value
+       other than the default internal tables were used at compile time.
+. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
+     now diagnosed as an error. Previously, most of the time, a negative number
+     would have been treated as zero, but if in addition "ovector" was passed as
+     NULL, a crash could occur.
+. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
+     new versions from the libtool 1.5 distribution (the last one is a copy of
+     a file called libtool.m4). This seems to have fixed the need to patch
+     "configure" to support Darwin 1.3 (which I used to do). However, I still
+     had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
+     workstation).
+. Changed the PCRE licence to be the more standard "BSD" licence.
+ Version 4.5 01-Dec-03
+ ---------------------
+. There has been some re-arrangement of the code for the match() function so
+     that it can be compiled in a version that does not call itself recursively.
+     Instead, it keeps those local variables that need separate instances for
+     each "recursion" in a frame on the heap, and gets/frees frames whenever it
+     needs to "recurse". Keeping track of where control must go is done by means
+     of setjmp/longjmp. The whole thing is implemented by a set of macros that
+     hide most of the details from the main code, and operates only if
+     NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
+     "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
+     operating.
+     To make it easier for callers to provide specially tailored get/free
+     functions for this usage, two new functions, pcre_stack_malloc, and
+     pcre_stack_free, are used. They are always called in strict stacking order,
+     and the size of block requested is always the same.
+     The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
+     PCRE has been compiled to use the stack or the heap for recursion. The
+     -C option of pcretest uses this to show which version is compiled.
+     A new data escape \S, is added to pcretest; it causes the amounts of store
+     obtained and freed by both kinds of malloc/free at match time to be added
+     to the output.
+. Changed the locale test to use "fr_FR" instead of "fr" because that's
+     what's available on my current Linux desktop machine.
+. When matching a UTF-8 string, the test for a valid string at the start has
+     been extended. If start_offset is not zero, PCRE now checks that it points
+     to a byte that is the start of a UTF-8 character. If not, it returns
+     PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
+     this is necessary because there may be backward assertions in the pattern.
+     When matching the same subject several times, it may save resources to use
+     PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
+. The code for checking the validity of UTF-8 strings has been tightened so
+     that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
+     containing "overlong sequences".
+. Fixed a bug (appearing twice) that I could not find any way of exploiting!
+     I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
+     should have been "&", but it just so happened that all the cases this let
+     through by mistake were picked up later in the function.
+. I had used a variable called "isblank" - this is a C99 function, causing
+     some compilers to warn. To avoid this, I renamed it (as "blankclass").
+. Cosmetic: (a) only output another newline at the end of pcretest if it is
+     prompting; (b) run "./pcretest /dev/null" at the start of the test script
+     so the version is shown; (c) stop "make test" echoing "./RunTest".
+. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
+. The prototype for memmove() for systems that don't have it was using
+     size_t, but the inclusion of the header that defines size_t was later. I've
+     moved the #includes for the C headers earlier to avoid this.
+. Added some adjustments to the code to make it easier to compiler on certain
+     special systems:
+       (a) Some "const" qualifiers were missing.
+       (b) Added the macro EXPORT before all exported functions; by default this
+           is defined to be empty.
+       (c) Changed the dftables auxiliary program (that builds chartables.c) so
+           that it reads its output file name as an argument instead of writing
+           to the standard output and assuming this can be redirected.
+. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
+     class containing characters with values greater than 255, PCRE compilation
+     went into a loop.
+. A recursive reference to a subpattern that was within another subpattern
+     that had a minimum quantifier of zero caused PCRE to crash. For example,
+     (x(y(?2))z)? provoked this bug with a subject that got as far as the
+     recursion. If the recursively-called subpattern itself had a zero repeat,
+     that was OK.
+. In pcretest, the buffer for reading a data line was set at 30K, but the
+     buffer into which it was copied (for escape processing) was still set at
+, so long lines caused crashes.
+. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
+     "internal error: code overflow...". This applied to any character class
+     that was followed by a possessive quantifier.
+. Modified the Makefile to add libpcre.la as a prerequisite for
+     libpcreposix.la because I was told this is needed for a parallel build to
+     work.
+. If a pattern that contained .* following optional items at the start was
+     studied, the wrong optimizing data was generated, leading to matching
+     errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
+     matching string must start with a or b or c. The correct conclusion for
+     this pattern is that a match can start with any character.
+ Version 4.4 13-Aug-03
+ ---------------------
+. In UTF-8 mode, a character class containing characters with values between
+and 255 was not handled correctly if the compiled pattern was studied.
+     In fixing this, I have also improved the studying algorithm for such
+     classes (slightly).
+. Three internal functions had redundant arguments passed to them. Removal
+     might give a very teeny performance improvement.
+. Documentation bug: the value of the capture_top field in a callout is *one
+     more than* the number of the hightest numbered captured substring.
+. The Makefile linked pcretest and pcregrep with -lpcre, which could result
+     in incorrectly linking with a previously installed version. They now link
+     explicitly with libpcre.la.
+. configure.in no longer needs to recognize Cygwin specially.
+. A problem in pcre.in for Windows platforms is fixed.
+. If a pattern was successfully studied, and the -d (or /D) flag was given to
+     pcretest, it used to include the size of the study block as part of its
+     output. Unfortunately, the structure contains a field that has a different
+     size on different hardware architectures. This meant that the tests that
+     showed this size failed. As the block is currently always of a fixed size,
+     this information isn't actually particularly useful in pcretest output, so
+     I have just removed it.
+. Three pre-processor statements accidentally did not start in column 1.
+     Sadly, there are *still* compilers around that complain, even though
+     standard C has not required this for well over a decade. Sigh.
+. In pcretest, the code for checking callouts passed small integers in the
+     callout_data field, which is a void * field. However, some picky compilers
+     complained about the casts involved for this on 64-bit systems. Now
+     pcretest passes the address of the small integer instead, which should get
+     rid of the warnings.
+. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
+     both compile and run time, and gives an error if an invalid UTF-8 sequence
+     is found. There is a option for disabling this check in cases where the
+     string is known to be correct and/or the maximum performance is wanted.
+. In response to a bug report, I changed one line in Makefile.in from
+         -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
+     to
+         -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \
+     to look similar to other lines, but I have no way of telling whether this
+     is the right thing to do, as I do not use Windows. No doubt I'll get told
+     if it's wrong...
  Version 4.3 21-May-03
  ---------------------

 Legend:



Removed from v.69
 


changed lines


 
Added in v.79
 Legend:



Removed from v.69
 


changed lines


 
Added in v.79
-Removed from v.69
+Added in v.79

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12