/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 3 by nigel, Sat Feb 24 21:38:01 2007 UTC revision 37 by nigel, Sat Feb 24 21:39:09 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    
5    Version 2.07 29-Jul-99
6    ----------------------
7    
8    1. The documentation is now supplied in plain text form and HTML as well as in
9    the form of man page sources.
10    
11    2. C++ compilers don't like assigning (void *) values to other pointer types.
12    In particular this affects malloc(). Although there is no problem in Standard
13    C, I've put in casts to keep C++ compilers happy.
14    
15    3. Typo on pcretest.c; a cast of (unsigned char *) in the POSIX regexec() call
16    should be (const char *).
17    
18    4. If NOPOSIX is defined, pcretest.c compiles without POSIX support. This may
19    be useful for non-Unix systems who don't want to bother with the POSIX stuff.
20    However, I haven't made this a standard facility. The documentation doesn't
21    mention it, and the Makefile doesn't support it.
22    
23    5. The Makefile now contains an "install" target, with editable destinations at
24    the top of the file. The pcretest program is not installed.
25    
26    6. pgrep -V now gives the PCRE version number and date.
27    
28    7. Fixed bug: a zero repetition after a literal string (e.g. /abcde{0}/) was
29    causing the entire string to be ignored, instead of just the last character.
30    
31    8. If a pattern like /"([^\\"]+|\\.)*"/ is applied in the normal way to a
32    non-matching string, it can take a very, very long time, even for strings of
33    quite modest length, because of the nested recursion. PCRE now does better in
34    some of these cases. It does this by remembering the last required literal
35    character in the pattern, and pre-searching the subject to ensure it is present
36    before running the real match. In other words, it applies a heuristic to detect
37    some types of certain failure quickly, and in the above example, if presented
38    with a string that has no trailing " it gives "no match" very quickly.
39    
40    9. A new runtime option PCRE_NOTEMPTY causes null string matches to be ignored;
41    other alternatives are tried instead.
42    
43    
44    Version 2.06 09-Jun-99
45    ----------------------
46    
47    1. Change pcretest's output for amount of store used to show just the code
48    space, because the remainder (the data block) varies in size between 32-bit and
49    64-bit systems.
50    
51    2. Added an extra argument to pcre_exec() to supply an offset in the subject to
52    start matching at. This allows lookbehinds to work when searching for multiple
53    occurrences in a string.
54    
55    3. Added additional options to pcretest for testing multiple occurrences:
56    
57       /+   outputs the rest of the string that follows a match
58       /g   loops for multiple occurrences, using the new startoffset argument
59       /G   loops for multiple occurrences by passing an incremented pointer
60    
61    4. PCRE wasn't doing the "first character" optimization for patterns starting
62    with \b or \B, though it was doing it for other lookbehind assertions. That is,
63    it wasn't noticing that a match for a pattern such as /\bxyz/ has to start with
64    the letter 'x'. On long subject strings, this gives a significant speed-up.
65    
66    
67    Version 2.05 21-Apr-99
68    ----------------------
69    
70    1. Changed the type of magic_number from int to long int so that it works
71    properly on 16-bit systems.
72    
73    2. Fixed a bug which caused patterns starting with .* not to work correctly
74    when the subject string contained newline characters. PCRE was assuming
75    anchoring for such patterns in all cases, which is not correct because .* will
76    not pass a newline unless PCRE_DOTALL is set. It now assumes anchoring only if
77    DOTALL is set at top level; otherwise it knows that patterns starting with .*
78    must be retried after every newline in the subject.
79    
80    
81    Version 2.04 18-Feb-99
82    ----------------------
83    
84    1. For parenthesized subpatterns with repeats whose minimum was zero, the
85    computation of the store needed to hold the pattern was incorrect (too large).
86    If such patterns were nested a few deep, this could multiply and become a real
87    problem.
88    
89    2. Added /M option to pcretest to show the memory requirement of a specific
90    pattern. Made -m a synonym of -s (which does this globally) for compatibility.
91    
92    3. Subpatterns of the form (regex){n,m} (i.e. limited maximum) were being
93    compiled in such a way that the backtracking after subsequent failure was
94    pessimal. Something like (a){0,3} was compiled as (a)?(a)?(a)? instead of
95    ((a)((a)(a)?)?)? with disastrous performance if the maximum was of any size.
96    
97    
98    Version 2.03 02-Feb-99
99    ----------------------
100    
101    1. Fixed typo and small mistake in man page.
102    
103    2. Added 4th condition (GPL supersedes if conflict) and created separate
104    LICENCE file containing the conditions.
105    
106    3. Updated pcretest so that patterns such as /abc\/def/ work like they do in
107    Perl, that is the internal \ allows the delimiter to be included in the
108    pattern. Locked out the use of \ as a delimiter. If \ immediately follows
109    the final delimiter, add \ to the end of the pattern (to test the error).
110    
111    4. Added the convenience functions for extracting substrings after a successful
112    match. Updated pcretest to make it able to test these functions.
113    
114    
115    Version 2.02 14-Jan-99
116    ----------------------
117    
118    1. Initialized the working variables associated with each extraction so that
119    their saving and restoring doesn't refer to uninitialized store.
120    
121    2. Put dummy code into study.c in order to trick the optimizer of the IBM C
122    compiler for OS/2 into generating correct code. Apparently IBM isn't going to
123    fix the problem.
124    
125    3. Pcretest: the timing code wasn't using LOOPREPEAT for timing execution
126    calls, and wasn't printing the correct value for compiling calls. Increased the
127    default value of LOOPREPEAT, and the number of significant figures in the
128    times.
129    
130    4. Changed "/bin/rm" in the Makefile to "-rm" so it works on Windows NT.
131    
132    5. Renamed "deftables" as "dftables" to get it down to 8 characters, to avoid
133    a building problem on Windows NT with a FAT file system.
134    
135    
136    Version 2.01 21-Oct-98
137    ----------------------
138    
139    1. Changed the API for pcre_compile() to allow for the provision of a pointer
140    to character tables built by pcre_maketables() in the current locale. If NULL
141    is passed, the default tables are used.
142    
143    
144    Version 2.00 24-Sep-98
145    ----------------------
146    
147    1. Since the (>?) facility is in Perl 5.005, don't require PCRE_EXTRA to enable
148    it any more.
149    
150    2. Allow quantification of (?>) groups, and make it work correctly.
151    
152    3. The first character computation wasn't working for (?>) groups.
153    
154    4. Correct the implementation of \Z (it is permitted to match on the \n at the
155    end of the subject) and add 5.005's \z, which really does match only at the
156    very end of the subject.
157    
158    5. Remove the \X "cut" facility; Perl doesn't have it, and (?> is neater.
159    
160    6. Remove the ability to specify CASELESS, MULTILINE, DOTALL, and
161    DOLLAR_END_ONLY at runtime, to make it possible to implement the Perl 5.005
162    localized options. All options to pcre_study() were also removed.
163    
164    7. Add other new features from 5.005:
165    
166       $(?<=           positive lookbehind
167       $(?<!           negative lookbehind
168       (?imsx-imsx)    added the unsetting capability
169                       such a setting is global if at outer level; local otherwise
170       (?imsx-imsx:)   non-capturing groups with option setting
171       (?(cond)re|re)  conditional pattern matching
172    
173       A backreference to itself in a repeated group matches the previous
174       captured string.
175    
176    8. General tidying up of studying (both automatic and via "study")
177    consequential on the addition of new assertions.
178    
179    9. As in 5.005, unlimited repeated groups that could match an empty substring
180    are no longer faulted at compile time. Instead, the loop is forcibly broken at
181    runtime if any iteration does actually match an empty substring.
182    
183    10. Include the RunTest script in the distribution.
184    
185    11. Added tests from the Perl 5.005_02 distribution. This showed up a few
186    discrepancies, some of which were old and were also with respect to 5.004. They
187    have now been fixed.
188    
189    
190    Version 1.09 28-Apr-98
191    ----------------------
192    
193    1. A negated single character class followed by a quantifier with a minimum
194    value of one (e.g.  [^x]{1,6}  ) was not compiled correctly. This could lead to
195    program crashes, or just wrong answers. This did not apply to negated classes
196    containing more than one character, or to minima other than one.
197    
198    
199    Version 1.08 27-Mar-98
200    ----------------------
201    
202    1. Add PCRE_UNGREEDY to invert the greediness of quantifiers.
203    
204    2. Add (?U) and (?X) to set PCRE_UNGREEDY and PCRE_EXTRA respectively. The
205    latter must appear before anything that relies on it in the pattern.
206    
207    
208    Version 1.07 16-Feb-98
209    ----------------------
210    
211    1. A pattern such as /((a)*)*/ was not being diagnosed as in error (unlimited
212    repeat of a potentially empty string).
213    
214    
215    Version 1.06 23-Jan-98
216    ----------------------
217    
218    1. Added Markus Oberhumer's little patches for C++.
219    
220    2. Literal strings longer than 255 characters were broken.
221    
222    
223    Version 1.05 23-Dec-97
224    ----------------------
225    
226    1. Negated character classes containing more than one character were failing if
227    PCRE_CASELESS was set at run time.
228    
229    
230    Version 1.04 19-Dec-97
231    ----------------------
232    
233    1. Corrected the man page, where some "const" qualifiers had been omitted.
234    
235    2. Made debugging output print "{0,xxx}" instead of just "{,xxx}" to agree with
236    input syntax.
237    
238    3. Fixed memory leak which occurred when a regex with back references was
239    matched with an offsets vector that wasn't big enough. The temporary memory
240    that is used in this case wasn't being freed if the match failed.
241    
242    4. Tidied pcretest to ensure it frees memory that it gets.
243    
244    5. Temporary memory was being obtained in the case where the passed offsets
245    vector was exactly big enough.
246    
247    6. Corrected definition of offsetof() from change 5 below.
248    
249    7. I had screwed up change 6 below and broken the rules for the use of
250    setjmp(). Now fixed.
251    
252    
253    Version 1.03 18-Dec-97
254    ----------------------
255    
256    1. A erroneous regex with a missing opening parenthesis was correctly
257    diagnosed, but PCRE attempted to access brastack[-1], which could cause crashes
258    on some systems.
259    
260    2. Replaced offsetof(real_pcre, code) by offsetof(real_pcre, code[0]) because
261    it was reported that one broken compiler failed on the former because "code" is
262    also an independent variable.
263    
264    3. The erroneous regex a[]b caused an array overrun reference.
265    
266    4. A regex ending with a one-character negative class (e.g. /[^k]$/) did not
267    fail on data ending with that character. (It was going on too far, and checking
268    the next character, typically a binary zero.) This was specific to the
269    optimized code for single-character negative classes.
270    
271    5. Added a contributed patch from the TIN world which does the following:
272    
273      + Add an undef for memmove, in case the the system defines a macro for it.
274    
275      + Add a definition of offsetof(), in case there isn't one. (I don't know
276        the reason behind this - offsetof() is part of the ANSI standard - but
277        it does no harm).
278    
279      + Reduce the ifdef's in pcre.c using macro DPRINTF, thereby eliminating
280        most of the places where whitespace preceded '#'. I have given up and
281        allowed the remaining 2 cases to be at the margin.
282    
283      + Rename some variables in pcre to eliminate shadowing. This seems very
284        pedantic, but does no harm, of course.
285    
286    6. Moved the call to setjmp() into its own function, to get rid of warnings
287    from gcc -Wall, and avoided calling it at all unless PCRE_EXTRA is used.
288    
289    7. Constructs such as \d{8,} were compiling into the equivalent of
290    \d{8}\d{0,65527} instead of \d{8}\d* which didn't make much difference to the
291    outcome, but in this particular case used more store than had been allocated,
292    which caused the bug to be discovered because it threw up an internal error.
293    
294    8. The debugging code in both pcre and pcretest for outputting the compiled
295    form of a regex was going wrong in the case of back references followed by
296    curly-bracketed repeats.
297    
298    
299    Version 1.02 12-Dec-97
300    ----------------------
301    
302    1. Typos in pcre.3 and comments in the source fixed.
303    
304    2. Applied a contributed patch to get rid of places where it used to remove
305    'const' from variables, and fixed some signed/unsigned and uninitialized
306    variable warnings.
307    
308    3. Added the "runtest" target to Makefile.
309    
310    4. Set default compiler flag to -O2 rather than just -O.
311    
312    
313    Version 1.01 19-Nov-97
314    ----------------------
315    
316    1. PCRE was failing to diagnose unlimited repeat of empty string for patterns
317    like /([ab]*)*/, that is, for classes with more than one character in them.
318    
319    2. Likewise, it wasn't diagnosing patterns with "once-only" subpatterns, such
320    as /((?>a*))*/ (a PCRE_EXTRA facility).
321    
322    
323    Version 1.00 18-Nov-97
324    ----------------------
325    
326    1. Added compile-time macros to support systems such as SunOS4 which don't have
327    memmove() or strerror() but have other things that can be used instead.
328    
329    2. Arranged that "make clean" removes the executables.
330    
331    
332  Version 0.99 27-Oct-97  Version 0.99 27-Oct-97
333  ----------------------  ----------------------
334    

Legend:
Removed from v.3  
changed lines
  Added in v.37

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12