ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 69 by nigel, Sat Feb 24 21:40:18 2007 UTC revision 175 by ph10, Mon Jun 11 13:38:38 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 7.2 05-June-07
5    ---------------------
7     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
8        which is apparently normally available under Windows.
10     2. Re-jig the pcregrep tests with different newline settings in an attempt
11        to make them independent of the local environment's newline setting.
13     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
15     4. Some of the "internals" tests were previously cut out when the link size
16        was not 2, because the output contained actual offsets. The recent new
17        "Z" feature of pcretest means that these can be cut out, making the tests
18        usable with all link sizes.
20     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
21        stack recursion. This gives a massive performance boost under BSD, but just
22        a small improvement under Linux. However, it saves one field in the frame
23        in all cases.
25     6. Added more features from the forthcoming Perl 5.10:
27        (a) (?-n) (where n is a string of digits) is a relative subroutine or
28            recursion call. It refers to the nth most recently opened parentheses.
30        (b) (?+n) is also a relative subroutine call; it refers to the nth next
31            to be opened parentheses.
33        (c) Conditions that refer to capturing parentheses can be specified
34            relatively, for example, (?(-2)... or (?(+3)...
36        (d) \K resets the start of the current match so that everything before
37            is not part of it.
39        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
41        (f) \g{name} is another synonym - part of Perl 5.10's unification of
42            reference syntax.
44        (g) (?| introduces a group in which the numbering of parentheses in each
45            alternative starts with the same number.
47     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
50     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
51        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
52        for detecting groups that can match an empty string.
54     9. A pattern with a very large number of alternatives (more than several
55        hundred) was running out of internal workspace during the pre-compile
56        phase, where pcre_compile() figures out how much memory will be needed. A
57        bit of new cunning has reduced the workspace needed for groups with
58        alternatives. The 1000-alternative test pattern now uses 12 bytes of
59        workspace instead of running out of the 4096 that are available.
62    Version 7.1 24-Apr-07
63    ---------------------
65     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
66        that is more "standard", making use of automake and other Autotools. There
67        is some re-arrangement of the files and adjustment of comments consequent
68        on this.
70     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
71        for recursive directory scanning broke on some systems because the files
72        are not scanned in any specific order and on different systems the order
73        was different. A call to "sort" has been inserted into RunGrepTest for the
74        approprate test as a short-term fix. In the longer term there may be an
75        alternative.
77     3. I had an email from Eric Raymond about problems translating some of PCRE's
78        man pages to HTML (despite the fact that I distribute HTML pages, some
79        people do their own conversions for various reasons). The problems
80        concerned the use of low-level troff macros .br and .in. I have therefore
81        removed all such uses from the man pages (some were redundant, some could
82        be replaced by .nf/.fi pairs). The 132html script that I use to generate
83        HTML has been updated to handle .nf/.fi and to complain if it encounters
84        .br or .in.
86     4. Updated comments in configure.ac that get placed in config.h.in and also
87        arranged for config.h to be included in the distribution, with the name
88        config.h.generic, for the benefit of those who have to compile without
89        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
91     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
92        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
93        makevp.bat for the current PCRE, using the additional files
94        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
96     6. A Windows user reported a minor discrepancy with test 2, which turned out
97        to be caused by a trailing space on an input line that had got lost in his
98        copy. The trailing space was an accident, so I've just removed it.
100     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
101        that is needed.
103     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
104        as "const" (a) because they are and (b) because it helps the PHP
105        maintainers who have recently made a script to detect big data structures
106        in the php code that should be moved to the .rodata section. I remembered
107        to update Builducptable as well, so it won't revert if ucptable.h is ever
108        re-created.
110     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
111        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
112        order to be able to cut out the UTF-8 tables in the latter when UTF-8
113        support is not required. This saves 1.5-2K of code, which is important in
114        some applications.
116        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
117        so as not to refer to the tables, even though these functions will never be
118        called when UTF-8 support is disabled. Otherwise there are problems with a
119        shared library.
121    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
123        (a) It was defining its arguments as char * instead of void *.
125        (b) It was assuming that all moves were upwards in memory; this was true
126            a long time ago when I wrote it, but is no longer the case.
128        The emulated memove() is provided for those environments that have neither
129        memmove() nor bcopy(). I didn't think anyone used it these days, but that
130        is clearly not the case, as these two bugs were recently reported.
132    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
133        and Detrail to create the HTML documentation, the .txt form of the man
134        pages, and it removes trailing spaces from listed files. It also creates
135        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
136        case, it wraps all the #defines with #ifndefs. This script should be run
137        before "make dist".
139    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
140        with Unicode property support.
142        (a) For a maximizing quantifier, if the two different cases of the
143            character were of different lengths in their UTF-8 codings (there are
144            some cases like this - I found 11), and the matching function had to
145            back up over a mixture of the two cases, it incorrectly assumed they
146            were both the same length.
148        (b) When PCRE was configured to use the heap rather than the stack for
149            recursion during matching, it was not correctly preserving the data for
150            the other case of a UTF-8 character when checking ahead for a match
151            while processing a minimizing repeat. If the check also involved
152            matching a wide character, but failed, corruption could cause an
153            erroneous result when trying to check for a repeat of the original
154            character.
156    13. Some tidying changes to the testing mechanism:
158        (a) The RunTest script now detects the internal link size and whether there
159            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
160            values substituted by "configure". (The RunGrepTest script already did
161            this for UTF-8.) The configure.ac script no longer substitutes the
162            relevant variables.
164        (b) The debugging options /B and /D in pcretest show the compiled bytecode
165            with length and offset values. This means that the output is different
166            for different internal link sizes. Test 2 is skipped for link sizes
167            other than 2 because of this, bypassing the problem. Unfortunately,
168            there was also a test in test 3 (the locale tests) that used /B and
169            failed for link sizes other than 2. Rather than cut the whole test out,
170            I have added a new /Z option to pcretest that replaces the length and
171            offset values with spaces. This is now used to make test 3 independent
172            of link size. (Test 2 will be tidied up later.)
174    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
175        segmentation fault instead of returning the appropriate error message.
177    15. In multiline mode when the newline sequence was set to "any", the pattern
178        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
179        This doesn't seem right; it now treats the CRLF combination as the line
180        ending, and so does not match in that case. It's only a pattern such as ^$
181        that would hit this one: something like ^ABC$ would have failed after \r
182        and then tried again after \r\n.
184    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
185        in an attempt to make files that differ only in their line terminators
186        compare equal. This works on Linux.
188    17. Under certain error circumstances pcregrep might try to free random memory
189        as it exited. This is now fixed, thanks to valgrind.
191    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
192        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
193        was because its rules for how to advance for /g after matching an empty
194        string at the end of a line did not allow for this case. They now check for
195        it specially.
197    20. pcretest is supposed to handle patterns and data of any length, by
198        extending its buffers when necessary. It was getting this wrong when the
199        buffer for a data line had to be extended.
201    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
202        CRLF as a newline sequence.
204    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
205        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
206        I have nevertheless tidied it up.
208    23. Added some casts to kill warnings from HP-UX ia64 compiler.
210    24. Added a man page for pcre-config.
213    Version 7.0 19-Dec-06
214    ---------------------
216     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
217        moving to gcc 4.1.1.
219     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
220        sys/time.h, which is documented as needed for this function. It doesn't
221        seem to matter on Linux, but it showed up on some releases of OS X.
223     3. It seems that there are systems where bytes whose values are greater than
224        127 match isprint() in the "C" locale. The "C" locale should be the
225        default when a C program starts up. In most systems, only ASCII printing
226        characters match isprint(). This difference caused the output from pcretest
227        to vary, making some of the tests fail. I have changed pcretest so that:
229        (a) When it is outputting text in the compiled version of a pattern, bytes
230            other than 32-126 are always shown as hex escapes.
232        (b) When it is outputting text that is a matched part of a subject string,
233            it does the same, unless a different locale has been set for the match
234            (using the /L modifier). In this case, it uses isprint() to decide.
236     4. Fixed a major bug that caused incorrect computation of the amount of memory
237        required for a compiled pattern when options that changed within the
238        pattern affected the logic of the preliminary scan that determines the
239        length. The relevant options are -x, and -i in UTF-8 mode. The result was
240        that the computed length was too small. The symptoms of this bug were
241        either the PCRE error "internal error: code overflow" from pcre_compile(),
242        or a glibc crash with a message such as "pcretest: free(): invalid next
243        size (fast)". Examples of patterns that provoked this bug (shown in
244        pcretest format) are:
246          /(?-x: )/x
247          /(?x)(?-x: \s*#\s*)/
248          /((?i)[\x{c0}])/8
249          /(?i:[\x{c0}])/8
251        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
252        is now done differently.
254     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
255        wrapper classes; (b) implement a new function in the C++ scanner that is
256        more efficient than the old way of doing things because it avoids levels of
257        recursion in the regex matching; (c) add a paragraph to the documentation
258        for the FullMatch() function.
260     6. The escape sequence \n was being treated as whatever was defined as
261        "newline". Not only was this contrary to the documentation, which states
262        that \n is character 10 (hex 0A), but it also went horribly wrong when
263        "newline" was defined as CRLF. This has been fixed.
265     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
266        was being set to -1 for the "end of line" case (supposedly a value that no
267        character can have). Though this value is never used (the check for end of
268        line is "zero bytes in current character"), it caused compiler complaints.
269        I've changed it to 0xffffffff.
271     8. In pcre_version.c, the version string was being built by a sequence of
272        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
273        string (as it is for production releases) called a macro with an empty
274        argument. The C standard says the result of this is undefined. The gcc
275        compiler treats it as an empty string (which was what was wanted) but it is
276        reported that Visual C gives an error. The source has been hacked around to
277        avoid this problem.
279     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
280        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
281        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
282        of them did).
284    10. Originally, pcretest opened its input and output without "b"; then I was
285        told that "b" was needed in some environments, so it was added for release
286        5.0 to both the input and output. (It makes no difference on Unix-like
287        systems.) Later I was told that it is wrong for the input on Windows. I've
288        now abstracted the modes into two macros, to make it easier to fiddle with
289        them, and removed "b" from the input mode under Windows.
291    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
293    12. Added -help and --help to pcretest as an official way of being reminded
294        of the options.
296    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
297        and pcrecpp.cc because they annoy compilers at high warning levels.
299    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
301    15. Fixed an occurrence of == in configure.ac that should have been = (shell
302        scripts are not C programs :-) and which was not noticed because it works
303        on Linux.
305    16. pcretest is supposed to handle any length of pattern and data line (as one
306        line or as a continued sequence of lines) by extending its input buffer if
307        necessary. This feature was broken for very long pattern lines, leading to
308        a string of junk being passed to pcre_compile() if the pattern was longer
309        than about 50K.
311    17. I have done a major re-factoring of the way pcre_compile() computes the
312        amount of memory needed for a compiled pattern. Previously, there was code
313        that made a preliminary scan of the pattern in order to do this. That was
314        OK when PCRE was new, but as the facilities have expanded, it has become
315        harder and harder to keep it in step with the real compile phase, and there
316        have been a number of bugs (see for example, 4 above). I have now found a
317        cunning way of running the real compile function in a "fake" mode that
318        enables it to compute how much memory it would need, while actually only
319        ever using a few hundred bytes of working memory and without too many
320        tests of the mode. This should make future maintenance and development
321        easier. A side effect of this work is that the limit of 200 on the nesting
322        depth of parentheses has been removed (though this was never a serious
323        limitation, I suspect). However, there is a downside: pcre_compile() now
324        runs more slowly than before (30% or more, depending on the pattern). I
325        hope this isn't a big issue. There is no effect on runtime performance.
327    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
328        newline (only possible for the last line of a file) and it was a
329        pattern that set a locale (followed by /Lsomething), pcretest crashed.
331    19. Added additional timing features to pcretest. (1) The -tm option now times
332        matching only, not compiling. (2) Both -t and -tm can be followed, as a
333        separate command line item, by a number that specifies the number of
334        repeats to use when timing. The default is 50000; this gives better
335        precision, but takes uncomfortably long for very large patterns.
337    20. Extended pcre_study() to be more clever in cases where a branch of a
338        subpattern has no definite first character. For example, (a*|b*)[cd] would
339        previously give no result from pcre_study(). Now it recognizes that the
340        first character must be a, b, c, or d.
342    21. There was an incorrect error "recursive call could loop indefinitely" if
343        a subpattern (or the entire pattern) that was being tested for matching an
344        empty string contained only one non-empty item after a nested subpattern.
345        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
346        incorrectly, because the \d was being skipped in the check.
348    22. The pcretest program now has a new pattern option /B and a command line
349        option -b, which is equivalent to adding /B to every pattern. This causes
350        it to show the compiled bytecode, without the additional information that
351        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
352        is the same as /B/I).
354    23. A new optimization is now able automatically to treat some sequences such
355        as a*b as a*+b. More specifically, if something simple (such as a character
356        or a simple class like \d) has an unlimited quantifier, and is followed by
357        something that cannot possibly match the quantified thing, the quantifier
358        is automatically "possessified".
360    24. A recursive reference to a subpattern whose number was greater than 39
361        went wrong under certain circumstances in UTF-8 mode. This bug could also
362        have affected the operation of pcre_study().
364    25. Realized that a little bit of performance could be had by replacing
365        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
367    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
369    27. Possessive quantifiers such as a++ were previously implemented by turning
370        them into atomic groups such as ($>a+). Now they have their own opcodes,
371        which improves performance. This includes the automatically created ones
372        from 23 above.
374    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
375        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
376        the first matched character to be a colon. This applied both to named and
377        numbered groups.
379    29. The ucpinternal.h header file was missing its idempotency #ifdef.
381    30. I was sent a "project" file called libpcre.a.dev which I understand makes
382        building PCRE on Windows easier, so I have included it in the distribution.
384    31. There is now a check in pcretest against a ridiculously large number being
385        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
386        loop, the loop is abandoned.
388    32. Forward references to subpatterns in conditions such as (?(2)...) where
389        subpattern 2 is defined later cause pcre_compile() to search forwards in
390        the pattern for the relevant set of parentheses. This search went wrong
391        when there were unescaped parentheses in a character class, parentheses
392        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
394    33. "Subroutine" calls and backreferences were previously restricted to
395        referencing subpatterns earlier in the regex. This restriction has now
396        been removed.
398    34. Added a number of extra features that are going to be in Perl 5.10. On the
399        whole, these are just syntactic alternatives for features that PCRE had
400        previously implemented using the Python syntax or my own invention. The
401        other formats are all retained for compatibility.
403        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
404            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
405            also .NET compatible.
407        (b) A recursion or subroutine call to a named group can now be defined as
408            (?&name) as well as (?P>name).
410        (c) A backreference to a named group can now be defined as \k<name> or
411            \k'name' as well as (?P=name). The new forms, as well as being in Perl
412            5.10, are also .NET compatible.
414        (d) A conditional reference to a named group can now use the syntax
415            (?(<name>) or (?('name') as well as (?(name).
417        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
418            groups (named and numbered) that are never evaluated inline, but can be
419            called as "subroutines" from elsewhere. In effect, the DEFINE condition
420            is always false. There may be only one alternative in such a group.
422        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
423            as the simple (?(R). The condition is true only if the most recent
424            recursion is that of the given number or name. It does not search out
425            through the entire recursion stack.
427        (g) The escape \gN or \g{N} has been added, where N is a positive or
428            negative number, specifying an absolute or relative reference.
430    35. Tidied to get rid of some further signed/unsigned compiler warnings and
431        some "unreachable code" warnings.
433    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
434        things, this adds five new scripts.
436    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
437        There were also incompatibilities regarding the handling of \Q..\E inside
438        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
439        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
441    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
442        matches an empty string, and forcibly breaks the loop. There were bugs in
443        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
444        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
445        separate and independent bugs (that affected different cases) have been
446        fixed.
448    39. Refactored the code to abolish the use of different opcodes for small
449        capturing bracket numbers. This is a tidy that I avoided doing when I
450        removed the limit on the number of capturing brackets for 3.5 back in 2001.
451        The new approach is not only tidier, it makes it possible to reduce the
452        memory needed to fix the previous bug (38).
454    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
455        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
456        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
457        mode.
459    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
460        report.
462    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
463        copy construction and assignment in the C++ wrapper.
465    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
466        couple of bugs that could have given wrong results in the "--newline=crlf"
467        case.
469    44. Added a number of casts and did some reorganization of signed/unsigned int
470        variables following suggestions from Dair Grant. Also renamed the variable
471        "this" as "item" because it is a C++ keyword.
473    45. Arranged for dftables to add
475          #include "pcre_internal.h"
477        to pcre_chartables.c because without it, gcc 4.x may remove the array
478        definition from the final binary if PCRE is built into a static library and
479        dead code stripping is activated.
481    46. For an unanchored pattern, if a match attempt fails at the start of a
482        newline sequence, and the newline setting is CRLF or ANY, and the next two
483        characters are CRLF, advance by two characters instead of one.
486    Version 6.7 04-Jul-06
487    ---------------------
489     1. In order to handle tests when input lines are enormously long, pcretest has
490        been re-factored so that it automatically extends its buffers when
491        necessary. The code is crude, but this _is_ just a test program. The
492        default size has been increased from 32K to 50K.
494     2. The code in pcre_study() was using the value of the re argument before
495        testing it for NULL. (Of course, in any sensible call of the function, it
496        won't be NULL.)
498     3. The memmove() emulation function in pcre_internal.h, which is used on
499        systems that lack both memmove() and bcopy() - that is, hardly ever -
500        was missing a "static" storage class specifier.
502     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
503        containing an extended class (one that cannot be represented by a bitmap
504        because it contains high-valued characters or Unicode property items, e.g.
505        [\pZ]). Almost always one would set UTF-8 mode when processing such a
506        pattern, but PCRE should not loop if you do not (it no longer does).
507        [Detail: two cases were found: (a) a repeated subpattern containing an
508        extended class; (b) a recursive reference to a subpattern that followed a
509        previous extended class. It wasn't skipping over the extended class
510        correctly when UTF-8 mode was not set.]
512     5. A negated single-character class was not being recognized as fixed-length
513        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
514        compile error "lookbehind assertion is not fixed length".
516     6. The RunPerlTest auxiliary script was showing an unexpected difference
517        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
518        write a Perl script that can interpret lines of an input file either as
519        byte characters or as UTF-8, which is what "perltest" was being required to
520        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
521        can't do is switch easily at run time between having the "use utf8;" pragma
522        or not. In the end, I fudged it by using the RunPerlTest script to insert
523        "use utf8;" explicitly for the UTF-8 tests.
525     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
526        the end of the subject string, contrary to the documentation and to what
527        Perl does. This was true of both matching functions. Now it matches only at
528        the start of the subject and immediately after *internal* newlines.
530     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
531        a pointer to an int instead of a pointer to an unsigned long int. This
532        caused problems on 64-bit systems.
534     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
535        instance of the 'standard' template library not being so standard".
537    10. There was no check on the number of named subpatterns nor the maximum
538        length of a subpattern name. The product of these values is used to compute
539        the size of the memory block for a compiled pattern. By supplying a very
540        long subpattern name and a large number of named subpatterns, the size
541        computation could be caused to overflow. This is now prevented by limiting
542        the length of names to 32 characters, and the number of named subpatterns
543        to 10,000.
545    11. Subpatterns that are repeated with specific counts have to be replicated in
546        the compiled pattern. The size of memory for this was computed from the
547        length of the subpattern and the repeat count. The latter is limited to
548        65535, but there was no limit on the former, meaning that integer overflow
549        could in principle occur. The compiled length of a repeated subpattern is
550        now limited to 30,000 bytes in order to prevent this.
552    12. Added the optional facility to have named substrings with the same name.
554    13. Added the ability to use a named substring as a condition, using the
555        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
556        are numbers (not recommended). Forward references are permitted.
558    14. Added forward references in named backreferences (if you see what I mean).
560    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
561        pattern could run off the end of the subject. For example, the pattern
562        "(?s)(.{1,5})"8 did this with the subject "ab".
564    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
565        PCRE_CASELESS was set when matching characters that were quantified with ?
566        or *.
568    17. A character class other than a single negated character that had a minimum
569        but no maximum quantifier - for example [ab]{6,} - was not handled
570        correctly by pce_dfa_exec(). It would match only one character.
572    18. A valid (though odd) pattern that looked like a POSIX character
573        class but used an invalid character after [ (for example [[,abc,]]) caused
574        pcre_compile() to give the error "Failed: internal error: code overflow" or
575        in some cases to crash with a glibc free() error. This could even happen if
576        the pattern terminated after [[ but there just happened to be a sequence of
577        letters, a binary zero, and a closing ] in the memory that followed.
579    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
580        over the years. Originally (before any Unicode support), just the bottom 8
581        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
582        output from "man perlunicode" includes this:
584          The regular expression compiler produces polymorphic opcodes.  That
585          is, the pattern adapts to the data and automatically switches to
586          the Unicode character scheme when presented with Unicode data--or
587          instead uses a traditional byte scheme when presented with byte
588          data.
590        Sadly, a wide octal escape does not cause a switch, and in a string with
591        no other multibyte characters, these octal escapes are treated as before.
592        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
593        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
594        Unicode string.
596        I have not perpetrated such confusion in PCRE. Up till now, it took just
597        the bottom 8 bits, as in old Perl. I have now made octal escapes with
598        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
599        translate to the appropriate multibyte character.
601    29. Applied some refactoring to reduce the number of warnings from Microsoft
602        and Borland compilers. This has included removing the fudge introduced
603        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
604        a warning about an unused variable.
606    21. PCRE has not included VT (character 0x0b) in the set of whitespace
607        characters since release 4.0, because Perl (from release 5.004) does not.
608        [Or at least, is documented not to: some releases seem to be in conflict
609        with the documentation.] However, when a pattern was studied with
610        pcre_study() and all its branches started with \s, PCRE still included VT
611        as a possible starting character. Of course, this did no harm; it just
612        caused an unnecessary match attempt.
614    22. Removed a now-redundant internal flag bit that recorded the fact that case
615        dependency changed within the pattern. This was once needed for "required
616        byte" processing, but is no longer used. This recovers a now-scarce options
617        bit. Also moved the least significant internal flag bit to the most-
618        significant bit of the word, which was not previously used (hangover from
619        the days when it was an int rather than a uint) to free up another bit for
620        the future.
622    23. Added support for CRLF line endings as well as CR and LF. As well as the
623        default being selectable at build time, it can now be changed at runtime
624        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
625        specify that it is scanning data with non-default line endings.
627    24. Changed the definition of CXXLINK to make it agree with the definition of
628        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
630    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
631        recursions. This makes a big different to stack usage for some patterns.
633    26. If a subpattern containing a named recursion or subroutine reference such
634        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
635        the space required for the compiled pattern went wrong and gave too small a
636        value. Depending on the environment, this could lead to "Failed: internal
637        error: code overflow at offset 49" or "glibc detected double free or
638        corruption" errors.
640    27. Applied patches from Google (a) to support the new newline modes and (b) to
641        advance over multibyte UTF-8 characters in GlobalReplace.
643    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
644        difference for some implementation of PCRE in some Windows version.
646    29. Added some extra testing facilities to pcretest:
648        \q<number>   in a data line sets the "match limit" value
649        \Q<number>   in a data line sets the "match recursion limt" value
650        -S <number>  sets the stack size, where <number> is in megabytes
652        The -S option isn't available for Windows.
655    Version 6.6 06-Feb-06
656    ---------------------
658     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
659        in pcreposix.h. I have copied the definition from pcre.h.
661     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
662        because pcre.h is no longer a built file.
664     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
665        not normally included in the compiled code.
668    Version 6.5 01-Feb-06
669    ---------------------
671     1. When using the partial match feature with pcre_dfa_exec(), it was not
672        anchoring the second and subsequent partial matches at the new starting
673        point. This could lead to incorrect results. For example, with the pattern
674        /1234/, partially matching against "123" and then "a4" gave a match.
676     2. Changes to pcregrep:
678        (a) All non-match returns from pcre_exec() were being treated as failures
679            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
680            error message is output. Some extra information is given for the
681            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
682            probably the only errors that are likely to be caused by users (by
683            specifying a regex that has nested indefinite repeats, for instance).
684            If there are more than 20 of these errors, pcregrep is abandoned.
686        (b) A binary zero was treated as data while matching, but terminated the
687            output line if it was written out. This has been fixed: binary zeroes
688            are now no different to any other data bytes.
690        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
691            used to set a locale for matching. The --locale=xxxx long option has
692            been added (no short equivalent) to specify a locale explicitly on the
693            pcregrep command, overriding the environment variables.
695        (d) When -B was used with -n, some line numbers in the output were one less
696            than they should have been.
698        (e) Added the -o (--only-matching) option.
700        (f) If -A or -C was used with -c (count only), some lines of context were
701            accidentally printed for the final match.
703        (g) Added the -H (--with-filename) option.
705        (h) The combination of options -rh failed to suppress file names for files
706            that were found from directory arguments.
708        (i) Added the -D (--devices) and -d (--directories) options.
710        (j) Added the -F (--fixed-strings) option.
712        (k) Allow "-" to be used as a file name for -f as well as for a data file.
714        (l) Added the --colo(u)r option.
716        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
717            is not present by default.
719     3. A nasty bug was discovered in the handling of recursive patterns, that is,
720        items such as (?R) or (?1), when the recursion could match a number of
721        alternatives. If it matched one of the alternatives, but subsequently,
722        outside the recursion, there was a failure, the code tried to back up into
723        the recursion. However, because of the way PCRE is implemented, this is not
724        possible, and the result was an incorrect result from the match.
726        In order to prevent this happening, the specification of recursion has
727        been changed so that all such subpatterns are automatically treated as
728        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
730     4. I had overlooked the fact that, in some locales, there are characters for
731        which isalpha() is true but neither isupper() nor islower() are true. In
732        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
733        and ordfeminine) are like this. This affected the treatment of \w and \W
734        when they appeared in character classes, but not when they appeared outside
735        a character class. The bit map for "word" characters is now created
736        separately from the results of isalnum() instead of just taking it from the
737        upper, lower, and digit maps. (Plus the underscore character, of course.)
739     5. The above bug also affected the handling of POSIX character classes such as
740        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
741        permanent tables. Instead, the bit maps for such a class were previously
742        created as the appropriate unions of the upper, lower, and digit bitmaps.
743        Now they are created by subtraction from the [[:word:]] class, which has
744        its own bitmap.
746     6. The [[:blank:]] character class matches horizontal, but not vertical space.
747        It is created by subtracting the vertical space characters (\x09, \x0a,
748        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
749        subtraction was done in the overall bitmap for a character class, meaning
750        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
751        be recognized. This bug has been fixed.
753     7. Patches from the folks at Google:
755          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
756          real life, but is still worth protecting against".
758          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
759          regular expressions".
761          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
762          have it.
764          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
765          "configure" and the latter not, in order to fix a problem somebody had
766          with compiling the Arg class on HP-UX.
768          (e) Improve the error-handling of the C++ wrapper a little bit.
770          (f) New tests for checking recursion limiting.
772     8. The pcre_memmove() function, which is used only if the environment does not
773        have a standard memmove() function (and is therefore rarely compiled),
774        contained two bugs: (a) use of int instead of size_t, and (b) it was not
775        returning a result (though PCRE never actually uses the result).
777     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
778        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
779        returned instead of calling malloc() with an overflowing number that would
780        most likely cause subsequent chaos.
782    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
784    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
785        with this option is matched, the nmatch and pmatch options of regexec() are
786        ignored.
788    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
789        provided in case anyone wants to the the POSIX interface with UTF-8
790        strings.
792    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
793        C++ linking (needed for some HP-UX environments).
795    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
796        (unused parameter) and in the pcre_printint() function (omitted "default"
797        switch label when the default is to do nothing).
799    15. Added some code to make it possible, when PCRE is compiled as a C++
800        library, to replace subject pointers for pcre_exec() with a smart pointer
801        class, thus making it possible to process discontinuous strings.
803    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
804        much the same function. They were added by different people who were trying
805        to make PCRE easy to compile on non-Unix systems. It has been suggested
806        that PCRE_EXPORT be abolished now that there is more automatic apparatus
807        for compiling on Windows systems. I have therefore replaced it with
808        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
809        defaults to "extern" for C or "extern C" for C++, which works fine on
810        Unix-like systems. It is now possible to override the value of PCRE_DATA_
811        SCOPE with something explicit in config.h. In addition:
813        (a) pcreposix.h still had just "extern" instead of either of these macros;
814            I have replaced it with PCRE_DATA_SCOPE.
816        (b) Functions such as _pcre_xclass(), which are internal to the library,
817            but external in the C sense, all had PCRE_EXPORT in their definitions.
818            This is apparently wrong for the Windows case, so I have removed it.
819            (It makes no difference on Unix-like systems.)
821    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
822        of recursive calls to match(). This is different to MATCH_LIMIT because
823        that limits the total number of calls to match(), not all of which increase
824        the depth of recursion. Limiting the recursion depth limits the amount of
825        stack (or heap if NO_RECURSE is set) that is used. The default can be set
826        when PCRE is compiled, and changed at run time. A patch from Google adds
827        this functionality to the C++ interface.
829    18. Changes to the handling of Unicode character properties:
831        (a) Updated the table to Unicode 4.1.0.
833        (b) Recognize characters that are not in the table as "Cn" (undefined).
835        (c) I revised the way the table is implemented to a much improved format
836            which includes recognition of ranges. It now supports the ranges that
837            are defined in UnicodeData.txt, and it also amalgamates other
838            characters into ranges. This has reduced the number of entries in the
839            table from around 16,000 to around 3,000, thus reducing its size
840            considerably. I realized I did not need to use a tree structure after
841            all - a binary chop search is just as efficient. Having reduced the
842            number of entries, I extended their size from 6 bytes to 8 bytes to
843            allow for more data.
845        (d) Added support for Unicode script names via properties such as \p{Han}.
847    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
848        matching that character.
850    20. When matching a repeated Unicode property with a minimum greater than zero,
851        (for example \pL{2,}), PCRE could look past the end of the subject if it
852        reached it while seeking the minimum number of characters. This could
853        happen only if some of the characters were more than one byte long, because
854        there is a check for at least the minimum number of bytes.
856    21. Refactored the implementation of \p and \P so as to be more general, to
857        allow for more different types of property in future. This has changed the
858        compiled form incompatibly. Anybody with saved compiled patterns that use
859        \p or \P will have to recompile them.
861    22. Added "Any" and "L&" to the supported property types.
863    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
864        but give a compile time error if the value is greater than 0xff.
866    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
867        accidentally not being installed or uninstalled.
869    25. The pcre.h file was built from pcre.h.in, but the only changes that were
870        made were to insert the current release number. This seemed silly, because
871        it made things harder for people building PCRE on systems that don't run
872        "configure". I have turned pcre.h into a distributed file, no longer built
873        by "configure", with the version identification directly included. There is
874        no longer a pcre.h.in file.
876        However, this change necessitated a change to the pcre-config script as
877        well. It is built from pcre-config.in, and one of the substitutions was the
878        release number. I have updated configure.ac so that ./configure now finds
879        the release number by grepping pcre.h.
881    26. Added the ability to run the tests under valgrind.
884    Version 6.4 05-Sep-05
885    ---------------------
887     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
888        "--" to be printed when multiple files were scanned, even when none of the
889        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
890        consider it to be a bug, and have restored the previous behaviour.
892     2. A couple of code tidies to get rid of compiler warnings.
894     3. The pcretest program used to cheat by referring to symbols in the library
895        whose names begin with _pcre_. These are internal symbols that are not
896        really supposed to be visible externally, and in some environments it is
897        possible to suppress them. The cheating is now confined to including
898        certain files from the library's source, which is a bit cleaner.
900     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
901        file's purpose clearer.
903     5. Reorganized pcre_ucp_findchar().
906    Version 6.3 15-Aug-05
907    ---------------------
909     1. The file libpcre.pc.in did not have general read permission in the tarball.
911     2. There were some problems when building without C++ support:
913        (a) If C++ support was not built, "make install" and "make test" still
914            tried to test it.
916        (b) There were problems when the value of CXX was explicitly set. Some
917            changes have been made to try to fix these, and ...
919        (c) --disable-cpp can now be used to explicitly disable C++ support.
921        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
922            backslash in a target when C++ was disabled. This confuses some
923            versions of "make", apparently. Using an intermediate variable solves
924            this. (Same for CPP_LOBJ.)
926     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
927        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
928        necessary on certain architectures.
930     4. Added a setting of -export-symbols-regex to the link command to remove
931        those symbols that are exported in the C sense, but actually are local
932        within the library, and not documented. Their names all begin with
933        "_pcre_". This is not a perfect job, because (a) we have to except some
934        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
935        available (and never for static libraries). I have made a note to try to
936        find a way round (a) in the future.
939    Version 6.2 01-Aug-05
940    ---------------------
942     1. There was no test for integer overflow of quantifier values. A construction
943        such as {1111111111111111} would give undefined results. What is worse, if
944        a minimum quantifier for a parenthesized subpattern overflowed and became
945        negative, the calculation of the memory size went wrong. This could have
946        led to memory overwriting.
948     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
950     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
951        operating environments where this matters.
953     4. Applied Giuseppe Maxia's patch to add additional features for controlling
954        PCRE options from within the C++ wrapper.
956     5. Named capturing subpatterns were not being correctly counted when a pattern
957        was compiled. This caused two problems: (a) If there were more than 100
958        such subpatterns, the calculation of the memory needed for the whole
959        compiled pattern went wrong, leading to an overflow error. (b) Numerical
960        back references of the form \12, where the number was greater than 9, were
961        not recognized as back references, even though there were sufficient
962        previous subpatterns.
964     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
965        versions of gcc, e.g. 2.95.4.
968    Version 6.1 21-Jun-05
969    ---------------------
971     1. There was one reference to the variable "posix" in pcretest.c that was not
972        surrounded by "#if !defined NOPOSIX".
974     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
975        the cross-check on the old pcre_info() function, for the benefit of the
976        cut-down version of PCRE that is currently imported into Exim.
978     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
979        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
980        patterns that start (?i) but I don't think that matters. The use of (?i) is
981        just an example; this all applies to the other options as well.
983     4. Since libtool seems to echo the compile commands it is issuing, the output
984        from "make" can be reduced a bit by putting "@" in front of each libtool
985        compile command.
987     5. Patch from the folks at Google for configure.in to be a bit more thorough
988        in checking for a suitable C++ installation before trying to compile the
989        C++ stuff. This should fix a reported problem when a compiler was present,
990        but no suitable headers.
992     6. The man pages all had just "PCRE" as their title. I have changed them to
993        be the relevant file name. I have also arranged that these names are
994        retained in the file doc/pcre.txt, which is a concatenation in text format
995        of all the man pages except the little individual ones for each function.
997     7. The NON-UNIX-USE file had not been updated for the different set of source
998        files that come with release 6. I also added a few comments about the C++
999        wrapper.
1002    Version 6.0 07-Jun-05
1003    ---------------------
1005     1. Some minor internal re-organization to help with my DFA experiments.
1007     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
1008        didn't matter for the library itself when fully configured, but did matter
1009        when compiling without UCP support, or within Exim, where the ucp files are
1010        not imported.
1012     3. Refactoring of the library code to split up the various functions into
1013        different source modules. The addition of the new DFA matching code (see
1014        below) to a single monolithic source would have made it really too
1015        unwieldy, quite apart from causing all the code to be include in a
1016        statically linked application, when only some functions are used. This is
1017        relevant even without the DFA addition now that patterns can be compiled in
1018        one application and matched in another.
1020        The downside of splitting up is that there have to be some external
1021        functions and data tables that are used internally in different modules of
1022        the library but which are not part of the API. These have all had their
1023        names changed to start with "_pcre_" so that they are unlikely to clash
1024        with other external names.
1026     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
1027        a different (DFA) algorithm. Although it is slower than the original
1028        function, it does have some advantages for certain types of matching
1029        problem.
1031     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
1032        including restarting after a partial match.
1034     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
1035        defined when compiling for Windows was sent to me. I have put it into the
1036        code, though I have no means of testing or verifying it.
1038     7. Added the pcre_refcount() auxiliary function.
1040     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
1041        match before or at the first newline in the subject string. In pcretest,
1042        the /f option on a pattern can be used to set this.
1044     9. A repeated \w when used in UTF-8 mode with characters greater than 256
1045        would behave wrongly. This has been present in PCRE since release 4.0.
1047    10. A number of changes to the pcregrep command:
1049        (a) Refactored how -x works; insert ^(...)$ instead of setting
1050            PCRE_ANCHORED and checking the length, in preparation for adding
1051            something similar for -w.
1053        (b) Added the -w (match as a word) option.
1055        (c) Refactored the way lines are read and buffered so as to have more
1056            than one at a time available.
1058        (d) Implemented a pcregrep test script.
1060        (e) Added the -M (multiline match) option. This allows patterns to match
1061            over several lines of the subject. The buffering ensures that at least
1062            8K, or the rest of the document (whichever is the shorter) is available
1063            for matching (and similarly the previous 8K for lookbehind assertions).
1065        (f) Changed the --help output so that it now says
1067              -w, --word-regex(p)
1069            instead of two lines, one with "regex" and the other with "regexp"
1070            because that confused at least one person since the short forms are the
1071            same. (This required a bit of code, as the output is generated
1072            automatically from a table. It wasn't just a text change.)
1074        (g) -- can be used to terminate pcregrep options if the next thing isn't an
1075            option but starts with a hyphen. Could be a pattern or a path name
1076            starting with a hyphen, for instance.
1078        (h) "-" can be given as a file name to represent stdin.
1080        (i) When file names are being printed, "(standard input)" is used for
1081            the standard input, for compatibility with GNU grep. Previously
1082            "<stdin>" was used.
1084        (j) The option --label=xxx can be used to supply a name to be used for
1085            stdin when file names are being printed. There is no short form.
1087        (k) Re-factored the options decoding logic because we are going to add
1088            two more options that take data. Such options can now be given in four
1089            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
1091        (l) Added the -A, -B, and -C options for requesting that lines of context
1092            around matches be printed.
1094        (m) Added the -L option to print the names of files that do not contain
1095            any matching lines, that is, the complement of -l.
1097        (n) The return code is 2 if any file cannot be opened, but pcregrep does
1098            continue to scan other files.
1100        (o) The -s option was incorrectly implemented. For compatibility with other
1101            greps, it now suppresses the error message for a non-existent or non-
1102            accessible file (but not the return code). There is a new option called
1103            -q that suppresses the output of matching lines, which was what -s was
1104            previously doing.
1106        (p) Added --include and --exclude options to specify files for inclusion
1107            and exclusion when recursing.
1109    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
1110        Hopefully, it now does.
1112    12. Missing cast in pcre_study().
1114    13. Added an "uninstall" target to the makefile.
1116    14. Replaced "extern" in the function prototypes in Makefile.in with
1117        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
1118        world, but is set differently for Windows.
1120    15. Added a second compiling function called pcre_compile2(). The only
1121        difference is that it has an extra argument, which is a pointer to an
1122        integer error code. When there is a compile-time failure, this is set
1123        non-zero, in addition to the error test pointer being set to point to an
1124        error message. The new argument may be NULL if no error number is required
1125        (but then you may as well call pcre_compile(), which is now just a
1126        wrapper). This facility is provided because some applications need a
1127        numeric error indication, but it has also enabled me to tidy up the way
1128        compile-time errors are handled in the POSIX wrapper.
1130    16. Added VPATH=.libs to the makefile; this should help when building with one
1131        prefix path and installing with another. (Or so I'm told by someone who
1132        knows more about this stuff than I do.)
1134    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
1135        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
1136        match everything, including newlines. This is not POSIX-compatible, but
1137        somebody wanted the feature. From pcretest it can be activated by using
1138        both the P and the s flags.
1140    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
1142    19. libpcre.pc was being incorrectly installed as executable.
1144    20. A couple of places in pcretest check for end-of-line by looking for '\n';
1145        it now also looks for '\r' so that it will work unmodified on Windows.
1147    21. Added Google's contributed C++ wrapper to the distribution.
1149    22. Added some untidy missing memory free() calls in pcretest, to keep
1150        Electric Fence happy when testing.
1154    Version 5.0 13-Sep-04
1155    ---------------------
1157     1. Internal change: literal characters are no longer packed up into items
1158        containing multiple characters in a single byte-string. Each character
1159        is now matched using a separate opcode. However, there may be more than one
1160        byte in the character in UTF-8 mode.
1162     2. The pcre_callout_block structure has two new fields: pattern_position and
1163        next_item_length. These contain the offset in the pattern to the next match
1164        item, and its length, respectively.
1166     3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
1167        insertion of callouts before each pattern item. Added the /C option to
1168        pcretest to make use of this.
1170     4. On the advice of a Windows user, the lines
1172          #if defined(_WIN32) || defined(WIN32)
1173          _setmode( _fileno( stdout ), 0x8000 );
1174          #endif  /* defined(_WIN32) || defined(WIN32) */
1176        have been added to the source of pcretest. This apparently does useful
1177        magic in relation to line terminators.
1179     5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
1180        for the benefit of those environments where the "b" makes a difference.
1182     6. The icc compiler has the same options as gcc, but "configure" doesn't seem
1183        to know about it. I have put a hack into configure.in that adds in code
1184        to set GCC=yes if CC=icc. This seems to end up at a point in the
1185        generated configure script that is early enough to affect the setting of
1186        compiler options, which is what is needed, but I have no means of testing
1187        whether it really works. (The user who reported this had patched the
1188        generated configure script, which of course I cannot do.)
1190        LATER: After change 22 below (new libtool files), the configure script
1191        seems to know about icc (and also ecc). Therefore, I have commented out
1192        this hack in configure.in.
1194     7. Added support for pkg-config (2 patches were sent in).
1196     8. Negated POSIX character classes that used a combination of internal tables
1197        were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
1198        [[:^ascii]]. Typically, they would match almost any characters. The other
1199        POSIX classes were not broken in this way.
1201     9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
1202        to find the match, as PCRE was deluded into thinking that the match had to
1203        start at the start point or following a newline. The same bug applied to
1204        patterns with negative forward assertions or any backward assertions
1205        preceding ".*" at the start, unless the pattern required a fixed first
1206        character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
1208    10. In UTF-8 mode, when moving forwards in the subject after a failed match
1209        starting at the last subject character, bytes beyond the end of the subject
1210        string were read.
1212    11. Renamed the variable "class" as "classbits" to make life easier for C++
1213        users. (Previously there was a macro definition, but it apparently wasn't
1214        enough.)
1216    12. Added the new field "tables" to the extra data so that tables can be passed
1217        in at exec time, or the internal tables can be re-selected. This allows
1218        a compiled regex to be saved and re-used at a later time by a different
1219        program that might have everything at different addresses.
1221    13. Modified the pcre-config script so that, when run on Solaris, it shows a
1222        -R library as well as a -L library.
1224    14. The debugging options of pcretest (-d on the command line or D on a
1225        pattern) showed incorrect output for anything following an extended class
1226        that contained multibyte characters and which was followed by a quantifier.
1228    15. Added optional support for general category Unicode character properties
1229        via the \p, \P, and \X escapes. Unicode property support implies UTF-8
1230        support. It adds about 90K to the size of the library. The meanings of the
1231        inbuilt class escapes such as \d and \s have NOT been changed.
1233    16. Updated pcredemo.c to include calls to free() to release the memory for the
1234        compiled pattern.
1236    17. The generated file chartables.c was being created in the source directory
1237        instead of in the building directory. This caused the build to fail if the
1238        source directory was different from the building directory, and was
1239        read-only.
1241    18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
1242        file. No doubt somebody will tell me if they don't make sense... Also added
1243        Dan Mooney's comments about building on OpenVMS.
1245    19. Added support for partial matching via the PCRE_PARTIAL option for
1246        pcre_exec() and the \P data escape in pcretest.
1248    20. Extended pcretest with 3 new pattern features:
1250        (i)   A pattern option of the form ">rest-of-line" causes pcretest to
1251              write the compiled pattern to the file whose name is "rest-of-line".
1252              This is a straight binary dump of the data, with the saved pointer to
1253              the character tables forced to be NULL. The study data, if any, is
1254              written too. After writing, pcretest reads a new pattern.
1256        (ii)  If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
1257              compiled pattern from the given file. There must not be any
1258              occurrences of "<" in the file name (pretty unlikely); if there are,
1259              pcretest will instead treat the initial "<" as a pattern delimiter.
1260              After reading in the pattern, pcretest goes on to read data lines as
1261              usual.
1263        (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
1264              and 16-bit fields in a compiled pattern, to simulate a pattern that
1265              was compiled on a host of opposite endianness.
1267    21. The pcre-exec() function can now cope with patterns that were compiled on
1268        hosts of opposite endianness, with this restriction:
1270          As for any compiled expression that is saved and used later, the tables
1271          pointer field cannot be preserved; the extra_data field in the arguments
1272          to pcre_exec() should be used to pass in a tables address if a value
1273          other than the default internal tables were used at compile time.
1275    22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
1276        now diagnosed as an error. Previously, most of the time, a negative number
1277        would have been treated as zero, but if in addition "ovector" was passed as
1278        NULL, a crash could occur.
1280    23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
1281        new versions from the libtool 1.5 distribution (the last one is a copy of
1282        a file called libtool.m4). This seems to have fixed the need to patch
1283        "configure" to support Darwin 1.3 (which I used to do). However, I still
1284        had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
1285        workstation).
1287    24. Changed the PCRE licence to be the more standard "BSD" licence.
1290    Version 4.5 01-Dec-03
1291    ---------------------
1293     1. There has been some re-arrangement of the code for the match() function so
1294        that it can be compiled in a version that does not call itself recursively.
1295        Instead, it keeps those local variables that need separate instances for
1296        each "recursion" in a frame on the heap, and gets/frees frames whenever it
1297        needs to "recurse". Keeping track of where control must go is done by means
1298        of setjmp/longjmp. The whole thing is implemented by a set of macros that
1299        hide most of the details from the main code, and operates only if
1300        NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
1301        "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
1302        operating.
1304        To make it easier for callers to provide specially tailored get/free
1305        functions for this usage, two new functions, pcre_stack_malloc, and
1306        pcre_stack_free, are used. They are always called in strict stacking order,
1307        and the size of block requested is always the same.
1309        The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
1310        PCRE has been compiled to use the stack or the heap for recursion. The
1311        -C option of pcretest uses this to show which version is compiled.
1313        A new data escape \S, is added to pcretest; it causes the amounts of store
1314        obtained and freed by both kinds of malloc/free at match time to be added
1315        to the output.
1317     2. Changed the locale test to use "fr_FR" instead of "fr" because that's
1318        what's available on my current Linux desktop machine.
1320     3. When matching a UTF-8 string, the test for a valid string at the start has
1321        been extended. If start_offset is not zero, PCRE now checks that it points
1322        to a byte that is the start of a UTF-8 character. If not, it returns
1323        PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
1324        this is necessary because there may be backward assertions in the pattern.
1325        When matching the same subject several times, it may save resources to use
1326        PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
1328     4. The code for checking the validity of UTF-8 strings has been tightened so
1329        that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
1330        containing "overlong sequences".
1332     5. Fixed a bug (appearing twice) that I could not find any way of exploiting!
1333        I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
1334        should have been "&", but it just so happened that all the cases this let
1335        through by mistake were picked up later in the function.
1337     6. I had used a variable called "isblank" - this is a C99 function, causing
1338        some compilers to warn. To avoid this, I renamed it (as "blankclass").
1340     7. Cosmetic: (a) only output another newline at the end of pcretest if it is
1341        prompting; (b) run "./pcretest /dev/null" at the start of the test script
1342        so the version is shown; (c) stop "make test" echoing "./RunTest".
1344     8. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
1346     9. The prototype for memmove() for systems that don't have it was using
1347        size_t, but the inclusion of the header that defines size_t was later. I've
1348        moved the #includes for the C headers earlier to avoid this.
1350    10. Added some adjustments to the code to make it easier to compiler on certain
1351        special systems:
1353          (a) Some "const" qualifiers were missing.
1354          (b) Added the macro EXPORT before all exported functions; by default this
1355              is defined to be empty.
1356          (c) Changed the dftables auxiliary program (that builds chartables.c) so
1357              that it reads its output file name as an argument instead of writing
1358              to the standard output and assuming this can be redirected.
1360    11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
1361        class containing characters with values greater than 255, PCRE compilation
1362        went into a loop.
1364    12. A recursive reference to a subpattern that was within another subpattern
1365        that had a minimum quantifier of zero caused PCRE to crash. For example,
1366        (x(y(?2))z)? provoked this bug with a subject that got as far as the
1367        recursion. If the recursively-called subpattern itself had a zero repeat,
1368        that was OK.
1370    13. In pcretest, the buffer for reading a data line was set at 30K, but the
1371        buffer into which it was copied (for escape processing) was still set at
1372        1024, so long lines caused crashes.
1374    14. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
1375        "internal error: code overflow...". This applied to any character class
1376        that was followed by a possessive quantifier.
1378    15. Modified the Makefile to add libpcre.la as a prerequisite for
1379        libpcreposix.la because I was told this is needed for a parallel build to
1380        work.
1382    16. If a pattern that contained .* following optional items at the start was
1383        studied, the wrong optimizing data was generated, leading to matching
1384        errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
1385        matching string must start with a or b or c. The correct conclusion for
1386        this pattern is that a match can start with any character.
1389    Version 4.4 13-Aug-03
1390    ---------------------
1392     1. In UTF-8 mode, a character class containing characters with values between
1393        127 and 255 was not handled correctly if the compiled pattern was studied.
1394        In fixing this, I have also improved the studying algorithm for such
1395        classes (slightly).
1397     2. Three internal functions had redundant arguments passed to them. Removal
1398        might give a very teeny performance improvement.
1400     3. Documentation bug: the value of the capture_top field in a callout is *one
1401        more than* the number of the hightest numbered captured substring.
1403     4. The Makefile linked pcretest and pcregrep with -lpcre, which could result
1404        in incorrectly linking with a previously installed version. They now link
1405        explicitly with libpcre.la.
1407     5. configure.in no longer needs to recognize Cygwin specially.
1409     6. A problem in pcre.in for Windows platforms is fixed.
1411     7. If a pattern was successfully studied, and the -d (or /D) flag was given to
1412        pcretest, it used to include the size of the study block as part of its
1413        output. Unfortunately, the structure contains a field that has a different
1414        size on different hardware architectures. This meant that the tests that
1415        showed this size failed. As the block is currently always of a fixed size,
1416        this information isn't actually particularly useful in pcretest output, so
1417        I have just removed it.
1419     8. Three pre-processor statements accidentally did not start in column 1.
1420        Sadly, there are *still* compilers around that complain, even though
1421        standard C has not required this for well over a decade. Sigh.
1423     9. In pcretest, the code for checking callouts passed small integers in the
1424        callout_data field, which is a void * field. However, some picky compilers
1425        complained about the casts involved for this on 64-bit systems. Now
1426        pcretest passes the address of the small integer instead, which should get
1427        rid of the warnings.
1429    10. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
1430        both compile and run time, and gives an error if an invalid UTF-8 sequence
1431        is found. There is a option for disabling this check in cases where the
1432        string is known to be correct and/or the maximum performance is wanted.
1434    11. In response to a bug report, I changed one line in Makefile.in from
1436            -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
1437        to
1438            -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \
1440        to look similar to other lines, but I have no way of telling whether this
1441        is the right thing to do, as I do not use Windows. No doubt I'll get told
1442        if it's wrong...
1445  Version 4.3 21-May-03  Version 4.3 21-May-03
1446  ---------------------  ---------------------

Removed from v.69  
changed lines
  Added in v.175

  ViewVC Help
Powered by ViewVC 1.1.5