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

Contents of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log


Revision 13 - (show annotations) (download)
Sat Feb 24 21:38:21 2007 UTC (7 years, 8 months ago) by nigel
File size: 10194 byte(s)
Load pcre-1.05 into code/trunk.

1 ChangeLog for PCRE
2 ------------------
3
4
5 Version 1.05 23-Dec-97
6 ----------------------
7
8 1. Negated character classes containing more than one character were failing if
9 PCRE_CASELESS was set at run time.
10
11
12 Version 1.04 19-Dec-97
13 ----------------------
14
15 1. Corrected the man page, where some "const" qualifiers had been omitted.
16
17 2. Made debugging output print "{0,xxx}" instead of just "{,xxx}" to agree with
18 input syntax.
19
20 3. Fixed memory leak which occurred when a regex with back references was
21 matched with an offsets vector that wasn't big enough. The temporary memory
22 that is used in this case wasn't being freed if the match failed.
23
24 4. Tidied pcretest to ensure it frees memory that it gets.
25
26 5. Temporary memory was being obtained in the case where the passed offsets
27 vector was exactly big enough.
28
29 6. Corrected definition of offsetof() from change 5 below.
30
31 7. I had screwed up change 6 below and broken the rules for the use of
32 setjmp(). Now fixed.
33
34
35 Version 1.03 18-Dec-97
36 ----------------------
37
38 1. A erroneous regex with a missing opening parenthesis was correctly
39 diagnosed, but PCRE attempted to access brastack[-1], which could cause crashes
40 on some systems.
41
42 2. Replaced offsetof(real_pcre, code) by offsetof(real_pcre, code[0]) because
43 it was reported that one broken compiler failed on the former because "code" is
44 also an independent variable.
45
46 3. The erroneous regex a[]b caused an array overrun reference.
47
48 4. A regex ending with a one-character negative class (e.g. /[^k]$/) did not
49 fail on data ending with that character. (It was going on too far, and checking
50 the next character, typically a binary zero.) This was specific to the
51 optimized code for single-character negative classes.
52
53 5. Added a contributed patch from the TIN world which does the following:
54
55 + Add an undef for memmove, in case the the system defines a macro for it.
56
57 + Add a definition of offsetof(), in case there isn't one. (I don't know
58 the reason behind this - offsetof() is part of the ANSI standard - but
59 it does no harm).
60
61 + Reduce the ifdef's in pcre.c using macro DPRINTF, thereby eliminating
62 most of the places where whitespace preceded '#'. I have given up and
63 allowed the remaining 2 cases to be at the margin.
64
65 + Rename some variables in pcre to eliminate shadowing. This seems very
66 pedantic, but does no harm, of course.
67
68 6. Moved the call to setjmp() into its own function, to get rid of warnings
69 from gcc -Wall, and avoided calling it at all unless PCRE_EXTRA is used.
70
71 7. Constructs such as \d{8,} were compiling into the equivalent of
72 \d{8}\d{0,65527} instead of \d{8}\d* which didn't make much difference to the
73 outcome, but in this particular case used more store than had been allocated,
74 which caused the bug to be discovered because it threw up an internal error.
75
76 8. The debugging code in both pcre and pcretest for outputting the compiled
77 form of a regex was going wrong in the case of back references followed by
78 curly-bracketed repeats.
79
80
81 Version 1.02 12-Dec-97
82 ----------------------
83
84 1. Typos in pcre.3 and comments in the source fixed.
85
86 2. Applied a contributed patch to get rid of places where it used to remove
87 'const' from variables, and fixed some signed/unsigned and uninitialized
88 variable warnings.
89
90 3. Added the "runtest" target to Makefile.
91
92 4. Set default compiler flag to -O2 rather than just -O.
93
94
95 Version 1.01 19-Nov-97
96 ----------------------
97
98 1. PCRE was failing to diagnose unlimited repeat of empty string for patterns
99 like /([ab]*)*/, that is, for classes with more than one character in them.
100
101 2. Likewise, it wasn't diagnosing patterns with "once-only" subpatterns, such
102 as /((?>a*))*/ (a PCRE_EXTRA facility).
103
104
105 Version 1.00 18-Nov-97
106 ----------------------
107
108 1. Added compile-time macros to support systems such as SunOS4 which don't have
109 memmove() or strerror() but have other things that can be used instead.
110
111 2. Arranged that "make clean" removes the executables.
112
113
114 Version 0.99 27-Oct-97
115 ----------------------
116
117 1. Fixed bug in code for optimizing classes with only one character. It was
118 initializing a 32-byte map regardless, which could cause it to run off the end
119 of the memory it had got.
120
121 2. Added, conditional on PCRE_EXTRA, the proposed (?>REGEX) construction.
122
123
124 Version 0.98 22-Oct-97
125 ----------------------
126
127 1. Fixed bug in code for handling temporary memory usage when there are more
128 back references than supplied space in the ovector. This could cause segfaults.
129
130
131 Version 0.97 21-Oct-97
132 ----------------------
133
134 1. Added the \X "cut" facility, conditional on PCRE_EXTRA.
135
136 2. Optimized negated single characters not to use a bit map.
137
138 3. Brought error texts together as macro definitions; clarified some of them;
139 fixed one that was wrong - it said "range out of order" when it meant "invalid
140 escape sequence".
141
142 4. Changed some char * arguments to const char *.
143
144 5. Added PCRE_NOTBOL and PCRE_NOTEOL (from POSIX).
145
146 6. Added the POSIX-style API wrapper in pcreposix.a and testing facilities in
147 pcretest.
148
149
150 Version 0.96 16-Oct-97
151 ----------------------
152
153 1. Added a simple "pgrep" utility to the distribution.
154
155 2. Fixed an incompatibility with Perl: "{" is now treated as a normal character
156 unless it appears in one of the precise forms "{ddd}", "{ddd,}", or "{ddd,ddd}"
157 where "ddd" means "one or more decimal digits".
158
159 3. Fixed serious bug. If a pattern had a back reference, but the call to
160 pcre_exec() didn't supply a large enough ovector to record the related
161 identifying subpattern, the match always failed. PCRE now remembers the number
162 of the largest back reference, and gets some temporary memory in which to save
163 the offsets during matching if necessary, in order to ensure that
164 backreferences always work.
165
166 4. Increased the compatibility with Perl in a number of ways:
167
168 (a) . no longer matches \n by default; an option PCRE_DOTALL is provided
169 to request this handling. The option can be set at compile or exec time.
170
171 (b) $ matches before a terminating newline by default; an option
172 PCRE_DOLLAR_ENDONLY is provided to override this (but not in multiline
173 mode). The option can be set at compile or exec time.
174
175 (c) The handling of \ followed by a digit other than 0 is now supposed to be
176 the same as Perl's. If the decimal number it represents is less than 10
177 or there aren't that many previous left capturing parentheses, an octal
178 escape is read. Inside a character class, it's always an octal escape,
179 even if it is a single digit.
180
181 (d) An escaped but undefined alphabetic character is taken as a literal,
182 unless PCRE_EXTRA is set. Currently this just reserves the remaining
183 escapes.
184
185 (e) {0} is now permitted. (The previous item is removed from the compiled
186 pattern).
187
188 5. Changed all the names of code files so that the basic parts are no longer
189 than 10 characters, and abolished the teeny "globals.c" file.
190
191 6. Changed the handling of character classes; they are now done with a 32-byte
192 bit map always.
193
194 7. Added the -d and /D options to pcretest to make it possible to look at the
195 internals of compilation without having to recompile pcre.
196
197
198 Version 0.95 23-Sep-97
199 ----------------------
200
201 1. Fixed bug in pre-pass concerning escaped "normal" characters such as \x5c or
202 \x20 at the start of a run of normal characters. These were being treated as
203 real characters, instead of the source characters being re-checked.
204
205
206 Version 0.94 18-Sep-97
207 ----------------------
208
209 1. The functions are now thread-safe, with the caveat that the global variables
210 containing pointers to malloc() and free() or alternative functions are the
211 same for all threads.
212
213 2. Get pcre_study() to generate a bitmap of initial characters for non-
214 anchored patterns when this is possible, and use it if passed to pcre_exec().
215
216
217 Version 0.93 15-Sep-97
218 ----------------------
219
220 1. /(b)|(:+)/ was computing an incorrect first character.
221
222 2. Add pcre_study() to the API and the passing of pcre_extra to pcre_exec(),
223 but not actually doing anything yet.
224
225 3. Treat "-" characters in classes that cannot be part of ranges as literals,
226 as Perl does (e.g. [-az] or [az-]).
227
228 4. Set the anchored flag if a branch starts with .* or .*? because that tests
229 all possible positions.
230
231 5. Split up into different modules to avoid including unneeded functions in a
232 compiled binary. However, compile and exec are still in one module. The "study"
233 function is split off.
234
235 6. The character tables are now in a separate module whose source is generated
236 by an auxiliary program - but can then be edited by hand if required. There are
237 now no calls to isalnum(), isspace(), isdigit(), isxdigit(), tolower() or
238 toupper() in the code.
239
240 7. Turn the malloc/free funtions variables into pcre_malloc and pcre_free and
241 make them global. Abolish the function for setting them, as the caller can now
242 set them directly.
243
244
245 Version 0.92 11-Sep-97
246 ----------------------
247
248 1. A repeat with a fixed maximum and a minimum of 1 for an ordinary character
249 (e.g. /a{1,3}/) was broken (I mis-optimized it).
250
251 2. Caseless matching was not working in character classes if the characters in
252 the pattern were in upper case.
253
254 3. Make ranges like [W-c] work in the same way as Perl for caseless matching.
255
256 4. Make PCRE_ANCHORED public and accept as a compile option.
257
258 5. Add an options word to pcre_exec() and accept PCRE_ANCHORED and
259 PCRE_CASELESS at run time. Add escapes \A and \I to pcretest to cause it to
260 pass them.
261
262 6. Give an error if bad option bits passed at compile or run time.
263
264 7. Add PCRE_MULTILINE at compile and exec time, and (?m) as well. Add \M to
265 pcretest to cause it to pass that flag.
266
267 8. Add pcre_info(), to get the number of identifying subpatterns, the stored
268 options, and the first character, if set.
269
270 9. Recognize C+ or C{n,m} where n >= 1 as providing a fixed starting character.
271
272
273 Version 0.91 10-Sep-97
274 ----------------------
275
276 1. PCRE was failing to diagnose unlimited repeats of subpatterns that could
277 match the empty string as in /(a*)*/. It was looping and ultimately crashing.
278
279 2. PCRE was looping on encountering an indefinitely repeated back reference to
280 a subpattern that had matched an empty string, e.g. /(a|)\1*/. It now does what
281 Perl does - treats the match as successful.
282
283 ****

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12