ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 141 by ph10, Fri Mar 30 15:46:27 2007 UTC revision 325 by ph10, Sat Mar 8 17:13:02 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.1 12-Mar-07  Version 7.7 05-Mar-08
5    ---------------------
7    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
8        a string to a long long, pretend we don't even have a long long." This is
9        done by checking for the strtoq, strtoll, and _strtoi64 functions.
11    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
12        pre-7.6 versions, which defined a global no_arg variable instead of putting
13        it in the RE class.
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
23        (2) If there was more than one level of directory, the subdirectories were
24            skipped unless they satisfied the include/exclude conditions. This is
25            inconsistent with GNU grep (and could even be seen as contrary to the
26            pcregrep specification - which I improved to make it absolutely clear).
27            The action now is always to scan all levels of directory, and just
28            apply the include/exclude patterns to regular files.
30    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
31        --exclude_dir in the tests to avoid scanning .svn directories.
34    Version 7.6 28-Jan-08
35    ---------------------
37    1.  A character class containing a very large number of characters with
38        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
39        overflow.
41    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
42        HAVE_LONG_LONG is not defined.
44    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
45        bring them up to date and include new features. This patch includes:
47        - Fixed PH's badly added libz and libbz2 support.
48        - Fixed a problem with static linking.
49        - Added pcredemo. [But later removed - see 7 below.]
50        - Fixed dftables problem and added an option.
51        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
52            HAVE_LONG_LONG.
53        - Added readline support for pcretest.
54        - Added an listing of the option settings after cmake has run.
56    4.  A user submitted a patch to Makefile that makes it easy to create
57        "pcre.dll" under mingw when using Configure/Make. I added stuff to
58        Makefile.am that cause it to include this special target, without
59        affecting anything else. Note that the same mingw target plus all
60        the other distribution libraries and programs are now supported
61        when configuring with CMake (see 6 below) instead of with
62        Configure/Make.
64    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
65        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
66        exported in the Windows port". It has not yet been confirmed that the patch
67        solves the problem, but it does no harm.
69    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
70        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
71        with CMake, and also correct the comment about stack recursion.
73    7.  Remove the automatic building of pcredemo from the ./configure system and
74        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
75        of a program that users should build themselves after PCRE is installed, so
76        building it automatically is not really right. What is more, it gave
77        trouble in some build environments.
79    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
82    Version 7.5 10-Jan-08
83    ---------------------
85    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
86        values in parens when parsing an RE using the C++ wrapper."
88    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
89        Characters greater than 255 were excluded from the class instead of being
90        included.
92    3.  The same bug as (2) above applied to negated POSIX classes such as
93        [:^space:].
95    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
96        defined or documented. It seems to have been a typo for PCRE_STATIC, so
97        I have changed it.
99    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
100        first named subpattern) and a construct such as (?&a) would reference the
101        first named subpattern whose name started with "a" (in other words, the
102        length check was missing). Both these problems are fixed. "Subpattern name
103        expected" is now given for (?&) (a zero-length name), and this patch also
104        makes it give the same error for \k'' (previously it complained that that
105        was a reference to a non-existent subpattern).
107    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
108        this is right because (?- can be followed by option settings as well as by
109        digits. I have, however, made the messages clearer.
111    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
112        than the number used in the conditional) now cause a compile-time error.
113        This is actually not compatible with Perl, which accepts such patterns, but
114        treats the conditional as always being FALSE (as PCRE used to), but it
115        seems to me that giving a diagnostic is better.
117    8.  Change "alphameric" to the more common word "alphanumeric" in comments
118        and messages.
120    9.  Fix two occurrences of "backslash" in comments that should have been
121        "backspace".
123    10. Remove two redundant lines of code that can never be obeyed (their function
124        was moved elsewhere).
126    11. The program that makes PCRE's Unicode character property table had a bug
127        which caused it to generate incorrect table entries for sequences of
128        characters that have the same character type, but are in different scripts.
129        It amalgamated them into a single range, with the script of the first of
130        them. In other words, some characters were in the wrong script. There were
131        thirteen such cases, affecting characters in the following ranges:
133          U+002b0 - U+002c1
134          U+0060c - U+0060d
135          U+0061e - U+00612
136          U+0064b - U+0065e
137          U+0074d - U+0076d
138          U+01800 - U+01805
139          U+01d00 - U+01d77
140          U+01d9b - U+01dbf
141          U+0200b - U+0200f
142          U+030fc - U+030fe
143          U+03260 - U+0327f
144          U+0fb46 - U+0fbb1
145          U+10450 - U+1049d
147    12. The -o option (show only the matching part of a line) for pcregrep was not
148        compatible with GNU grep in that, if there was more than one match in a
149        line, it showed only the first of them. It now behaves in the same way as
150        GNU grep.
152    13. If the -o and -v options were combined for pcregrep, it printed a blank
153        line for every non-matching line. GNU grep prints nothing, and pcregrep now
154        does the same. The return code can be used to tell if there were any
155        non-matching lines.
157    14. Added --file-offsets and --line-offsets to pcregrep.
159    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
160        infinitely looping recursion. The bug was that positive lookaheads were not
161        being skipped when checking for a possible empty match (negative lookaheads
162        and both kinds of lookbehind were skipped).
164    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
165        inclusion of <windows.h> to before rather than after the definition of
166        INVALID_FILE_ATTRIBUTES (patch from David Byron).
168    17. Specifying a possessive quantifier with a specific limit for a Unicode
169        character property caused pcre_compile() to compile bad code, which led at
170        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
171        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
172        caused the error; without that there was no problem.
174    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
176    19. Added --enable-pcretest-libreadline.
178    20. In pcrecpp.cc, the variable 'count' was incremented twice in
179        RE::GlobalReplace(). As a result, the number of replacements returned was
180        double what it should be. I removed one of the increments, but Craig sent a
181        later patch that removed the other one (the right fix) and added unit tests
182        that check the return values (which was not done before).
184    21. Several CMake things:
186        (1) Arranged that, when cmake is used on Unix, the libraries end up with
187            the names libpcre and libpcreposix, not just pcre and pcreposix.
189        (2) The above change means that pcretest and pcregrep are now correctly
190            linked with the newly-built libraries, not previously installed ones.
194    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
195        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
196        UTF-8 newline character). The key issue is that the pattern starts .*;
197        this means that the match must be either at the beginning, or after a
198        newline. The bug was in the code for advancing after a failed match and
199        checking that the new position followed a newline. It was not taking
200        account of UTF-8 characters correctly.
202    23. PCRE was behaving differently from Perl in the way it recognized POSIX
203        character classes. PCRE was not treating the sequence [:...:] as a
204        character class unless the ... were all letters. Perl, however, seems to
205        allow any characters between [: and :], though of course it rejects as
206        unknown any "names" that contain non-letters, because all the known class
207        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
208        for example, whereas PCRE did not - it did not recognize a POSIX character
209        class. This seemed a bit dangerous, so the code has been changed to be
210        closer to Perl. The behaviour is not identical to Perl, because PCRE will
211        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
212        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
213        Perl does, and where it didn't before.
215    24. Rewrite so as to remove the single use of %n from pcregrep because in some
216        Windows environments %n is disabled by default.
219    Version 7.4 21-Sep-07
220    ---------------------
222    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
223        means that a class such as [\s] counted as "explicit reference to CR or
224        LF". That isn't really right - the whole point of the change was to try to
225        help when there was an actual mention of one of the two characters. So now
226        the change happens only if \r or \n (or a literal CR or LF) character is
227        encountered.
229    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
230        of both had grown to the point where there were only 3 bits left.
231        Fortunately, there was spare space in the data structure, and so I have
232        moved the internal flags into a new 16-bit field to free up more option
233        bits.
235    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
236        but did not set the internal JCHANGED flag - either of these is enough to
237        control the way the "get" function works - but the PCRE_INFO_JCHANGED
238        facility is supposed to tell if (?J) was ever used, so now (?J) at the
239        start sets both bits.
241    4.  Added options (at build time, compile time, exec time) to change \R from
242        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
244    5.  doc/pcresyntax.html was missing from the distribution.
246    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
247        compatibility, even though it is no longer used.
249    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
250        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
251        windows.h file is present (where different names are used). [This was
252        reversed later after testing - see 16 below.]
254    8.  Changed all #include <config.h> to #include "config.h". There were also
255        some further <pcre.h> cases that I changed to "pcre.h".
257    9.  When pcregrep was used with the --colour option, it missed the line ending
258        sequence off the lines that it output.
260    10. It was pointed out to me that arrays of string pointers cause lots of
261        relocations when a shared library is dynamically loaded. A technique of
262        using a single long string with a table of offsets can drastically reduce
263        these. I have refactored PCRE in four places to do this. The result is
264        dramatic:
266          Originally:                          290
267          After changing UCP table:            187
268          After changing error message table:   43
269          After changing table of "verbs"       36
270          After changing table of Posix names   22
272        Thanks to the folks working on Gregex for glib for this insight.
274    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
275        unicode-properties was also set.
277    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
279    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
280        checked only for CRLF.
282    14. Added casts to pcretest.c to avoid compiler warnings.
284    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
286    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
287        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
288        entirely. This removes changes made in 7 above.
290    17. The CMake files have been updated, and there is now more information about
291        building with CMake in the NON-UNIX-USE document.
294    Version 7.3 28-Aug-07
295    ---------------------
297     1. In the rejigging of the build system that eventually resulted in 7.1, the
298        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
299        brackets there is not right, since it causes compilers to look for an
300        installed pcre.h, not the version that is in the source that is being
301        compiled (which of course may be different). I have changed it back to:
303          #include "pcre.h"
305        I have a vague recollection that the change was concerned with compiling in
306        different directories, but in the new build system, that is taken care of
307        by the VPATH setting the Makefile.
309     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
310        when the subject happened to end in the byte 0x85 (e.g. if the last
311        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
312        characters but of course it shouldn't be taken as a newline when it is part
313        of another character. The bug was that, for an unlimited repeat of . in
314        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
315        characters when looking for a newline.
317     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
319     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
320        in debug output.
322     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
323        long printing in the pcrecpp unittest when running under MinGW.
325     6. ESC_K was left out of the EBCDIC table.
327     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
328        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
329        limit also applies to "virtual nesting" when a pattern is recursive, and in
330        this case 1000 isn't so big. I have been able to remove this limit at the
331        expense of backing off one optimization in certain circumstances. Normally,
332        when pcre_exec() would call its internal match() function recursively and
333        immediately return the result unconditionally, it uses a "tail recursion"
334        feature to save stack. However, when a subpattern that can match an empty
335        string has an unlimited repetition quantifier, it no longer makes this
336        optimization. That gives it a stack frame in which to save the data for
337        checking that an empty string has been matched. Previously this was taken
338        from the 1000-entry workspace that had been reserved. So now there is no
339        explicit limit, but more stack is used.
341     8. Applied Daniel's patches to solve problems with the import/export magic
342        syntax that is required for Windows, and which was going wrong for the
343        pcreposix and pcrecpp parts of the library. These were overlooked when this
344        problem was solved for the main library.
346     9. There were some crude static tests to avoid integer overflow when computing
347        the size of patterns that contain repeated groups with explicit upper
348        limits. As the maximum quantifier is 65535, the maximum group length was
349        set at 30,000 so that the product of these two numbers did not overflow a
350        32-bit integer. However, it turns out that people want to use groups that
351        are longer than 30,000 bytes (though not repeat them that many times).
352        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
353        made it possible to implement the integer overflow checks in a much more
354        dynamic way, which I have now done. The artificial limitation on group
355        length has been removed - we now have only the limit on the total length of
356        the compiled pattern, which depends on the LINK_SIZE setting.
358    10. Fixed a bug in the documentation for get/copy named substring when
359        duplicate names are permitted. If none of the named substrings are set, the
360        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
361        empty string.
363    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
364        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
365        because the ] is interpreted as the first data character and the
366        terminating ] is not found. PCRE has been made compatible with Perl in this
367        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
368        cause memory overwriting.
370    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
371        string has been matched (to stop an infinite loop). It was not recognizing
372        a conditional subpattern that could match an empty string if that
373        subpattern was within another subpattern. For example, it looped when
374        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
375        condition was not nested. This bug has been fixed.
377    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
378        past the start of the subject in the presence of bytes with the top bit
379        set, for example "\x8aBCD".
381    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
382        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
384    14. Optimized (?!) to (*FAIL).
386    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
387        This restricts code points to be within the range 0 to 0x10FFFF, excluding
388        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
389        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
390        does: it's just the validity check that is more restrictive.
392    16. Inserted checks for integer overflows during escape sequence (backslash)
393        processing, and also fixed erroneous offset values for syntax errors during
394        backslash processing.
396    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
397        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
399    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
400        caused an overrun.
402    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
403        something other than just ASCII characters) inside a group that had an
404        unlimited repeat caused a loop at compile time (while checking to see
405        whether the group could match an empty string).
407    20. Debugging a pattern containing \p or \P could cause a crash. For example,
408        [\P{Any}] did so. (Error in the code for printing property names.)
410    21. An orphan \E inside a character class could cause a crash.
412    22. A repeated capturing bracket such as (A)? could cause a wild memory
413        reference during compilation.
415    23. There are several functions in pcre_compile() that scan along a compiled
416        expression for various reasons (e.g. to see if it's fixed length for look
417        behind). There were bugs in these functions when a repeated \p or \P was
418        present in the pattern. These operators have additional parameters compared
419        with \d, etc, and these were not being taken into account when moving along
420        the compiled data. Specifically:
422        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
423            length.
425        (b) An item such as \pL+ within a repeated group could cause crashes or
426            loops.
428        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
429            "reference to non-existent subpattern" error.
431        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
433    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
434        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
436    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
438    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
439        character were causing crashes (broken optimization).
441    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
442        \p or \P) caused a compile-time loop.
444    28. More problems have arisen in unanchored patterns when CRLF is a valid line
445        break. For example, the unstudied pattern [\r\n]A does not match the string
446        "\r\nA" because change 7.0/46 below moves the current point on by two
447        characters after failing to match at the start. However, the pattern \nA
448        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
449        the same is true. There doesn't seem any very clean way out of this, but
450        what I have chosen to do makes the common cases work: PCRE now takes note
451        of whether there can be an explicit match for \r or \n anywhere in the
452        pattern, and if so, 7.0/46 no longer applies. As part of this change,
453        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
454        pattern has explicit CR or LF references.
456    29. Added (*CR) etc for changing newline setting at start of pattern.
459    Version 7.2 19-Jun-07
460    ---------------------
462     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
463        which is apparently normally available under Windows.
465     2. Re-jig the pcregrep tests with different newline settings in an attempt
466        to make them independent of the local environment's newline setting.
468     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
470     4. Some of the "internals" tests were previously cut out when the link size
471        was not 2, because the output contained actual offsets. The recent new
472        "Z" feature of pcretest means that these can be cut out, making the tests
473        usable with all link sizes.
475     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
476        stack recursion. This gives a massive performance boost under BSD, but just
477        a small improvement under Linux. However, it saves one field in the frame
478        in all cases.
480     6. Added more features from the forthcoming Perl 5.10:
482        (a) (?-n) (where n is a string of digits) is a relative subroutine or
483            recursion call. It refers to the nth most recently opened parentheses.
485        (b) (?+n) is also a relative subroutine call; it refers to the nth next
486            to be opened parentheses.
488        (c) Conditions that refer to capturing parentheses can be specified
489            relatively, for example, (?(-2)... or (?(+3)...
491        (d) \K resets the start of the current match so that everything before
492            is not part of it.
494        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
496        (f) \g{name} is another synonym - part of Perl 5.10's unification of
497            reference syntax.
499        (g) (?| introduces a group in which the numbering of parentheses in each
500            alternative starts with the same number.
502        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
504     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
507     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
508        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
509        for detecting groups that can match an empty string.
511     9. A pattern with a very large number of alternatives (more than several
512        hundred) was running out of internal workspace during the pre-compile
513        phase, where pcre_compile() figures out how much memory will be needed. A
514        bit of new cunning has reduced the workspace needed for groups with
515        alternatives. The 1000-alternative test pattern now uses 12 bytes of
516        workspace instead of running out of the 4096 that are available.
518    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
520    11. Applied patch from Google to remove an optimization that didn't quite work.
521        The report of the bug said:
523          pcrecpp::RE("a*").FullMatch("aaa") matches, while
524          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
525          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
527    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
528        it matched the wrong number of bytes.
531    Version 7.1 24-Apr-07
532  ---------------------  ---------------------
534   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
# Line 126  Version 7.1 12-Mar-07 Line 653  Version 7.1 12-Mar-07
653  16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"  16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
654      in an attempt to make files that differ only in their line terminators      in an attempt to make files that differ only in their line terminators
655      compare equal. This works on Linux.      compare equal. This works on Linux.
657  17. Under certain error circumstances pcregrep might try to free random memory  17. Under certain error circumstances pcregrep might try to free random memory
658      as it exited. This is now fixed, thanks to valgrind.      as it exited. This is now fixed, thanks to valgrind.
660  19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string  19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
661      "abc\r\n\r\n", it found an unwanted second match after the second \r. This      "abc\r\n\r\n", it found an unwanted second match after the second \r. This
662      was because its rules for how to advance for /g after matching an empty      was because its rules for how to advance for /g after matching an empty
663      string did not allow for this case. They now check for it specially.      string at the end of a line did not allow for this case. They now check for
664        it specially.
666    20. pcretest is supposed to handle patterns and data of any length, by
667        extending its buffers when necessary. It was getting this wrong when the
668        buffer for a data line had to be extended.
670    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
671        CRLF as a newline sequence.
673    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
674        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
675        I have nevertheless tidied it up.
677    23. Added some casts to kill warnings from HP-UX ia64 compiler.
679    24. Added a man page for pcre-config.
682  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06

Removed from v.141  
changed lines
  Added in v.325

  ViewVC Help
Powered by ViewVC 1.1.5