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

Contents of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log


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

Properties

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

  ViewVC Help
Powered by ViewVC 1.1.5