ViewVC logotype

Diff of /code/tags/pcre-3.5/ChangeLog

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

revision 27 by nigel, Sat Feb 24 21:38:49 2007 UTC revision 43 by nigel, Sat Feb 24 21:39:21 2007 UTC
# Line 2  ChangeLog for PCRE Line 2  ChangeLog for PCRE
2  ------------------  ------------------
5    Version 3.0 01-Feb-00
6    ---------------------
8    1. Add support for the /+ modifier to perltest (to output $` like it does in
9    pcretest).
11    2. Add support for the /g modifier to perltest.
13    3. Fix pcretest so that it behaves even more like Perl for /g when the pattern
14    matches null strings.
16    4. Fix perltest so that it doesn't do unwanted things when fed an empty
17    pattern. Perl treats empty patterns specially - it reuses the most recent
18    pattern, which is not what we want. Replace // by /(?#)/ in order to avoid this
19    effect.
21    5. The POSIX interface was broken in that it was just handing over the POSIX
22    captured string vector to pcre_exec(), but (since release 2.00) PCRE has
23    required a bigger vector, with some working space on the end. This means that
24    the POSIX wrapper now has to get and free some memory, and copy the results.
26    6. Added some simple autoconf support, placing the test data and the
27    documentation in separate directories, re-organizing some of the
28    information files, and making it build pcre-config (a GNU standard). Also added
29    libtool support for building PCRE as a shared library, which is now the
30    default.
32    7. Got rid of the leading zero in the definition of PCRE_MINOR because 08 and
33    09 are not valid octal constants. Single digits will be used for minor values
34    less than 10.
36    8. Defined REG_EXTENDED and REG_NOSUB as zero in the POSIX header, so that
37    existing programs that set these in the POSIX interface can use PCRE without
38    modification.
40    9. Added a new function, pcre_fullinfo() with an extensible interface. It can
41    return all that pcre_info() returns, plus additional data. The pcre_info()
42    function is retained for compatibility, but is considered to be obsolete.
44    10. Added experimental recursion feature (?R) to handle one common case that
45    Perl 5.6 will be able to do with (?p{...}).
47    11. Added support for POSIX character classes like [:alpha:], which Perl is
48    adopting.
51    Version 2.08 31-Aug-99
52    ----------------------
54    1. When startoffset was not zero and the pattern began with ".*", PCRE was not
55    trying to match at the startoffset position, but instead was moving forward to
56    the next newline as if a previous match had failed.
58    2. pcretest was not making use of PCRE_NOTEMPTY when repeating for /g and /G,
59    and could get into a loop if a null string was matched other than at the start
60    of the subject.
62    3. Added definitions of PCRE_MAJOR and PCRE_MINOR to pcre.h so the version can
63    be distinguished at compile time, and for completeness also added PCRE_DATE.
65    5. Added Paul Sokolovsky's minor changes to make it easy to compile a Win32 DLL
66    in GnuWin32 environments.
69    Version 2.07 29-Jul-99
70    ----------------------
72    1. The documentation is now supplied in plain text form and HTML as well as in
73    the form of man page sources.
75    2. C++ compilers don't like assigning (void *) values to other pointer types.
76    In particular this affects malloc(). Although there is no problem in Standard
77    C, I've put in casts to keep C++ compilers happy.
79    3. Typo on pcretest.c; a cast of (unsigned char *) in the POSIX regexec() call
80    should be (const char *).
82    4. If NOPOSIX is defined, pcretest.c compiles without POSIX support. This may
83    be useful for non-Unix systems who don't want to bother with the POSIX stuff.
84    However, I haven't made this a standard facility. The documentation doesn't
85    mention it, and the Makefile doesn't support it.
87    5. The Makefile now contains an "install" target, with editable destinations at
88    the top of the file. The pcretest program is not installed.
90    6. pgrep -V now gives the PCRE version number and date.
92    7. Fixed bug: a zero repetition after a literal string (e.g. /abcde{0}/) was
93    causing the entire string to be ignored, instead of just the last character.
95    8. If a pattern like /"([^\\"]+|\\.)*"/ is applied in the normal way to a
96    non-matching string, it can take a very, very long time, even for strings of
97    quite modest length, because of the nested recursion. PCRE now does better in
98    some of these cases. It does this by remembering the last required literal
99    character in the pattern, and pre-searching the subject to ensure it is present
100    before running the real match. In other words, it applies a heuristic to detect
101    some types of certain failure quickly, and in the above example, if presented
102    with a string that has no trailing " it gives "no match" very quickly.
104    9. A new runtime option PCRE_NOTEMPTY causes null string matches to be ignored;
105    other alternatives are tried instead.
108    Version 2.06 09-Jun-99
109    ----------------------
111    1. Change pcretest's output for amount of store used to show just the code
112    space, because the remainder (the data block) varies in size between 32-bit and
113    64-bit systems.
115    2. Added an extra argument to pcre_exec() to supply an offset in the subject to
116    start matching at. This allows lookbehinds to work when searching for multiple
117    occurrences in a string.
119    3. Added additional options to pcretest for testing multiple occurrences:
121       /+   outputs the rest of the string that follows a match
122       /g   loops for multiple occurrences, using the new startoffset argument
123       /G   loops for multiple occurrences by passing an incremented pointer
125    4. PCRE wasn't doing the "first character" optimization for patterns starting
126    with \b or \B, though it was doing it for other lookbehind assertions. That is,
127    it wasn't noticing that a match for a pattern such as /\bxyz/ has to start with
128    the letter 'x'. On long subject strings, this gives a significant speed-up.
131    Version 2.05 21-Apr-99
132    ----------------------
134    1. Changed the type of magic_number from int to long int so that it works
135    properly on 16-bit systems.
137    2. Fixed a bug which caused patterns starting with .* not to work correctly
138    when the subject string contained newline characters. PCRE was assuming
139    anchoring for such patterns in all cases, which is not correct because .* will
140    not pass a newline unless PCRE_DOTALL is set. It now assumes anchoring only if
141    DOTALL is set at top level; otherwise it knows that patterns starting with .*
142    must be retried after every newline in the subject.
145    Version 2.04 18-Feb-99
146    ----------------------
148    1. For parenthesized subpatterns with repeats whose minimum was zero, the
149    computation of the store needed to hold the pattern was incorrect (too large).
150    If such patterns were nested a few deep, this could multiply and become a real
151    problem.
153    2. Added /M option to pcretest to show the memory requirement of a specific
154    pattern. Made -m a synonym of -s (which does this globally) for compatibility.
156    3. Subpatterns of the form (regex){n,m} (i.e. limited maximum) were being
157    compiled in such a way that the backtracking after subsequent failure was
158    pessimal. Something like (a){0,3} was compiled as (a)?(a)?(a)? instead of
159    ((a)((a)(a)?)?)? with disastrous performance if the maximum was of any size.
162    Version 2.03 02-Feb-99
163    ----------------------
165    1. Fixed typo and small mistake in man page.
167    2. Added 4th condition (GPL supersedes if conflict) and created separate
168    LICENCE file containing the conditions.
170    3. Updated pcretest so that patterns such as /abc\/def/ work like they do in
171    Perl, that is the internal \ allows the delimiter to be included in the
172    pattern. Locked out the use of \ as a delimiter. If \ immediately follows
173    the final delimiter, add \ to the end of the pattern (to test the error).
175    4. Added the convenience functions for extracting substrings after a successful
176    match. Updated pcretest to make it able to test these functions.
179  Version 2.02 14-Jan-99  Version 2.02 14-Jan-99
180  ----------------------  ----------------------

Removed from v.27  
changed lines
  Added in v.43

  ViewVC Help
Powered by ViewVC 1.1.5