ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 100 by ph10, Tue Mar 6 14:53:10 2007 UTC revision 274 by ph10, Tue Nov 20 10:05:23 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.1 05-Mar-07  Version 7.5 12-Nov-07
5  ---------------------  ---------------------
7   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8      that is more "standard", making use of automake and other autotools. There      values in parens when parsing an RE using the C++ wrapper."
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing). Both these problems are fixed. "Subpattern name
25        expected" is now given for (?&) (a zero-length name), and this patch also
26        makes it give the same error for \k'' (previously it complained that that
27        was a reference to a non-existent subpattern).
29    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
30        this is right because (?- can be followed by option settings as well as by
31        digits. I have, however, made the messages clearer.
33    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
34        than the number used in the conditional) now cause a compile-time error.
35        This is actually not compatible with Perl, which accepts such patterns, but
36        treats the conditional as always being FALSE (as PCRE used to), but it
37        seems to me that giving a diagnostic is better.
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
43    Version 7.4 21-Sep-07
44    ---------------------
46    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
47        means that a class such as [\s] counted as "explicit reference to CR or
48        LF". That isn't really right - the whole point of the change was to try to
49        help when there was an actual mention of one of the two characters. So now
50        the change happens only if \r or \n (or a literal CR or LF) character is
51        encountered.
53    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
54        of both had grown to the point where there were only 3 bits left.
55        Fortunately, there was spare space in the data structure, and so I have
56        moved the internal flags into a new 16-bit field to free up more option
57        bits.
59    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
60        but did not set the internal JCHANGED flag - either of these is enough to
61        control the way the "get" function works - but the PCRE_INFO_JCHANGED
62        facility is supposed to tell if (?J) was ever used, so now (?J) at the
63        start sets both bits.
65    4.  Added options (at build time, compile time, exec time) to change \R from
66        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
68    5.  doc/pcresyntax.html was missing from the distribution.
70    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
71        compatibility, even though it is no longer used.
73    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
74        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
75        windows.h file is present (where different names are used). [This was
76        reversed later after testing - see 16 below.]
78    8.  Changed all #include <config.h> to #include "config.h". There were also
79        some further <pcre.h> cases that I changed to "pcre.h".
81    9.  When pcregrep was used with the --colour option, it missed the line ending
82        sequence off the lines that it output.
84    10. It was pointed out to me that arrays of string pointers cause lots of
85        relocations when a shared library is dynamically loaded. A technique of
86        using a single long string with a table of offsets can drastically reduce
87        these. I have refactored PCRE in four places to do this. The result is
88        dramatic:
90          Originally:                          290
91          After changing UCP table:            187
92          After changing error message table:   43
93          After changing table of "verbs"       36
94          After changing table of Posix names   22
96        Thanks to the folks working on Gregex for glib for this insight.
98    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
99        unicode-properties was also set.
101    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
103    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
104        checked only for CRLF.
106    14. Added casts to pcretest.c to avoid compiler warnings.
108    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
110    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
111        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
112        entirely. This removes changes made in 7 above.
114    17. The CMake files have been updated, and there is now more information about
115        building with CMake in the NON-UNIX-USE document.
118    Version 7.3 28-Aug-07
119    ---------------------
121     1. In the rejigging of the build system that eventually resulted in 7.1, the
122        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
123        brackets there is not right, since it causes compilers to look for an
124        installed pcre.h, not the version that is in the source that is being
125        compiled (which of course may be different). I have changed it back to:
127          #include "pcre.h"
129        I have a vague recollection that the change was concerned with compiling in
130        different directories, but in the new build system, that is taken care of
131        by the VPATH setting the Makefile.
133     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
134        when the subject happened to end in the byte 0x85 (e.g. if the last
135        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
136        characters but of course it shouldn't be taken as a newline when it is part
137        of another character. The bug was that, for an unlimited repeat of . in
138        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
139        characters when looking for a newline.
141     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
143     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
144        in debug output.
146     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
147        long printing in the pcrecpp unittest when running under MinGW.
149     6. ESC_K was left out of the EBCDIC table.
151     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
152        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
153        limit also applies to "virtual nesting" when a pattern is recursive, and in
154        this case 1000 isn't so big. I have been able to remove this limit at the
155        expense of backing off one optimization in certain circumstances. Normally,
156        when pcre_exec() would call its internal match() function recursively and
157        immediately return the result unconditionally, it uses a "tail recursion"
158        feature to save stack. However, when a subpattern that can match an empty
159        string has an unlimited repetition quantifier, it no longer makes this
160        optimization. That gives it a stack frame in which to save the data for
161        checking that an empty string has been matched. Previously this was taken
162        from the 1000-entry workspace that had been reserved. So now there is no
163        explicit limit, but more stack is used.
165     8. Applied Daniel's patches to solve problems with the import/export magic
166        syntax that is required for Windows, and which was going wrong for the
167        pcreposix and pcrecpp parts of the library. These were overlooked when this
168        problem was solved for the main library.
170     9. There were some crude static tests to avoid integer overflow when computing
171        the size of patterns that contain repeated groups with explicit upper
172        limits. As the maximum quantifier is 65535, the maximum group length was
173        set at 30,000 so that the product of these two numbers did not overflow a
174        32-bit integer. However, it turns out that people want to use groups that
175        are longer than 30,000 bytes (though not repeat them that many times).
176        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
177        made it possible to implement the integer overflow checks in a much more
178        dynamic way, which I have now done. The artificial limitation on group
179        length has been removed - we now have only the limit on the total length of
180        the compiled pattern, which depends on the LINK_SIZE setting.
182    10. Fixed a bug in the documentation for get/copy named substring when
183        duplicate names are permitted. If none of the named substrings are set, the
184        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
185        empty string.
187    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
188        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
189        because the ] is interpreted as the first data character and the
190        terminating ] is not found. PCRE has been made compatible with Perl in this
191        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
192        cause memory overwriting.
194    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
195        string has been matched (to stop an infinite loop). It was not recognizing
196        a conditional subpattern that could match an empty string if that
197        subpattern was within another subpattern. For example, it looped when
198        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
199        condition was not nested. This bug has been fixed.
201    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
202        past the start of the subject in the presence of bytes with the top bit
203        set, for example "\x8aBCD".
205    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
206        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
208    14. Optimized (?!) to (*FAIL).
210    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
211        This restricts code points to be within the range 0 to 0x10FFFF, excluding
212        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
213        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
214        does: it's just the validity check that is more restrictive.
216    16. Inserted checks for integer overflows during escape sequence (backslash)
217        processing, and also fixed erroneous offset values for syntax errors during
218        backslash processing.
220    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
221        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
223    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
224        caused an overrun.
226    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
227        something other than just ASCII characters) inside a group that had an
228        unlimited repeat caused a loop at compile time (while checking to see
229        whether the group could match an empty string).
231    20. Debugging a pattern containing \p or \P could cause a crash. For example,
232        [\P{Any}] did so. (Error in the code for printing property names.)
234    21. An orphan \E inside a character class could cause a crash.
236    22. A repeated capturing bracket such as (A)? could cause a wild memory
237        reference during compilation.
239    23. There are several functions in pcre_compile() that scan along a compiled
240        expression for various reasons (e.g. to see if it's fixed length for look
241        behind). There were bugs in these functions when a repeated \p or \P was
242        present in the pattern. These operators have additional parameters compared
243        with \d, etc, and these were not being taken into account when moving along
244        the compiled data. Specifically:
246        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
247            length.
249        (b) An item such as \pL+ within a repeated group could cause crashes or
250            loops.
252        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
253            "reference to non-existent subpattern" error.
255        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
257    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
258        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
260    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
262    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
263        character were causing crashes (broken optimization).
265    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
266        \p or \P) caused a compile-time loop.
268    28. More problems have arisen in unanchored patterns when CRLF is a valid line
269        break. For example, the unstudied pattern [\r\n]A does not match the string
270        "\r\nA" because change 7.0/46 below moves the current point on by two
271        characters after failing to match at the start. However, the pattern \nA
272        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
273        the same is true. There doesn't seem any very clean way out of this, but
274        what I have chosen to do makes the common cases work: PCRE now takes note
275        of whether there can be an explicit match for \r or \n anywhere in the
276        pattern, and if so, 7.0/46 no longer applies. As part of this change,
277        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
278        pattern has explicit CR or LF references.
280    29. Added (*CR) etc for changing newline setting at start of pattern.
283    Version 7.2 19-Jun-07
284    ---------------------
286     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
287        which is apparently normally available under Windows.
289     2. Re-jig the pcregrep tests with different newline settings in an attempt
290        to make them independent of the local environment's newline setting.
292     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
294     4. Some of the "internals" tests were previously cut out when the link size
295        was not 2, because the output contained actual offsets. The recent new
296        "Z" feature of pcretest means that these can be cut out, making the tests
297        usable with all link sizes.
299     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
300        stack recursion. This gives a massive performance boost under BSD, but just
301        a small improvement under Linux. However, it saves one field in the frame
302        in all cases.
304     6. Added more features from the forthcoming Perl 5.10:
306        (a) (?-n) (where n is a string of digits) is a relative subroutine or
307            recursion call. It refers to the nth most recently opened parentheses.
309        (b) (?+n) is also a relative subroutine call; it refers to the nth next
310            to be opened parentheses.
312        (c) Conditions that refer to capturing parentheses can be specified
313            relatively, for example, (?(-2)... or (?(+3)...
315        (d) \K resets the start of the current match so that everything before
316            is not part of it.
318        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
320        (f) \g{name} is another synonym - part of Perl 5.10's unification of
321            reference syntax.
323        (g) (?| introduces a group in which the numbering of parentheses in each
324            alternative starts with the same number.
326        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
328     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
331     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
332        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
333        for detecting groups that can match an empty string.
335     9. A pattern with a very large number of alternatives (more than several
336        hundred) was running out of internal workspace during the pre-compile
337        phase, where pcre_compile() figures out how much memory will be needed. A
338        bit of new cunning has reduced the workspace needed for groups with
339        alternatives. The 1000-alternative test pattern now uses 12 bytes of
340        workspace instead of running out of the 4096 that are available.
342    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
344    11. Applied patch from Google to remove an optimization that didn't quite work.
345        The report of the bug said:
347          pcrecpp::RE("a*").FullMatch("aaa") matches, while
348          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
349          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
351    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
352        it matched the wrong number of bytes.
355    Version 7.1 24-Apr-07
356    ---------------------
358     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
359        that is more "standard", making use of automake and other Autotools. There
360      is some re-arrangement of the files and adjustment of comments consequent      is some re-arrangement of the files and adjustment of comments consequent
361      on this.      on this.
363   2. Part of the patch fixed a problem with the pcregrep tests. The test of -r   2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
364      for recursive directory scanning broke on some systems because the files      for recursive directory scanning broke on some systems because the files
365      are not scanned in any specific order and on different systems the order      are not scanned in any specific order and on different systems the order
366      was different. A call to "sort" has been inserted into RunGrepTest for the      was different. A call to "sort" has been inserted into RunGrepTest for the
367      approprate test as a short-term fix. In the longer term there may be an      approprate test as a short-term fix. In the longer term there may be an
368      alternative.      alternative.
370   3. I had an email from Eric Raymond about problems translating some of PCRE's   3. I had an email from Eric Raymond about problems translating some of PCRE's
371      man pages to HTML (despite the fact that I distribute HTML pages, some      man pages to HTML (despite the fact that I distribute HTML pages, some
372      people do their own conversions for various reasons). The problems      people do their own conversions for various reasons). The problems
373      concerned the use of low-level troff macros .br and .in. I have therefore      concerned the use of low-level troff macros .br and .in. I have therefore
374      removed all such uses from the man pages (some were redundant, some could      removed all such uses from the man pages (some were redundant, some could
375      be replaced by .nf/.fi pairs). The maintain/132html script that I use to      be replaced by .nf/.fi pairs). The 132html script that I use to generate
376      generate HTML has been updated to handle .nf/.fi and to complain if it      HTML has been updated to handle .nf/.fi and to complain if it encounters
377      encounters .br or .in.      .br or .in.
379   4. Updated comments in configure.ac that get placed in config.h.in and also   4. Updated comments in configure.ac that get placed in config.h.in and also
380      arranged for config.h to be included in the distribution, for the benefit      arranged for config.h to be included in the distribution, with the name
381      of those who have to compile without Autotools (compare pcre.h).      config.h.generic, for the benefit of those who have to compile without
382        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
384     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
385        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
386        makevp.bat for the current PCRE, using the additional files
387        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
389     6. A Windows user reported a minor discrepancy with test 2, which turned out
390        to be caused by a trailing space on an input line that had got lost in his
391        copy. The trailing space was an accident, so I've just removed it.
393     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
394        that is needed.
396     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
397        as "const" (a) because they are and (b) because it helps the PHP
398        maintainers who have recently made a script to detect big data structures
399        in the php code that should be moved to the .rodata section. I remembered
400        to update Builducptable as well, so it won't revert if ucptable.h is ever
401        re-created.
403     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
404        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
405        order to be able to cut out the UTF-8 tables in the latter when UTF-8
406        support is not required. This saves 1.5-2K of code, which is important in
407        some applications.
409        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
410        so as not to refer to the tables, even though these functions will never be
411        called when UTF-8 support is disabled. Otherwise there are problems with a
412        shared library.
414    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
416        (a) It was defining its arguments as char * instead of void *.
418        (b) It was assuming that all moves were upwards in memory; this was true
419            a long time ago when I wrote it, but is no longer the case.
421        The emulated memove() is provided for those environments that have neither
422        memmove() nor bcopy(). I didn't think anyone used it these days, but that
423        is clearly not the case, as these two bugs were recently reported.
425    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
426        and Detrail to create the HTML documentation, the .txt form of the man
427        pages, and it removes trailing spaces from listed files. It also creates
428        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
429        case, it wraps all the #defines with #ifndefs. This script should be run
430        before "make dist".
432    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
433        with Unicode property support.
435        (a) For a maximizing quantifier, if the two different cases of the
436            character were of different lengths in their UTF-8 codings (there are
437            some cases like this - I found 11), and the matching function had to
438            back up over a mixture of the two cases, it incorrectly assumed they
439            were both the same length.
441        (b) When PCRE was configured to use the heap rather than the stack for
442            recursion during matching, it was not correctly preserving the data for
443            the other case of a UTF-8 character when checking ahead for a match
444            while processing a minimizing repeat. If the check also involved
445            matching a wide character, but failed, corruption could cause an
446            erroneous result when trying to check for a repeat of the original
447            character.
449    13. Some tidying changes to the testing mechanism:
451        (a) The RunTest script now detects the internal link size and whether there
452            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
453            values substituted by "configure". (The RunGrepTest script already did
454            this for UTF-8.) The configure.ac script no longer substitutes the
455            relevant variables.
457        (b) The debugging options /B and /D in pcretest show the compiled bytecode
458            with length and offset values. This means that the output is different
459            for different internal link sizes. Test 2 is skipped for link sizes
460            other than 2 because of this, bypassing the problem. Unfortunately,
461            there was also a test in test 3 (the locale tests) that used /B and
462            failed for link sizes other than 2. Rather than cut the whole test out,
463            I have added a new /Z option to pcretest that replaces the length and
464            offset values with spaces. This is now used to make test 3 independent
465            of link size. (Test 2 will be tidied up later.)
467    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
468        segmentation fault instead of returning the appropriate error message.
470    15. In multiline mode when the newline sequence was set to "any", the pattern
471        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
472        This doesn't seem right; it now treats the CRLF combination as the line
473        ending, and so does not match in that case. It's only a pattern such as ^$
474        that would hit this one: something like ^ABC$ would have failed after \r
475        and then tried again after \r\n.
477    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
478        in an attempt to make files that differ only in their line terminators
479        compare equal. This works on Linux.
481    17. Under certain error circumstances pcregrep might try to free random memory
482        as it exited. This is now fixed, thanks to valgrind.
484    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
485        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
486        was because its rules for how to advance for /g after matching an empty
487        string at the end of a line did not allow for this case. They now check for
488        it specially.
490    20. pcretest is supposed to handle patterns and data of any length, by
491        extending its buffers when necessary. It was getting this wrong when the
492        buffer for a data line had to be extended.
494    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
495        CRLF as a newline sequence.
497    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
498        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
499        I have nevertheless tidied it up.
501    23. Added some casts to kill warnings from HP-UX ia64 compiler.
503    24. Added a man page for pcre-config.
506  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
507  ---------------------  ---------------------

Removed from v.100  
changed lines
  Added in v.274

  ViewVC Help
Powered by ViewVC 1.1.5