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

Contents of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log


Revision 978 - (show annotations)
Sun Jun 17 16:55:07 2012 UTC (7 years, 5 months ago) by ph10
File size: 231784 byte(s)
Apply character value checks to \u.... in JavaScript mode, for compatibility 
with \x{....} in non-JavaScript mode.
1 ChangeLog for PCRE
2 ------------------
3
4 Version 8.31 02-June-2012
5 -------------------------
6
7 1. Fixing a wrong JIT test case and some compiler warnings.
8
9 2. Removed a bashism from the RunTest script.
10
11 3. Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
12 to unsigned type, result still unsigned" that was given by an MS compiler
13 on encountering the code "-sizeof(xxx)".
14
15 4. Partial matching support is added to the JIT compiler.
16
17 5. Fixed several bugs concerned with partial matching of items that consist
18 of more than one character:
19
20 (a) /^(..)\1/ did not partially match "aba" because checking references was
21 done on an "all or nothing" basis. This also applied to repeated
22 references.
23
24 (b) \R did not give a hard partial match if \r was found at the end of the
25 subject.
26
27 (c) \X did not give a hard partial match after matching one or more
28 characters at the end of the subject.
29
30 (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
31 a partial match for the string "\r".
32
33 (e) When newline was set to CRLF, the metacharacter "." did not recognize
34 a partial match for a CR character at the end of the subject string.
35
36 6. If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
37 running pcretest, the text "(JIT)" added to the output whenever JIT is
38 actually used to run the match.
39
40 7. Individual JIT compile options can be set in pcretest by following -s+[+]
41 or /S+[+] with a digit between 1 and 7.
42
43 8. OP_NOT now supports any UTF character not just single-byte ones.
44
45 9. (*MARK) control verb is now supported by the JIT compiler.
46
47 10. The command "./RunTest list" lists the available tests without actually
48 running any of them. (Because I keep forgetting what they all are.)
49
50 11. Add PCRE_INFO_MAXLOOKBEHIND.
51
52 12. Applied a (slightly modified) user-supplied patch that improves performance
53 when the heap is used for recursion (compiled with --disable-stack-for-
54 recursion). Instead of malloc and free for each heap frame each time a
55 logical recursion happens, frames are retained on a chain and re-used where
56 possible. This sometimes gives as much as 30% improvement.
57
58 13. As documented, (*COMMIT) is now confined to within a recursive subpattern
59 call.
60
61 14. As documented, (*COMMIT) is now confined to within a positive assertion.
62
63 15. It is now possible to link pcretest with libedit as an alternative to
64 libreadline.
65
66 16. (*COMMIT) control verb is now supported by the JIT compiler.
67
68 17. The Unicode data tables have been updated to Unicode 6.1.0.
69
70 18. Added --file-list option to pcregrep.
71
72 19. Added binary file support to pcregrep, including the -a, --binary-files,
73 -I, and --text options.
74
75 20. The madvise function is renamed for posix_madvise for QNX compatibility
76 reasons. Fixed by Giuseppe D'Angelo.
77
78 21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
79
80 22. Changed the option for creating symbolic links for 16-bit man pages from
81 -s to -sf so that re-installing does not cause issues.
82
83 23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
84
85 24. Fixed a very old bug in pcretest that caused errors with restarted DFA
86 matches in certain environments (the workspace was not being correctly
87 retained). Also added to pcre_dfa_exec() a simple plausibility check on
88 some of the workspace data at the beginning of a restart.
89
90 25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
91 was not doing so when it should - probably a typo introduced by SVN 528
92 (change 8.10/14).
93
94 26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
95 \w+ when the character tables indicated that \x{c4} was a word character.
96 There were several related cases, all because the tests for doing a table
97 lookup were testing for characters less than 127 instead of 255.
98
99 27. If a pattern contains capturing parentheses that are not used in a match,
100 their slots in the ovector are set to -1. For those that are higher than
101 any matched groups, this happens at the end of processing. In the case when
102 there were back references that the ovector was too small to contain
103 (causing temporary malloc'd memory to be used during matching), and the
104 highest capturing number was not used, memory off the end of the ovector
105 was incorrectly being set to -1. (It was using the size of the temporary
106 memory instead of the true size.)
107
108 28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
109 ovector size, it uses memory at the end of the block that it has got.
110
111 29. Check for an overlong MARK name and give an error at compile time. The
112 limit is 255 for the 8-bit library and 65535 for the 16-bit library.
113
114 30. JIT compiler update.
115
116 31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
117 Rill for the patch.
118
119 32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
120
121 33. Variable renamings in the PCRE-JIT compiler. No functionality change.
122
123 34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
124 SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
125 was enabled.
126
127 35. Improve JIT code generation for greedy plus quantifier.
128
129 36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
130 1 to "aa" instead of to an empty string. The bug affected repeated groups
131 that could potentially match an empty string.
132
133 37. Optimizing single character iterators in JIT.
134
135 38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
136 the same checks as \x{...} characters in non-JavaScript mode. Specifically,
137 codepoints that are too big for the mode are faulted, and in a UTF mode,
138 disallowed codepoints are also faulted.
139
140
141 Version 8.30 04-February-2012
142 -----------------------------
143
144 1. Renamed "isnumber" as "is_a_number" because in some Mac environments this
145 name is defined in ctype.h.
146
147 2. Fixed a bug in fixed-length calculation for lookbehinds that would show up
148 only in quite long subpatterns.
149
150 3. Removed the function pcre_info(), which has been obsolete and deprecated
151 since it was replaced by pcre_fullinfo() in February 2000.
152
153 4. For a non-anchored pattern, if (*SKIP) was given with a name that did not
154 match a (*MARK), and the match failed at the start of the subject, a
155 reference to memory before the start of the subject could occur. This bug
156 was introduced by fix 17 of release 8.21.
157
158 5. A reference to an unset group with zero minimum repetition was giving
159 totally wrong answers (in non-JavaScript-compatibility mode). For example,
160 /(another)?(\1?)test/ matched against "hello world test". This bug was
161 introduced in release 8.13.
162
163 6. Add support for 16-bit character strings (a large amount of work involving
164 many changes and refactorings).
165
166 7. RunGrepTest failed on msys because \r\n was replaced by whitespace when the
167 command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
168 from a file.
169
170 8. Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
171 rounding is not applied in this particular case).
172
173 9. The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
174 if they appear, or are escaped, in patterns.
175
176 10. Get rid of a number of -Wunused-but-set-variable warnings.
177
178 11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
179 "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
180 Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
181 also returns the mark "x". This bug applied to capturing parentheses,
182 non-capturing parentheses, and atomic parentheses. It also applied to some
183 assertions.
184
185 12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
186 information out of configure.ac instead of relying on pcre.h.generic, which
187 is not stored in the repository.
188
189 13. Applied Dmitry V. Levin's patch for a more portable method for linking with
190 -lreadline.
191
192 14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
193
194 15. Applied Graycode's patch to put the top-level frame on the stack rather
195 than the heap when not using the stack for recursion. This gives a
196 performance improvement in many cases when recursion is not deep.
197
198 16. Experimental code added to "pcretest -C" to output the stack frame size.
199
200
201 Version 8.21 12-Dec-2011
202 ------------------------
203
204 1. Updating the JIT compiler.
205
206 2. JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
207 are added as well.
208
209 3. Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
210 PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
211 calling _pcre_jit_exec. Some extra comments are added.
212
213 4. (*MARK) settings inside atomic groups that do not contain any capturing
214 parentheses, for example, (?>a(*:m)), were not being passed out. This bug
215 was introduced by change 18 for 8.20.
216
217 5. Supporting of \x, \U and \u in JavaScript compatibility mode based on the
218 ECMA-262 standard.
219
220 6. Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
221 erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
222 This bug was probably introduced by change 9 of 8.13.
223
224 7. While fixing 6 above, I noticed that a number of other items were being
225 incorrectly rejected as "not fixed length". This arose partly because newer
226 opcodes had not been added to the fixed-length checking code. I have (a)
227 corrected the bug and added tests for these items, and (b) arranged for an
228 error to occur if an unknown opcode is encountered while checking for fixed
229 length instead of just assuming "not fixed length". The items that were
230 rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
231 (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
232 repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
233
234 8. A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
235 being incorrectly compiled and would have given unpredicatble results.
236
237 9. A possessively repeated subpattern with minimum repeat count greater than
238 one behaved incorrectly. For example, (A){2,}+ behaved as if it was
239 (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
240 the first (A) could occur when it should not.
241
242 10. Add a cast and remove a redundant test from the code.
243
244 11. JIT should use pcre_malloc/pcre_free for allocation.
245
246 12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
247 best practice nowadays, and helps with cross-compiling. (If the exec_prefix
248 is anything other than /usr, -L is still shown).
249
250 13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
251
252 14. Perl does not support \N without a following name in a [] class; PCRE now
253 also gives an error.
254
255 15. If a forward reference was repeated with an upper limit of around 2000,
256 it caused the error "internal error: overran compiling workspace". The
257 maximum number of forward references (including repeats) was limited by the
258 internal workspace, and dependent on the LINK_SIZE. The code has been
259 rewritten so that the workspace expands (via pcre_malloc) if necessary, and
260 the default depends on LINK_SIZE. There is a new upper limit (for safety)
261 of around 200,000 forward references. While doing this, I also speeded up
262 the filling in of repeated forward references.
263
264 16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
265 incorrectly expecting the subject to contain another "a" after the start.
266
267 17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
268 in the match, the SKIP should be ignored. This was not happening; instead
269 the SKIP was being treated as NOMATCH. For patterns such as
270 /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
271 tested.
272
273 18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
274 now much more compatible with Perl, in particular in cases where the result
275 is a non-match for a non-anchored pattern. For example, if
276 /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
277 "m", where previously it did not return a name. A side effect of this
278 change is that for partial matches, the last encountered mark name is
279 returned, as for non matches. A number of tests that were previously not
280 Perl-compatible have been moved into the Perl-compatible test files. The
281 refactoring has had the pleasing side effect of removing one argument from
282 the match() function, thus reducing its stack requirements.
283
284 19. If the /S+ option was used in pcretest to study a pattern using JIT,
285 subsequent uses of /S (without +) incorrectly behaved like /S+.
286
287 21. Retrieve executable code size support for the JIT compiler and fixing
288 some warnings.
289
290 22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
291 not work when the shorter character appeared right at the end of the
292 subject string.
293
294 23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
295 systems.
296
297 24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
298 output it when the /M option is used in pcretest.
299
300 25. The CheckMan script was not being included in the distribution. Also, added
301 an explicit "perl" to run Perl scripts from the PrepareRelease script
302 because this is reportedly needed in Windows.
303
304 26. If study data was being save in a file and studying had not found a set of
305 "starts with" bytes for the pattern, the data written to the file (though
306 never used) was taken from uninitialized memory and so caused valgrind to
307 complain.
308
309 27. Updated RunTest.bat as provided by Sheri Pierce.
310
311 28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
312
313 29. Computation of memory usage for the table of capturing group names was
314 giving an unnecessarily large value.
315
316
317 Version 8.20 21-Oct-2011
318 ------------------------
319
320 1. Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
321 a POSIX class. After further experiments with Perl, which convinced me that
322 Perl has bugs and confusions, a closing square bracket is no longer allowed
323 in a POSIX name. This bug also affected patterns with classes that started
324 with full stops.
325
326 2. If a pattern such as /(a)b|ac/ is matched against "ac", there is no
327 captured substring, but while checking the failing first alternative,
328 substring 1 is temporarily captured. If the output vector supplied to
329 pcre_exec() was not big enough for this capture, the yield of the function
330 was still zero ("insufficient space for captured substrings"). This cannot
331 be totally fixed without adding another stack variable, which seems a lot
332 of expense for a edge case. However, I have improved the situation in cases
333 such as /(a)(b)x|abc/ matched against "abc", where the return code
334 indicates that fewer than the maximum number of slots in the ovector have
335 been set.
336
337 3. Related to (2) above: when there are more back references in a pattern than
338 slots in the output vector, pcre_exec() uses temporary memory during
339 matching, and copies in the captures as far as possible afterwards. It was
340 using the entire output vector, but this conflicts with the specification
341 that only 2/3 is used for passing back captured substrings. Now it uses
342 only the first 2/3, for compatibility. This is, of course, another edge
343 case.
344
345 4. Zoltan Herczeg's just-in-time compiler support has been integrated into the
346 main code base, and can be used by building with --enable-jit. When this is
347 done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
348 runtime --no-jit option is given.
349
350 5. When the number of matches in a pcre_dfa_exec() run exactly filled the
351 ovector, the return from the function was zero, implying that there were
352 other matches that did not fit. The correct "exactly full" value is now
353 returned.
354
355 6. If a subpattern that was called recursively or as a subroutine contained
356 (*PRUNE) or any other control that caused it to give a non-standard return,
357 invalid errors such as "Error -26 (nested recursion at the same subject
358 position)" or even infinite loops could occur.
359
360 7. If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
361 computing the minimum length on reaching *ACCEPT, and so ended up with the
362 wrong value of 1 rather than 0. Further investigation indicates that
363 computing a minimum subject length in the presence of *ACCEPT is difficult
364 (think back references, subroutine calls), and so I have changed the code
365 so that no minimum is registered for a pattern that contains *ACCEPT.
366
367 8. If (*THEN) was present in the first (true) branch of a conditional group,
368 it was not handled as intended. [But see 16 below.]
369
370 9. Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
371 Sheri Pierce.
372
373 10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
374 the first byte in a match must be "a".
375
376 11. Change 17 for 8.13 increased the recursion depth for patterns like
377 /a(?:.)*?a/ drastically. I've improved things by remembering whether a
378 pattern contains any instances of (*THEN). If it does not, the old
379 optimizations are restored. It would be nice to do this on a per-group
380 basis, but at the moment that is not feasible.
381
382 12. In some environments, the output of pcretest -C is CRLF terminated. This
383 broke RunTest's code that checks for the link size. A single white space
384 character after the value is now allowed for.
385
386 13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
387 For "fr", it uses the Windows-specific input and output files.
388
389 14. If (*THEN) appeared in a group that was called recursively or as a
390 subroutine, it did not work as intended. [But see next item.]
391
392 15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
393 pattern fragments (but not containing any | characters). If A and B are
394 matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
395 was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
396 D. In other words, Perl considers parentheses that do not contain any |
397 characters to be part of a surrounding alternative, whereas PCRE was
398 treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
399 differently. PCRE now behaves in the same way as Perl, except in the case
400 of subroutine/recursion calls such as (?1) which have in any case always
401 been different (but PCRE had them first :-).
402
403 16. Related to 15 above: Perl does not treat the | in a conditional group as
404 creating alternatives. Such a group is treated in the same way as an
405 ordinary group without any | characters when processing (*THEN). PCRE has
406 been changed to match Perl's behaviour.
407
408 17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
409 RunGrepTest script failed.
410
411 18. Change 22 for version 13 caused atomic groups to use more stack. This is
412 inevitable for groups that contain captures, but it can lead to a lot of
413 stack use in large patterns. The old behaviour has been restored for atomic
414 groups that do not contain any capturing parentheses.
415
416 19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
417 suppress the check for a minimum subject length at run time. (If it was
418 given to pcre_exec() or pcre_dfa_exec() it did work.)
419
420 20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
421 fail to work when decoding hex characters in data strings in EBCDIC
422 environments.
423
424 21. It appears that in at least one Mac OS environment, the isxdigit() function
425 is implemented as a macro that evaluates to its argument more than once,
426 contravening the C 90 Standard (I haven't checked a later standard). There
427 was an instance in pcretest which caused it to go wrong when processing
428 \x{...} escapes in subject strings. The has been rewritten to avoid using
429 things like p++ in the argument of isxdigit().
430
431
432 Version 8.13 16-Aug-2011
433 ------------------------
434
435 1. The Unicode data tables have been updated to Unicode 6.0.0.
436
437 2. Two minor typos in pcre_internal.h have been fixed.
438
439 3. Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
440 pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
441 in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
442
443 4. There were a number of related bugs in the code for matching backrefences
444 caselessly in UTF-8 mode when codes for the characters concerned were
445 different numbers of bytes. For example, U+023A and U+2C65 are an upper
446 and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
447 (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
448 code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
449 2-byte code at the end of the subject (it thought there wasn't enough data
450 left).
451
452 5. Comprehensive information about what went wrong is now returned by
453 pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
454 as the output vector has at least 2 elements. The offset of the start of
455 the failing character and a reason code are placed in the vector.
456
457 6. When the UTF-8 string check fails for pcre_compile(), the offset that is
458 now returned is for the first byte of the failing character, instead of the
459 last byte inspected. This is an incompatible change, but I hope it is small
460 enough not to be a problem. It makes the returned offset consistent with
461 pcre_exec() and pcre_dfa_exec().
462
463 7. pcretest now gives a text phrase as well as the error number when
464 pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
465 failure, the offset and reason code are output.
466
467 8. When \R was used with a maximizing quantifier it failed to skip backwards
468 over a \r\n pair if the subsequent match failed. Instead, it just skipped
469 back over a single character (\n). This seems wrong (because it treated the
470 two characters as a single entity when going forwards), conflicts with the
471 documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
472 behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
473 has been changed.
474
475 9. Some internal refactoring has changed the processing so that the handling
476 of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
477 time (the PCRE_DOTALL option was changed this way some time ago: version
478 7.7 change 16). This has made it possible to abolish the OP_OPT op code,
479 which was always a bit of a fudge. It also means that there is one less
480 argument for the match() function, which reduces its stack requirements
481 slightly. This change also fixes an incompatibility with Perl: the pattern
482 (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
483
484 10. More internal refactoring has drastically reduced the number of recursive
485 calls to match() for possessively repeated groups such as (abc)++ when
486 using pcre_exec().
487
488 11. While implementing 10, a number of bugs in the handling of groups were
489 discovered and fixed:
490
491 (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
492 (a|)*(?1) gave a compile-time internal error.
493 ((a|)+)+ did not notice that the outer group could match an empty string.
494 (^a|^)+ was not marked as anchored.
495 (.*a|.*)+ was not marked as matching at start or after a newline.
496
497 12. Yet more internal refactoring has removed another argument from the match()
498 function. Special calls to this function are now indicated by setting a
499 value in a variable in the "match data" data block.
500
501 13. Be more explicit in pcre_study() instead of relying on "default" for
502 opcodes that mean there is no starting character; this means that when new
503 ones are added and accidentally left out of pcre_study(), testing should
504 pick them up.
505
506 14. The -s option of pcretest has been documented for ages as being an old
507 synonym of -m (show memory usage). I have changed it to mean "force study
508 for every regex", that is, assume /S for every regex. This is similar to -i
509 and -d etc. It's slightly incompatible, but I'm hoping nobody is still
510 using it. It makes it easier to run collections of tests with and without
511 study enabled, and thereby test pcre_study() more easily. All the standard
512 tests are now run with and without -s (but some patterns can be marked as
513 "never study" - see 20 below).
514
515 15. When (*ACCEPT) was used in a subpattern that was called recursively, the
516 restoration of the capturing data to the outer values was not happening
517 correctly.
518
519 16. If a recursively called subpattern ended with (*ACCEPT) and matched an
520 empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
521 pattern had matched an empty string, and so incorrectly returned a no
522 match.
523
524 17. There was optimizing code for the last branch of non-capturing parentheses,
525 and also for the obeyed branch of a conditional subexpression, which used
526 tail recursion to cut down on stack usage. Unfortunately, now that there is
527 the possibility of (*THEN) occurring in these branches, tail recursion is
528 no longer possible because the return has to be checked for (*THEN). These
529 two optimizations have therefore been removed. [But see 8.20/11 above.]
530
531 18. If a pattern containing \R was studied, it was assumed that \R always
532 matched two bytes, thus causing the minimum subject length to be
533 incorrectly computed because \R can also match just one byte.
534
535 19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
536 was incorrectly computed.
537
538 20. If /S is present twice on a test pattern in pcretest input, it now
539 *disables* studying, thereby overriding the use of -s on the command line
540 (see 14 above). This is necessary for one or two tests to keep the output
541 identical in both cases.
542
543 21. When (*ACCEPT) was used in an assertion that matched an empty string and
544 PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
545
546 22. When an atomic group that contained a capturing parenthesis was
547 successfully matched, but the branch in which it appeared failed, the
548 capturing was not being forgotten if a higher numbered group was later
549 captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
550 group 1 to "a", when in fact it should be unset. This applied to multi-
551 branched capturing and non-capturing groups, repeated or not, and also to
552 positive assertions (capturing in negative assertions does not happen
553 in PCRE) and also to nested atomic groups.
554
555 23. Add the ++ qualifier feature to pcretest, to show the remainder of the
556 subject after a captured substring, to make it easier to tell which of a
557 number of identical substrings has been captured.
558
559 24. The way atomic groups are processed by pcre_exec() has been changed so that
560 if they are repeated, backtracking one repetition now resets captured
561 values correctly. For example, if ((?>(a+)b)+aabab) is matched against
562 "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
563 "aaa". Previously, it would have been "a". As part of this code
564 refactoring, the way recursive calls are handled has also been changed.
565
566 25. If an assertion condition captured any substrings, they were not passed
567 back unless some other capturing happened later. For example, if
568 (?(?=(a))a) was matched against "a", no capturing was returned.
569
570 26. When studying a pattern that contained subroutine calls or assertions,
571 the code for finding the minimum length of a possible match was handling
572 direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
573 group 1 called group 2 while simultaneously a separate group 2 called group
574 1). A stack overflow occurred in this case. I have fixed this by limiting
575 the recursion depth to 10.
576
577 27. Updated RunTest.bat in the distribution to the version supplied by Tom
578 Fortmann. This supports explicit test numbers on the command line, and has
579 argument validation and error reporting.
580
581 28. An instance of \X with an unlimited repeat could fail if at any point the
582 first character it looked at was a mark character.
583
584 29. Some minor code refactoring concerning Unicode properties and scripts
585 should reduce the stack requirement of match() slightly.
586
587 30. Added the '=' option to pcretest to check the setting of unused capturing
588 slots at the end of the pattern, which are documented as being -1, but are
589 not included in the return count.
590
591 31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
592 compiled something random. Now it gives a compile-time error (as does
593 Perl).
594
595 32. A *MARK encountered during the processing of a positive assertion is now
596 recorded and passed back (compatible with Perl).
597
598 33. If --only-matching or --colour was set on a pcregrep call whose pattern
599 had alternative anchored branches, the search for a second match in a line
600 was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
601 matched the line "0102" twice. The same bug affected patterns that started
602 with a backwards assertion. For example /\b01|\b02/ also matched "0102"
603 twice.
604
605 34. Previously, PCRE did not allow quantification of assertions. However, Perl
606 does, and because of capturing effects, quantifying parenthesized
607 assertions may at times be useful. Quantifiers are now allowed for
608 parenthesized assertions.
609
610 35. A minor code tidy in pcre_compile() when checking options for \R usage.
611
612 36. \g was being checked for fancy things in a character class, when it should
613 just be a literal "g".
614
615 37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
616 appearance of a nested POSIX class supersedes an apparent external class.
617 For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
618 unescaped square brackets may also appear as part of class names. For
619 example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
620 more like Perl. (But see 8.20/1 above.)
621
622 38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
623 was because it thought it was \N{name}, which is not supported).
624
625 39. Add minix to OS list not supporting the -S option in pcretest.
626
627 40. PCRE tries to detect cases of infinite recursion at compile time, but it
628 cannot analyze patterns in sufficient detail to catch mutual recursions
629 such as ((?1))((?2)). There is now a runtime test that gives an error if a
630 subgroup is called recursively as a subpattern for a second time at the
631 same position in the subject string. In previous releases this might have
632 been caught by the recursion limit, or it might have run out of stack.
633
634 41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
635 happen only once. PCRE was, however incorrectly giving a compile time error
636 "recursive call could loop indefinitely" because it cannot analyze the
637 pattern in sufficient detail. The compile time test no longer happens when
638 PCRE is compiling a conditional subpattern, but actual runaway loops are
639 now caught at runtime (see 40 above).
640
641 42. It seems that Perl allows any characters other than a closing parenthesis
642 to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
643 has been changed to be the same.
644
645 43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
646 as not to get warnings when autogen.sh is called. Also changed
647 AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
648
649 44. To help people who use pcregrep to scan files containing exceedingly long
650 lines, the following changes have been made:
651
652 (a) The default value of the buffer size parameter has been increased from
653 8K to 20K. (The actual buffer used is three times this size.)
654
655 (b) The default can be changed by ./configure --with-pcregrep-bufsize when
656 PCRE is built.
657
658 (c) A --buffer-size=n option has been added to pcregrep, to allow the size
659 to be set at run time.
660
661 (d) Numerical values in pcregrep options can be followed by K or M, for
662 example --buffer-size=50K.
663
664 (e) If a line being scanned overflows pcregrep's buffer, an error is now
665 given and the return code is set to 2.
666
667 45. Add a pointer to the latest mark to the callout data block.
668
669 46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
670 partial match of an empty string instead of no match. This was specific to
671 the use of ".".
672
673 47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
674 complete match instead of a partial match. This bug was dependent on both
675 the PCRE_UTF8 and PCRE_DOTALL options being set.
676
677 48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
678 starting byte set, because \b was not being ignored.
679
680
681 Version 8.12 15-Jan-2011
682 ------------------------
683
684 1. Fixed some typos in the markup of the man pages, and wrote a script that
685 checks for such things as part of the documentation building process.
686
687 2. On a big-endian 64-bit system, pcregrep did not correctly process the
688 --match-limit and --recursion-limit options (added for 8.11). In
689 particular, this made one of the standard tests fail. (The integer value
690 went into the wrong half of a long int.)
691
692 3. If the --colour option was given to pcregrep with -v (invert match), it
693 did strange things, either producing crazy output, or crashing. It should,
694 of course, ignore a request for colour when reporting lines that do not
695 match.
696
697 4. Another pcregrep bug caused similar problems if --colour was specified with
698 -M (multiline) and the pattern match finished with a line ending.
699
700 5. In pcregrep, when a pattern that ended with a literal newline sequence was
701 matched in multiline mode, the following line was shown as part of the
702 match. This seems wrong, so I have changed it.
703
704 6. Another pcregrep bug in multiline mode, when --colour was specified, caused
705 the check for further matches in the same line (so they could be coloured)
706 to overrun the end of the current line. If another match was found, it was
707 incorrectly shown (and then shown again when found in the next line).
708
709 7. If pcregrep was compiled under Windows, there was a reference to the
710 function pcregrep_exit() before it was defined. I am assuming this was
711 the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
712 reported by a user. I've moved the definition above the reference.
713
714
715 Version 8.11 10-Dec-2010
716 ------------------------
717
718 1. (*THEN) was not working properly if there were untried alternatives prior
719 to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
720 backtracked to try for "b" instead of moving to the next alternative branch
721 at the same level (in this case, to look for "c"). The Perl documentation
722 is clear that when (*THEN) is backtracked onto, it goes to the "next
723 alternative in the innermost enclosing group".
724
725 2. (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
726 such as (A(*COMMIT)B(*THEN)C|D) any failure after matching A should
727 result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
728 (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
729 (*THEN).
730
731 3. If \s appeared in a character class, it removed the VT character from
732 the class, even if it had been included by some previous item, for example
733 in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
734 of \s, but is part of the POSIX "space" class.)
735
736 4. A partial match never returns an empty string (because you can always
737 match an empty string at the end of the subject); however the checking for
738 an empty string was starting at the "start of match" point. This has been
739 changed to the "earliest inspected character" point, because the returned
740 data for a partial match starts at this character. This means that, for
741 example, /(?<=abc)def/ gives a partial match for the subject "abc"
742 (previously it gave "no match").
743
744 5. Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
745 of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
746 previously a full match would be given. However, setting PCRE_PARTIAL_HARD
747 has an implication that the given string is incomplete (because a partial
748 match is preferred over a full match). For this reason, these items now
749 give a partial match in this situation. [Aside: previously, the one case
750 /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
751 match rather than a full match, which was wrong by the old rules, but is
752 now correct.]
753
754 6. There was a bug in the handling of #-introduced comments, recognized when
755 PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
756 If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
757 UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
758 scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
759 but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
760 places in pcre_compile().
761
762 7. Related to (6) above, when pcre_compile() was skipping #-introduced
763 comments when looking ahead for named forward references to subpatterns,
764 the only newline sequence it recognized was NL. It now handles newlines
765 according to the set newline convention.
766
767 8. SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
768 former, but used strtoul(), whereas pcretest avoided strtoul() but did not
769 cater for a lack of strerror(). These oversights have been fixed.
770
771 9. Added --match-limit and --recursion-limit to pcregrep.
772
773 10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
774
775 11. When the -o option was used, pcregrep was setting a return code of 1, even
776 when matches were found, and --line-buffered was not being honoured.
777
778 12. Added an optional parentheses number to the -o and --only-matching options
779 of pcregrep.
780
781 13. Imitating Perl's /g action for multiple matches is tricky when the pattern
782 can match an empty string. The code to do it in pcretest and pcredemo
783 needed fixing:
784
785 (a) When the newline convention was "crlf", pcretest got it wrong, skipping
786 only one byte after an empty string match just before CRLF (this case
787 just got forgotten; "any" and "anycrlf" were OK).
788
789 (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
790 mode when an empty string match preceded an ASCII character followed by
791 a non-ASCII character. (The code for advancing by one character rather
792 than one byte was nonsense.)
793
794 (c) The pcredemo.c sample program did not have any code at all to handle
795 the cases when CRLF is a valid newline sequence.
796
797 14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
798 as a starting offset was within the subject string. There is now a new
799 error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
800 negative or greater than the length of the string. In order to test this,
801 pcretest is extended to allow the setting of negative starting offsets.
802
803 15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
804 starting offset points to the beginning of a UTF-8 character was
805 unnecessarily clumsy. I tidied it up.
806
807 16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
808 bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
809
810 17. Nobody had reported that the --include_dir option, which was added in
811 release 7.7 should have been called --include-dir (hyphen, not underscore)
812 for compatibility with GNU grep. I have changed it to --include-dir, but
813 left --include_dir as an undocumented synonym, and the same for
814 --exclude-dir, though that is not available in GNU grep, at least as of
815 release 2.5.4.
816
817 18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
818 characters from a string of bytes) have been redefined so as not to use
819 loops, in order to improve performance in some environments. At the same
820 time, I abstracted some of the common code into auxiliary macros to save
821 repetition (this should not affect the compiled code).
822
823 19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
824 compile-time error is now given if \c is not followed by an ASCII
825 character, that is, a byte less than 128. (In EBCDIC mode, the code is
826 different, and any byte value is allowed.)
827
828 20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
829 START_OPTIMIZE option, which is now allowed at compile time - but just
830 passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
831 to pcregrep and other applications that have no direct access to PCRE
832 options. The new /Y option in pcretest sets this option when calling
833 pcre_compile().
834
835 21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
836 back references. Groups containing recursive back references were forced to
837 be atomic by that change, but in the case of named groups, the amount of
838 memory required was incorrectly computed, leading to "Failed: internal
839 error: code overflow". This has been fixed.
840
841 22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
842 pcretest.c, to avoid build problems in some Borland environments.
843
844
845 Version 8.10 25-Jun-2010
846 ------------------------
847
848 1. Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
849 THEN.
850
851 2. (*ACCEPT) was not working when inside an atomic group.
852
853 3. Inside a character class, \B is treated as a literal by default, but
854 faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
855 causes the error). The code is unchanged, but I tidied the documentation.
856
857 4. Inside a character class, PCRE always treated \R and \X as literals,
858 whereas Perl faults them if its -w option is set. I have changed PCRE so
859 that it faults them when PCRE_EXTRA is set.
860
861 5. Added support for \N, which always matches any character other than
862 newline. (It is the same as "." when PCRE_DOTALL is not set.)
863
864 6. When compiling pcregrep with newer versions of gcc which may have
865 FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
866 declared with attribute warn_unused_result" were given. Just casting the
867 result to (void) does not stop the warnings; a more elaborate fudge is
868 needed. I've used a macro to implement this.
869
870 7. Minor change to pcretest.c to avoid a compiler warning.
871
872 8. Added four artifical Unicode properties to help with an option to make
873 \s etc use properties (see next item). The new properties are: Xan
874 (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
875
876 9. Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
877 use Unicode properties. (*UCP) at the start of a pattern can be used to set
878 this option. Modified pcretest to add /W to test this facility. Added
879 REG_UCP to make it available via the POSIX interface.
880
881 10. Added --line-buffered to pcregrep.
882
883 11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
884 studied, and the match started with a letter with a code point greater than
885 127 whose first byte was different to the first byte of the other case of
886 the letter, the other case of this starting letter was not recognized
887 (#976).
888
889 12. If a pattern that was studied started with a repeated Unicode property
890 test, for example, \p{Nd}+, there was the theoretical possibility of
891 setting up an incorrect bitmap of starting bytes, but fortunately it could
892 not have actually happened in practice until change 8 above was made (it
893 added property types that matched character-matching opcodes).
894
895 13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
896 possible starting bytes for non-anchored patterns.
897
898 14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
899 \R, and also a number of cases that involve Unicode properties, both
900 explicit and implicit when PCRE_UCP is set.
901
902 15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
903 input, it could crash or give wrong results if characters with values
904 greater than 0xc0 were present in the subject string. (Detail: it assumed
905 UTF-8 input when processing these items.)
906
907 16. Added a lot of (int) casts to avoid compiler warnings in systems where
908 size_t is 64-bit (#991).
909
910 17. Added a check for running out of memory when PCRE is compiled with
911 --disable-stack-for-recursion (#990).
912
913 18. If the last data line in a file for pcretest does not have a newline on
914 the end, a newline was missing in the output.
915
916 19. The default pcre_chartables.c file recognizes only ASCII characters (values
917 less than 128) in its various bitmaps. However, there is a facility for
918 generating tables according to the current locale when PCRE is compiled. It
919 turns out that in some environments, 0x85 and 0xa0, which are Unicode space
920 characters, are recognized by isspace() and therefore were getting set in
921 these tables, and indeed these tables seem to approximate to ISO 8859. This
922 caused a problem in UTF-8 mode when pcre_study() was used to create a list
923 of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
924 which of course cannot start UTF-8 characters. I have changed the code so
925 that only real ASCII characters (less than 128) and the correct starting
926 bytes for UTF-8 encodings are set for characters greater than 127 when in
927 UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
928 altogether.)
929
930 20. Added the /T option to pcretest so as to be able to run tests with non-
931 standard character tables, thus making it possible to include the tests
932 used for 19 above in the standard set of tests.
933
934 21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
935 reference to a subpattern the other side of a comment that contains an
936 opening parenthesis caused either an internal compiling error, or a
937 reference to the wrong subpattern.
938
939
940 Version 8.02 19-Mar-2010
941 ------------------------
942
943 1. The Unicode data tables have been updated to Unicode 5.2.0.
944
945 2. Added the option --libs-cpp to pcre-config, but only when C++ support is
946 configured.
947
948 3. Updated the licensing terms in the pcregexp.pas file, as agreed with the
949 original author of that file, following a query about its status.
950
951 4. On systems that do not have stdint.h (e.g. Solaris), check for and include
952 inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
953
954 5. A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
955 quantifier applied to a forward-referencing subroutine call, could compile
956 incorrect code or give the error "internal error: previously-checked
957 referenced subpattern not found".
958
959 6. Both MS Visual Studio and Symbian OS have problems with initializing
960 variables to point to external functions. For these systems, therefore,
961 pcre_malloc etc. are now initialized to local functions that call the
962 relevant global functions.
963
964 7. There were two entries missing in the vectors called coptable and poptable
965 in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
966 I've fixed the data, and added a kludgy way of testing at compile time that
967 the lengths are correct (equal to the number of opcodes).
968
969 8. Following on from 7, I added a similar kludge to check the length of the
970 eint vector in pcreposix.c.
971
972 9. Error texts for pcre_compile() are held as one long string to avoid too
973 much relocation at load time. To find a text, the string is searched,
974 counting zeros. There was no check for running off the end of the string,
975 which could happen if a new error number was added without updating the
976 string.
977
978 10. \K gave a compile-time error if it appeared in a lookbehind assersion.
979
980 11. \K was not working if it appeared in an atomic group or in a group that
981 was called as a "subroutine", or in an assertion. Perl 5.11 documents that
982 \K is "not well defined" if used in an assertion. PCRE now accepts it if
983 the assertion is positive, but not if it is negative.
984
985 12. Change 11 fortuitously reduced the size of the stack frame used in the
986 "match()" function of pcre_exec.c by one pointer. Forthcoming
987 implementation of support for (*MARK) will need an extra pointer on the
988 stack; I have reserved it now, so that the stack frame size does not
989 decrease.
990
991 13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
992 item in branch that calls a recursion is a subroutine call - as in the
993 second branch in the above example - was incorrectly given the compile-
994 time error "recursive call could loop indefinitely" because pcre_compile()
995 was not correctly checking the subroutine for matching a non-empty string.
996
997 14. The checks for overrunning compiling workspace could trigger after an
998 overrun had occurred. This is a "should never occur" error, but it can be
999 triggered by pathological patterns such as hundreds of nested parentheses.
1000 The checks now trigger 100 bytes before the end of the workspace.
1001
1002 15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1003
1004
1005 Version 8.01 19-Jan-2010
1006 ------------------------
1007
1008 1. If a pattern contained a conditional subpattern with only one branch (in
1009 particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1010 computed the wrong minimum data length (which is of course zero for such
1011 subpatterns). This could cause incorrect "no match" results.
1012
1013 2. For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1014 the pattern is reset in the first branch, pcre_compile() failed with
1015 "internal error: code overflow at offset...". This happened only when
1016 the reset was to the original external option setting. (An optimization
1017 abstracts leading options settings into an external setting, which was the
1018 cause of this.)
1019
1020 3. A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1021 of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1022 assertion pattern did not match (meaning that the assertion was true), it
1023 was incorrectly treated as false if the SKIP had been reached during the
1024 matching. This also applied to assertions used as conditions.
1025
1026 4. If an item that is not supported by pcre_dfa_exec() was encountered in an
1027 assertion subpattern, including such a pattern used as a condition,
1028 unpredictable results occurred, instead of the error return
1029 PCRE_ERROR_DFA_UITEM.
1030
1031 5. The C++ GlobalReplace function was not working like Perl for the special
1032 situation when an empty string is matched. It now does the fancy magic
1033 stuff that is necessary.
1034
1035 6. In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1036 removed. (These were left over from very, very early versions of PCRE.)
1037
1038 7. Some cosmetic changes to the code to make life easier when compiling it
1039 as part of something else:
1040
1041 (a) Change DEBUG to PCRE_DEBUG.
1042
1043 (b) In pcre_compile(), rename the member of the "branch_chain" structure
1044 called "current" as "current_branch", to prevent a collision with the
1045 Linux macro when compiled as a kernel module.
1046
1047 (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1048 prevent a collision with the Linux macro when compiled as a kernel
1049 module.
1050
1051 8. In pcre_compile() there are some checks for integer overflows that used to
1052 cast potentially large values to (double). This has been changed to that
1053 when building, a check for int64_t is made, and if it is found, it is used
1054 instead, thus avoiding the use of floating point arithmetic. (There is no
1055 other use of FP in PCRE.) If int64_t is not found, the fallback is to
1056 double.
1057
1058 9. Added two casts to avoid signed/unsigned warnings from VS Studio Express
1059 2005 (difference between two addresses compared to an unsigned value).
1060
1061 10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1062 custom one, because of the following reported problem in Windows:
1063
1064 - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1065 under Win32.
1066 - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1067 therefore missing the function definition.
1068 - The compiler thus generates a "C" signature for the test function.
1069 - The linker fails to find the "C" function.
1070 - PCRE fails to configure if asked to do so against libbz2.
1071
1072 11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1073 messages were output:
1074
1075 Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1076 rerunning libtoolize, to keep the correct libtool macros in-tree.
1077 Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1078
1079 I have done both of these things.
1080
1081 12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1082 most of the time, it *can* run out if it is given a pattern that contains a
1083 runaway infinite recursion. I updated the discussion in the pcrestack man
1084 page.
1085
1086 13. Now that we have gone to the x.xx style of version numbers, the minor
1087 version may start with zero. Using 08 or 09 is a bad idea because users
1088 might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1089 interpreted as invalid octal numbers. I've updated the previous comment in
1090 configure.ac, and also added a check that gives an error if 08 or 09 are
1091 used.
1092
1093 14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1094 causing partial matching to fail when the end of the subject matched \W
1095 in a UTF-8 pattern where \W was quantified with a minimum of 3.
1096
1097 15. There were some discrepancies between the declarations in pcre_internal.h
1098 of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1099 their definitions. The declarations used "const uschar *" and the
1100 definitions used USPTR. Even though USPTR is normally defined as "const
1101 unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1102 reported that: "This difference in casting confuses some C++ compilers, for
1103 example, SunCC recognizes above declarations as different functions and
1104 generates broken code for hbpcre." I have changed the declarations to use
1105 USPTR.
1106
1107 16. GNU libtool is named differently on some systems. The autogen.sh script now
1108 tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1109 (FreeBSD).
1110
1111 17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1112 (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1113 comment: "Figure out how to create a longlong from a string: strtoll and
1114 equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1115 instance, but it only takes 2 args instead of 3!"
1116
1117 18. A subtle bug concerned with back references has been fixed by a change of
1118 specification, with a corresponding code fix. A pattern such as
1119 ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1120 refers, was giving matches when it shouldn't. For example, xa=xaaa would
1121 match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1122 same bug. Such groups have to be quantified to be useful, or contained
1123 inside another quantified group. (If there's no repetition, the reference
1124 can never match.) The problem arises because, having left the group and
1125 moved on to the rest of the pattern, a later failure that backtracks into
1126 the group uses the captured value from the final iteration of the group
1127 rather than the correct earlier one. I have fixed this in PCRE by forcing
1128 any group that contains a reference to itself to be an atomic group; that
1129 is, there cannot be any backtracking into it once it has completed. This is
1130 similar to recursive and subroutine calls.
1131
1132
1133 Version 8.00 19-Oct-09
1134 ----------------------
1135
1136 1. The table for translating pcre_compile() error codes into POSIX error codes
1137 was out-of-date, and there was no check on the pcre_compile() error code
1138 being within the table. This could lead to an OK return being given in
1139 error.
1140
1141 2. Changed the call to open a subject file in pcregrep from fopen(pathname,
1142 "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1143 in a Windows environment.
1144
1145 3. The pcregrep --count option prints the count for each file even when it is
1146 zero, as does GNU grep. However, pcregrep was also printing all files when
1147 --files-with-matches was added. Now, when both options are given, it prints
1148 counts only for those files that have at least one match. (GNU grep just
1149 prints the file name in this circumstance, but including the count seems
1150 more useful - otherwise, why use --count?) Also ensured that the
1151 combination -clh just lists non-zero counts, with no names.
1152
1153 4. The long form of the pcregrep -F option was incorrectly implemented as
1154 --fixed_strings instead of --fixed-strings. This is an incompatible change,
1155 but it seems right to fix it, and I didn't think it was worth preserving
1156 the old behaviour.
1157
1158 5. The command line items --regex=pattern and --regexp=pattern were not
1159 recognized by pcregrep, which required --regex pattern or --regexp pattern
1160 (with a space rather than an '='). The man page documented the '=' forms,
1161 which are compatible with GNU grep; these now work.
1162
1163 6. No libpcreposix.pc file was created for pkg-config; there was just
1164 libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1165
1166 7. Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1167 when UCP support is not needed, by modifying the Python script that
1168 generates it from Unicode data files. This should not matter if the module
1169 is correctly used as a library, but I received one complaint about 50K of
1170 unwanted data. My guess is that the person linked everything into his
1171 program rather than using a library. Anyway, it does no harm.
1172
1173 8. A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1174 was a minimum greater than 1 for a wide character in a possessive
1175 repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1176 which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1177 character. Chaos in the form of incorrect output or a compiling loop could
1178 result.
1179
1180 9. The restrictions on what a pattern can contain when partial matching is
1181 requested for pcre_exec() have been removed. All patterns can now be
1182 partially matched by this function. In addition, if there are at least two
1183 slots in the offset vector, the offset of the earliest inspected character
1184 for the match and the offset of the end of the subject are set in them when
1185 PCRE_ERROR_PARTIAL is returned.
1186
1187 10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1188 synonymous with PCRE_PARTIAL, for backwards compatibility, and
1189 PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1190 and may be more useful for multi-segment matching.
1191
1192 11. Partial matching with pcre_exec() is now more intuitive. A partial match
1193 used to be given if ever the end of the subject was reached; now it is
1194 given only if matching could not proceed because another character was
1195 needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1196 string "Z", which now yields "no match" instead of "partial match". In the
1197 case of pcre_dfa_exec(), "no match" is given if every matching path for the
1198 final character ended with (*FAIL).
1199
1200 12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1201 if the pattern had a "must contain" character that was already found in the
1202 earlier partial match, unless partial matching was again requested. For
1203 example, with the pattern /dog.(body)?/, the "must contain" character is
1204 "g". If the first part-match was for the string "dog", restarting with
1205 "sbody" failed. This bug has been fixed.
1206
1207 13. The string returned by pcre_dfa_exec() after a partial match has been
1208 changed so that it starts at the first inspected character rather than the
1209 first character of the match. This makes a difference only if the pattern
1210 starts with a lookbehind assertion or \b or \B (\K is not supported by
1211 pcre_dfa_exec()). It's an incompatible change, but it makes the two
1212 matching functions compatible, and I think it's the right thing to do.
1213
1214 14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1215 so that the demonstration program is easily available in environments where
1216 PCRE has not been installed from source.
1217
1218 15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1219 libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1220 library.
1221
1222 16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1223 It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1224 is not the first non-POSIX option to be added. Clearly some people find
1225 these options useful.
1226
1227 17. If a caller to the POSIX matching function regexec() passes a non-zero
1228 value for nmatch with a NULL value for pmatch, the value of
1229 nmatch is forced to zero.
1230
1231 18. RunGrepTest did not have a test for the availability of the -u option of
1232 the diff command, as RunTest does. It now checks in the same way as
1233 RunTest, and also checks for the -b option.
1234
1235 19. If an odd number of negated classes containing just a single character
1236 interposed, within parentheses, between a forward reference to a named
1237 subpattern and the definition of the subpattern, compilation crashed with
1238 an internal error, complaining that it could not find the referenced
1239 subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1240 [The bug was that it was starting one character too far in when skipping
1241 over the character class, thus treating the ] as data rather than
1242 terminating the class. This meant it could skip too much.]
1243
1244 20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1245 /g option in pcretest when the pattern contains \K, which makes it possible
1246 to have an empty string match not at the start, even when the pattern is
1247 anchored. Updated pcretest and pcredemo to use this option.
1248
1249 21. If the maximum number of capturing subpatterns in a recursion was greater
1250 than the maximum at the outer level, the higher number was returned, but
1251 with unset values at the outer level. The correct (outer level) value is
1252 now given.
1253
1254 22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1255 PCRE did not set those parentheses (unlike Perl). I have now found a way to
1256 make it do so. The string so far is captured, making this feature
1257 compatible with Perl.
1258
1259 23. The tests have been re-organized, adding tests 11 and 12, to make it
1260 possible to check the Perl 5.10 features against Perl 5.10.
1261
1262 24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1263 pattern matches a fixed length string. PCRE did not allow this; now it
1264 does. Neither allows recursion.
1265
1266 25. I finally figured out how to implement a request to provide the minimum
1267 length of subject string that was needed in order to match a given pattern.
1268 (It was back references and recursion that I had previously got hung up
1269 on.) This code has now been added to pcre_study(); it finds a lower bound
1270 to the length of subject needed. It is not necessarily the greatest lower
1271 bound, but using it to avoid searching strings that are too short does give
1272 some useful speed-ups. The value is available to calling programs via
1273 pcre_fullinfo().
1274
1275 26. While implementing 25, I discovered to my embarrassment that pcretest had
1276 not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1277 study optimizations had never been tested with that matching function.
1278 Oops. What is worse, even when it was passed study data, there was a bug in
1279 pcre_dfa_exec() that meant it never actually used it. Double oops. There
1280 were also very few tests of studied patterns with pcre_dfa_exec().
1281
1282 27. If (?| is used to create subpatterns with duplicate numbers, they are now
1283 allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1284 on the other side of the coin, they are no longer allowed to have different
1285 names, because these cannot be distinguished in PCRE, and this has caused
1286 confusion. (This is a difference from Perl.)
1287
1288 28. When duplicate subpattern names are present (necessarily with different
1289 numbers, as required by 27 above), and a test is made by name in a
1290 conditional pattern, either for a subpattern having been matched, or for
1291 recursion in such a pattern, all the associated numbered subpatterns are
1292 tested, and the overall condition is true if the condition is true for any
1293 one of them. This is the way Perl works, and is also more like the way
1294 testing by number works.
1295
1296
1297 Version 7.9 11-Apr-09
1298 ---------------------
1299
1300 1. When building with support for bzlib/zlib (pcregrep) and/or readline
1301 (pcretest), all targets were linked against these libraries. This included
1302 libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1303 libraries. This caused unwanted dependencies to be created. This problem
1304 has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1305 pcretest is linked with readline.
1306
1307 2. The "typedef int BOOL" in pcre_internal.h that was included inside the
1308 "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1309 moved outside it again, because FALSE and TRUE are already defined in AIX,
1310 but BOOL is not.
1311
1312 3. The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1313 PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1314
1315 4. The pcregrep documentation said spaces were inserted as well as colons (or
1316 hyphens) following file names and line numbers when outputting matching
1317 lines. This is not true; no spaces are inserted. I have also clarified the
1318 wording for the --colour (or --color) option.
1319
1320 5. In pcregrep, when --colour was used with -o, the list of matching strings
1321 was not coloured; this is different to GNU grep, so I have changed it to be
1322 the same.
1323
1324 6. When --colo(u)r was used in pcregrep, only the first matching substring in
1325 each matching line was coloured. Now it goes on to look for further matches
1326 of any of the test patterns, which is the same behaviour as GNU grep.
1327
1328 7. A pattern that could match an empty string could cause pcregrep to loop; it
1329 doesn't make sense to accept an empty string match in pcregrep, so I have
1330 locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1331 seems to be how GNU grep behaves.
1332
1333 8. The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1334 start or after a newline", because the conditional assertion was not being
1335 correctly handled. The rule now is that both the assertion and what follows
1336 in the first alternative must satisfy the test.
1337
1338 9. If auto-callout was enabled in a pattern with a conditional group whose
1339 condition was an assertion, PCRE could crash during matching, both with
1340 pcre_exec() and pcre_dfa_exec().
1341
1342 10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1343 used for matching.
1344
1345 11. Unicode property support in character classes was not working for
1346 characters (bytes) greater than 127 when not in UTF-8 mode.
1347
1348 12. Added the -M command line option to pcretest.
1349
1350 14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1351
1352 15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1353
1354 16. Added comments and documentation about mis-use of no_arg in the C++
1355 wrapper.
1356
1357 17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1358 from Martin Jerabek that uses macro names for all relevant character and
1359 string constants.
1360
1361 18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1362 SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1363 SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1364 these, but not everybody uses configure.
1365
1366 19. A conditional group that had only one branch was not being correctly
1367 recognized as an item that could match an empty string. This meant that an
1368 enclosing group might also not be so recognized, causing infinite looping
1369 (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1370 with the subject "ab", where knowledge that the repeated group can match
1371 nothing is needed in order to break the loop.
1372
1373 20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1374 exec(), but without supplying a callout function, matching went wrong.
1375
1376 21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1377 leak if the size of the offset vector was greater than 30. When the vector
1378 is smaller, the saved offsets during recursion go onto a local stack
1379 vector, but for larger vectors malloc() is used. It was failing to free
1380 when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1381 error, in fact).
1382
1383 22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1384 heapframe that is used only when UTF-8 support is enabled. This caused no
1385 problem, but was untidy.
1386
1387 23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1388 CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1389 included within another project.
1390
1391 24. Steven Van Ingelgem's patches to add more options to the CMake support,
1392 slightly modified by me:
1393
1394 (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1395 not building pcregrep.
1396
1397 (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1398 if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1399
1400 25. Forward references, both numeric and by name, in patterns that made use of
1401 duplicate group numbers, could behave incorrectly or give incorrect errors,
1402 because when scanning forward to find the reference group, PCRE was not
1403 taking into account the duplicate group numbers. A pattern such as
1404 ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1405
1406 26. Changed a few more instances of "const unsigned char *" to USPTR, making
1407 the feature of a custom pointer more persuasive (as requested by a user).
1408
1409 27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1410 pcretest.c, inside #ifndefs, because it seems they are sometimes already
1411 pre-defined.
1412
1413 28. Added support for (*UTF8) at the start of a pattern.
1414
1415 29. Arrange for flags added by the "release type" setting in CMake to be shown
1416 in the configuration summary.
1417
1418
1419 Version 7.8 05-Sep-08
1420 ---------------------
1421
1422 1. Replaced UCP searching code with optimized version as implemented for Ad
1423 Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1424 stage table and inline lookup instead of a function, giving speed ups of 2
1425 to 5 times on some simple patterns that I tested. Permission was given to
1426 distribute the MultiStage2.py script that generates the tables (it's not in
1427 the tarball, but is in the Subversion repository).
1428
1429 2. Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1430 scripts.
1431
1432 3. Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1433 a group with a zero qualifier. The result of the study could be incorrect,
1434 or the function might crash, depending on the pattern.
1435
1436 4. Caseless matching was not working for non-ASCII characters in back
1437 references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1438 It now works when Unicode Property Support is available.
1439
1440 5. In pcretest, an escape such as \x{de} in the data was always generating
1441 a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1442 non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1443 truncation.
1444
1445 6. Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1446
1447 7. Added two (int) casts to pcregrep when printing the difference of two
1448 pointers, in case they are 64-bit values.
1449
1450 8. Added comments about Mac OS X stack usage to the pcrestack man page and to
1451 test 2 if it fails.
1452
1453 9. Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1454 and a #define of that name to empty if it is not externally set. This is to
1455 allow users of MSVC to set it if necessary.
1456
1457 10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1458 the convenience functions in the pcre_get.c source file.
1459
1460 11. An option change at the start of a pattern that had top-level alternatives
1461 could cause overwriting and/or a crash. This command provoked a crash in
1462 some environments:
1463
1464 printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1465
1466 This potential security problem was recorded as CVE-2008-2371.
1467
1468 12. For a pattern where the match had to start at the beginning or immediately
1469 after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1470 pcre_dfa_exec() could read past the end of the passed subject if there was
1471 no match. To help with detecting such bugs (e.g. with valgrind), I modified
1472 pcretest so that it places the subject at the end of its malloc-ed buffer.
1473
1474 13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1475 exec() might read past the end of the data buffer in UTF-8 mode.
1476
1477 14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1478 the data contained the byte 0x85 as part of a UTF-8 character within its
1479 first line. This applied both to normal and DFA matching.
1480
1481 15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1482 /^[^d]*?$/8 failed to match "abc".
1483
1484 16. Added a missing copyright notice to pcrecpp_internal.h.
1485
1486 17. Make it more clear in the documentation that values returned from
1487 pcre_exec() in ovector are byte offsets, not character counts.
1488
1489 18. Tidied a few places to stop certain compilers from issuing warnings.
1490
1491 19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1492 supplied by Stefan Weber. I made a further small update for 7.8 because
1493 there is a change of source arrangements: the pcre_searchfuncs.c module is
1494 replaced by pcre_ucd.c.
1495
1496
1497 Version 7.7 07-May-08
1498 ---------------------
1499
1500 1. Applied Craig's patch to sort out a long long problem: "If we can't convert
1501 a string to a long long, pretend we don't even have a long long." This is
1502 done by checking for the strtoq, strtoll, and _strtoi64 functions.
1503
1504 2. Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1505 pre-7.6 versions, which defined a global no_arg variable instead of putting
1506 it in the RE class. (See also #8 below.)
1507
1508 3. Remove a line of dead code, identified by coverity and reported by Nuno
1509 Lopes.
1510
1511 4. Fixed two related pcregrep bugs involving -r with --include or --exclude:
1512
1513 (1) The include/exclude patterns were being applied to the whole pathnames
1514 of files, instead of just to the final components.
1515
1516 (2) If there was more than one level of directory, the subdirectories were
1517 skipped unless they satisfied the include/exclude conditions. This is
1518 inconsistent with GNU grep (and could even be seen as contrary to the
1519 pcregrep specification - which I improved to make it absolutely clear).
1520 The action now is always to scan all levels of directory, and just
1521 apply the include/exclude patterns to regular files.
1522
1523 5. Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1524 --exclude_dir in the tests to avoid scanning .svn directories.
1525
1526 6. Applied Craig's patch to the QuoteMeta function so that it escapes the
1527 NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1528 doesn't support NULs in patterns.
1529
1530 7. Added some missing "const"s to declarations of static tables in
1531 pcre_compile.c and pcre_dfa_exec.c.
1532
1533 8. Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1534 caused by fix #2 above. (Subsequently also a second patch to fix the
1535 first patch. And a third patch - this was a messy problem.)
1536
1537 9. Applied Craig's patch to remove the use of push_back().
1538
1539 10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1540 matching function regexec().
1541
1542 11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1543 which, however, unlike Perl's \g{...}, are subroutine calls, not back
1544 references. PCRE supports relative numbers with this syntax (I don't think
1545 Oniguruma does).
1546
1547 12. Previously, a group with a zero repeat such as (...){0} was completely
1548 omitted from the compiled regex. However, this means that if the group
1549 was called as a subroutine from elsewhere in the pattern, things went wrong
1550 (an internal error was given). Such groups are now left in the compiled
1551 pattern, with a new opcode that causes them to be skipped at execution
1552 time.
1553
1554 13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1555 to the way PCRE behaves:
1556
1557 (a) A lone ] character is dis-allowed (Perl treats it as data).
1558
1559 (b) A back reference to an unmatched subpattern matches an empty string
1560 (Perl fails the current match path).
1561
1562 (c) A data ] in a character class must be notated as \] because if the
1563 first data character in a class is ], it defines an empty class. (In
1564 Perl it is not possible to have an empty class.) The empty class []
1565 never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1566 The negative empty class [^] matches any one character, independently
1567 of the DOTALL setting.
1568
1569 14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1570 non-existent subpattern following a character class starting with ']' and
1571 containing () gave an internal compiling error instead of "reference to
1572 non-existent subpattern". Fortunately, when the pattern did exist, the
1573 compiled code was correct. (When scanning forwards to check for the
1574 existencd of the subpattern, it was treating the data ']' as terminating
1575 the class, so got the count wrong. When actually compiling, the reference
1576 was subsequently set up correctly.)
1577
1578 15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1579 it was being rejected as not supported by pcre_dfa_exec(), even though
1580 other assertions are supported. I have made pcre_dfa_exec() support
1581 (*FAIL).
1582
1583 16. The implementation of 13c above involved the invention of a new opcode,
1584 OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1585 cannot be changed at match time, I realized I could make a small
1586 improvement to matching performance by compiling OP_ALLANY instead of
1587 OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1588 on the OP_ANY path.
1589
1590 17. Compiling pcretest on Windows with readline support failed without the
1591 following two fixes: (1) Make the unistd.h include conditional on
1592 HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1593
1594 18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1595 ncurses library to be included for pcretest when ReadLine support is
1596 requested, but also to allow for it to be overridden. This patch came from
1597 Daniel Bergström.
1598
1599 19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1600 as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1601 any errors with the current Unicode tables. Thanks to Peter Kankowski for
1602 spotting this.
1603
1604
1605 Version 7.6 28-Jan-08
1606 ---------------------
1607
1608 1. A character class containing a very large number of characters with
1609 codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
1610 overflow.
1611
1612 2. Patch to cut out the "long long" test in pcrecpp_unittest when
1613 HAVE_LONG_LONG is not defined.
1614
1615 3. Applied Christian Ehrlicher's patch to update the CMake build files to
1616 bring them up to date and include new features. This patch includes:
1617
1618 - Fixed PH's badly added libz and libbz2 support.
1619 - Fixed a problem with static linking.
1620 - Added pcredemo. [But later removed - see 7 below.]
1621 - Fixed dftables problem and added an option.
1622 - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
1623 HAVE_LONG_LONG.
1624 - Added readline support for pcretest.
1625 - Added an listing of the option settings after cmake has run.
1626
1627 4. A user submitted a patch to Makefile that makes it easy to create
1628 "pcre.dll" under mingw when using Configure/Make. I added stuff to
1629 Makefile.am that cause it to include this special target, without
1630 affecting anything else. Note that the same mingw target plus all
1631 the other distribution libraries and programs are now supported
1632 when configuring with CMake (see 6 below) instead of with
1633 Configure/Make.
1634
1635 5. Applied Craig's patch that moves no_arg into the RE class in the C++ code.
1636 This is an attempt to solve the reported problem "pcrecpp::no_arg is not
1637 exported in the Windows port". It has not yet been confirmed that the patch
1638 solves the problem, but it does no harm.
1639
1640 6. Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
1641 NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
1642 with CMake, and also correct the comment about stack recursion.
1643
1644 7. Remove the automatic building of pcredemo from the ./configure system and
1645 from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
1646 of a program that users should build themselves after PCRE is installed, so
1647 building it automatically is not really right. What is more, it gave
1648 trouble in some build environments.
1649
1650 8. Further tidies to CMakeLists.txt from Sheri and Christian.
1651
1652
1653 Version 7.5 10-Jan-08
1654 ---------------------
1655
1656 1. Applied a patch from Craig: "This patch makes it possible to 'ignore'
1657 values in parens when parsing an RE using the C++ wrapper."
1658
1659 2. Negative specials like \S did not work in character classes in UTF-8 mode.
1660 Characters greater than 255 were excluded from the class instead of being
1661 included.
1662
1663 3. The same bug as (2) above applied to negated POSIX classes such as
1664 [:^space:].
1665
1666 4. PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
1667 defined or documented. It seems to have been a typo for PCRE_STATIC, so
1668 I have changed it.
1669
1670 5. The construct (?&) was not diagnosed as a syntax error (it referenced the
1671 first named subpattern) and a construct such as (?&a) would reference the
1672 first named subpattern whose name started with "a" (in other words, the
1673 length check was missing). Both these problems are fixed. "Subpattern name
1674 expected" is now given for (?&) (a zero-length name), and this patch also
1675 makes it give the same error for \k'' (previously it complained that that
1676 was a reference to a non-existent subpattern).
1677
1678 6. The erroneous patterns (?+-a) and (?-+a) give different error messages;
1679 this is right because (?- can be followed by option settings as well as by
1680 digits. I have, however, made the messages clearer.
1681
1682 7. Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1683 than the number used in the conditional) now cause a compile-time error.
1684 This is actually not compatible with Perl, which accepts such patterns, but
1685 treats the conditional as always being FALSE (as PCRE used to), but it
1686 seems to me that giving a diagnostic is better.
1687
1688 8. Change "alphameric" to the more common word "alphanumeric" in comments
1689 and messages.
1690
1691 9. Fix two occurrences of "backslash" in comments that should have been
1692 "backspace".
1693
1694 10. Remove two redundant lines of code that can never be obeyed (their function
1695 was moved elsewhere).
1696
1697 11. The program that makes PCRE's Unicode character property table had a bug
1698 which caused it to generate incorrect table entries for sequences of
1699 characters that have the same character type, but are in different scripts.
1700 It amalgamated them into a single range, with the script of the first of
1701 them. In other words, some characters were in the wrong script. There were
1702 thirteen such cases, affecting characters in the following ranges:
1703
1704 U+002b0 - U+002c1
1705 U+0060c - U+0060d
1706 U+0061e - U+00612
1707 U+0064b - U+0065e
1708 U+0074d - U+0076d
1709 U+01800 - U+01805
1710 U+01d00 - U+01d77
1711 U+01d9b - U+01dbf
1712 U+0200b - U+0200f
1713 U+030fc - U+030fe
1714 U+03260 - U+0327f
1715 U+0fb46 - U+0fbb1
1716 U+10450 - U+1049d
1717
1718 12. The -o option (show only the matching part of a line) for pcregrep was not
1719 compatible with GNU grep in that, if there was more than one match in a
1720 line, it showed only the first of them. It now behaves in the same way as
1721 GNU grep.
1722
1723 13. If the -o and -v options were combined for pcregrep, it printed a blank
1724 line for every non-matching line. GNU grep prints nothing, and pcregrep now
1725 does the same. The return code can be used to tell if there were any
1726 non-matching lines.
1727
1728 14. Added --file-offsets and --line-offsets to pcregrep.
1729
1730 15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1731 infinitely looping recursion. The bug was that positive lookaheads were not
1732 being skipped when checking for a possible empty match (negative lookaheads
1733 and both kinds of lookbehind were skipped).
1734
1735 16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1736 inclusion of <windows.h> to before rather than after the definition of
1737 INVALID_FILE_ATTRIBUTES (patch from David Byron).
1738
1739 17. Specifying a possessive quantifier with a specific limit for a Unicode
1740 character property caused pcre_compile() to compile bad code, which led at
1741 runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1742 are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1743 caused the error; without that there was no problem.
1744
1745 18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1746
1747 19. Added --enable-pcretest-libreadline.
1748
1749 20. In pcrecpp.cc, the variable 'count' was incremented twice in
1750 RE::GlobalReplace(). As a result, the number of replacements returned was
1751 double what it should be. I removed one of the increments, but Craig sent a
1752 later patch that removed the other one (the right fix) and added unit tests
1753 that check the return values (which was not done before).
1754
1755 21. Several CMake things:
1756
1757 (1) Arranged that, when cmake is used on Unix, the libraries end up with
1758 the names libpcre and libpcreposix, not just pcre and pcreposix.
1759
1760 (2) The above change means that pcretest and pcregrep are now correctly
1761 linked with the newly-built libraries, not previously installed ones.
1762
1763 (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
1764
1765 22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1766 crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1767 UTF-8 newline character). The key issue is that the pattern starts .*;
1768 this means that the match must be either at the beginning, or after a
1769 newline. The bug was in the code for advancing after a failed match and
1770 checking that the new position followed a newline. It was not taking
1771 account of UTF-8 characters correctly.
1772
1773 23. PCRE was behaving differently from Perl in the way it recognized POSIX
1774 character classes. PCRE was not treating the sequence [:...:] as a
1775 character class unless the ... were all letters. Perl, however, seems to
1776 allow any characters between [: and :], though of course it rejects as
1777 unknown any "names" that contain non-letters, because all the known class
1778 names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1779 for example, whereas PCRE did not - it did not recognize a POSIX character
1780 class. This seemed a bit dangerous, so the code has been changed to be
1781 closer to Perl. The behaviour is not identical to Perl, because PCRE will
1782 diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1783 treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1784 Perl does, and where it didn't before.
1785
1786 24. Rewrite so as to remove the single use of %n from pcregrep because in some
1787 Windows environments %n is disabled by default.
1788
1789
1790 Version 7.4 21-Sep-07
1791 ---------------------
1792
1793 1. Change 7.3/28 was implemented for classes by looking at the bitmap. This
1794 means that a class such as [\s] counted as "explicit reference to CR or
1795 LF". That isn't really right - the whole point of the change was to try to
1796 help when there was an actual mention of one of the two characters. So now
1797 the change happens only if \r or \n (or a literal CR or LF) character is
1798 encountered.
1799
1800 2. The 32-bit options word was also used for 6 internal flags, but the numbers
1801 of both had grown to the point where there were only 3 bits left.
1802 Fortunately, there was spare space in the data structure, and so I have
1803 moved the internal flags into a new 16-bit field to free up more option
1804 bits.
1805
1806 3. The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1807 but did not set the internal JCHANGED flag - either of these is enough to
1808 control the way the "get" function works - but the PCRE_INFO_JCHANGED
1809 facility is supposed to tell if (?J) was ever used, so now (?J) at the
1810 start sets both bits.
1811
1812 4. Added options (at build time, compile time, exec time) to change \R from
1813 matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1814
1815 5. doc/pcresyntax.html was missing from the distribution.
1816
1817 6. Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1818 compatibility, even though it is no longer used.
1819
1820 7. Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1821 strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1822 windows.h file is present (where different names are used). [This was
1823 reversed later after testing - see 16 below.]
1824
1825 8. Changed all #include <config.h> to #include "config.h". There were also
1826 some further <pcre.h> cases that I changed to "pcre.h".
1827
1828 9. When pcregrep was used with the --colour option, it missed the line ending
1829 sequence off the lines that it output.
1830
1831 10. It was pointed out to me that arrays of string pointers cause lots of
1832 relocations when a shared library is dynamically loaded. A technique of
1833 using a single long string with a table of offsets can drastically reduce
1834 these. I have refactored PCRE in four places to do this. The result is
1835 dramatic:
1836
1837 Originally: 290
1838 After changing UCP table: 187
1839 After changing error message table: 43
1840 After changing table of "verbs" 36
1841 After changing table of Posix names 22
1842
1843 Thanks to the folks working on Gregex for glib for this insight.
1844
1845 11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1846 unicode-properties was also set.
1847
1848 12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1849
1850 13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1851 checked only for CRLF.
1852
1853 14. Added casts to pcretest.c to avoid compiler warnings.
1854
1855 15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1856
1857 16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1858 and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1859 entirely. This removes changes made in 7 above.
1860
1861 17. The CMake files have been updated, and there is now more information about
1862 building with CMake in the NON-UNIX-USE document.
1863
1864
1865 Version 7.3 28-Aug-07
1866 ---------------------
1867
1868 1. In the rejigging of the build system that eventually resulted in 7.1, the
1869 line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
1870 brackets there is not right, since it causes compilers to look for an
1871 installed pcre.h, not the version that is in the source that is being
1872 compiled (which of course may be different). I have changed it back to:
1873
1874 #include "pcre.h"
1875
1876 I have a vague recollection that the change was concerned with compiling in
1877 different directories, but in the new build system, that is taken care of
1878 by the VPATH setting the Makefile.
1879
1880 2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
1881 when the subject happened to end in the byte 0x85 (e.g. if the last
1882 character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
1883 characters but of course it shouldn't be taken as a newline when it is part
1884 of another character. The bug was that, for an unlimited repeat of . in
1885 not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
1886 characters when looking for a newline.
1887
1888 3. A small performance improvement in the DOTALL UTF-8 mode .* case.
1889
1890 4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1891 in debug output.
1892
1893 5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1894 long printing in the pcrecpp unittest when running under MinGW.
1895
1896 6. ESC_K was left out of the EBCDIC table.
1897
1898 7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
1899 parentheses; I made it 1000, which seemed large enough. Unfortunately, the
1900 limit also applies to "virtual nesting" when a pattern is recursive, and in
1901 this case 1000 isn't so big. I have been able to remove this limit at the
1902 expense of backing off one optimization in certain circumstances. Normally,
1903 when pcre_exec() would call its internal match() function recursively and
1904 immediately return the result unconditionally, it uses a "tail recursion"
1905 feature to save stack. However, when a subpattern that can match an empty
1906 string has an unlimited repetition quantifier, it no longer makes this
1907 optimization. That gives it a stack frame in which to save the data for
1908 checking that an empty string has been matched. Previously this was taken
1909 from the 1000-entry workspace that had been reserved. So now there is no
1910 explicit limit, but more stack is used.
1911
1912 8. Applied Daniel's patches to solve problems with the import/export magic
1913 syntax that is required for Windows, and which was going wrong for the
1914 pcreposix and pcrecpp parts of the library. These were overlooked when this
1915 problem was solved for the main library.
1916
1917 9. There were some crude static tests to avoid integer overflow when computing
1918 the size of patterns that contain repeated groups with explicit upper
1919 limits. As the maximum quantifier is 65535, the maximum group length was
1920 set at 30,000 so that the product of these two numbers did not overflow a
1921 32-bit integer. However, it turns out that people want to use groups that
1922 are longer than 30,000 bytes (though not repeat them that many times).
1923 Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1924 made it possible to implement the integer overflow checks in a much more
1925 dynamic way, which I have now done. The artificial limitation on group
1926 length has been removed - we now have only the limit on the total length of
1927 the compiled pattern, which depends on the LINK_SIZE setting.
1928
1929 10. Fixed a bug in the documentation for get/copy named substring when
1930 duplicate names are permitted. If none of the named substrings are set, the
1931 functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1932 empty string.
1933
1934 11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1935 instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1936 because the ] is interpreted as the first data character and the
1937 terminating ] is not found. PCRE has been made compatible with Perl in this
1938 regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1939 cause memory overwriting.
1940
1941 10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1942 string has been matched (to stop an infinite loop). It was not recognizing
1943 a conditional subpattern that could match an empty string if that
1944 subpattern was within another subpattern. For example, it looped when
1945 trying to match (((?(1)X|))*) but it was OK with ((?(1)X|)*) where the
1946 condition was not nested. This bug has been fixed.
1947
1948 12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1949 past the start of the subject in the presence of bytes with the top bit
1950 set, for example "\x8aBCD".
1951
1952 13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1953 (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1954
1955 14. Optimized (?!) to (*FAIL).
1956
1957 15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1958 This restricts code points to be within the range 0 to 0x10FFFF, excluding
1959 the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1960 full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1961 does: it's just the validity check that is more restrictive.
1962
1963 16. Inserted checks for integer overflows during escape sequence (backslash)
1964 processing, and also fixed erroneous offset values for syntax errors during
1965 backslash processing.
1966
1967 17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1968 for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1969
1970 18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1971 caused an overrun.
1972
1973 19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1974 something other than just ASCII characters) inside a group that had an
1975 unlimited repeat caused a loop at compile time (while checking to see
1976 whether the group could match an empty string).
1977
1978 20. Debugging a pattern containing \p or \P could cause a crash. For example,
1979 [\P{Any}] did so. (Error in the code for printing property names.)
1980
1981 21. An orphan \E inside a character class could cause a crash.
1982
1983 22. A repeated capturing bracket such as (A)? could cause a wild memory
1984 reference during compilation.
1985
1986 23. There are several functions in pcre_compile() that scan along a compiled
1987 expression for various reasons (e.g. to see if it's fixed length for look
1988 behind). There were bugs in these functions when a repeated \p or \P was
1989 present in the pattern. These operators have additional parameters compared
1990 with \d, etc, and these were not being taken into account when moving along
1991 the compiled data. Specifically:
1992
1993 (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1994 length.
1995
1996 (b) An item such as \pL+ within a repeated group could cause crashes or
1997 loops.
1998
1999 (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
2000 "reference to non-existent subpattern" error.
2001
2002 (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
2003
2004 24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
2005 characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
2006
2007 25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
2008
2009 26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
2010 character were causing crashes (broken optimization).
2011
2012 27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
2013 \p or \P) caused a compile-time loop.
2014
2015 28. More problems have arisen in unanchored patterns when CRLF is a valid line
2016 break. For example, the unstudied pattern [\r\n]A does not match the string
2017 "\r\nA" because change 7.0/46 below moves the current point on by two
2018 characters after failing to match at the start. However, the pattern \nA
2019 *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
2020 the same is true. There doesn't seem any very clean way out of this, but
2021 what I have chosen to do makes the common cases work: PCRE now takes note
2022 of whether there can be an explicit match for \r or \n anywhere in the
2023 pattern, and if so, 7.0/46 no longer applies. As part of this change,
2024 there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
2025 pattern has explicit CR or LF references.
2026
2027 29. Added (*CR) etc for changing newline setting at start of pattern.
2028
2029
2030 Version 7.2 19-Jun-07
2031 ---------------------
2032
2033 1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
2034 which is apparently normally available under Windows.
2035
2036 2. Re-jig the pcregrep tests with different newline settings in an attempt
2037 to make them independent of the local environment's newline setting.
2038
2039 3. Add code to configure.ac to remove -g from the CFLAGS default settings.
2040
2041 4. Some of the "internals" tests were previously cut out when the link size
2042 was not 2, because the output contained actual offsets. The recent new
2043 "Z" feature of pcretest means that these can be cut out, making the tests
2044 usable with all link sizes.
2045
2046 5. Implemented Stan Switzer's goto replacement for longjmp() when not using
2047 stack recursion. This gives a massive performance boost under BSD, but just
2048 a small improvement under Linux. However, it saves one field in the frame
2049 in all cases.
2050
2051 6. Added more features from the forthcoming Perl 5.10:
2052
2053 (a) (?-n) (where n is a string of digits) is a relative subroutine or
2054 recursion call. It refers to the nth most recently opened parentheses.
2055
2056 (b) (?+n) is also a relative subroutine call; it refers to the nth next
2057 to be opened parentheses.
2058
2059 (c) Conditions that refer to capturing parentheses can be specified
2060 relatively, for example, (?(-2)... or (?(+3)...
2061
2062 (d) \K resets the start of the current match so that everything before
2063 is not part of it.
2064
2065 (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
2066
2067 (f) \g{name} is another synonym - part of Perl 5.10's unification of
2068 reference syntax.
2069
2070 (g) (?| introduces a group in which the numbering of parentheses in each
2071 alternative starts with the same number.
2072
2073 (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
2074
2075 7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
2076 PCRE_INFO_JCHANGED.
2077
2078 8. A pattern such as (.*(.)?)* caused pcre_exec() to fail by either not
2079 terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
2080 for detecting groups that can match an empty string.
2081
2082 9. A pattern with a very large number of alternatives (more than several
2083 hundred) was running out of internal workspace during the pre-compile
2084 phase, where pcre_compile() figures out how much memory will be needed. A
2085 bit of new cunning has reduced the workspace needed for groups with
2086 alternatives. The 1000-alternative test pattern now uses 12 bytes of
2087 workspace instead of running out of the 4096 that are available.
2088
2089 10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
2090
2091 11. Applied patch from Google to remove an optimization that didn't quite work.
2092 The report of the bug said:
2093
2094 pcrecpp::RE("a*").FullMatch("aaa") matches, while
2095 pcrecpp::RE("a*?").FullMatch("aaa") does not, and
2096 pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
2097
2098 12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
2099 it matched the wrong number of bytes.
2100
2101
2102 Version 7.1 24-Apr-07
2103 ---------------------
2104
2105 1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
2106 that is more "standard", making use of automake and other Autotools. There
2107 is some re-arrangement of the files and adjustment of comments consequent
2108 on this.
2109
2110 2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
2111 for recursive directory scanning broke on some systems because the files
2112 are not scanned in any specific order and on different systems the order
2113 was different. A call to "sort" has been inserted into RunGrepTest for the
2114 approprate test as a short-term fix. In the longer term there may be an
2115 alternative.
2116
2117 3. I had an email from Eric Raymond about problems translating some of PCRE's
2118 man pages to HTML (despite the fact that I distribute HTML pages, some
2119 people do their own conversions for various reasons). The problems
2120 concerned the use of low-level troff macros .br and .in. I have therefore
2121 removed all such uses from the man pages (some were redundant, some could
2122 be replaced by .nf/.fi pairs). The 132html script that I use to generate
2123 HTML has been updated to handle .nf/.fi and to complain if it encounters
2124 .br or .in.
2125
2126 4. Updated comments in configure.ac that get placed in config.h.in and also
2127 arranged for config.h to be included in the distribution, with the name
2128 config.h.generic, for the benefit of those who have to compile without
2129 Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
2130
2131 5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
2132 Weber: (1) pcre_internal.h was missing some function renames; (2) updated
2133 makevp.bat for the current PCRE, using the additional files
2134 makevp_c.txt, makevp_l.txt, and pcregexp.pas.
2135
2136 6. A Windows user reported a minor discrepancy with test 2, which turned out
2137 to be caused by a trailing space on an input line that had got lost in his
2138 copy. The trailing space was an accident, so I've just removed it.
2139
2140 7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
2141 that is needed.
2142
2143 8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
2144 as "const" (a) because they are and (b) because it helps the PHP
2145 maintainers who have recently made a script to detect big data structures
2146 in the php code that should be moved to the .rodata section. I remembered
2147 to update Builducptable as well, so it won't revert if ucptable.h is ever
2148 re-created.
2149
2150 9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
2151 pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
2152 order to be able to cut out the UTF-8 tables in the latter when UTF-8
2153 support is not required. This saves 1.5-2K of code, which is important in
2154 some applications.
2155
2156 Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
2157 so as not to refer to the tables, even though these functions will never be
2158 called when UTF-8 support is disabled. Otherwise there are problems with a
2159 shared library.
2160
2161 10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
2162
2163 (a) It was defining its arguments as char * instead of void *.
2164
2165 (b) It was assuming that all moves were upwards in memory; this was true
2166 a long time ago when I wrote it, but is no longer the case.
2167
2168 The emulated memove() is provided for those environments that have neither
2169 memmove() nor bcopy(). I didn't think anyone used it these days, but that
2170 is clearly not the case, as these two bugs were recently reported.
2171
2172 11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
2173 and Detrail to create the HTML documentation, the .txt form of the man
2174 pages, and it removes trailing spaces from listed files. It also creates
2175 pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
2176 case, it wraps all the #defines with #ifndefs. This script should be run
2177 before "make dist".
2178
2179 12. Fixed two fairly obscure bugs concerned with quantified caseless matching
2180 with Unicode property support.
2181
2182 (a) For a maximizing quantifier, if the two different cases of the
2183 character were of different lengths in their UTF-8 codings (there are
2184 some cases like this - I found 11), and the matching function had to
2185 back up over a mixture of the two cases, it incorrectly assumed they
2186 were both the same length.
2187
2188 (b) When PCRE was configured to use the heap rather than the stack for
2189 recursion during matching, it was not correctly preserving the data for
2190 the other case of a UTF-8 character when checking ahead for a match
2191 while processing a minimizing repeat. If the check also involved
2192 matching a wide character, but failed, corruption could cause an
2193 erroneous result when trying to check for a repeat of the original
2194 character.
2195
2196 13. Some tidying changes to the testing mechanism:
2197
2198 (a) The RunTest script now detects the internal link size and whether there
2199 is UTF-8 and UCP support by running ./pcretest -C instead of relying on
2200 values substituted by "configure". (The RunGrepTest script already did
2201 this for UTF-8.) The configure.ac script no longer substitutes the
2202 relevant variables.
2203
2204 (b) The debugging options /B and /D in pcretest show the compiled bytecode
2205 with length and offset values. This means that the output is different
2206 for different internal link sizes. Test 2 is skipped for link sizes
2207 other than 2 because of this, bypassing the problem. Unfortunately,
2208 there was also a test in test 3 (the locale tests) that used /B and
2209 failed for link sizes other than 2. Rather than cut the whole test out,
2210 I have added a new /Z option to pcretest that replaces the length and
2211 offset values with spaces. This is now used to make test 3 independent
2212 of link size. (Test 2 will be tidied up later.)
2213
2214 14. If erroroffset was passed as NULL to pcre_compile, it provoked a
2215 segmentation fault instead of returning the appropriate error message.
2216
2217 15. In multiline mode when the newline sequence was set to "any", the pattern
2218 ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
2219 This doesn't seem right; it now treats the CRLF combination as the line
2220 ending, and so does not match in that case. It's only a pattern such as ^$
2221 that would hit this one: something like ^ABC$ would have failed after \r
2222 and then tried again after \r\n.
2223
2224 16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
2225 in an attempt to make files that differ only in their line terminators
2226 compare equal. This works on Linux.
2227
2228 17. Under certain error circumstances pcregrep might try to free random memory
2229 as it exited. This is now fixed, thanks to valgrind.
2230
2231 19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
2232 "abc\r\n\r\n", it found an unwanted second match after the second \r. This
2233 was because its rules for how to advance for /g after matching an empty
2234 string at the end of a line did not allow for this case. They now check for
2235 it specially.
2236
2237 20. pcretest is supposed to handle patterns and data of any length, by
2238 extending its buffers when necessary. It was getting this wrong when the
2239 buffer for a data line had to be extended.
2240
2241 21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
2242 CRLF as a newline sequence.
2243
2244 22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
2245 out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
2246 I have nevertheless tidied it up.
2247
2248 23. Added some casts to kill warnings from HP-UX ia64 compiler.
2249
2250 24. Added a man page for pcre-config.
2251
2252
2253 Version 7.0 19-Dec-06
2254 ---------------------
2255
2256 1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
2257 moving to gcc 4.1.1.
2258
2259 2. The -S option for pcretest uses setrlimit(); I had omitted to #include
2260 sys/time.h, which is documented as needed for this function. It doesn't
2261 seem to matter on Linux, but it showed up on some releases of OS X.
2262
2263 3. It seems that there are systems where bytes whose values are greater than
2264 127 match isprint() in the "C" locale. The "C" locale should be the
2265 default when a C program starts up. In most systems, only ASCII printing
2266 characters match isprint(). This difference caused the output from pcretest
2267 to vary, making some of the tests fail. I have changed pcretest so that:
2268
2269 (a) When it is outputting text in the compiled version of a pattern, bytes
2270 other than 32-126 are always shown as hex escapes.
2271
2272 (b) When it is outputting text that is a matched part of a subject string,
2273 it does the same, unless a different locale has been set for the match
2274 (using the /L modifier). In this case, it uses isprint() to decide.
2275
2276 4. Fixed a major bug that caused incorrect computation of the amount of memory
2277 required for a compiled pattern when options that changed within the
2278 pattern affected the logic of the preliminary scan that determines the
2279 length. The relevant options are -x, and -i in UTF-8 mode. The result was
2280 that the computed length was too small. The symptoms of this bug were
2281 either the PCRE error "internal error: code overflow" from pcre_compile(),
2282 or a glibc crash with a message such as "pcretest: free(): invalid next
2283 size (fast)". Examples of patterns that provoked this bug (shown in
2284 pcretest format) are:
2285
2286 /(?-x: )/x
2287 /(?x)(?-x: \s*#\s*)/
2288 /((?i)[\x{c0}])/8
2289 /(?i:[\x{c0}])/8
2290
2291 HOWEVER: Change 17 below makes this fix obsolete as the memory computation
2292 is now done differently.
2293
2294 5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
2295 wrapper classes; (b) implement a new function in the C++ scanner that is
2296 more efficient than the old way of doing things because it avoids levels of
2297 recursion in the regex matching; (c) add a paragraph to the documentation
2298 for the FullMatch() function.
2299
2300 6. The escape sequence \n was being treated as whatever was defined as
2301 "newline". Not only was this contrary to the documentation, which states
2302 that \n is character 10 (hex 0A), but it also went horribly wrong when
2303 "newline" was defined as CRLF. This has been fixed.
2304
2305 7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
2306 was being set to -1 for the "end of line" case (supposedly a value that no
2307 character can have). Though this value is never used (the check for end of
2308 line is "zero bytes in current character"), it caused compiler complaints.
2309 I've changed it to 0xffffffff.
2310
2311 8. In pcre_version.c, the version string was being built by a sequence of
2312 C macros that, in the event of PCRE_PRERELEASE being defined as an empty
2313 string (as it is for production releases) called a macro with an empty
2314 argument. The C standard says the result of this is undefined. The gcc
2315 compiler treats it as an empty string (which was what was wanted) but it is
2316 reported that Visual C gives an error. The source has been hacked around to
2317 avoid this problem.
2318
2319 9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
2320 builds of pcretest, and changed the call to _setmode() to use _O_BINARY
2321 instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
2322 of them did).
2323
2324 10. Originally, pcretest opened its input and output without "b"; then I was
2325 told that "b" was needed in some environments, so it was added for release
2326 5.0 to both the input and output. (It makes no difference on Unix-like
2327 systems.) Later I was told that it is wrong for the input on Windows. I've
2328 now abstracted the modes into two macros, to make it easier to fiddle with
2329 them, and removed "b" from the input mode under Windows.
2330
2331 11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
2332
2333 12. Added -help and --help to pcretest as an official way of being reminded
2334 of the options.
2335
2336 13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
2337 and pcrecpp.cc because they annoy compilers at high warning levels.
2338
2339 14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
2340
2341 15. Fixed an occurrence of == in configure.ac that should have been = (shell
2342 scripts are not C programs :-) and which was not noticed because it works
2343 on Linux.
2344
2345 16. pcretest is supposed to handle any length of pattern and data line (as one
2346 line or as a continued sequence of lines) by extending its input buffer if
2347 necessary. This feature was broken for very long pattern lines, leading to
2348 a string of junk being passed to pcre_compile() if the pattern was longer
2349 than about 50K.
2350
2351 17. I have done a major re-factoring of the way pcre_compile() computes the
2352 amount of memory needed for a compiled pattern. Previously, there was code
2353 that made a preliminary scan of the pattern in order to do this. That was
2354 OK when PCRE was new, but as the facilities have expanded, it has become
2355 harder and harder to keep it in step with the real compile phase, and there
2356 have been a number of bugs (see for example, 4 above). I have now found a
2357 cunning way of running the real compile function in a "fake" mode that
2358 enables it to compute how much memory it would need, while actually only
2359 ever using a few hundred bytes of working memory and without too many
2360 tests of the mode. This should make future maintenance and development
2361 easier. A side effect of this work is that the limit of 200 on the nesting
2362 depth of parentheses has been removed (though this was never a serious
2363 limitation, I suspect). However, there is a downside: pcre_compile() now
2364 runs more slowly than before (30% or more, depending on the pattern). I
2365 hope this isn't a big issue. There is no effect on runtime performance.
2366
2367 18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
2368 newline (only possible for the last line of a file) and it was a
2369 pattern that set a locale (followed by /Lsomething), pcretest crashed.
2370
2371 19. Added additional timing features to pcretest. (1) The -tm option now times
2372 matching only, not compiling. (2) Both -t and -tm can be followed, as a
2373 separate command line item, by a number that specifies the number of
2374 repeats to use when timing. The default is 50000; this gives better
2375 precision, but takes uncomfortably long for very large patterns.
2376
2377 20. Extended pcre_study() to be more clever in cases where a branch of a
2378 subpattern has no definite first character. For example, (a*|b*)[cd] would
2379 previously give no result from pcre_study(). Now it recognizes that the
2380 first character must be a, b, c, or d.
2381
2382 21. There was an incorrect error "recursive call could loop indefinitely" if
2383 a subpattern (or the entire pattern) that was being tested for matching an
2384 empty string contained only one non-empty item after a nested subpattern.
2385 For example, the pattern (?>\x{100}*)\d(?R) provoked this error
2386 incorrectly, because the \d was being skipped in the check.
2387
2388 22. The pcretest program now has a new pattern option /B and a command line
2389 option -b, which is equivalent to adding /B to every pattern. This causes
2390 it to show the compiled bytecode, without the additional information that
2391 -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
2392 is the same as /B/I).
2393
2394 23. A new optimization is now able automatically to treat some sequences such
2395 as a*b as a*+b. More specifically, if something simple (such as a character
2396 or a simple class like \d) has an unlimited quantifier, and is followed by
2397 something that cannot possibly match the quantified thing, the quantifier
2398 is automatically "possessified".
2399
2400 24. A recursive reference to a subpattern whose number was greater than 39
2401 went wrong under certain circumstances in UTF-8 mode. This bug could also
2402 have affected the operation of pcre_study().
2403
2404 25. Realized that a little bit of performance could be had by replacing
2405 (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
2406
2407 26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
2408
2409 27. Possessive quantifiers such as a++ were previously implemented by turning
2410 them into atomic groups such as ($>a+). Now they have their own opcodes,
2411 which improves performance. This includes the automatically created ones
2412 from 23 above.
2413
2414 28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
2415 lookahead was broken if it was not anchored. PCRE was mistakenly expecting
2416 the first matched character to be a colon. This applied both to named and
2417 numbered groups.
2418
2419 29. The ucpinternal.h header file was missing its idempotency #ifdef.
2420
2421 30. I was sent a "project" file called libpcre.a.dev which I understand makes
2422 building PCRE on Windows easier, so I have included it in the distribution.
2423
2424 31. There is now a check in pcretest against a ridiculously large number being
2425 returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
2426 loop, the loop is abandoned.
2427
2428 32. Forward references to subpatterns in conditions such as (?(2)...) where
2429 subpattern 2 is defined later cause pcre_compile() to search forwards in
2430 the pattern for the relevant set of parentheses. This search went wrong
2431 when there were unescaped parentheses in a character class, parentheses
2432 escaped with \Q...\E, or parentheses in a #-comment in /x mode.
2433
2434 33. "Subroutine" calls and backreferences were previously restricted to
2435 referencing subpatterns earlier in the regex. This restriction has now
2436 been removed.
2437
2438 34. Added a number of extra features that are going to be in Perl 5.10. On the
2439 whole, these are just syntactic alternatives for features that PCRE had
2440 previously implemented using the Python syntax or my own invention. The
2441 other formats are all retained for compatibility.
2442
2443 (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
2444 as (?P<name>...). The new forms, as well as being in Perl 5.10, are
2445 also .NET compatible.
2446
2447 (b) A recursion or subroutine call to a named group can now be defined as
2448 (?&name) as well as (?P>name).
2449
2450 (c) A backreference to a named group can now be defined as \k<name> or
2451 \k'name' as well as (?P=name). The new forms, as well as being in Perl
2452 5.10, are also .NET compatible.
2453
2454 (d) A conditional reference to a named group can now use the syntax
2455 (?(<name>) or (?('name') as well as (?(name).
2456
2457 (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
2458 groups (named and numbered) that are never evaluated inline, but can be
2459 called as "subroutines" from elsewhere. In effect, the DEFINE condition
2460 is always false. There may be only one alternative in such a group.
2461
2462 (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
2463 as the simple (?(R). The condition is true only if the most recent
2464 recursion is that of the given number or name. It does not search out
2465 through the entire recursion stack.
2466
2467 (g) The escape \gN or \g{N} has been added, where N is a positive or
2468 negative number, specifying an absolute or relative reference.
2469
2470 35. Tidied to get rid of some further signed/unsigned compiler warnings and
2471 some "unreachable code" warnings.
2472
2473 36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
2474 things, this adds five new scripts.
2475
2476 37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
2477 There were also incompatibilities regarding the handling of \Q..\E inside
2478 character classes, for example with patterns like [\Qa\E-\Qz\E] where the
2479 hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
2480
2481 38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
2482 matches an empty string, and forcibly breaks the loop. There were bugs in
2483 this code in non-simple cases. For a pattern such as ^(a()*)* matched
2484 against aaaa the result was just "a" rather than "aaaa", for example. Two
2485 separate and independent bugs (that affected different cases) have been
2486 fixed.
2487
2488 39. Refactored the code to abolish the use of different opcodes for small
2489 capturing bracket numbers. This is a tidy that I avoided doing when I
2490 removed the limit on the number of capturing brackets for 3.5 back in 2001.
2491 The new approach is not only tidier, it makes it possible to reduce the
2492 memory needed to fix the previous bug (38).
2493
2494 40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
2495 sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
2496 processing dot, circumflex, or dollar metacharacters, or #-comments in /x
2497 mode.
2498
2499 41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
2500 report.
2501
2502 42. Applied patch, originally from Ari Pollak, modified by Google, to allow
2503 copy construction and assignment in the C++ wrapper.
2504
2505 43. Updated pcregrep to support "--newline=any". In the process, I fixed a
2506 couple of bugs that could have given wrong results in the "--newline=crlf"
2507 case.
2508
2509 44. Added a number of casts and did some reorganization of signed/unsigned int
2510 variables following suggestions from Dair Grant. Also renamed the variable
2511 "this" as "item" because it is a C++ keyword.
2512
2513 45. Arranged for dftables to add
2514
2515 #include "pcre_internal.h"
2516
2517 to pcre_chartables.c because without it, gcc 4.x may remove the array
2518 definition from the final binary if PCRE is built into a static library and
2519 dead code stripping is activated.
2520
2521 46. For an unanchored pattern, if a match attempt fails at the start of a
2522 newline sequence, and the newline setting is CRLF or ANY, and the next two
2523 characters are CRLF, advance by two characters instead of one.
2524
2525
2526 Version 6.7 04-Jul-06
2527 ---------------------
2528
2529 1. In order to handle tests when input lines are enormously long, pcretest has
2530 been re-factored so that it automatically extends its buffers when
2531 necessary. The code is crude, but this _is_ just a test program. The
2532 default size has been increased from 32K to 50K.
2533
2534 2. The code in pcre_study() was using the value of the re argument before
2535 testing it for NULL. (Of course, in any sensible call of the function, it
2536 won't be NULL.)
2537
2538 3. The memmove() emulation function in pcre_internal.h, which is used on
2539 systems that lack both memmove() and bcopy() - that is, hardly ever -
2540 was missing a "static" storage class specifier.
2541
2542 4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
2543 containing an extended class (one that cannot be represented by a bitmap
2544 because it contains high-valued characters or Unicode property items, e.g.
2545 [\pZ]). Almost always one would set UTF-8 mode when processing such a
2546 pattern, but PCRE should not loop if you do not (it no longer does).
2547 [Detail: two cases were found: (a) a repeated subpattern containing an
2548 extended class; (b) a recursive reference to a subpattern that followed a
2549 previous extended class. It wasn't skipping over the extended class
2550 correctly when UTF-8 mode was not set.]
2551
2552 5. A negated single-character class was not being recognized as fixed-length
2553 in lookbehind assertions such as (?<=[^f]), leading to an incorrect
2554 compile error "lookbehind assertion is not fixed length".
2555
2556 6. The RunPerlTest auxiliary script was showing an unexpected difference
2557 between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
2558 write a Perl script that can interpret lines of an input file either as
2559 byte characters or as UTF-8, which is what "perltest" was being required to
2560 do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
2561 can't do is switch easily at run time between having the "use utf8;" pragma
2562 or not. In the end, I fudged it by using the RunPerlTest script to insert
2563 "use utf8;" explicitly for the UTF-8 tests.
2564
2565 7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
2566 the end of the subject string, contrary to the documentation and to what
2567 Perl does. This was true of both matching functions. Now it matches only at
2568 the start of the subject and immediately after *internal* newlines.
2569
2570 8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
2571 a pointer to an int instead of a pointer to an unsigned long int. This
2572 caused problems on 64-bit systems.
2573
2574 9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
2575 instance of the 'standard' template library not being so standard".
2576
2577 10. There was no check on the number of named subpatterns nor the maximum
2578 length of a subpattern name. The product of these values is used to compute
2579 the size of the memory block for a compiled pattern. By supplying a very
2580 long subpattern name and a large number of named subpatterns, the size
2581 computation could be caused to overflow. This is now prevented by limiting
2582 the length of names to 32 characters, and the number of named subpatterns
2583 to 10,000.
2584
2585 11. Subpatterns that are repeated with specific counts have to be replicated in
2586 the compiled pattern. The size of memory for this was computed from the
2587 length of the subpattern and the repeat count. The latter is limited to
2588 65535, but there was no limit on the former, meaning that integer overflow
2589 could in principle occur. The compiled length of a repeated subpattern is
2590 now limited to 30,000 bytes in order to prevent this.
2591
2592 12. Added the optional facility to have named substrings with the same name.
2593
2594 13. Added the ability to use a named substring as a condition, using the
2595 Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
2596 are numbers (not recommended). Forward references are permitted.
2597
2598 14. Added forward references in named backreferences (if you see what I mean).
2599
2600 15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
2601 pattern could run off the end of the subject. For example, the pattern
2602 "(?s)(.{1,5})"8 did this with the subject "ab".
2603
2604 16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
2605 PCRE_CASELESS was set when matching characters that were quantified with ?
2606 or *.
2607
2608 17. A character class other than a single negated character that had a minimum
2609 but no maximum quantifier - for example [ab]{6,} - was not handled
2610 correctly by pce_dfa_exec(). It would match only one character.
2611
2612 18. A valid (though odd) pattern that looked like a POSIX character
2613 class but used an invalid character after [ (for example [[,abc,]]) caused
2614 pcre_compile() to give the error "Failed: internal error: code overflow" or
2615 in some cases to crash with a glibc free() error. This could even happen if
2616 the pattern terminated after [[ but there just happened to be a sequence of
2617 letters, a binary zero, and a closing ] in the memory that followed.
2618
2619 19. Perl's treatment of octal escapes in the range \400 to \777 has changed
2620 over the years. Originally (before any Unicode support), just the bottom 8
2621 bits were taken. Thus, for example, \500 really meant \100. Nowadays the
2622 output from "man perlunicode" includes this:
2623
2624 The regular expression compiler produces polymorphic opcodes. That
2625 is, the pattern adapts to the data and automatically switches to
2626 the Unicode character scheme when presented with Unicode data--or
2627 instead uses a traditional byte scheme when presented with byte
2628 data.
2629
2630 Sadly, a wide octal escape does not cause a switch, and in a string with
2631 no other multibyte characters, these octal escapes are treated as before.
2632 Thus, in Perl, the pattern /\500/ actually matches \100 but the pattern
2633 /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
2634 Unicode string.
2635
2636 I have not perpetrated such confusion in PCRE. Up till now, it took just
2637 the bottom 8 bits, as in old Perl. I have now made octal escapes with
2638 values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
2639 translate to the appropriate multibyte character.
2640
2641 29. Applied some refactoring to reduce the number of warnings from Microsoft
2642 and Borland compilers. This has included removing the fudge introduced
2643 seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
2644 a warning about an unused variable.
2645
2646 21. PCRE has not included VT (character 0x0b) in the set of whitespace
2647 characters since release 4.0, because Perl (from release 5.004) does not.
2648 [Or at least, is documented not to: some releases seem to be in conflict
2649 with the documentation.] However, when a pattern was studied with
2650 pcre_study() and all its branches started with \s, PCRE still included VT
2651 as a possible starting character. Of course, this did no harm; it just
2652 caused an unnecessary match attempt.
2653
2654 22. Removed a now-redundant internal flag bit that recorded the fact that case
2655 dependency changed within the pattern. This was once needed for "required
2656 byte" processing, but is no longer used. This recovers a now-scarce options
2657 bit. Also moved the least significant internal flag bit to the most-
2658 significant bit of the word, which was not previously used (hangover from
2659 the days when it was an int rather than a uint) to free up another bit for
2660 the future.
2661
2662 23. Added support for CRLF line endings as well as CR and LF. As well as the
2663 default being selectable at build time, it can now be changed at runtime
2664 via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
2665 specify that it is scanning data with non-default line endings.
2666
2667 24. Changed the definition of CXXLINK to make it agree with the definition of
2668 LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
2669
2670 25. Applied Ian Taylor's patches to avoid using another stack frame for tail
2671 recursions. This makes a big different to stack usage for some patterns.
2672
2673 26. If a subpattern containing a named recursion or subroutine reference such
2674 as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
2675 the space required for the compiled pattern went wrong and gave too small a
2676 value. Depending on the environment, this could lead to "Failed: internal
2677 error: code overflow at offset 49" or "glibc detected double free or
2678 corruption" errors.
2679
2680 27. Applied patches from Google (a) to support the new newline modes and (b) to
2681 advance over multibyte UTF-8 characters in GlobalReplace.
2682
2683 28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
2684 difference for some implementation of PCRE in some Windows version.
2685
2686 29. Added some extra testing facilities to pcretest:
2687
2688 \q<number> in a data line sets the "match limit" value
2689 \Q<number> in a data line sets the "match recursion limt" value
2690 -S <number> sets the stack size, where <number> is in megabytes
2691
2692 The -S option isn't available for Windows.
2693
2694
2695 Version 6.6 06-Feb-06
2696 ---------------------
2697
2698 1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
2699 in pcreposix.h. I have copied the definition from pcre.h.
2700
2701 2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
2702 because pcre.h is no longer a built file.
2703
2704 3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
2705 not normally included in the compiled code.
2706
2707
2708 Version 6.5 01-Feb-06
2709 ---------------------
2710
2711 1. When using the partial match feature with pcre_dfa_exec(), it was not
2712 anchoring the second and subsequent partial matches at the new starting
2713 point. This could lead to incorrect results. For example, with the pattern
2714 /1234/, partially matching against "123" and then "a4" gave a match.
2715
2716 2. Changes to pcregrep:
2717
2718 (a) All non-match returns from pcre_exec() were being treated as failures
2719 to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
2720 error message is output. Some extra information is given for the
2721 PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
2722 probably the only errors that are likely to be caused by users (by
2723 specifying a regex that has nested indefinite repeats, for instance).
2724 If there are more than 20 of these errors, pcregrep is abandoned.
2725
2726 (b) A binary zero was treated as data while matching, but terminated the
2727 output line if it was written out. This has been fixed: binary zeroes
2728 are now no different to any other data bytes.
2729
2730 (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
2731 used to set a locale for matching. The --locale=xxxx long option has
2732 been added (no short equivalent) to specify a locale explicitly on the
2733 pcregrep command, overriding the environment variables.
2734
2735 (d) When -B was used with -n, some line numbers in the output were one less
2736 than they should have been.
2737
2738 (e) Added the -o (--only-matching) option.
2739
2740 (f) If -A or -C was used with -c (count only), some lines of context were
2741 accidentally printed for the final match.
2742
2743 (g) Added the -H (--with-filename) option.
2744
2745 (h) The combination of options -rh failed to suppress file names for files
2746 that were found from directory arguments.
2747
2748 (i) Added the -D (--devices) and -d (--directories) options.
2749
2750 (j) Added the -F (--fixed-strings) option.
2751
2752 (k) Allow "-" to be used as a file name for -f as well as for a data file.
2753
2754 (l) Added the --colo(u)r option.
2755
2756 (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
2757 is not present by default.
2758
2759 3. A nasty bug was discovered in the handling of recursive patterns, that is,
2760 items such as (?R) or (?1), when the recursion could match a number of
2761 alternatives. If it matched one of the alternatives, but subsequently,
2762 outside the recursion, there was a failure, the code tried to back up into
2763 the recursion. However, because of the way PCRE is implemented, this is not
2764 possible, and the result was an incorrect result from the match.
2765
2766 In order to prevent this happening, the specification of recursion has
2767 been changed so that all such subpatterns are automatically treated as
2768 atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
2769
2770 4. I had overlooked the fact that, in some locales, there are characters for
2771 which isalpha() is true but neither isupper() nor islower() are true. In
2772 the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
2773 and ordfeminine) are like this. This affected the treatment of \w and \W
2774 when they appeared in character classes, but not when they appeared outside
2775 a character class. The bit map for "word" characters is now created
2776 separately from the results of isalnum() instead of just taking it from the
2777 upper, lower, and digit maps. (Plus the underscore character, of course.)
2778
2779 5. The above bug also affected the handling of POSIX character classes such as
2780 [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
2781 permanent tables. Instead, the bit maps for such a class were previously
2782 created as the appropriate unions of the upper, lower, and digit bitmaps.
2783 Now they are created by subtraction from the [[:word:]] class, which has
2784 its own bitmap.
2785
2786 6. The [[:blank:]] character class matches horizontal, but not vertical space.
2787 It is created by subtracting the vertical space characters (\x09, \x0a,
2788 \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
2789 subtraction was done in the overall bitmap for a character class, meaning
2790 that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
2791 be recognized. This bug has been fixed.
2792
2793 7. Patches from the folks at Google:
2794
2795 (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
2796 real life, but is still worth protecting against".
2797
2798 (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
2799 regular expressions".
2800
2801 (c) pcre_scanner.cc: avoid use of std::count() because not all systems
2802 have it.
2803
2804 (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
2805 "configure" and the latter not, in order to fix a problem somebody had
2806 with compiling the Arg class on HP-UX.
2807
2808 (e) Improve the error-handling of the C++ wrapper a little bit.
2809
2810 (f) New tests for checking recursion limiting.
2811
2812 8. The pcre_memmove() function, which is used only if the environment does not
2813 have a standard memmove() function (and is therefore rarely compiled),
2814 contained two bugs: (a) use of int instead of size_t, and (b) it was not
2815 returning a result (though PCRE never actually uses the result).
2816
2817 9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
2818 large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
2819 returned instead of calling malloc() with an overflowing number that would
2820 most likely cause subsequent chaos.
2821
2822 10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
2823
2824 11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
2825 with this option is matched, the nmatch and pmatch options of regexec() are
2826 ignored.
2827
2828 12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
2829 provided in case anyone wants to the the POSIX interface with UTF-8
2830 strings.
2831
2832 13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
2833 C++ linking (needed for some HP-UX environments).
2834
2835 14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
2836 (unused parameter) and in the pcre_printint() function (omitted "default"
2837 switch label when the default is to do nothing).
2838
2839 15. Added some code to make it possible, when PCRE is compiled as a C++
2840 library, to replace subject pointers for pcre_exec() with a smart pointer
2841 class, thus making it possible to process discontinuous strings.
2842
2843 16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
2844 much the same function. They were added by different people who were trying
2845 to make PCRE easy to compile on non-Unix systems. It has been suggested
2846 that PCRE_EXPORT be abolished now that there is more automatic apparatus
2847 for compiling on Windows systems. I have therefore replaced it with
2848 PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
2849 defaults to "extern" for C or "extern C" for C++, which works fine on
2850 Unix-like systems. It is now possible to override the value of PCRE_DATA_
2851 SCOPE with something explicit in config.h. In addition:
2852
2853 (a) pcreposix.h still had just "extern" instead of either of these macros;
2854 I have replaced it with PCRE_DATA_SCOPE.
2855
2856 (b) Functions such as _pcre_xclass(), which are internal to the library,
2857 but external in the C sense, all had PCRE_EXPORT in their definitions.
2858 This is apparently wrong for the Windows case, so I have removed it.
2859 (It makes no difference on Unix-like systems.)
2860
2861 17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
2862 of recursive calls to match(). This is different to MATCH_LIMIT because
2863 that limits the total number of calls to match(), not all of which increase
2864 the depth of recursion. Limiting the recursion depth limits the amount of
2865 stack (or heap if NO_RECURSE is set) that is used. The default can be set
2866 when PCRE is compiled, and changed at run time. A patch from Google adds
2867 this functionality to the C++ interface.
2868
2869 18. Changes to the handling of Unicode character properties:
2870
2871 (a) Updated the table to Unicode 4.1.0.
2872
2873 (b) Recognize characters that are not in the table as "Cn" (undefined).
2874
2875 (c) I revised the way the table is implemented to a much improved format
2876 which includes recognition of ranges. It now supports the ranges that
2877 are defined in UnicodeData.txt, and it also amalgamates other
2878 characters into ranges. This has reduced the number of entries in the
2879 table from around 16,000 to around 3,000, thus reducing its size
2880 considerably. I realized I did not need to use a tree structure after
2881 all - a binary chop search is just as efficient. Having reduced the
2882 number of entries, I extended their size from 6 bytes to 8 bytes to
2883 allow for more data.
2884
2885 (d) Added support for Unicode script names via properties such as \p{Han}.
2886
2887 19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
2888 matching that character.
2889
2890 20. When matching a repeated Unicode property with a minimum greater than zero,
2891 (for example \pL{2,}), PCRE could look past the end of the subject if it
2892 reached it while seeking the minimum number of characters. This could
2893 happen only if some of the characters were more than one byte long, because
2894 there is a check for at least the minimum number of bytes.
2895
2896 21. Refactored the implementation of \p and \P so as to be more general, to
2897 allow for more different types of property in future. This has changed the
2898 compiled form incompatibly. Anybody with saved compiled patterns that use
2899 \p or \P will have to recompile them.
2900
2901 22. Added "Any" and "L&" to the supported property types.
2902
2903 23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
2904 but give a compile time error if the value is greater than 0xff.
2905
2906 24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
2907 accidentally not being installed or uninstalled.
2908
2909 25. The pcre.h file was built from pcre.h.in, but the only changes that were
2910 made were to insert the current release number. This seemed silly, because
2911 it made things harder for people building PCRE on systems that don't run
2912 "configure". I have turned pcre.h into a distributed file, no longer built
2913 by "configure", with the version identification directly included. There is
2914 no longer a pcre.h.in file.
2915
2916 However, this change necessitated a change to the pcre-config script as
2917 well. It is built from pcre-config.in, and one of the substitutions was the
2918 release number. I have updated configure.ac so that ./configure now finds
2919 the release number by grepping pcre.h.
2920
2921 26. Added the ability to run the tests under valgrind.
2922
2923
2924 Version 6.4 05-Sep-05
2925 ---------------------
2926
2927 1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
2928 "--" to be printed when multiple files were scanned, even when none of the
2929 -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
2930 consider it to be a bug, and have restored the previous behaviour.
2931
2932 2. A couple of code tidies to get rid of compiler warnings.
2933
2934 3. The pcretest program used to cheat by referring to symbols in the library
2935 whose names begin with _pcre_. These are internal symbols that are not
2936 really supposed to be visible externally, and in some environments it is
2937 possible to suppress them. The cheating is now confined to including
2938 certain files from the library's source, which is a bit cleaner.
2939
2940 4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
2941 file's purpose clearer.
2942
2943 5. Reorganized pcre_ucp_findchar().
2944
2945
2946 Version 6.3 15-Aug-05
2947 ---------------------
2948
2949 1. The file libpcre.pc.in did not have general read permission in the tarball.
2950
2951 2. There were some problems when building without C++ support:
2952
2953 (a) If C++ support was not built, "make install" and "make test" still
2954 tried to test it.
2955
2956 (b) There were problems when the value of CXX was explicitly set. Some
2957 changes have been made to try to fix these, and ...
2958
2959 (c) --disable-cpp can now be used to explicitly disable C++ support.
2960
2961 (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
2962 backslash in a target when C++ was disabled. This confuses some
2963 versions of "make", apparently. Using an intermediate variable solves
2964 this. (Same for CPP_LOBJ.)
2965
2966 3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
2967 (non-Windows) now includes $(CFLAGS) because these flags are sometimes
2968 necessary on certain architectures.
2969
2970 4. Added a setting of -export-symbols-regex to the link command to remove
2971 those symbols that are exported in the C sense, but actually are local
2972 within the library, and not documented. Their names all begin with
2973 "_pcre_". This is not a perfect job, because (a) we have to except some
2974 symbols that pcretest ("illegally") uses, and (b) the facility isn't always
2975 available (and never for static libraries). I have made a note to try to
2976 find a way round (a) in the future.
2977
2978
2979 Version 6.2 01-Aug-05
2980 ---------------------
2981
2982 1. There was no test for integer overflow of quantifier values. A construction
2983 such as {1111111111111111} would give undefined results. What is worse, if
2984 a minimum quantifier for a parenthesized subpattern overflowed and became
2985 negative, the calculation of the memory size went wrong. This could have
2986 led to memory overwriting.
2987
2988 2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
2989
2990 3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
2991 operating environments where this matters.
2992
2993 4. Applied Giuseppe Maxia's patch to add additional features for controlling
2994 PCRE options from within the C++ wrapper.
2995
2996 5. Named capturing subpatterns were not being correctly counted when a pattern
2997 was compiled. This caused two problems: (a) If there were more than 100
2998 such subpatterns, the calculation of the memory needed for the whole
2999 compiled pattern went wrong, leading to an overflow error. (b) Numerical
3000 back references of the form \12, where the number was greater than 9, were
3001 not recognized as back references, even though there were sufficient
3002 previous subpatterns.
3003
3004 6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
3005 versions of gcc, e.g. 2.95.4.
3006
3007
3008 Version 6.1 21-Jun-05
3009 ---------------------
3010
3011 1. There was one reference to the variable "posix" in pcretest.c that was not
3012 surrounded by "#if !defined NOPOSIX".
3013
3014 2. Make it possible to compile pcretest without DFA support, UTF8 support, or
3015 the cross-check on the old pcre_info() function, for the benefit of the
3016 cut-down version of PCRE that is currently imported into Exim.
3017
3018 3. A (silly) pattern starting with (?i)(?-i) caused an internal space
3019 allocation error. I've done the easy fix, which wastes 2 bytes for sensible
3020 patterns that start (?i) but I don't think that matters. The use of (?i) is
3021 just an example; this all applies to the other options as well.
3022
3023 4. Since libtool seems to echo the compile commands it is issuing, the output
3024 from "make" can be reduced a bit by putting "@" in front of each libtool
3025 compile command.
3026
3027 5. Patch from the folks at Google for configure.in to be a bit more thorough
3028 in checking for a suitable C++ installation before trying to compile the
3029 C++ stuff. This should fix a reported problem when a compiler was present,
3030 but no suitable headers.
3031
3032 6. The man pages all had just "PCRE" as their title. I have changed them to
3033 be the relevant file name. I have also arranged that these names are
3034 retained in the file doc/pcre.txt, which is a concatenation in text format
3035 of all the man pages except the little individual ones for each function.
3036
3037 7. The NON-UNIX-USE file had not been updated for the different set of source
3038 files that come with release 6. I also added a few comments about the C++
3039 wrapper.
3040
3041
3042 Version 6.0 07-Jun-05
3043 ---------------------
3044
3045 1. Some minor internal re-organization to help with my DFA experiments.
3046
3047 2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
3048 didn't matter for the library itself when fully configured, but did matter
3049 when compiling without UCP support, or within Exim, where the ucp files are
3050 not imported.
3051
3052 3. Refactoring of the library code to split up the various functions into
3053 different source modules. The addition of the new DFA matching code (see
3054 below) to a single monolithic source would have made it really too
3055 unwieldy, quite apart from causing all the code to be include in a
3056 statically linked application, when only some functions are used. This is
3057 relevant even without the DFA addition now that patterns can be compiled in
3058 one application and matched in another.
3059
3060 The downside of splitting up is that there have to be some external
3061 functions and data tables that are used internally in different modules of
3062 the library but which are not part of the API. These have all had their
3063 names changed to start with "_pcre_" so that they are unlikely to clash
3064 with other external names.
3065
3066 4. Added an alternate matching function, pcre_dfa_exec(), which matches using
3067 a different (DFA) algorithm. Although it is slower than the original
3068 function, it does have some advantages for certain types of matching
3069 problem.
3070
3071 5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
3072 including restarting after a partial match.
3073
3074 6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
3075 defined when compiling for Windows was sent to me. I have put it into the
3076 code, though I have no means of testing or verifying it.
3077
3078 7. Added the pcre_refcount() auxiliary function.
3079
3080 8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
3081 match before or at the first newline in the subject string. In pcretest,
3082 the /f option on a pattern can be used to set this.
3083
3084 9. A repeated \w when used in UTF-8 mode with characters greater than 256
3085 would behave wrongly. This has been present in PCRE since release 4.0.
3086
3087 10. A number of changes to the pcregrep command:
3088
3089 (a) Refactored how -x works; insert ^(...)$ instead of setting
3090 PCRE_ANCHORED and checking the length, in preparation for adding
3091 something similar for -w.
3092
3093 (b) Added the -w (match as a word) option.
3094
3095 (c) Refactored the way lines are read and buffered so as to have more
3096 than one at a time available.
3097
3098 (d) Implemented a pcregrep test script.
3099
3100 (e) Added the -M (multiline match) option. This allows patterns to match
3101 over several lines of the subject. The buffering ensures that at least
3102 8K, or the rest of the document (whichever is the shorter) is available
3103 for matching (and similarly the previous 8K for lookbehind assertions).
3104
3105 (f) Changed the --help output so that it now says
3106
3107 -w, --word-regex(p)
3108
3109 instead of two lines, one with "regex" and the other with "regexp"
3110 because that confused at least one person since the short forms are the
3111 same. (This required a bit of code, as the output is generated
3112 automatically from a table. It wasn't just a text change.)
3113
3114 (g) -- can be used to terminate pcregrep options if the next thing isn't an
3115 option but starts with a hyphen. Could be a pattern or a path name
3116 starting with a hyphen, for instance.
3117
3118 (h) "-" can be given as a file name to represent stdin.
3119
3120 (i) When file names are being printed, "(standard input)" is used for
3121 the standard input, for compatibility with GNU grep. Previously
3122 "<stdin>" was used.
3123
3124 (j) The option --label=xxx can be used to supply a name to be used for
3125 stdin when file names are being printed. There is no short form.
3126
3127 (k) Re-factored the options decoding logic because we are going to add
3128 two more options that take data. Such options can now be given in four
3129 different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
3130
3131 (l) Added the -A, -B, and -C options for requesting that lines of context
3132 around matches be printed.
3133
3134 (m) Added the -L option to print the names of files that do not contain
3135 any matching lines, that is, the complement of -l.
3136
3137 (n) The return code is 2 if any file cannot be opened, but pcregrep does
3138 continue to scan other files.
3139
3140 (o) The -s option was incorrectly implemented. For compatibility with other
3141 greps, it now suppresses the error message for a non-existent or non-
3142 accessible file (but not the return code). There is a new option called
3143 -q that suppresses the output of matching lines, which was what -s was
3144 previously doing.
3145
3146 (p) Added --include and --exclude options to specify files for inclusion
3147 and exclusion when recursing.
3148
3149 11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
3150 Hopefully, it now does.
3151
3152 12. Missing cast in pcre_study().
3153
3154 13. Added an "uninstall" target to the makefile.
3155
3156 14. Replaced "extern" in the function prototypes in Makefile.in with
3157 "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
3158 world, but is set differently for Windows.
3159
3160 15. Added a second compiling function called pcre_compile2(). The only
3161 difference is that it has an extra argument, which is a pointer to an
3162 integer error code. When there is a compile-time failure, this is set
3163 non-zero, in addition to the error test pointer being set to point to an
3164 error message. The new argument may be NULL if no error number is required
3165 (but then you may as well call pcre_compile(), which is now just a
3166 wrapper). This facility is provided because some applications need a
3167 numeric error indication, but it has also enabled me to tidy up the way
3168 compile-time errors are handled in the POSIX wrapper.
3169
3170 16. Added VPATH=.libs to the makefile; this should help when building with one
3171 prefix path and installing with another. (Or so I'm told by someone who
3172 knows more about this stuff than I do.)
3173
3174 17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
3175 passes PCRE_DOTALL to the pcre_compile() function, making the "." character
3176 match everything, including newlines. This is not POSIX-compatible, but
3177 somebody wanted the feature. From pcretest it can be activated by using
3178 both the P and the s flags.
3179
3180 18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
3181
3182 19. libpcre.pc was being incorrectly installed as executable.
3183
3184 20. A couple of places in pcretest check for end-of-line by looking for '\n';
3185 it now also looks for '\r' so that it will work unmodified on Windows.
3186
3187 21. Added Google's contributed C++ wrapper to the distribution.
3188
3189 22. Added some untidy missing memory free() calls in pcretest, to keep
3190 Electric Fence happy when testing.
3191
3192
3193
3194 Version 5.0 13-Sep-04
3195 ---------------------
3196
3197 1. Internal change: literal characters are no longer packed up into items
3198 containing multiple characters in a single byte-string. Each character
3199 is now matched using a separate opcode. However, there may be more than one
3200 byte in the character in UTF-8 mode.
3201
3202 2. The pcre_callout_block structure has two new fields: pattern_position and
3203 next_item_length. These contain the offset in the pattern to the next match
3204 item, and its length, respectively.
3205
3206 3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
3207 insertion of callouts before each pattern item. Added the /C option to
3208 pcretest to make use of this.
3209
3210 4. On the advice of a Windows user, the lines
3211
3212 #if defined(_WIN32) || defined(WIN32)
3213 _setmode( _fileno( stdout ), 0x8000 );
3214 #endif /* defined(_WIN32) || defined(WIN32) */
3215
3216 have been added to the source of pcretest. This apparently does useful
3217 magic in relation to line terminators.
3218
3219 5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
3220 for the benefit of those environments where the "b" makes a difference.
3221
3222 6. The icc compiler has the same options as gcc, but "configure" doesn't seem
3223 to know about it. I have put a hack into configure.in that adds in code
3224 to set GCC=yes if CC=icc. This seems to end up at a point in the
3225 generated configure script that is early enough to affect the setting of
3226 compiler options, which is what is needed, but I have no means of testing
3227 whether it really works. (The user who reported this had patched the
3228 generated configure script, which of course I cannot do.)
3229
3230 LATER: After change 22 below (new libtool files), the configure script
3231 seems to know about icc (and also ecc). Therefore, I have commented out
3232 this hack in configure.in.
3233
3234 7. Added support for pkg-config (2 patches were sent in).
3235
3236 8. Negated POSIX character classes that used a combination of internal tables
3237 were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
3238 [[:^ascii]]. Typically, they would match almost any characters. The other
3239 POSIX classes were not broken in this way.
3240
3241 9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
3242 to find the match, as PCRE was deluded into thinking that the match had to
3243 start at the start point or following a newline. The same bug applied to
3244 patterns with negative forward assertions or any backward assertions
3245 preceding ".*" at the start, unless the pattern required a fixed first
3246 character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
3247
3248 10. In UTF-8 mode, when moving forwards in the subject after a failed match
3249 starting at the last subject character, bytes beyond the end of the subject
3250 string were read.
3251
3252 11. Renamed the variable "class" as "classbits" to make life easier for C++
3253 users. (Previously there was a macro definition, but it apparently wasn't
3254 enough.)
3255
3256 12. Added the new field "tables" to the extra data so that tables can be passed
3257 in at exec time, or the internal tables can be re-selected. This allows
3258 a compiled regex to be saved and re-used at a later time by a different
3259 program that might have everything at different addresses.
3260
3261 13. Modified the pcre-config script so that, when run on Solaris, it shows a
3262 -R library as well as a -L library.
3263
3264 14. The debugging options of pcretest (-d on the command line or D on a
3265 pattern) showed incorrect output for anything following an extended class
3266 that contained multibyte characters and which was followed by a quantifier.
3267
3268 15. Added optional support for general category Unicode character properties
3269 via the \p, \P, and \X escapes. Unicode property support implies UTF-8
3270 support. It adds about 90K to the size of the library. The meanings of the
3271 inbuilt class escapes such as \d and \s have NOT been changed.
3272
3273 16. Updated pcredemo.c to include calls to free() to release the memory for the
3274 compiled pattern.
3275
3276 17. The generated file chartables.c was being created in the source directory
3277 instead of in the building directory. This caused the build to fail if the
3278 source directory was different from the building directory, and was
3279 read-only.
3280
3281 18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
3282 file. No doubt somebody will tell me if they don't make sense... Also added
3283 Dan Mooney's comments about building on OpenVMS.
3284
3285 19. Added support for partial matching via the PCRE_PARTIAL option for
3286 pcre_exec() and the \P data escape in pcretest.
3287
3288 20. Extended pcretest with 3 new pattern features:
3289
3290 (i) A pattern option of the form ">rest-of-line" causes pcretest to
3291 write the compiled pattern to the file whose name is "rest-of-line".
3292 This is a straight binary dump of the data, with the saved pointer to
3293 the character tables forced to be NULL. The study data, if any, is
3294 written too. After writing, pcretest reads a new pattern.
3295
3296 (ii) If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
3297 compiled pattern from the given file. There must not be any
3298 occurrences of "<" in the file name (pretty unlikely); if there are,
3299 pcretest will instead treat the initial "<" as a pattern delimiter.
3300 After reading in the pattern, pcretest goes on to read data lines as
3301 usual.
3302
3303 (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
3304 and 16-bit fields in a compiled pattern, to simulate a pattern that
3305 was compiled on a host of opposite endianness.
3306
3307 21. The pcre-exec() function can now cope with patterns that were compiled on
3308 hosts of opposite endianness, with this restriction:
3309
3310 As for any compiled expression that is saved and used later, the tables
3311 pointer field cannot be preserved; the extra_data field in the arguments
3312 to pcre_exec() should be used to pass in a tables address if a value
3313 other than the default internal tables were used at compile time.
3314
3315 22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
3316 now diagnosed as an error. Previously, most of the time, a negative number
3317 would have been treated as zero, but if in addition "ovector" was passed as
3318 NULL, a crash could occur.
3319
3320 23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
3321 new versions from the libtool 1.5 distribution (the last one is a copy of
3322 a file called libtool.m4). This seems to have fixed the need to patch
3323 "configure" to support Darwin 1.3 (which I used to do). However, I still
3324 had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
3325 workstation).
3326
3327 24. Changed the PCRE licence to be the more standard "BSD" licence.
3328
3329
3330 Version 4.5 01-Dec-03
3331 ---------------------
3332
3333 1. There has been some re-arrangement of the code for the match() function so
3334 that it can be compiled in a version that does not call itself recursively.
3335 Instead, it keeps those local variables that need separate instances for
3336 each "recursion" in a frame on the heap, and gets/frees frames whenever it
3337 needs to "recurse". Keeping track of where control must go is done by means
3338 of setjmp/longjmp. The whole thing is implemented by a set of macros that
3339 hide most of the details from the main code, and operates only if
3340 NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
3341 "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
3342 operating.
3343
3344 To make it easier for callers to provide specially tailored get/free
3345 functions for this usage, two new functions, pcre_stack_malloc, and
3346 pcre_stack_free, are used. They are always called in strict stacking order,
3347 and the size of block requested is always the same.
3348
3349 The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
3350 PCRE has been compiled to use the stack or the heap for recursion. The
3351 -C option of pcretest uses this to show which version is compiled.
3352
3353 A new data escape \S, is added to pcretest; it causes the amounts of store
3354 obtained and freed by both kinds of malloc/free at match time to be added
3355 to the output.
3356
3357 2. Changed the locale test to use "fr_FR" instead of "fr" because that's
3358 what's available on my current Linux desktop machine.
3359
3360 3. When matching a UTF-8 string, the test for a valid string at the start has
3361 been extended. If start_offset is not zero, PCRE now checks that it points
3362 to a byte that is the start of a UTF-8 character. If not, it returns
3363 PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
3364 this is necessary because there may be backward assertions in the pattern.
3365 When matching the same subject several times, it may save resources to use
3366 PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
3367
3368 4. The code for checking the validity of UTF-8 strings has been tightened so
3369 that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
3370 containing "overlong sequences".
3371
3372 5. Fixed a bug (appearing twice) that I could not find any way of exploiting!
3373 I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
3374 should have been "&", but it just so happened that all the cases this let
3375 through by mistake were picked up later in the function.
3376
3377 6. I had used a variable called "isblank" - this is a C99 function, causing
3378 some compilers to warn. To avoid this, I renamed it (as "blankclass").
3379
3380 7. Cosmetic: (a) only output another newline at the end of pcretest if it is
3381 prompting; (b) run "./pcretest /dev/null" at the start of the test script
3382 so the version is shown; (c) stop "make test" echoing "./RunTest".
3383
3384 8. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
3385
3386 9. The prototype for memmove() for systems that don't have it was using
3387 size_t, but the inclusion of the header that defines size_t was later. I've
3388 moved the #includes for the C headers earlier to avoid this.
3389
3390 10. Added some adjustments to the code to make it easier to compiler on certain
3391 special systems:
3392
3393 (a) Some "const" qualifiers were missing.
3394 (b) Added the macro EXPORT before all exported functions; by default this
3395 is defined to be empty.
3396 (c) Changed the dftables auxiliary program (that builds chartables.c) so
3397 that it reads its output file name as an argument instead of writing
3398 to the standard output and assuming this can be redirected.
3399
3400 11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
3401 class containing characters with values greater than 255, PCRE compilation
3402 went into a loop.
3403
3404 12. A recursive reference to a subpattern that was within another subpattern
3405 that had a minimum quantifier of zero caused PCRE to crash. For example,
3406 (x(y(?2))z)? provoked this bug with a subject that got as far as the
3407 recursion. If the recursively-called subpattern itself had a zero repeat,
3408 that was OK.
3409
3410 13. In pcretest, the buffer for reading a data line was set at 30K, but the
3411 buffer into which it was copied (for escape processing) was still set at
3412 1024, so long lines caused crashes.
3413
3414 14. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
3415 "internal error: code overflow...". This applied to any character class
3416 that was followed by a possessive quantifier.
3417
3418 15. Modified the Makefile to add libpcre.la as a prerequisite for
3419 libpcreposix.la because I was told this is needed for a parallel build to
3420 work.
3421
3422 16. If a pattern that contained .* following optional items at the start was
3423 studied, the wrong optimizing data was generated, leading to matching
3424 errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
3425 matching string must start with a or b or c. The correct conclusion for
3426 this pattern is that a match can start with any character.
3427
3428
3429 Version 4.4 13-Aug-03
3430 ---------------------
3431
3432 1. In UTF-8 mode, a character class containing characters with values between
3433 127 and 255 was not handled correctly if the compiled pattern was studied.
3434 In fixing this, I have also improved the studying algorithm for such
3435 classes (slightly).
3436
3437 2. Three internal functions had redundant arguments passed to them. Removal
3438 might give a very teeny performance improvement.
3439
3440 3. Documentation bug: the value of the capture_top field in a callout is *one
3441 more than* the number of the hightest numbered captured substring.
3442
3443 4. The Makefile linked pcretest and pcregrep with -lpcre, which could result
3444 in incorrectly linking with a previously installed version. They now link
3445 explicitly with libpcre.la.
3446
3447 5. configure.in no longer needs to recognize Cygwin specially.
3448
3449 6. A problem in pcre.in for Windows platforms is fixed.
3450
3451 7. If a pattern was successfully studied, and the -d (or /D) flag was given to
3452 pcretest, it used to include the size of the study block as part of its
3453 output. Unfortunately, the structure contains a field that has a different
3454 size on different hardware architectures. This meant that the tests that
3455 showed this size failed. As the block is currently always of a fixed size,
3456 this information isn't actually particularly useful in pcretest output, so
3457 I have just removed it.
3458
3459 8. Three pre-processor statements accidentally did not start in column 1.
3460 Sadly, there are *still* compilers around that complain, even though
3461 standard C has not required this for well over a decade. Sigh.
3462
3463 9. In pcretest, the code for checking callouts passed small integers in the
3464 callout_data field, which is a void * field. However, some picky compilers
3465 complained about the casts involved for this on 64-bit systems. Now
3466 pcretest passes the address of the small integer instead, which should get
3467 rid of the warnings.
3468
3469 10. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
3470 both compile and run time, and gives an error if an invalid UTF-8 sequence
3471 is found. There is a option for disabling this check in cases where the
3472 string is known to be correct and/or the maximum performance is wanted.
3473
3474 11. In response to a bug report, I changed one line in Makefile.in from
3475
3476 -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
3477 to
3478 -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \
3479
3480 to look similar to other lines, but I have no way of telling whether this
3481 is the right thing to do, as I do not use Windows. No doubt I'll get told
3482 if it's wrong...
3483
3484
3485 Version 4.3 21-May-03
3486 ---------------------
3487
3488 1. Two instances of @WIN_PREFIX@ omitted from the Windows targets in the
3489 Makefile.
3490
3491 2. Some refactoring to improve the quality of the code:
3492
3493 (i) The utf8_table... variables are now declared "const".
3494
3495 (ii) The code for \cx, which used the "case flipping" table to upper case
3496 lower case letters, now just substracts 32. This is ASCII-specific,
3497 but the whole concept of \cx is ASCII-specific, so it seems
3498 reasonable.
3499
3500 (iii) PCRE was using its character types table to recognize decimal and
3501 hexadecimal digits in the pattern. This is silly, because it handles
3502 only 0-9, a-f, and A-F, but the character types table is locale-
3503 specific, which means strange things might happen. A private
3504 table is now used for this - though it costs 256 bytes, a table is
3505 much faster than multiple explicit tests. Of course, the standard
3506 character types table is still used for matching digits in subject
3507 strings against \d.
3508
3509 (iv) Strictly, the identifier ESC_t is reserved by POSIX (all identifiers
3510 ending in _t are). So I've renamed it as ESC_tee.
3511
3512 3. The first argument for regexec() in the POSIX wrapper should have been
3513 defined as "const".
3514
3515 4. Changed pcretest to use malloc() for its buffers so that they can be
3516 Electric Fenced for debugging.
3517
3518 5. There were several places in the code where, in UTF-8 mode, PCRE would try
3519 to read one or more bytes before the start of the subject string. Often this
3520 had no effect on PCRE's behaviour, but in some circumstances it could
3521 provoke a segmentation fault.
3522
3523 6. A lookbehind at the start of a pattern in UTF-8 mode could also cause PCRE
3524 to try to read one or more bytes before the start of the subject string.
3525
3526 7. A lookbehind in a pattern matched in non-UTF-8 mode on a PCRE compiled with
3527 UTF-8 support could misbehave in various ways if the subject string
3528 contained bytes with the 0x80 bit set and the 0x40 bit unset in a lookbehind
3529 area. (PCRE was not checking for the UTF-8 mode flag, and trying to move
3530 back over UTF-8 characters.)
3531
3532
3533 Version 4.2 14-Apr-03
3534 ---------------------
3535
3536 1. Typo "#if SUPPORT_UTF8" instead of "#ifdef SUPPORT_UTF8" fixed.
3537
3538 2. Changes to the building process, supplied by Ronald Landheer-Cieslak
3539 [ON_WINDOWS]: new variable, "#" on non-Windows platforms
3540 [NOT_ON_WINDOWS]: new variable, "#" on Windows platforms
3541 [WIN_PREFIX]: new variable, "cyg" for Cygwin
3542 * Makefile.in: use autoconf substitution for OBJEXT, EXEEXT, BUILD_OBJEXT
3543 and BUILD_EXEEXT
3544 Note: automatic setting of the BUILD variables is not yet working
3545 set CPPFLAGS and BUILD_CPPFLAGS (but don't use yet) - should be used at
3546 compile-time but not at link-time
3547 [LINK]: use for linking executables only
3548 make different versions for Windows and non-Windows
3549 [LINKLIB]: new variable, copy of UNIX-style LINK, used for linking
3550 libraries
3551 [LINK_FOR_BUILD]: new variable
3552 [OBJEXT]: use throughout
3553 [EXEEXT]: use throughout
3554 <winshared>: new target
3555 <wininstall>: new target
3556 <dftables.o>: use native compiler
3557 <dftables>: use native linker
3558 <install>: handle Windows platform correctly
3559 <clean>: ditto
3560 <check>: ditto
3561 copy DLL to top builddir before testing
3562
3563 As part of these changes, -no-undefined was removed again. This was reported
3564 to give trouble on HP-UX 11.0, so getting rid of it seems like a good idea
3565 in any case.
3566
3567 3. Some tidies to get rid of compiler warnings:
3568
3569 . In the match_data structure, match_limit was an unsigned long int, whereas
3570 match_call_count was an int. I've made them both unsigned long ints.
3571
3572 . In pcretest the fact that a const uschar * doesn't automatically cast to
3573 a void * provoked a warning.
3574
3575 . Turning on some more compiler warnings threw up some "shadow" variables
3576 and a few more missing casts.
3577
3578 4. If PCRE was complied with UTF-8 support, but called without the PCRE_UTF8
3579 option, a class that contained a single character with a value between 128
3580 and 255 (e.g. /[\xFF]/) caused PCRE to crash.
3581
3582 5. If PCRE was compiled with UTF-8 support, but called without the PCRE_UTF8
3583 option, a class that contained several characters, but with at least one
3584 whose value was between 128 and 255 caused PCRE to crash.
3585
3586
3587 Version 4.1 12-Mar-03
3588 ---------------------
3589
3590 1. Compiling with gcc -pedantic found a couple of places where casts were
3591 needed, and a string in dftables.c that was longer than standard compilers are
3592 required to support.
3593
3594 2. Compiling with Sun's compiler found a few more places where the code could
3595 be tidied up in order to avoid warnings.
3596
3597 3. The variables for cross-compiling were called HOST_CC and HOST_CFLAGS; the
3598 first of these names is deprecated in the latest Autoconf in favour of the name
3599 CC_FOR_BUILD, because "host" is typically used to mean the system on which the
3600 compiled code will be run. I can't find a reference for HOST_CFLAGS, but by
3601 analogy I have changed it to CFLAGS_FOR_BUILD.
3602
3603 4. Added -no-undefined to the linking command in the Makefile, because this is
3604 apparently helpful for Windows. To make it work, also added "-L. -lpcre" to the
3605 linking step for the pcreposix library.
3606
3607 5. PCRE was failing to diagnose the case of two named groups with the same
3608 name.
3609
3610 6. A problem with one of PCRE's optimizations was discovered. PCRE remembers a
3611 literal character that is needed in the subject for a match, and scans along to
3612 ensure that it is present before embarking on the full matching process. This
3613 saves time in cases of nested unlimited repeats that are never going to match.
3614 Problem: the scan can take a lot of time if the subject is very long (e.g.
3615 megabytes), thus penalizing straightforward matches. It is now done only if the
3616 amount of subject to be scanned is less than 1000 bytes.
3617
3618 7. A lesser problem with the same optimization is that it was recording the
3619 first character of an anchored pattern as "needed", thus provoking a search
3620 right along the subject, even when the first match of the pattern was going to
3621 fail. The "needed" character is now not set for anchored patterns, unless it
3622 follows something in the pattern that is of non-fixed length. Thus, it still
3623 fulfils its original purpose of finding quick non-matches in cases of nested
3624 unlimited repeats, but isn't used for simple anchored patterns such as /^abc/.
3625
3626
3627 Version 4.0 17-Feb-03
3628 ---------------------
3629
3630 1. If a comment in an extended regex that started immediately after a meta-item
3631 extended to the end of string, PCRE compiled incorrect data. This could lead to
3632 all kinds of weird effects. Example: /#/ was bad; /()#/ was bad; /a#/ was not.
3633
3634 2. Moved to autoconf 2.53 and libtool 1.4.2.
3635
3636 3. Perl 5.8 no longer needs "use utf8" for doing UTF-8 things. Consequently,
3637 the special perltest8 script is no longer needed - all the tests can be run
3638 from a single perltest script.
3639
3640 4. From 5.004, Perl has not included the VT character (0x0b) in the set defined
3641 by \s. It has now been removed in PCRE. This means it isn't recognized as
3642 whitespace in /x regexes too, which is the same as Perl. Note that the POSIX
3643 class [:space:] *does* include VT, thereby creating a mess.
3644
3645 5. Added the class [:blank:] (a GNU extension from Perl 5.8) to match only
3646 space and tab.
3647
3648 6. Perl 5.005 was a long time ago. It's time to amalgamate the tests that use
3649 its new features into the main test script, reducing the number of scripts.
3650
3651 7. Perl 5.8 has changed the meaning of patterns like /a(?i)b/. Earlier versions
3652 were backward compatible, and made the (?i) apply to the whole pattern, as if
3653 /i were given. Now it behaves more logically, and applies the option setting
3654 only to what follows. PCRE has been changed to follow suit. However, if it
3655 finds options settings right at the start of the pattern, it extracts them into
3656 the global options, as before. Thus, they show up in the info data.
3657
3658 8. Added support for the \Q...\E escape sequence. Characters in between are
3659 treated as literals. This is slightly different from Perl in that $ and @ are
3660 also handled as literals inside the quotes. In Perl, they will cause variable
3661 interpolation. Note the following examples:
3662
3663 Pattern PCRE matches Perl matches
3664
3665 \Qabc$xyz\E abc$xyz abc followed by the contents of $xyz
3666 \Qabc\$xyz\E abc\$xyz abc\$xyz
3667 \Qabc\E\$\Qxyz\E abc$xyz abc$xyz
3668
3669 For compatibility with Perl, \Q...\E sequences are recognized inside character
3670 classes as well as outside them.
3671
3672 9. Re-organized 3 code statements in pcretest to avoid "overflow in
3673 floating-point constant arithmetic" warnings from a Microsoft compiler. Added a
3674 (size_t) cast to one statement in pcretest and one in pcreposix to avoid
3675 signed/unsigned warnings.
3676
3677 10. SunOS4 doesn't have strtoul(). This was used only for unpicking the -o
3678 option for pcretest, so I've replaced it by a simple function that does just
3679 that job.
3680
3681 11. pcregrep was ending with code 0 instead of 2 for the commands "pcregrep" or
3682 "pcregrep -".
3683
3684 12. Added "possessive quantifiers" ?+, *+, ++, and {,}+ which come from Sun's
3685 Java package. This provides some syntactic sugar for simple cases of what my
3686 documentation calls "once-only subpatterns". A pattern such as x*+ is the same
3687 as (?>x*). In other words, if what is inside (?>...) is just a single repeated
3688 item, you can use this simplified notation. Note that only makes sense with
3689 greedy quantifiers. Consequently, the use of the possessive quantifier forces
3690 greediness, whatever the setting of the PCRE_UNGREEDY option.
3691
3692 13. A change of greediness default within a pattern was not taking effect at
3693 the current level for patterns like /(b+(?U)a+)/. It did apply to parenthesized
3694 subpatterns that followed. Patterns like /b+(?U)a+/ worked because the option
3695 was abstracted outside.
3696
3697 14. PCRE now supports the \G assertion. It is true when the current matching
3698 position is at the start point of the match. This differs from \A when the
3699 starting offset is non-zero. Used with the /g option of pcretest (or similar
3700 code), it works in the same way as it does for Perl's /g option. If all
3701 alternatives of a regex begin with \G, the expression is anchored to the start
3702 match position, and the "anchored" flag is set in the compiled expression.
3703
3704 15. Some bugs concerning the handling of certain option changes within patterns
3705 have been fixed. These applied to options other than (?ims). For example,
3706 "a(?x: b c )d" did not match "XabcdY" but did match "Xa b c dY". It should have
3707 been the other way round. Some of this was related to change 7 above.
3708
3709 16. PCRE now gives errors for /[.x.]/ and /[=x=]/ as unsupported POSIX
3710 features, as Perl does. Previously, PCRE gave the warnings only for /[[.x.]]/
3711 and /[[=x=]]/. PCRE now also gives an error for /[:name:]/ because it supports
3712 POSIX classes only within a class (e.g. /[[:alpha:]]/).
3713
3714 17. Added support for Perl's \C escape. This matches one byte, even in UTF8
3715 mode. Unlike ".", it always matches newline, whatever the setting of
3716 PCRE_DOTALL. However, PCRE does not permit \C to appear in lookbehind
3717 assertions. Perl allows it, but it doesn't (in general) work because it can't
3718 calculate the length of the lookbehind. At least, that's the case for Perl
3719 5.8.0 - I've been told they are going to document that it doesn't work in
3720 future.
3721
3722 18. Added an error diagnosis for escapes that PCRE does not support: these are
3723 \L, \l, \N, \P, \p, \U, \u, and \X.
3724
3725 19. Although correctly diagnosing a missing ']' in a character class, PCRE was
3726 reading past the end of the pattern in cases such as /[abcd/.
3727
3728 20. PCRE was getting more memory than necessary for patterns with classes that
3729 contained both POSIX named classes and other characters, e.g. /[[:space:]abc/.
3730
3731 21. Added some code, conditional on #ifdef VPCOMPAT, to make life easier for
3732 compiling PCRE for use with Virtual Pascal.
3733
3734 22. Small fix to the Makefile to make it work properly if the build is done
3735 outside the source tree.
3736
3737 23. Added a new extension: a condition to go with recursion. If a conditional
3738 subpattern starts with (?(R) the "true" branch is used if recursion has
3739 happened, whereas the "false" branch is used only at the top level.
3740
3741 24. When there was a very long string of literal characters (over 255 bytes
3742 without UTF support, over 250 bytes with UTF support), the computation of how
3743 much memory was required could be incorrect, leading to segfaults or other
3744 strange effects.
3745
3746 25. PCRE was incorrectly assuming anchoring (either to start of subject or to
3747 start of line for a non-DOTALL pattern) when a pattern started with (.*) and
3748 there was a subsequent back reference to those brackets. This meant that, for
3749 example, /(.*)\d+\1/ failed to match "abc123bc". Unfortunately, it isn't
3750 possible to check for precisely this case. All we can do is abandon the
3751 optimization if .* occurs inside capturing brackets when there are any back
3752 references whatsoever. (See below for a better fix that came later.)
3753
3754 26. The handling of the optimization for finding the first character of a
3755 non-anchored pattern, and for finding a character that is required later in the
3756 match were failing in some cases. This didn't break the matching; it just
3757 failed to optimize when it could. The way this is done has been re-implemented.
3758
3759 27. Fixed typo in error message for invalid (?R item (it said "(?p").
3760
3761 28. Added a new feature that provides some of the functionality that Perl
3762 provides with (?{...}). The facility is termed a "callout". The way it is done
3763 in PCRE is for the caller to provide an optional function, by setting
3764 pcre_callout to its entry point. Like pcre_malloc and pcre_free, this is a
3765 global variable. By default it is unset, which disables all calling out. To get
3766 the function called, the regex must include (?C) at appropriate points. This
3767 is, in fact, equivalent to (?C0), and any number <= 255 may be given with (?C).
3768 This provides a means of identifying different callout points. When PCRE
3769 reaches such a point in the regex, if pcre_callout has been set, the external
3770 function is called. It is provided with data in a structure called
3771 pcre_callout_block, which is defined in pcre.h. If the function returns 0,
3772 matching continues; if it returns a non-zero value, the match at the current
3773 point fails. However, backtracking will occur if possible. [This was changed
3774 later and other features added - see item 49 below.]
3775
3776 29. pcretest is upgraded to test the callout functionality. It provides a
3777 callout function that displays information. By default, it shows the start of
3778 the match and the current position in the text. There are some new data escapes
3779 to vary what happens:
3780
3781 \C+ in addition, show current contents of captured substrings
3782 \C- do not supply a callout function
3783 \C!n return 1 when callout number n is reached
3784 \C!n!m return 1 when callout number n is reached for the mth time
3785
3786 30. If pcregrep was called with the -l option and just a single file name, it
3787 output "<stdin>" if a match was found, instead of the file name.
3788
3789 31. Improve the efficiency of the POSIX API to PCRE. If the number of capturing
3790 slots is less than POSIX_MALLOC_THRESHOLD, use a block on the stack to pass to
3791 pcre_exec(). This saves a malloc/free per call. The default value of
3792 POSIX_MALLOC_THRESHOLD is 10; it can be changed by --with-posix-malloc-threshold
3793 when configuring.
3794
3795 32. The default maximum size of a compiled pattern is 64K. There have been a
3796 few cases of people hitting this limit. The code now uses macros to handle the
3797 storing of links as offsets within the compiled pattern. It defaults to 2-byte
3798 links, but this can be changed to 3 or 4 bytes by --with-link-size when
3799 configuring. Tests 2 and 5 work only with 2-byte links because they output
3800 debugging information about compiled patterns.
3801
3802 33. Internal code re-arrangements:
3803
3804 (a) Moved the debugging function for printing out a compiled regex into
3805 its own source file (printint.c) and used #include to pull it into
3806 pcretest.c and, when DEBUG is defined, into pcre.c, instead of having two
3807 separate copies.
3808
3809 (b) Defined the list of op-code names for debugging as a macro in
3810 internal.h so that it is next to the definition of the opcodes.
3811
3812 (c) Defined a table of op-code lengths for simpler skipping along compiled
3813 code. This is again a macro in internal.h so that it is next to the
3814 definition of the opcodes.
3815
3816 34. Added support for recursive calls to individual subpatterns, along the
3817 lines of Robin Houston's patch (but implemented somewhat differently).
3818
3819 35. Further mods to the Makefile to help Win32. Also, added code to pcregrep to
3820 allow it to read and process whole directories in Win32. This code was
3821 contributed by Lionel Fourquaux; it has not been tested by me.
3822
3823 36. Added support for named subpatterns. The Python syntax (?P<name>...) is
3824 used to name a group. Names consist of alphanumerics and underscores, and must
3825 be unique. Back references use the syntax (?P=name) and recursive calls use
3826 (?P>name) which is a PCRE extension to the Python extension. Groups still have
3827 numbers. The function pcre_fullinfo() can be used after compilation to extract
3828 a name/number map. There are three relevant calls:
3829
3830 PCRE_INFO_NAMEENTRYSIZE yields the size of each entry in the map
3831 PCRE_INFO_NAMECOUNT yields the number of entries
3832 PCRE_INFO_NAMETABLE yields a pointer to the map.
3833
3834 The map is a vector of fixed-size entries. The size of each entry depends on
3835 the length of the longest name used. The first two bytes of each entry are the
3836 group number, most significant byte first. There follows the corresponding
3837 name, zero terminated. The names are in alphabetical order.
3838
3839 37. Make the maximum literal string in the compiled code 250 for the non-UTF-8
3840 case instead of 255. Making it the same both with and without UTF-8 support
3841 means that the same test output works with both.
3842
3843 38. There was a case of malloc(0) in the POSIX testing code in pcretest. Avoid
3844 calling malloc() with a zero argument.
3845
3846 39. Change 25 above had to resort to a heavy-handed test for the .* anchoring
3847 optimization. I've improved things by keeping a bitmap of backreferences with
3848 numbers 1-31 so that if .* occurs inside capturing brackets that are not in
3849 fact referenced, the optimization can be applied. It is unlikely that a
3850 relevant occurrence of .* (i.e. one which might indicate anchoring or forcing
3851 the match to follow \n) will appear inside brackets with a number greater than
3852 31, but if it does, any back reference > 31 suppresses the optimization.
3853
3854 40. Added a new compile-time option PCRE_NO_AUTO_CAPTURE. This has the effect
3855 of disabling numbered capturing parentheses. Any opening parenthesis that is
3856 not followed by ? behaves as if it were followed by ?: but named parentheses
3857 can still be used for capturing (and they will acquire numbers in the usual
3858 way).
3859
3860 41. Redesigned the return codes from the match() function into yes/no/error so
3861 that errors can be passed back from deep inside the nested calls. A malloc
3862 failure while inside a recursive subpattern call now causes the
3863 PCRE_ERROR_NOMEMORY return instead of quietly going wrong.
3864
3865 42. It is now possible to set a limit on the number of times the match()
3866 function is called in a call to pcre_exec(). This facility makes it possible to
3867 limit the amount of recursion and backtracking, though not in a directly
3868 obvious way, because the match() function is used in a number of different
3869 circumstances. The count starts from zero for each position in the subject
3870 string (for non-anchored patterns). The default limit is, for compatibility, a
3871 large number, namely 10 000 000. You can change this in two ways:
3872
3873 (a) When configuring PCRE before making, you can use --with-match-limit=n
3874 to set a default value for the compiled library.
3875
3876 (b) For each call to pcre_exec(), you can pass a pcre_extra block in which
3877 a different value is set. See 45 below.
3878
3879 If the limit is exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
3880
3881 43. Added a new function pcre_config(int, void *) to enable run-time extraction
3882 of things that can be changed at compile time. The first argument specifies
3883 what is wanted and the second points to where the information is to be placed.
3884 The current list of available information is:
3885
3886 PCRE_CONFIG_UTF8
3887
3888 The output is an integer that is set to one if UTF-8 support is available;
3889 otherwise it is set to zero.
3890
3891 PCRE_CONFIG_NEWLINE
3892
3893 The output is an integer that it set to the value of the code that is used for
3894 newline. It is either LF (10) or CR (13).
3895
3896 PCRE_CONFIG_LINK_SIZE
3897
3898 The output is an integer that contains the number of bytes used for internal
3899 linkage in compiled expressions. The value is 2, 3, or 4. See item 32 above.
3900
3901 PCRE_CONFIG_POSIX_MALLOC_THRESHOLD
3902
3903 The output is an integer that contains the threshold above which the POSIX
3904 interface uses malloc() for output vectors. See item 31 above.
3905
3906 PCRE_CONFIG_MATCH_LIMIT
3907
3908 The output is an unsigned integer that contains the default limit of the number
3909 of match() calls in a pcre_exec() execution. See 42 above.
3910
3911 44. pcretest has been upgraded by the addition of the -C option. This causes it
3912 to extract all the available output from the new pcre_config() function, and to
3913 output it. The program then exits immediately.
3914
3915 45. A need has arisen to pass over additional data with calls to pcre_exec() in
3916 order to support additional features. One way would have been to define
3917 pcre_exec2() (for example) with extra arguments, but this would not have been
3918 extensible, and would also have required all calls to the original function to
3919 be mapped to the new one. Instead, I have chosen to extend the mechanism that
3920 is used for passing in "extra" data from pcre_study().
3921
3922 The pcre_extra structure is now exposed and defined in pcre.h. It currently
3923 contains the following fields:
3924
3925 flags a bitmap indicating which of the following fields are set
3926 study_data opaque data from pcre_study()
3927 match_limit a way of specifying a limit on match() calls for a specific
3928 call to pcre_exec()
3929 callout_data data for callouts (see 49 below)
3930
3931 The flag bits are also defined in pcre.h, and are
3932
3933 PCRE_EXTRA_STUDY_DATA
3934 PCRE_EXTRA_MATCH_LIMIT
3935 PCRE_EXTRA_CALLOUT_DATA
3936
3937 The pcre_study() function now returns one of these new pcre_extra blocks, with
3938 the actual study data pointed to by the study_data field, and the
3939 PCRE_EXTRA_STUDY_DATA flag set. This can be passed directly to pcre_exec() as
3940 before. That is, this change is entirely upwards-compatible and requires no
3941 change to existing code.
3942
3943 If you want to pass in additional data to pcre_exec(), you can either place it
3944 in a pcre_extra block provided by pcre_study(), or create your own pcre_extra
3945 block.
3946
3947 46. pcretest has been extended to test the PCRE_EXTRA_MATCH_LIMIT feature. If a
3948 data string contains the escape sequence \M, pcretest calls pcre_exec() several
3949 times with different match limits, until it finds the minimum value needed for
3950 pcre_exec() to complete. The value is then output. This can be instructive; for
3951 most simple matches the number is quite small, but for pathological cases it
3952 gets very large very quickly.
3953
3954 47. There's a new option for pcre_fullinfo() called PCRE_INFO_STUDYSIZE. It
3955 returns the size of the data block pointed to by the study_data field in a
3956 pcre_extra block, that is, the value that was passed as the argument to
3957 pcre_malloc() when PCRE was getting memory in which to place the information
3958 created by pcre_study(). The fourth argument should point to a size_t variable.
3959 pcretest has been extended so that this information is shown after a successful
3960 pcre_study() call when information about the compiled regex is being displayed.
3961
3962 48. Cosmetic change to Makefile: there's no need to have / after $(DESTDIR)
3963 because what follows is always an absolute path. (Later: it turns out that this
3964 is more than cosmetic for MinGW, because it doesn't like empty path
3965 components.)
3966
3967 49. Some changes have been made to the callout feature (see 28 above):
3968
3969 (i) A callout function now has three choices for what it returns:
3970
3971 0 => success, carry on matching
3972 > 0 => failure at this point, but backtrack if possible
3973 < 0 => serious error, return this value from pcre_exec()
3974
3975 Negative values should normally be chosen from the set of PCRE_ERROR_xxx
3976 values. In particular, returning PCRE_ERROR_NOMATCH forces a standard
3977 "match failed" error. The error number PCRE_ERROR_CALLOUT is reserved for
3978 use by callout functions. It will never be used by PCRE itself.
3979
3980 (ii) The pcre_extra structure (see 45 above) has a void * field called
3981 callout_data, with corresponding flag bit PCRE_EXTRA_CALLOUT_DATA. The
3982 pcre_callout_block structure has a field of the same name. The contents of
3983 the field passed in the pcre_extra structure are passed to the callout
3984 function in the corresponding field in the callout block. This makes it
3985 easier to use the same callout-containing regex from multiple threads. For
3986 testing, the pcretest program has a new data escape
3987
3988 \C*n pass the number n (may be negative) as callout_data
3989
3990 If the callout function in pcretest receives a non-zero value as
3991 callout_data, it returns that value.
3992
3993 50. Makefile wasn't handling CFLAGS properly when compiling dftables. Also,
3994 there were some redundant $(CFLAGS) in commands that are now specified as
3995 $(LINK), which already includes $(CFLAGS).
3996
3997 51. Extensions to UTF-8 support are listed below. These all apply when (a) PCRE
3998 has been compiled with UTF-8 support *and* pcre_compile() has been compiled
3999 with the PCRE_UTF8 flag. Patterns that are compiled without that flag assume
4000 one-byte characters throughout. Note that case-insensitive matching applies
4001 only to characters whose values are less than 256. PCRE doesn't support the
4002 notion of cases for higher-valued characters.
4003
4004 (i) A character class whose characters are all within 0-255 is handled as
4005 a bit map, and the map is inverted for negative classes. Previously, a
4006 character > 255 always failed to match such a class; however it should
4007 match if the class was a negative one (e.g. [^ab]). This has been fixed.
4008
4009 (ii) A negated character class with a single character < 255 is coded as
4010 "not this character" (OP_NOT). This wasn't working properly when the test
4011 character was multibyte, either singly or repeated.
4012
4013 (iii) Repeats of multibyte characters are now handled correctly in UTF-8
4014 mode, for example: \x{100}{2,3}.
4015
4016 (iv) The character escapes \b, \B, \d, \D, \s, \S, \w, and \W (either
4017 singly or repeated) now correctly test multibyte characters. However,
4018 PCRE doesn't recognize any characters with values greater than 255 as
4019 digits, spaces, or word characters. Such characters always match \D, \S,
4020 and \W, and never match \d, \s, or \w.
4021
4022 (v) Classes may now contain characters and character ranges with values
4023 greater than 255. For example: [ab\x{100}-\x{400}].
4024
4025 (vi) pcregrep now has a --utf-8 option (synonym -u) which makes it call
4026 PCRE in UTF-8 mode.
4027
4028 52. The info request value PCRE_INFO_FIRSTCHAR has been renamed
4029 PCRE_INFO_FIRSTBYTE because it is a byte value. However, the old name is
4030 retained for backwards compatibility. (Note that LASTLITERAL is also a byte
4031 value.)
4032
4033 53. The single man page has become too large. I have therefore split it up into
4034 a number of separate man pages. These also give rise to individual HTML pages;
4035 these are now put in a separate directory, and there is an index.html page that
4036 lists them all. Some hyperlinking between the pages has been installed.
4037
4038 54. Added convenience functions for handling named capturing parentheses.
4039
4040 55. Unknown escapes inside character classes (e.g. [\M]) and escapes that
4041 aren't interpreted therein (e.g. [\C]) are literals in Perl. This is now also
4042 true in PCRE, except when the PCRE_EXTENDED option is set, in which case they
4043 are faulted.
4044
4045 56. Introduced HOST_CC and HOST_CFLAGS which can be set in the environment when
4046 calling configure. These values are used when compiling the dftables.c program
4047 which is run to generate the source of the default character tables. They
4048 default to the values of CC and CFLAGS. If you are cross-compiling PCRE,
4049 you will need to set these values.
4050
4051 57. Updated the building process for Windows DLL, as provided by Fred Cox.
4052
4053
4054 Version 3.9 02-Jan-02
4055 ---------------------
4056
4057 1. A bit of extraneous text had somehow crept into the pcregrep documentation.
4058
4059 2. If --disable-static was given, the building process failed when trying to
4060 build pcretest and pcregrep. (For some reason it was using libtool to compile
4061 them, which is not right, as they aren't part of the library.)
4062
4063
4064 Version 3.8 18-Dec-01
4065 ---------------------
4066
4067 1. The experimental UTF-8 code was completely screwed up. It was packing the
4068 bytes in the wrong order. How dumb can you get?
4069
4070
4071 Version 3.7 29-Oct-01
4072 ---------------------
4073
4074 1. In updating pcretest to check change 1 of version 3.6, I screwed up.
4075 This caused pcretest, when used on the test data, to segfault. Unfortunately,
4076 this didn't happen under Solaris 8, where I normally test things.
4077
4078 2. The Makefile had to be changed to make it work on BSD systems, where 'make'
4079 doesn't seem to recognize that ./xxx and xxx are the same file. (This entry
4080 isn't in ChangeLog distributed with 3.7 because I forgot when I hastily made
4081 this fix an hour or so after the initial 3.7 release.)
4082
4083
4084 Version 3.6 23-Oct-01
4085 ---------------------
4086
4087 1. Crashed with /(sens|respons)e and \1ibility/ and "sense and sensibility" if
4088 offsets passed as NULL with zero offset count.
4089
4090 2. The config.guess and config.sub files had not been updated when I moved to
4091 the latest autoconf.
4092
4093
4094 Version 3.5 15-Aug-01
4095 ---------------------
4096
4097 1. Added some missing #if !defined NOPOSIX conditionals in pcretest.c that
4098 had been forgotten.
4099
4100 2. By using declared but undefined structures, we can avoid using "void"
4101 definitions in pcre.h while keeping the internal definitions of the structures
4102 private.
4103
4104 3. The distribution is now built using autoconf 2.50 and libtool 1.4. From a
4105 user point of view, this means that both static and shared libraries are built
4106 by default, but this can be individually controlled. More of the work of
4107 handling this static/shared cases is now inside libtool instead of PCRE's make
4108 file.
4109
4110 4. The pcretest utility is now installed along with pcregrep because it is
4111 useful for users (to test regexs) and by doing this, it automatically gets
4112 relinked by libtool. The documentation has been turned into a man page, so
4113 there are now .1, .txt, and .html versions in /doc.
4114
4115 5. Upgrades to pcregrep:
4116 (i) Added long-form option names like gnu grep.
4117 (ii) Added --help to list all options with an explanatory phrase.
4118 (iii) Added -r, --recursive to recurse into sub-directories.
4119 (iv) Added -f, --file to read patterns from a file.
4120
4121 6. pcre_exec() was referring to its "code" argument before testing that
4122 argument for NULL (and giving an error if it was NULL).
4123
4124 7. Upgraded Makefile.in to allow for compiling in a different directory from
4125 the source directory.
4126
4127 8. Tiny buglet in pcretest: when pcre_fullinfo() was called to retrieve the
4128 options bits, the pointer it was passed was to an int instead of to an unsigned
4129 long int. This mattered only on 64-bit systems.
4130
4131 9. Fixed typo (3.4/1) in pcre.h again. Sigh. I had changed pcre.h (which is
4132 generated) instead of pcre.in, which it its source. Also made the same change
4133 in several of the .c files.
4134
4135 10. A new release of gcc defines printf() as a macro, which broke pcretest
4136 because it had an ifdef in the middle of a string argument for printf(). Fixed
4137 by using separate calls to printf().
4138
4139 11. Added --enable-newline-is-cr and --enable-newline-is-lf to the configure
4140 script, to force use of CR or LF instead of \n in the source. On non-Unix
4141 systems, the value can be set in config.h.
4142
4143 12. The limit of 200 on non-capturing parentheses is a _nesting_ limit, not an
4144 absolute limit. Changed the text of the error message to make this clear, and
4145 likewise updated the man page.
4146
4147 13. The limit of 99 on the number of capturing subpatterns has been removed.
4148 The new limit is 65535, which I hope will not be a "real" limit.
4149
4150
4151 Version 3.4 22-Aug-00
4152 ---------------------
4153
4154 1. Fixed typo in pcre.h: unsigned const char * changed to const unsigned char *.
4155
4156 2. Diagnose condition (?(0) as an error instead of crashing on matching.
4157
4158
4159 Version 3.3 01-Aug-00
4160 ---------------------
4161
4162 1. If an octal character was given, but the value was greater than \377, it
4163 was not getting masked to the least significant bits, as documented. This could
4164 lead to crashes in some systems.
4165
4166 2. Perl 5.6 (if not earlier versions) accepts classes like [a-\d] and treats
4167 the hyphen as a literal. PCRE used to give an error; it now behaves like Perl.
4168
4169 3. Added the functions pcre_free_substring() and pcre_free_substring_list().
4170 These just pass their arguments on to (pcre_free)(), but they are provided
4171 because some uses of PCRE bind it to non-C systems that can call its functions,
4172 but cannot call free() or pcre_free() directly.
4173
4174 4. Add "make test" as a synonym for "make check". Corrected some comments in
4175 the Makefile.
4176
4177 5. Add $(DESTDIR)/ in front of all the paths in the "install" target in the
4178 Makefile.
4179
4180 6. Changed the name of pgrep to pcregrep, because Solaris has introduced a
4181 command called pgrep for grepping around the active processes.
4182
4183 7. Added the beginnings of support for UTF-8 character strings.
4184
4185 8. Arranged for the Makefile to pass over the settings of CC, CFLAGS, and
4186 RANLIB to ./ltconfig so that they are used by libtool. I think these are all
4187 the relevant ones. (AR is not passed because ./ltconfig does its own figuring
4188 out for the ar command.)
4189
4190
4191 Version 3.2 12-May-00
4192 ---------------------
4193
4194 This is purely a bug fixing release.
4195
4196 1. If the pattern /((Z)+|A)*/ was matched agained ZABCDEFG it matched Z instead
4197 of ZA. This was just one example of several cases that could provoke this bug,
4198 which was introduced by change 9 of version 2.00. The code for breaking
4199 infinite loops after an iteration that matches an empty string was't working
4200 correctly.
4201
4202 2. The pcretest program was not imitating Perl correctly for the pattern /a*/g
4203 when matched against abbab (for example). After matching an empty string, it
4204 wasn't forcing anchoring when setting PCRE_NOTEMPTY for the next attempt; this
4205 caused it to match further down the string than it should.
4206
4207 3. The code contained an inclusion of sys/types.h. It isn't clear why this
4208 was there because it doesn't seem to be needed, and it causes trouble on some
4209 systems, as it is not a Standard C header. It has been removed.
4210
4211 4. Made 4 silly changes to the source to avoid stupid compiler warnings that
4212 were reported on the Macintosh. The changes were from
4213
4214 while ((c = *(++ptr)) != 0 && c != '\n');
4215 to
4216 while ((c = *(++ptr)) != 0 && c != '\n') ;
4217
4218 Totally extraordinary, but if that's what it takes...
4219
4220 5. PCRE is being used in one environment where neither memmove() nor bcopy() is
4221 available. Added HAVE_BCOPY and an autoconf test for it; if neither
4222 HAVE_MEMMOVE nor HAVE_BCOPY is set, use a built-in emulation function which
4223 assumes the way PCRE uses memmove() (always moving upwards).
4224
4225 6. PCRE is being used in one environment where strchr() is not available. There
4226 was only one use in pcre.c, and writing it out to avoid strchr() probably gives
4227 faster code anyway.
4228
4229
4230 Version 3.1 09-Feb-00
4231 ---------------------
4232
4233 The only change in this release is the fixing of some bugs in Makefile.in for
4234 the "install" target:
4235
4236 (1) It was failing to install pcreposix.h.
4237
4238 (2) It was overwriting the pcre.3 man page with the pcreposix.3 man page.
4239
4240
4241 Version 3.0 01-Feb-00
4242 ---------------------
4243
4244 1. Add support for the /+ modifier to perltest (to output $` like it does in
4245 pcretest).
4246
4247 2. Add support for the /g modifier to perltest.
4248
4249 3. Fix pcretest so that it behaves even more like Perl for /g when the pattern
4250 matches null strings.
4251
4252 4. Fix perltest so that it doesn't do unwanted things when fed an empty
4253 pattern. Perl treats empty patterns specially - it reuses the most recent
4254 pattern, which is not what we want. Replace // by /(?#)/ in order to avoid this
4255 effect.
4256
4257 5. The POSIX interface was broken in that it was just handing over the POSIX
4258 captured string vector to pcre_exec(), but (since release 2.00) PCRE has
4259 required a bigger vector, with some working space on the end. This means that
4260 the POSIX wrapper now has to get and free some memory, and copy the results.
4261
4262 6. Added some simple autoconf support, placing the test data and the
4263 documentation in separate directories, re-organizing some of the
4264 information files, and making it build pcre-config (a GNU standard). Also added
4265 libtool support for building PCRE as a shared library, which is now the
4266 default.
4267
4268 7. Got rid of the leading zero in the definition of PCRE_MINOR because 08 and
4269 09 are not valid octal constants. Single digits will be used for minor values
4270 less than 10.
4271
4272 8. Defined REG_EXTENDED and REG_NOSUB as zero in the POSIX header, so that
4273 existing programs that set these in the POSIX interface can use PCRE without
4274 modification.
4275
4276 9. Added a new function, pcre_fullinfo() with an extensible interface. It can
4277 return all that pcre_info() returns, plus additional data. The pcre_info()
4278 function is retained for compatibility, but is considered to be obsolete.
4279
4280 10. Added experimental recursion feature (?R) to handle one common case that
4281 Perl 5.6 will be able to do with (?p{...}).
4282
4283 11. Added support for POSIX character classes like [:alpha:], which Perl is
4284 adopting.
4285
4286
4287 Version 2.08 31-Aug-99
4288 ----------------------
4289
4290 1. When startoffset was not zero and the pattern began with ".*", PCRE was not
4291 trying to match at the startoffset position, but instead was moving forward to
4292 the next newline as if a previous match had failed.
4293
4294 2. pcretest was not making use of PCRE_NOTEMPTY when repeating for /g and /G,
4295 and could get into a loop if a null string was matched other than at the start
4296 of the subject.
4297
4298 3. Added definitions of PCRE_MAJOR and PCRE_MINOR to pcre.h so the version can
4299 be distinguished at compile time, and for completeness also added PCRE_DATE.
4300
4301 5. Added Paul Sokolovsky's minor changes to make it easy to compile a Win32 DLL
4302 in GnuWin32 environments.
4303
4304
4305 Version 2.07 29-Jul-99
4306 ----------------------
4307
4308 1. The documentation is now supplied in plain text form and HTML as well as in
4309 the form of man page sources.
4310
4311 2. C++ compilers don't like assigning (void *) values to other pointer types.
4312 In particular this affects malloc(). Although there is no problem in Standard
4313 C, I've put in casts to keep C++ compilers happy.
4314
4315 3. Typo on pcretest.c; a cast of (unsigned char *) in the POSIX regexec() call
4316 should be (const char *).
4317
4318 4. If NOPOSIX is defined, pcretest.c compiles without POSIX support. This may
4319 be useful for non-Unix systems who don't want to bother with the POSIX stuff.
4320 However, I haven't made this a standard facility. The documentation doesn't
4321 mention it, and the Makefile doesn't support it.
4322
4323 5. The Makefile now contains an "install" target, with editable destinations at
4324 the top of the file. The pcretest program is not installed.
4325
4326 6. pgrep -V now gives the PCRE version number and date.
4327
4328 7. Fixed bug: a zero repetition after a literal string (e.g. /abcde{0}/) was
4329 causing the entire string to be ignored, instead of just the last character.
4330
4331 8. If a pattern like /"([^\\"]+|\\.)*"/ is applied in the normal way to a
4332 non-matching string, it can take a very, very long time, even for strings of
4333 quite modest length, because of the nested recursion. PCRE now does better in
4334 some of these cases. It does this by remembering the last required literal
4335 character in the pattern, and pre-searching the subject to ensure it is present
4336 before running the real match. In other words, it applies a heuristic to detect
4337 some types of certain failure quickly, and in the above example, if presented
4338 with a string that has no trailing " it gives "no match" very quickly.
4339
4340 9. A new runtime option PCRE_NOTEMPTY causes null string matches to be ignored;
4341 other alternatives are tried instead.
4342
4343
4344 Version 2.06 09-Jun-99
4345 ----------------------
4346
4347 1. Change pcretest's output for amount of store used to show just the code
4348 space, because the remainder (the data block) varies in size between 32-bit and
4349 64-bit systems.
4350
4351 2. Added an extra argument to pcre_exec() to supply an offset in the subject to
4352 start matching at. This allows lookbehinds to work when searching for multiple
4353 occurrences in a string.
4354
4355 3. Added additional options to pcretest for testing multiple occurrences:
4356
4357 /+ outputs the rest of the string that follows a match
4358 /g loops for multiple occurrences, using the new startoffset argument
4359 /G loops for multiple occurrences by passing an incremented pointer
4360
4361 4. PCRE wasn't doing the "first character" optimization for patterns starting
4362 with \b or \B, though it was doing it for other lookbehind assertions. That is,
4363 it wasn't noticing that a match for a pattern such as /\bxyz/ has to start with
4364 the letter 'x'. On long subject strings, this gives a significant speed-up.
4365
4366
4367 Version 2.05 21-Apr-99
4368 ----------------------
4369
4370 1. Changed the type of magic_number from int to long int so that it works
4371 properly on 16-bit systems.
4372
4373 2. Fixed a bug which caused patterns starting with .* not to work correctly
4374 when the subject string contained newline characters. PCRE was assuming
4375 anchoring for such patterns in all cases, which is not correct because .* will
4376 not pass a newline unless PCRE_DOTALL is set. It now assumes anchoring only if
4377 DOTALL is set at top level; otherwise it knows that patterns starting with .*
4378 must be retried after every newline in the subject.
4379
4380
4381 Version 2.04 18-Feb-99
4382 ----------------------
4383
4384 1. For parenthesized subpatterns with repeats whose minimum was zero, the
4385 computation of the store needed to hold the pattern was incorrect (too large).
4386 If such patterns were nested a few deep, this could multiply and become a real
4387 problem.
4388
4389 2. Added /M option to pcretest to show the memory requirement of a specific
4390 pattern. Made -m a synonym of -s (which does this globally) for compatibility.
4391
4392 3. Subpatterns of the form (regex){n,m} (i.e. limited maximum) were being
4393 compiled in such a way that the backtracking after subsequent failure was
4394 pessimal. Something like (a){0,3} was compiled as (a)?(a)?(a)? instead of
4395 ((a)((a)(a)?)?)? with disastrous performance if the maximum was of any size.
4396
4397
4398 Version 2.03 02-Feb-99
4399 ----------------------
4400
4401 1. Fixed typo and small mistake in man page.
4402
4403 2. Added 4th condition (GPL supersedes if conflict) and created separate
4404 LICENCE file containing the conditions.
4405
4406 3. Updated pcretest so that patterns such as /abc\/def/ work like they do in
4407 Perl, that is the internal \ allows the delimiter to be included in the
4408 pattern. Locked out the use of \ as a delimiter. If \ immediately follows
4409 the final delimiter, add \ to the end of the pattern (to test the error).
4410
4411 4. Added the convenience functions for extracting substrings after a successful
4412 match. Updated pcretest to make it able to test these functions.
4413
4414
4415 Version 2.02 14-Jan-99
4416 ----------------------
4417
4418 1. Initialized the working variables associated with each extraction so that
4419 their saving and restoring doesn't refer to uninitialized store.
4420
4421 2. Put dummy code into study.c in order to trick the optimizer of the IBM C
4422 compiler for OS/2 into generating correct code. Apparently IBM isn't going to
4423 fix the problem.
4424
4425 3. Pcretest: the timing code wasn't using LOOPREPEAT for timing execution
4426 calls, and wasn't printing the correct value for compiling calls. Increased the
4427 default value of LOOPREPEAT, and the number of significant figures in the
4428 times.
4429
4430 4. Changed "/bin/rm" in the Makefile to "-rm" so it works on Windows NT.
4431
4432 5. Renamed "deftables" as "dftables" to get it down to 8 characters, to avoid
4433 a building problem on Windows NT with a FAT file system.
4434
4435
4436 Version 2.01 21-Oct-98
4437 ----------------------
4438
4439 1. Changed the API for pcre_compile() to allow for the provision of a pointer
4440 to character tables built by pcre_maketables() in the current locale. If NULL
4441 is passed, the default tables are used.
4442
4443
4444 Version 2.00 24-Sep-98
4445 ----------------------
4446
4447 1. Since the (>?) facility is in Perl 5.005, don't require PCRE_EXTRA to enable
4448 it any more.
4449
4450 2. Allow quantification of (?>) groups, and make it work correctly.
4451
4452 3. The first character computation wasn't working for (?>) groups.
4453
4454 4. Correct the implementation of \Z (it is permitted to match on the \n at the
4455 end of the subject) and add 5.005's \z, which really does match only at the
4456 very end of the subject.
4457
4458 5. Remove the \X "cut" facility; Perl doesn't have it, and (?> is neater.
4459
4460 6. Remove the ability to specify CASELESS, MULTILINE, DOTALL, and
4461 DOLLAR_END_ONLY at runtime, to make it possible to implement the Perl 5.005
4462 localized options. All options to pcre_study() were also removed.
4463
4464 7. Add other new features from 5.005:
4465
4466 $(?<= positive lookbehind
4467 $(?<! negative lookbehind
4468 (?imsx-imsx) added the unsetting capability
4469 such a setting is global if at outer level; local otherwise
4470 (?imsx-imsx:) non-capturing groups with option setting
4471 (?(cond)re|re) conditional pattern matching
4472
4473 A backreference to itself in a repeated group matches the previous
4474 captured string.
4475
4476 8. General tidying up of studying (both automatic and via "study")
4477 consequential on the addition of new assertions.
4478
4479 9. As in 5.005, unlimited repeated groups that could match an empty substring
4480 are no longer faulted at compile time. Instead, the loop is forcibly broken at
4481 runtime if any iteration does actually match an empty substring.
4482
4483 10. Include the RunTest script in the distribution.
4484
4485 11. Added tests from the Perl 5.005_02 distribution. This showed up a few
4486 discrepancies, some of which were old and were also with respect to 5.004. They
4487 have now been fixed.
4488
4489
4490 Version 1.09 28-Apr-98
4491 ----------------------
4492
4493 1. A negated single character class followed by a quantifier with a minimum
4494 value of one (e.g. [^x]{1,6} ) was not compiled correctly. This could lead to
4495 program crashes, or just wrong answers. This did not apply to negated classes
4496 containing more than one character, or to minima other than one.
4497
4498
4499 Version 1.08 27-Mar-98
4500 ----------------------
4501
4502 1. Add PCRE_UNGREEDY to invert the greediness of quantifiers.
4503
4504 2. Add (?U) and (?X) to set PCRE_UNGREEDY and PCRE_EXTRA respectively. The
4505 latter must appear before anything that relies on it in the pattern.
4506
4507
4508 Version 1.07 16-Feb-98
4509 ----------------------
4510
4511 1. A pattern such as /((a)*)*/ was not being diagnosed as in error (unlimited
4512 repeat of a potentially empty string).
4513
4514
4515 Version 1.06 23-Jan-98
4516 ----------------------
4517
4518 1. Added Markus Oberhumer's little patches for C++.
4519
4520 2. Literal strings longer than 255 characters were broken.
4521
4522
4523 Version 1.05 23-Dec-97
4524 ----------------------
4525
4526 1. Negated character classes containing more than one character were failing if
4527 PCRE_CASELESS was set at run time.
4528
4529
4530 Version 1.04 19-Dec-97
4531 ----------------------
4532
4533 1. Corrected the man page, where some "const" qualifiers had been omitted.
4534
4535 2. Made debugging output print "{0,xxx}" instead of just "{,xxx}" to agree with
4536 input syntax.
4537
4538 3. Fixed memory leak which occurred when a regex with back references was
4539 matched with an offsets vector that wasn't big enough. The temporary memory
4540 that is used in this case wasn't being freed if the match failed.
4541
4542 4. Tidied pcretest to ensure it frees memory that it gets.
4543
4544 5. Temporary memory was being obtained in the case where the passed offsets
4545 vector was exactly big enough.
4546
4547 6. Corrected definition of offsetof() from change 5 below.
4548
4549 7. I had screwed up change 6 below and broken the rules for the use of
4550 setjmp(). Now fixed.
4551
4552
4553 Version 1.03 18-Dec-97
4554 ----------------------
4555
4556 1. A erroneous regex with a missing opening parenthesis was correctly
4557 diagnosed, but PCRE attempted to access brastack[-1], which could cause crashes
4558 on some systems.
4559
4560 2. Replaced offsetof(real_pcre, code) by offsetof(real_pcre, code[0]) because
4561 it was reported that one broken compiler failed on the former because "code" is
4562 also an independent variable.
4563
4564 3. The erroneous regex a[]b caused an array overrun reference.
4565
4566 4. A regex ending with a one-character negative class (e.g. /[^k]$/) did not
4567 fail on data ending with that character. (It was going on too far, and checking
4568 the next character, typically a binary zero.) This was specific to the
4569 optimized code for single-character negative classes.
4570
4571 5. Added a contributed patch from the TIN world which does the following:
4572
4573 + Add an undef for memmove, in case the the system defines a macro for it.
4574
4575 + Add a definition of offsetof(), in case there isn't one. (I don't know
4576 the reason behind this - offsetof() is part of the ANSI standard - but
4577 it does no harm).
4578
4579 + Reduce the ifdef's in pcre.c using macro DPRINTF, thereby eliminating
4580 most of the places where whitespace preceded '#'. I have given up and
4581 allowed the remaining 2 cases to be at the margin.
4582
4583 + Rename some variables in pcre to eliminate shadowing. This seems very
4584 pedantic, but does no harm, of course.
4585
4586 6. Moved the call to setjmp() into its own function, to get rid of warnings
4587 from gcc -Wall, and avoided calling it at all unless PCRE_EXTRA is used.
4588
4589 7. Constructs such as \d{8,} were compiling into the equivalent of
4590 \d{8}\d{0,65527} instead of \d{8}\d* which didn't make much difference to the
4591 outcome, but in this particular case used more store than had been allocated,
4592 which caused the bug to be discovered because it threw up an internal error.
4593
4594 8. The debugging code in both pcre and pcretest for outputting the compiled
4595 form of a regex was going wrong in the case of back references followed by
4596 curly-bracketed repeats.
4597
4598
4599 Version 1.02 12-Dec-97
4600 ----------------------
4601
4602 1. Typos in pcre.3 and comments in the source fixed.
4603
4604 2. Applied a contributed patch to get rid of places where it used to remove
4605 'const' from variables, and fixed some signed/unsigned and uninitialized
4606 variable warnings.
4607
4608 3. Added the "runtest" target to Makefile.
4609
4610 4. Set default compiler flag to -O2 rather than just -O.
4611
4612
4613 Version 1.01 19-Nov-97
4614 ----------------------
4615
4616 1. PCRE was failing to diagnose unlimited repeat of empty string for patterns
4617 like /([ab]*)*/, that is, for classes with more than one character in them.
4618
4619 2. Likewise, it wasn't diagnosing patterns with "once-only" subpatterns, such
4620 as /((?>a*))*/ (a PCRE_EXTRA facility).
4621
4622
4623 Version 1.00 18-Nov-97
4624 ----------------------
4625
4626 1. Added compile-time macros to support systems such as SunOS4 which don't have
4627 memmove() or strerror() but have other things that can be used instead.
4628
4629 2. Arranged that "make clean" removes the executables.
4630
4631
4632 Version 0.99 27-Oct-97
4633 ----------------------
4634
4635 1. Fixed bug in code for optimizing classes with only one character. It was
4636 initializing a 32-byte map regardless, which could cause it to run off the end
4637 of the memory it had got.
4638
4639 2. Added, conditional on PCRE_EXTRA, the proposed (?>REGEX) construction.
4640
4641
4642 Version 0.98 22-Oct-97
4643 ----------------------
4644
4645 1. Fixed bug in code for handling temporary memory usage when there are more
4646 back references than supplied space in the ovector. This could cause segfaults.
4647
4648
4649 Version 0.97 21-Oct-97
4650 ----------------------
4651
4652 1. Added the \X "cut" facility, conditional on PCRE_EXTRA.
4653
4654 2. Optimized negated single characters not to use a bit map.
4655
4656 3. Brought error texts together as macro definitions; clarified some of them;
4657 fixed one that was wrong - it said "range out of order" when it meant "invalid
4658 escape sequence".
4659
4660 4. Changed some char * arguments to const char *.
4661
4662 5. Added PCRE_NOTBOL and PCRE_NOTEOL (from POSIX).
4663
4664 6. Added the POSIX-style API wrapper in pcreposix.a and testing facilities in
4665 pcretest.
4666
4667
4668 Version 0.96 16-Oct-97
4669 ----------------------
4670
4671 1. Added a simple "pgrep" utility to the distribution.
4672
4673 2. Fixed an incompatibility with Perl: "{" is now treated as a normal character
4674 unless it appears in one of the precise forms "{ddd}", "{ddd,}", or "{ddd,ddd}"
4675 where "ddd" means "one or more decimal digits".
4676
4677 3. Fixed serious bug. If a pattern had a back reference, but the call to
4678 pcre_exec() didn't supply a large enough ovector to record the related
4679 identifying subpattern, the match always failed. PCRE now remembers the number
4680 of the largest back reference, and gets some temporary memory in which to save
4681 the offsets during matching if necessary, in order to ensure that
4682 backreferences always work.
4683
4684 4. Increased the compatibility with Perl in a number of ways:
4685
4686 (a) . no longer matches \n by default; an option PCRE_DOTALL is provided
4687 to request this handling. The option can be set at compile or exec time.
4688
4689 (b) $ matches before a terminating newline by default; an option
4690 PCRE_DOLLAR_ENDONLY is provided to override this (but not in multiline
4691 mode). The option can be set at compile or exec time.
4692
4693 (c) The handling of \ followed by a digit other than 0 is now supposed to be
4694 the same as Perl's. If the decimal number it represents is less than 10
4695 or there aren't that many previous left capturing parentheses, an octal
4696 escape is read. Inside a character class, it's always an octal escape,
4697 even if it is a single digit.
4698
4699 (d) An escaped but undefined alphabetic character is taken as a literal,
4700 unless PCRE_EXTRA is set. Currently this just reserves the remaining
4701 escapes.
4702
4703 (e) {0} is now permitted. (The previous item is removed from the compiled
4704 pattern).
4705
4706 5. Changed all the names of code files so that the basic parts are no longer
4707 than 10 characters, and abolished the teeny "globals.c" file.
4708
4709 6. Changed the handling of character classes; they are now done with a 32-byte
4710 bit map always.
4711
4712 7. Added the -d and /D options to pcretest to make it possible to look at the
4713 internals of compilation without having to recompile pcre.
4714
4715
4716 Version 0.95 23-Sep-97
4717 ----------------------
4718
4719 1. Fixed bug in pre-pass concerning escaped "normal" characters such as \x5c or
4720 \x20 at the start of a run of normal characters. These were being treated as
4721 real characters, instead of the source characters being re-checked.
4722
4723
4724 Version 0.94 18-Sep-97
4725 ----------------------
4726
4727 1. The functions are now thread-safe, with the caveat that the global variables
4728 containing pointers to malloc() and free() or alternative functions are the
4729 same for all threads.
4730
4731 2. Get pcre_study() to generate a bitmap of initial characters for non-
4732 anchored patterns when this is possible, and use it if passed to pcre_exec().
4733
4734
4735 Version 0.93 15-Sep-97
4736 ----------------------
4737
4738 1. /(b)|(:+)/ was computing an incorrect first character.
4739
4740 2. Add pcre_study() to the API and the passing of pcre_extra to pcre_exec(),
4741 but not actually doing anything yet.
4742
4743 3. Treat "-" characters in classes that cannot be part of ranges as literals,
4744 as Perl does (e.g. [-az] or [az-]).
4745
4746 4. Set the anchored flag if a branch starts with .* or .*? because that tests
4747 all possible positions.
4748
4749 5. Split up into different modules to avoid including unneeded functions in a
4750 compiled binary. However, compile and exec are still in one module. The "study"
4751 function is split off.
4752
4753 6. The character tables are now in a separate module whose source is generated
4754 by an auxiliary program - but can then be edited by hand if required. There are
4755 now no calls to isalnum(), isspace(), isdigit(), isxdigit(), tolower() or
4756 toupper() in the code.
4757
4758 7. Turn the malloc/free funtions variables into pcre_malloc and pcre_free and
4759 make them global. Abolish the function for setting them, as the caller can now
4760 set them directly.
4761
4762
4763 Version 0.92 11-Sep-97
4764 ----------------------
4765
4766 1. A repeat with a fixed maximum and a minimum of 1 for an ordinary character
4767 (e.g. /a{1,3}/) was broken (I mis-optimized it).
4768
4769 2. Caseless matching was not working in character classes if the characters in
4770 the pattern were in upper case.
4771
4772 3. Make ranges like [W-c] work in the same way as Perl for caseless matching.
4773
4774 4. Make PCRE_ANCHORED public and accept as a compile option.
4775
4776 5. Add an options word to pcre_exec() and accept PCRE_ANCHORED and
4777 PCRE_CASELESS at run time. Add escapes \A and \I to pcretest to cause it to
4778 pass them.
4779
4780 6. Give an error if bad option bits passed at compile or run time.
4781
4782 7. Add PCRE_MULTILINE at compile and exec time, and (?m) as well. Add \M to
4783 pcretest to cause it to pass that flag.
4784
4785 8. Add pcre_info(), to get the number of identifying subpatterns, the stored
4786 options, and the first character, if set.
4787
4788 9. Recognize C+ or C{n,m} where n >= 1 as providing a fixed starting character.
4789
4790
4791 Version 0.91 10-Sep-97
4792 ----------------------
4793
4794 1. PCRE was failing to diagnose unlimited repeats of subpatterns that could
4795 match the empty string as in /(a*)*/. It was looping and ultimately crashing.
4796
4797 2. PCRE was looping on encountering an indefinitely repeated back reference to
4798 a subpattern that had matched an empty string, e.g. /(a|)\1*/. It now does what
4799 Perl does - treats the match as successful.
4800
4801 ****

Properties

Name Value
svn:eol-style native
svn:keywords "Author Date Id Revision Url"

  ViewVC Help
Powered by ViewVC 1.1.5