ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 83 by nigel, Sat Feb 24 21:41:06 2007 UTC revision 134 by ph10, Mon Mar 26 16:00:17 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 7.1 12-Mar-07
5    ---------------------
7     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
8        that is more "standard", making use of automake and other Autotools. There
9        is some re-arrangement of the files and adjustment of comments consequent
10        on this.
12     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
13        for recursive directory scanning broke on some systems because the files
14        are not scanned in any specific order and on different systems the order
15        was different. A call to "sort" has been inserted into RunGrepTest for the
16        approprate test as a short-term fix. In the longer term there may be an
17        alternative.
19     3. I had an email from Eric Raymond about problems translating some of PCRE's
20        man pages to HTML (despite the fact that I distribute HTML pages, some
21        people do their own conversions for various reasons). The problems
22        concerned the use of low-level troff macros .br and .in. I have therefore
23        removed all such uses from the man pages (some were redundant, some could
24        be replaced by .nf/.fi pairs). The 132html script that I use to generate
25        HTML has been updated to handle .nf/.fi and to complain if it encounters
26        .br or .in.
28     4. Updated comments in configure.ac that get placed in config.h.in and also
29        arranged for config.h to be included in the distribution, with the name
30        config.h.generic, for the benefit of those who have to compile without
31        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
33     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
34        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
35        makevp.bat for the current PCRE, using the additional files
36        makevp-c.txt, makevp-l.txt, and pcregexp.pas.
38     6. A Windows user reported a minor discrepancy with test 2, which turned out
39        to be caused by a trailing space on an input line that had got lost in his
40        copy. The trailing space was an accident, so I've just removed it.
42     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
43        that is needed.
45     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
46        as "const" (a) because they are and (b) because it helps the PHP
47        maintainers who have recently made a script to detect big data structures
48        in the php code that should be moved to the .rodata section. I remembered
49        to update Builducptable as well, so it won't revert if ucptable.h is ever
50        re-created.
52     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
53        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
54        order to be able to cut out the UTF-8 tables in the latter when UTF-8
55        support is not required. This saves 1.5-2K of code, which is important in
56        some applications.
58        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
59        so as not to refer to the tables, even though these functions will never be
60        called when UTF-8 support is disabled. Otherwise there are problems with a
61        shared library.
63    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
65        (a) It was defining its arguments as char * instead of void *.
67        (b) It was assuming that all moves were upwards in memory; this was true
68            a long time ago when I wrote it, but is no longer the case.
70        The emulated memove() is provided for those environments that have neither
71        memmove() nor bcopy(). I didn't think anyone used it these days, but that
72        is clearly not the case, as these two bugs were recently reported.
74    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
75        and Detrail to create the HTML documentation, the .txt form of the man
76        pages, and it removes trailing spaces from listed files. It also creates
77        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
78        case, it wraps all the #defines with #ifndefs. This script should be run
79        before "make dist".
81    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
82        with Unicode property support.
84        (a) For a maximizing quantifier, if the two different cases of the
85            character were of different lengths in their UTF-8 codings (there are
86            some cases like this - I found 11), and the matching function had to
87            back up over a mixture of the two cases, it incorrectly assumed they
88            were both the same length.
90        (b) When PCRE was configured to use the heap rather than the stack for
91            recursion during matching, it was not correctly preserving the data for
92            the other case of a UTF-8 character when checking ahead for a match
93            while processing a minimizing repeat. If the check also involved
94            matching a wide character, but failed, corruption could cause an
95            erroneous result when trying to check for a repeat of the original
96            character.
98    13. Some tidying changes to the testing mechanism:
100        (a) The RunTest script now detects the internal link size and whether there
101            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
102            values substituted by "configure". (The RunGrepTest script already did
103            this for UTF-8.) The configure.ac script no longer substitutes the
104            relevant variables.
106        (b) The debugging options /B and /D in pcretest show the compiled bytecode
107            with length and offset values. This means that the output is different
108            for different internal link sizes. Test 2 is skipped for link sizes
109            other than 2 because of this, bypassing the problem. Unfortunately,
110            there was also a test in test 3 (the locale tests) that used /B and
111            failed for link sizes other than 2. Rather than cut the whole test out,
112            I have added a new /Z option to pcretest that replaces the length and
113            offset values with spaces. This is now used to make test 3 independent
114            of link size. (Test 2 will be tidied up later.)
116    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
117        segmentation fault instead of returning the appropriate error message.
119    15. In multiline mode when the newline sequence was set to "any", the pattern
120        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
121        This doesn't seem right; it now treats the CRLF combination as the line
122        ending, and so does not match in that case. It's only a pattern such as ^$
123        that would hit this one: something like ^ABC$ would have failed after \r
124        and then tried again after \r\n.
126    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
127        in an attempt to make files that differ only in their line terminators
128        compare equal. This works on Linux.
131    Version 7.0 19-Dec-06
132    ---------------------
134     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
135        moving to gcc 4.1.1.
137     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
138        sys/time.h, which is documented as needed for this function. It doesn't
139        seem to matter on Linux, but it showed up on some releases of OS X.
141     3. It seems that there are systems where bytes whose values are greater than
142        127 match isprint() in the "C" locale. The "C" locale should be the
143        default when a C program starts up. In most systems, only ASCII printing
144        characters match isprint(). This difference caused the output from pcretest
145        to vary, making some of the tests fail. I have changed pcretest so that:
147        (a) When it is outputting text in the compiled version of a pattern, bytes
148            other than 32-126 are always shown as hex escapes.
150        (b) When it is outputting text that is a matched part of a subject string,
151            it does the same, unless a different locale has been set for the match
152            (using the /L modifier). In this case, it uses isprint() to decide.
154     4. Fixed a major bug that caused incorrect computation of the amount of memory
155        required for a compiled pattern when options that changed within the
156        pattern affected the logic of the preliminary scan that determines the
157        length. The relevant options are -x, and -i in UTF-8 mode. The result was
158        that the computed length was too small. The symptoms of this bug were
159        either the PCRE error "internal error: code overflow" from pcre_compile(),
160        or a glibc crash with a message such as "pcretest: free(): invalid next
161        size (fast)". Examples of patterns that provoked this bug (shown in
162        pcretest format) are:
164          /(?-x: )/x
165          /(?x)(?-x: \s*#\s*)/
166          /((?i)[\x{c0}])/8
167          /(?i:[\x{c0}])/8
169        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
170        is now done differently.
172     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
173        wrapper classes; (b) implement a new function in the C++ scanner that is
174        more efficient than the old way of doing things because it avoids levels of
175        recursion in the regex matching; (c) add a paragraph to the documentation
176        for the FullMatch() function.
178     6. The escape sequence \n was being treated as whatever was defined as
179        "newline". Not only was this contrary to the documentation, which states
180        that \n is character 10 (hex 0A), but it also went horribly wrong when
181        "newline" was defined as CRLF. This has been fixed.
183     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
184        was being set to -1 for the "end of line" case (supposedly a value that no
185        character can have). Though this value is never used (the check for end of
186        line is "zero bytes in current character"), it caused compiler complaints.
187        I've changed it to 0xffffffff.
189     8. In pcre_version.c, the version string was being built by a sequence of
190        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
191        string (as it is for production releases) called a macro with an empty
192        argument. The C standard says the result of this is undefined. The gcc
193        compiler treats it as an empty string (which was what was wanted) but it is
194        reported that Visual C gives an error. The source has been hacked around to
195        avoid this problem.
197     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
198        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
199        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
200        of them did).
202    10. Originally, pcretest opened its input and output without "b"; then I was
203        told that "b" was needed in some environments, so it was added for release
204        5.0 to both the input and output. (It makes no difference on Unix-like
205        systems.) Later I was told that it is wrong for the input on Windows. I've
206        now abstracted the modes into two macros, to make it easier to fiddle with
207        them, and removed "b" from the input mode under Windows.
209    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
211    12. Added -help and --help to pcretest as an official way of being reminded
212        of the options.
214    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
215        and pcrecpp.cc because they annoy compilers at high warning levels.
217    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
219    15. Fixed an occurrence of == in configure.ac that should have been = (shell
220        scripts are not C programs :-) and which was not noticed because it works
221        on Linux.
223    16. pcretest is supposed to handle any length of pattern and data line (as one
224        line or as a continued sequence of lines) by extending its input buffer if
225        necessary. This feature was broken for very long pattern lines, leading to
226        a string of junk being passed to pcre_compile() if the pattern was longer
227        than about 50K.
229    17. I have done a major re-factoring of the way pcre_compile() computes the
230        amount of memory needed for a compiled pattern. Previously, there was code
231        that made a preliminary scan of the pattern in order to do this. That was
232        OK when PCRE was new, but as the facilities have expanded, it has become
233        harder and harder to keep it in step with the real compile phase, and there
234        have been a number of bugs (see for example, 4 above). I have now found a
235        cunning way of running the real compile function in a "fake" mode that
236        enables it to compute how much memory it would need, while actually only
237        ever using a few hundred bytes of working memory and without too many
238        tests of the mode. This should make future maintenance and development
239        easier. A side effect of this work is that the limit of 200 on the nesting
240        depth of parentheses has been removed (though this was never a serious
241        limitation, I suspect). However, there is a downside: pcre_compile() now
242        runs more slowly than before (30% or more, depending on the pattern). I
243        hope this isn't a big issue. There is no effect on runtime performance.
245    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
246        newline (only possible for the last line of a file) and it was a
247        pattern that set a locale (followed by /Lsomething), pcretest crashed.
249    19. Added additional timing features to pcretest. (1) The -tm option now times
250        matching only, not compiling. (2) Both -t and -tm can be followed, as a
251        separate command line item, by a number that specifies the number of
252        repeats to use when timing. The default is 50000; this gives better
253        precision, but takes uncomfortably long for very large patterns.
255    20. Extended pcre_study() to be more clever in cases where a branch of a
256        subpattern has no definite first character. For example, (a*|b*)[cd] would
257        previously give no result from pcre_study(). Now it recognizes that the
258        first character must be a, b, c, or d.
260    21. There was an incorrect error "recursive call could loop indefinitely" if
261        a subpattern (or the entire pattern) that was being tested for matching an
262        empty string contained only one non-empty item after a nested subpattern.
263        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
264        incorrectly, because the \d was being skipped in the check.
266    22. The pcretest program now has a new pattern option /B and a command line
267        option -b, which is equivalent to adding /B to every pattern. This causes
268        it to show the compiled bytecode, without the additional information that
269        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
270        is the same as /B/I).
272    23. A new optimization is now able automatically to treat some sequences such
273        as a*b as a*+b. More specifically, if something simple (such as a character
274        or a simple class like \d) has an unlimited quantifier, and is followed by
275        something that cannot possibly match the quantified thing, the quantifier
276        is automatically "possessified".
278    24. A recursive reference to a subpattern whose number was greater than 39
279        went wrong under certain circumstances in UTF-8 mode. This bug could also
280        have affected the operation of pcre_study().
282    25. Realized that a little bit of performance could be had by replacing
283        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
285    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
287    27. Possessive quantifiers such as a++ were previously implemented by turning
288        them into atomic groups such as ($>a+). Now they have their own opcodes,
289        which improves performance. This includes the automatically created ones
290        from 23 above.
292    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
293        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
294        the first matched character to be a colon. This applied both to named and
295        numbered groups.
297    29. The ucpinternal.h header file was missing its idempotency #ifdef.
299    30. I was sent a "project" file called libpcre.a.dev which I understand makes
300        building PCRE on Windows easier, so I have included it in the distribution.
302    31. There is now a check in pcretest against a ridiculously large number being
303        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
304        loop, the loop is abandoned.
306    32. Forward references to subpatterns in conditions such as (?(2)...) where
307        subpattern 2 is defined later cause pcre_compile() to search forwards in
308        the pattern for the relevant set of parentheses. This search went wrong
309        when there were unescaped parentheses in a character class, parentheses
310        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
312    33. "Subroutine" calls and backreferences were previously restricted to
313        referencing subpatterns earlier in the regex. This restriction has now
314        been removed.
316    34. Added a number of extra features that are going to be in Perl 5.10. On the
317        whole, these are just syntactic alternatives for features that PCRE had
318        previously implemented using the Python syntax or my own invention. The
319        other formats are all retained for compatibility.
321        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
322            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
323            also .NET compatible.
325        (b) A recursion or subroutine call to a named group can now be defined as
326            (?&name) as well as (?P>name).
328        (c) A backreference to a named group can now be defined as \k<name> or
329            \k'name' as well as (?P=name). The new forms, as well as being in Perl
330            5.10, are also .NET compatible.
332        (d) A conditional reference to a named group can now use the syntax
333            (?(<name>) or (?('name') as well as (?(name).
335        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
336            groups (named and numbered) that are never evaluated inline, but can be
337            called as "subroutines" from elsewhere. In effect, the DEFINE condition
338            is always false. There may be only one alternative in such a group.
340        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
341            as the simple (?(R). The condition is true only if the most recent
342            recursion is that of the given number or name. It does not search out
343            through the entire recursion stack.
345        (g) The escape \gN or \g{N} has been added, where N is a positive or
346            negative number, specifying an absolute or relative reference.
348    35. Tidied to get rid of some further signed/unsigned compiler warnings and
349        some "unreachable code" warnings.
351    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
352        things, this adds five new scripts.
354    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
355        There were also incompatibilities regarding the handling of \Q..\E inside
356        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
357        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
359    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
360        matches an empty string, and forcibly breaks the loop. There were bugs in
361        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
362        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
363        separate and independent bugs (that affected different cases) have been
364        fixed.
366    39. Refactored the code to abolish the use of different opcodes for small
367        capturing bracket numbers. This is a tidy that I avoided doing when I
368        removed the limit on the number of capturing brackets for 3.5 back in 2001.
369        The new approach is not only tidier, it makes it possible to reduce the
370        memory needed to fix the previous bug (38).
372    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
373        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
374        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
375        mode.
377    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
378        report.
380    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
381        copy construction and assignment in the C++ wrapper.
383    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
384        couple of bugs that could have given wrong results in the "--newline=crlf"
385        case.
387    44. Added a number of casts and did some reorganization of signed/unsigned int
388        variables following suggestions from Dair Grant. Also renamed the variable
389        "this" as "item" because it is a C++ keyword.
391    45. Arranged for dftables to add
393          #include "pcre_internal.h"
395        to pcre_chartables.c because without it, gcc 4.x may remove the array
396        definition from the final binary if PCRE is built into a static library and
397        dead code stripping is activated.
399    46. For an unanchored pattern, if a match attempt fails at the start of a
400        newline sequence, and the newline setting is CRLF or ANY, and the next two
401        characters are CRLF, advance by two characters instead of one.
404    Version 6.7 04-Jul-06
405    ---------------------
407     1. In order to handle tests when input lines are enormously long, pcretest has
408        been re-factored so that it automatically extends its buffers when
409        necessary. The code is crude, but this _is_ just a test program. The
410        default size has been increased from 32K to 50K.
412     2. The code in pcre_study() was using the value of the re argument before
413        testing it for NULL. (Of course, in any sensible call of the function, it
414        won't be NULL.)
416     3. The memmove() emulation function in pcre_internal.h, which is used on
417        systems that lack both memmove() and bcopy() - that is, hardly ever -
418        was missing a "static" storage class specifier.
420     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
421        containing an extended class (one that cannot be represented by a bitmap
422        because it contains high-valued characters or Unicode property items, e.g.
423        [\pZ]). Almost always one would set UTF-8 mode when processing such a
424        pattern, but PCRE should not loop if you do not (it no longer does).
425        [Detail: two cases were found: (a) a repeated subpattern containing an
426        extended class; (b) a recursive reference to a subpattern that followed a
427        previous extended class. It wasn't skipping over the extended class
428        correctly when UTF-8 mode was not set.]
430     5. A negated single-character class was not being recognized as fixed-length
431        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
432        compile error "lookbehind assertion is not fixed length".
434     6. The RunPerlTest auxiliary script was showing an unexpected difference
435        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
436        write a Perl script that can interpret lines of an input file either as
437        byte characters or as UTF-8, which is what "perltest" was being required to
438        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
439        can't do is switch easily at run time between having the "use utf8;" pragma
440        or not. In the end, I fudged it by using the RunPerlTest script to insert
441        "use utf8;" explicitly for the UTF-8 tests.
443     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
444        the end of the subject string, contrary to the documentation and to what
445        Perl does. This was true of both matching functions. Now it matches only at
446        the start of the subject and immediately after *internal* newlines.
448     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
449        a pointer to an int instead of a pointer to an unsigned long int. This
450        caused problems on 64-bit systems.
452     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
453        instance of the 'standard' template library not being so standard".
455    10. There was no check on the number of named subpatterns nor the maximum
456        length of a subpattern name. The product of these values is used to compute
457        the size of the memory block for a compiled pattern. By supplying a very
458        long subpattern name and a large number of named subpatterns, the size
459        computation could be caused to overflow. This is now prevented by limiting
460        the length of names to 32 characters, and the number of named subpatterns
461        to 10,000.
463    11. Subpatterns that are repeated with specific counts have to be replicated in
464        the compiled pattern. The size of memory for this was computed from the
465        length of the subpattern and the repeat count. The latter is limited to
466        65535, but there was no limit on the former, meaning that integer overflow
467        could in principle occur. The compiled length of a repeated subpattern is
468        now limited to 30,000 bytes in order to prevent this.
470    12. Added the optional facility to have named substrings with the same name.
472    13. Added the ability to use a named substring as a condition, using the
473        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
474        are numbers (not recommended). Forward references are permitted.
476    14. Added forward references in named backreferences (if you see what I mean).
478    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
479        pattern could run off the end of the subject. For example, the pattern
480        "(?s)(.{1,5})"8 did this with the subject "ab".
482    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
483        PCRE_CASELESS was set when matching characters that were quantified with ?
484        or *.
486    17. A character class other than a single negated character that had a minimum
487        but no maximum quantifier - for example [ab]{6,} - was not handled
488        correctly by pce_dfa_exec(). It would match only one character.
490    18. A valid (though odd) pattern that looked like a POSIX character
491        class but used an invalid character after [ (for example [[,abc,]]) caused
492        pcre_compile() to give the error "Failed: internal error: code overflow" or
493        in some cases to crash with a glibc free() error. This could even happen if
494        the pattern terminated after [[ but there just happened to be a sequence of
495        letters, a binary zero, and a closing ] in the memory that followed.
497    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
498        over the years. Originally (before any Unicode support), just the bottom 8
499        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
500        output from "man perlunicode" includes this:
502          The regular expression compiler produces polymorphic opcodes.  That
503          is, the pattern adapts to the data and automatically switches to
504          the Unicode character scheme when presented with Unicode data--or
505          instead uses a traditional byte scheme when presented with byte
506          data.
508        Sadly, a wide octal escape does not cause a switch, and in a string with
509        no other multibyte characters, these octal escapes are treated as before.
510        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
511        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
512        Unicode string.
514        I have not perpetrated such confusion in PCRE. Up till now, it took just
515        the bottom 8 bits, as in old Perl. I have now made octal escapes with
516        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
517        translate to the appropriate multibyte character.
519    29. Applied some refactoring to reduce the number of warnings from Microsoft
520        and Borland compilers. This has included removing the fudge introduced
521        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
522        a warning about an unused variable.
524    21. PCRE has not included VT (character 0x0b) in the set of whitespace
525        characters since release 4.0, because Perl (from release 5.004) does not.
526        [Or at least, is documented not to: some releases seem to be in conflict
527        with the documentation.] However, when a pattern was studied with
528        pcre_study() and all its branches started with \s, PCRE still included VT
529        as a possible starting character. Of course, this did no harm; it just
530        caused an unnecessary match attempt.
532    22. Removed a now-redundant internal flag bit that recorded the fact that case
533        dependency changed within the pattern. This was once needed for "required
534        byte" processing, but is no longer used. This recovers a now-scarce options
535        bit. Also moved the least significant internal flag bit to the most-
536        significant bit of the word, which was not previously used (hangover from
537        the days when it was an int rather than a uint) to free up another bit for
538        the future.
540    23. Added support for CRLF line endings as well as CR and LF. As well as the
541        default being selectable at build time, it can now be changed at runtime
542        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
543        specify that it is scanning data with non-default line endings.
545    24. Changed the definition of CXXLINK to make it agree with the definition of
546        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
548    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
549        recursions. This makes a big different to stack usage for some patterns.
551    26. If a subpattern containing a named recursion or subroutine reference such
552        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
553        the space required for the compiled pattern went wrong and gave too small a
554        value. Depending on the environment, this could lead to "Failed: internal
555        error: code overflow at offset 49" or "glibc detected double free or
556        corruption" errors.
558    27. Applied patches from Google (a) to support the new newline modes and (b) to
559        advance over multibyte UTF-8 characters in GlobalReplace.
561    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
562        difference for some implementation of PCRE in some Windows version.
564    29. Added some extra testing facilities to pcretest:
566        \q<number>   in a data line sets the "match limit" value
567        \Q<number>   in a data line sets the "match recursion limt" value
568        -S <number>  sets the stack size, where <number> is in megabytes
570        The -S option isn't available for Windows.
573    Version 6.6 06-Feb-06
574    ---------------------
576     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
577        in pcreposix.h. I have copied the definition from pcre.h.
579     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
580        because pcre.h is no longer a built file.
582     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
583        not normally included in the compiled code.
586    Version 6.5 01-Feb-06
587    ---------------------
589     1. When using the partial match feature with pcre_dfa_exec(), it was not
590        anchoring the second and subsequent partial matches at the new starting
591        point. This could lead to incorrect results. For example, with the pattern
592        /1234/, partially matching against "123" and then "a4" gave a match.
594     2. Changes to pcregrep:
596        (a) All non-match returns from pcre_exec() were being treated as failures
597            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
598            error message is output. Some extra information is given for the
599            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
600            probably the only errors that are likely to be caused by users (by
601            specifying a regex that has nested indefinite repeats, for instance).
602            If there are more than 20 of these errors, pcregrep is abandoned.
604        (b) A binary zero was treated as data while matching, but terminated the
605            output line if it was written out. This has been fixed: binary zeroes
606            are now no different to any other data bytes.
608        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
609            used to set a locale for matching. The --locale=xxxx long option has
610            been added (no short equivalent) to specify a locale explicitly on the
611            pcregrep command, overriding the environment variables.
613        (d) When -B was used with -n, some line numbers in the output were one less
614            than they should have been.
616        (e) Added the -o (--only-matching) option.
618        (f) If -A or -C was used with -c (count only), some lines of context were
619            accidentally printed for the final match.
621        (g) Added the -H (--with-filename) option.
623        (h) The combination of options -rh failed to suppress file names for files
624            that were found from directory arguments.
626        (i) Added the -D (--devices) and -d (--directories) options.
628        (j) Added the -F (--fixed-strings) option.
630        (k) Allow "-" to be used as a file name for -f as well as for a data file.
632        (l) Added the --colo(u)r option.
634        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
635            is not present by default.
637     3. A nasty bug was discovered in the handling of recursive patterns, that is,
638        items such as (?R) or (?1), when the recursion could match a number of
639        alternatives. If it matched one of the alternatives, but subsequently,
640        outside the recursion, there was a failure, the code tried to back up into
641        the recursion. However, because of the way PCRE is implemented, this is not
642        possible, and the result was an incorrect result from the match.
644        In order to prevent this happening, the specification of recursion has
645        been changed so that all such subpatterns are automatically treated as
646        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
648     4. I had overlooked the fact that, in some locales, there are characters for
649        which isalpha() is true but neither isupper() nor islower() are true. In
650        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
651        and ordfeminine) are like this. This affected the treatment of \w and \W
652        when they appeared in character classes, but not when they appeared outside
653        a character class. The bit map for "word" characters is now created
654        separately from the results of isalnum() instead of just taking it from the
655        upper, lower, and digit maps. (Plus the underscore character, of course.)
657     5. The above bug also affected the handling of POSIX character classes such as
658        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
659        permanent tables. Instead, the bit maps for such a class were previously
660        created as the appropriate unions of the upper, lower, and digit bitmaps.
661        Now they are created by subtraction from the [[:word:]] class, which has
662        its own bitmap.
664     6. The [[:blank:]] character class matches horizontal, but not vertical space.
665        It is created by subtracting the vertical space characters (\x09, \x0a,
666        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
667        subtraction was done in the overall bitmap for a character class, meaning
668        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
669        be recognized. This bug has been fixed.
671     7. Patches from the folks at Google:
673          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
674          real life, but is still worth protecting against".
676          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
677          regular expressions".
679          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
680          have it.
682          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
683          "configure" and the latter not, in order to fix a problem somebody had
684          with compiling the Arg class on HP-UX.
686          (e) Improve the error-handling of the C++ wrapper a little bit.
688          (f) New tests for checking recursion limiting.
690     8. The pcre_memmove() function, which is used only if the environment does not
691        have a standard memmove() function (and is therefore rarely compiled),
692        contained two bugs: (a) use of int instead of size_t, and (b) it was not
693        returning a result (though PCRE never actually uses the result).
695     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
696        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
697        returned instead of calling malloc() with an overflowing number that would
698        most likely cause subsequent chaos.
700    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
702    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
703        with this option is matched, the nmatch and pmatch options of regexec() are
704        ignored.
706    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
707        provided in case anyone wants to the the POSIX interface with UTF-8
708        strings.
710    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
711        C++ linking (needed for some HP-UX environments).
713    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
714        (unused parameter) and in the pcre_printint() function (omitted "default"
715        switch label when the default is to do nothing).
717    15. Added some code to make it possible, when PCRE is compiled as a C++
718        library, to replace subject pointers for pcre_exec() with a smart pointer
719        class, thus making it possible to process discontinuous strings.
721    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
722        much the same function. They were added by different people who were trying
723        to make PCRE easy to compile on non-Unix systems. It has been suggested
724        that PCRE_EXPORT be abolished now that there is more automatic apparatus
725        for compiling on Windows systems. I have therefore replaced it with
726        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
727        defaults to "extern" for C or "extern C" for C++, which works fine on
728        Unix-like systems. It is now possible to override the value of PCRE_DATA_
729        SCOPE with something explicit in config.h. In addition:
731        (a) pcreposix.h still had just "extern" instead of either of these macros;
732            I have replaced it with PCRE_DATA_SCOPE.
734        (b) Functions such as _pcre_xclass(), which are internal to the library,
735            but external in the C sense, all had PCRE_EXPORT in their definitions.
736            This is apparently wrong for the Windows case, so I have removed it.
737            (It makes no difference on Unix-like systems.)
739    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
740        of recursive calls to match(). This is different to MATCH_LIMIT because
741        that limits the total number of calls to match(), not all of which increase
742        the depth of recursion. Limiting the recursion depth limits the amount of
743        stack (or heap if NO_RECURSE is set) that is used. The default can be set
744        when PCRE is compiled, and changed at run time. A patch from Google adds
745        this functionality to the C++ interface.
747    18. Changes to the handling of Unicode character properties:
749        (a) Updated the table to Unicode 4.1.0.
751        (b) Recognize characters that are not in the table as "Cn" (undefined).
753        (c) I revised the way the table is implemented to a much improved format
754            which includes recognition of ranges. It now supports the ranges that
755            are defined in UnicodeData.txt, and it also amalgamates other
756            characters into ranges. This has reduced the number of entries in the
757            table from around 16,000 to around 3,000, thus reducing its size
758            considerably. I realized I did not need to use a tree structure after
759            all - a binary chop search is just as efficient. Having reduced the
760            number of entries, I extended their size from 6 bytes to 8 bytes to
761            allow for more data.
763        (d) Added support for Unicode script names via properties such as \p{Han}.
765    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
766        matching that character.
768    20. When matching a repeated Unicode property with a minimum greater than zero,
769        (for example \pL{2,}), PCRE could look past the end of the subject if it
770        reached it while seeking the minimum number of characters. This could
771        happen only if some of the characters were more than one byte long, because
772        there is a check for at least the minimum number of bytes.
774    21. Refactored the implementation of \p and \P so as to be more general, to
775        allow for more different types of property in future. This has changed the
776        compiled form incompatibly. Anybody with saved compiled patterns that use
777        \p or \P will have to recompile them.
779    22. Added "Any" and "L&" to the supported property types.
781    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
782        but give a compile time error if the value is greater than 0xff.
784    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
785        accidentally not being installed or uninstalled.
787    25. The pcre.h file was built from pcre.h.in, but the only changes that were
788        made were to insert the current release number. This seemed silly, because
789        it made things harder for people building PCRE on systems that don't run
790        "configure". I have turned pcre.h into a distributed file, no longer built
791        by "configure", with the version identification directly included. There is
792        no longer a pcre.h.in file.
794        However, this change necessitated a change to the pcre-config script as
795        well. It is built from pcre-config.in, and one of the substitutions was the
796        release number. I have updated configure.ac so that ./configure now finds
797        the release number by grepping pcre.h.
799    26. Added the ability to run the tests under valgrind.
802    Version 6.4 05-Sep-05
803    ---------------------
805     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
806        "--" to be printed when multiple files were scanned, even when none of the
807        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
808        consider it to be a bug, and have restored the previous behaviour.
810     2. A couple of code tidies to get rid of compiler warnings.
812     3. The pcretest program used to cheat by referring to symbols in the library
813        whose names begin with _pcre_. These are internal symbols that are not
814        really supposed to be visible externally, and in some environments it is
815        possible to suppress them. The cheating is now confined to including
816        certain files from the library's source, which is a bit cleaner.
818     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
819        file's purpose clearer.
821     5. Reorganized pcre_ucp_findchar().
824  Version 6.3 15-Aug-05  Version 6.3 15-Aug-05
825  ---------------------  ---------------------

Removed from v.83  
changed lines
  Added in v.134

  ViewVC Help
Powered by ViewVC 1.1.5