/[pcre]/code/tags/pcre-3.2/ChangeLog
ViewVC logotype

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

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

revision 29 by nigel, Sat Feb 24 21:38:53 2007 UTC revision 41 by nigel, Sat Feb 24 21:39:17 2007 UTC
# Line 2  ChangeLog for PCRE Line 2  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    
5    Version 2.09 14-Sep-99
6    ----------------------
7    
8    1. Add support for the /+ modifier to perltest (to output $` like it does in
9    pcretest).
10    
11    2. Add support for the /g modifier to perltest.
12    
13    3. Fix pcretest so that it behaves even more like Perl for /g when the pattern
14    matches null strings.
15    
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.
20    
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.
25    
26    
27    Version 2.08 31-Aug-99
28    ----------------------
29    
30    1. When startoffset was not zero and the pattern began with ".*", PCRE was not
31    trying to match at the startoffset position, but instead was moving forward to
32    the next newline as if a previous match had failed.
33    
34    2. pcretest was not making use of PCRE_NOTEMPTY when repeating for /g and /G,
35    and could get into a loop if a null string was matched other than at the start
36    of the subject.
37    
38    3. Added definitions of PCRE_MAJOR and PCRE_MINOR to pcre.h so the version can
39    be distinguished at compile time, and for completeness also added PCRE_DATE.
40    
41    5. Added Paul Sokolovsky's minor changes to make it easy to compile a Win32 DLL
42    in GnuWin32 environments.
43    
44    
45    Version 2.07 29-Jul-99
46    ----------------------
47    
48    1. The documentation is now supplied in plain text form and HTML as well as in
49    the form of man page sources.
50    
51    2. C++ compilers don't like assigning (void *) values to other pointer types.
52    In particular this affects malloc(). Although there is no problem in Standard
53    C, I've put in casts to keep C++ compilers happy.
54    
55    3. Typo on pcretest.c; a cast of (unsigned char *) in the POSIX regexec() call
56    should be (const char *).
57    
58    4. If NOPOSIX is defined, pcretest.c compiles without POSIX support. This may
59    be useful for non-Unix systems who don't want to bother with the POSIX stuff.
60    However, I haven't made this a standard facility. The documentation doesn't
61    mention it, and the Makefile doesn't support it.
62    
63    5. The Makefile now contains an "install" target, with editable destinations at
64    the top of the file. The pcretest program is not installed.
65    
66    6. pgrep -V now gives the PCRE version number and date.
67    
68    7. Fixed bug: a zero repetition after a literal string (e.g. /abcde{0}/) was
69    causing the entire string to be ignored, instead of just the last character.
70    
71    8. If a pattern like /"([^\\"]+|\\.)*"/ is applied in the normal way to a
72    non-matching string, it can take a very, very long time, even for strings of
73    quite modest length, because of the nested recursion. PCRE now does better in
74    some of these cases. It does this by remembering the last required literal
75    character in the pattern, and pre-searching the subject to ensure it is present
76    before running the real match. In other words, it applies a heuristic to detect
77    some types of certain failure quickly, and in the above example, if presented
78    with a string that has no trailing " it gives "no match" very quickly.
79    
80    9. A new runtime option PCRE_NOTEMPTY causes null string matches to be ignored;
81    other alternatives are tried instead.
82    
83    
84    Version 2.06 09-Jun-99
85    ----------------------
86    
87    1. Change pcretest's output for amount of store used to show just the code
88    space, because the remainder (the data block) varies in size between 32-bit and
89    64-bit systems.
90    
91    2. Added an extra argument to pcre_exec() to supply an offset in the subject to
92    start matching at. This allows lookbehinds to work when searching for multiple
93    occurrences in a string.
94    
95    3. Added additional options to pcretest for testing multiple occurrences:
96    
97       /+   outputs the rest of the string that follows a match
98       /g   loops for multiple occurrences, using the new startoffset argument
99       /G   loops for multiple occurrences by passing an incremented pointer
100    
101    4. PCRE wasn't doing the "first character" optimization for patterns starting
102    with \b or \B, though it was doing it for other lookbehind assertions. That is,
103    it wasn't noticing that a match for a pattern such as /\bxyz/ has to start with
104    the letter 'x'. On long subject strings, this gives a significant speed-up.
105    
106    
107    Version 2.05 21-Apr-99
108    ----------------------
109    
110    1. Changed the type of magic_number from int to long int so that it works
111    properly on 16-bit systems.
112    
113    2. Fixed a bug which caused patterns starting with .* not to work correctly
114    when the subject string contained newline characters. PCRE was assuming
115    anchoring for such patterns in all cases, which is not correct because .* will
116    not pass a newline unless PCRE_DOTALL is set. It now assumes anchoring only if
117    DOTALL is set at top level; otherwise it knows that patterns starting with .*
118    must be retried after every newline in the subject.
119    
120    
121    Version 2.04 18-Feb-99
122    ----------------------
123    
124    1. For parenthesized subpatterns with repeats whose minimum was zero, the
125    computation of the store needed to hold the pattern was incorrect (too large).
126    If such patterns were nested a few deep, this could multiply and become a real
127    problem.
128    
129    2. Added /M option to pcretest to show the memory requirement of a specific
130    pattern. Made -m a synonym of -s (which does this globally) for compatibility.
131    
132    3. Subpatterns of the form (regex){n,m} (i.e. limited maximum) were being
133    compiled in such a way that the backtracking after subsequent failure was
134    pessimal. Something like (a){0,3} was compiled as (a)?(a)?(a)? instead of
135    ((a)((a)(a)?)?)? with disastrous performance if the maximum was of any size.
136    
137    
138  Version 2.03 02-Feb-99  Version 2.03 02-Feb-99
139  ----------------------  ----------------------
140    
141  1. Fixed typo and small mistake in man page.  1. Fixed typo and small mistake in man page.
142    
143  2. Added 4th condition (GPL supersedes) and created separate LICENCE file.  2. Added 4th condition (GPL supersedes if conflict) and created separate
144    LICENCE file containing the conditions.
145    
146  3. Updated pcretest so that patterns such as /abc\/def/ work like they do in  3. Updated pcretest so that patterns such as /abc\/def/ work like they do in
147  Perl, that is the internal \ allows the delimiter to be included in the  Perl, that is the internal \ allows the delimiter to be included in the
Legend:
Removed from v.29  
changed lines
  Added in v.41
  ViewVC Help
Powered by ViewVC 1.1.5