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

Diff of /code/trunk/ChangeLog

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

revision 150 by ph10, Tue Apr 17 08:22:40 2007 UTC revision 479 by ph10, Sun Jan 3 16:31:39 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.1 12-Mar-07  Version 8.01 11-Dec-09
5    ----------------------
6    
7    1.  If a pattern contained a conditional subpattern with only one branch (in
8        particular, this includes all (DEFINE) patterns), a call to pcre_study()
9        computed the wrong minimum data length (which is of course zero for such
10        subpatterns).
11    
12    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
13        the pattern is reset in the first branch, pcre_compile() failed with
14        "internal error: code overflow at offset...". This happened only when
15        the reset was to the original external option setting. (An optimization
16        abstracts leading options settings into an external setting, which was the
17        cause of this.)
18    
19    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
20        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
21        assertion pattern did not match (meaning that the assertion was true), it
22        was incorrectly treated as false if the SKIP had been reached during the
23        matching. This also applied to assertions used as conditions.
24    
25    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
26        assertion subpattern, including such a pattern used as a condition,
27        unpredictable results occurred, instead of the error return
28        PCRE_ERROR_DFA_UITEM.
29    
30    5.  The C++ GlobalReplace function was not working like Perl for the special
31        situation when an empty string is matched. It now does the fancy magic
32        stuff that is necessary.
33    
34    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
35        removed. (These were left over from very, very early versions of PCRE.)
36    
37    7.  Some cosmetic changes to the code to make life easier when compiling it
38        as part of something else:
39    
40        (a) Change DEBUG to PCRE_DEBUG.
41    
42        (b) In pcre_compile(), rename the member of the "branch_chain" structure
43            called "current" as "current_branch", to prevent a collision with the
44            Linux macro when compiled as a kernel module.
45    
46        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
47            prevent a collision with the Linux macro when compiled as a kernel
48            module.
49    
50    8.  In pcre_compile() there are some checks for integer overflows that used to
51        cast potentially large values to (double). This has been changed to that
52        when building, a check for int64_t is made, and if it is found, it is used
53        instead, thus avoiding the use of floating point arithmetic. (There is no
54        other use of FP in PCRE.) If int64_t is not found, the fallback is to
55        double.
56    
57    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
58        2005 (difference between two addresses compared to an unsigned value).
59    
60    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
61        custom one, because of the following reported problem in Windows:
62    
63          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
64            under Win32.
65          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
66            therefore missing the function definition.
67          - The compiler thus generates a "C" signature for the test function.
68          - The linker fails to find the "C" function.
69          - PCRE fails to configure if asked to do so against libbz2.
70    
71    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
72        messages were output:
73    
74          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
75          rerunning libtoolize, to keep the correct libtool macros in-tree.
76          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
77    
78        I have done both of these things.
79    
80    
81    
82    Version 8.00 19-Oct-09
83    ----------------------
84    
85    1.  The table for translating pcre_compile() error codes into POSIX error codes
86        was out-of-date, and there was no check on the pcre_compile() error code
87        being within the table. This could lead to an OK return being given in
88        error.
89    
90    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
91        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
92        in a Windows environment.
93    
94    3.  The pcregrep --count option prints the count for each file even when it is
95        zero, as does GNU grep. However, pcregrep was also printing all files when
96        --files-with-matches was added. Now, when both options are given, it prints
97        counts only for those files that have at least one match. (GNU grep just
98        prints the file name in this circumstance, but including the count seems
99        more useful - otherwise, why use --count?) Also ensured that the
100        combination -clh just lists non-zero counts, with no names.
101    
102    4.  The long form of the pcregrep -F option was incorrectly implemented as
103        --fixed_strings instead of --fixed-strings. This is an incompatible change,
104        but it seems right to fix it, and I didn't think it was worth preserving
105        the old behaviour.
106    
107    5.  The command line items --regex=pattern and --regexp=pattern were not
108        recognized by pcregrep, which required --regex pattern or --regexp pattern
109        (with a space rather than an '='). The man page documented the '=' forms,
110        which are compatible with GNU grep; these now work.
111    
112    6.  No libpcreposix.pc file was created for pkg-config; there was just
113        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
114    
115    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
116        when UCP support is not needed, by modifying the Python script that
117        generates it from Unicode data files. This should not matter if the module
118        is correctly used as a library, but I received one complaint about 50K of
119        unwanted data. My guess is that the person linked everything into his
120        program rather than using a library. Anyway, it does no harm.
121    
122    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
123        was a minimum greater than 1 for a wide character in a possessive
124        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
125        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
126        character. Chaos in the form of incorrect output or a compiling loop could
127        result.
128    
129    9.  The restrictions on what a pattern can contain when partial matching is
130        requested for pcre_exec() have been removed. All patterns can now be
131        partially matched by this function. In addition, if there are at least two
132        slots in the offset vector, the offset of the earliest inspected character
133        for the match and the offset of the end of the subject are set in them when
134        PCRE_ERROR_PARTIAL is returned.
135    
136    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
137        synonymous with PCRE_PARTIAL, for backwards compatibility, and
138        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
139        and may be more useful for multi-segment matching.
140    
141    11. Partial matching with pcre_exec() is now more intuitive. A partial match
142        used to be given if ever the end of the subject was reached; now it is
143        given only if matching could not proceed because another character was
144        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
145        string "Z", which now yields "no match" instead of "partial match". In the
146        case of pcre_dfa_exec(), "no match" is given if every matching path for the
147        final character ended with (*FAIL).
148    
149    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
150        if the pattern had a "must contain" character that was already found in the
151        earlier partial match, unless partial matching was again requested. For
152        example, with the pattern /dog.(body)?/, the "must contain" character is
153        "g". If the first part-match was for the string "dog", restarting with
154        "sbody" failed. This bug has been fixed.
155    
156    13. The string returned by pcre_dfa_exec() after a partial match has been
157        changed so that it starts at the first inspected character rather than the
158        first character of the match. This makes a difference only if the pattern
159        starts with a lookbehind assertion or \b or \B (\K is not supported by
160        pcre_dfa_exec()). It's an incompatible change, but it makes the two
161        matching functions compatible, and I think it's the right thing to do.
162    
163    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
164        so that the demonstration program is easily available in environments where
165        PCRE has not been installed from source.
166    
167    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
168        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
169        library.
170    
171    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
172        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
173        is not the first non-POSIX option to be added. Clearly some people find
174        these options useful.
175    
176    17. If a caller to the POSIX matching function regexec() passes a non-zero
177        value for nmatch with a NULL value for pmatch, the value of
178        nmatch is forced to zero.
179    
180    18. RunGrepTest did not have a test for the availability of the -u option of
181        the diff command, as RunTest does. It now checks in the same way as
182        RunTest, and also checks for the -b option.
183    
184    19. If an odd number of negated classes containing just a single character
185        interposed, within parentheses, between a forward reference to a named
186        subpattern and the definition of the subpattern, compilation crashed with
187        an internal error, complaining that it could not find the referenced
188        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
189        [The bug was that it was starting one character too far in when skipping
190        over the character class, thus treating the ] as data rather than
191        terminating the class. This meant it could skip too much.]
192    
193    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
194        /g option in pcretest when the pattern contains \K, which makes it possible
195        to have an empty string match not at the start, even when the pattern is
196        anchored. Updated pcretest and pcredemo to use this option.
197    
198    21. If the maximum number of capturing subpatterns in a recursion was greater
199        than the maximum at the outer level, the higher number was returned, but
200        with unset values at the outer level. The correct (outer level) value is
201        now given.
202    
203    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
204        PCRE did not set those parentheses (unlike Perl). I have now found a way to
205        make it do so. The string so far is captured, making this feature
206        compatible with Perl.
207    
208    23. The tests have been re-organized, adding tests 11 and 12, to make it
209        possible to check the Perl 5.10 features against Perl 5.10.
210    
211    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
212        pattern matches a fixed length string. PCRE did not allow this; now it
213        does. Neither allows recursion.
214    
215    25. I finally figured out how to implement a request to provide the minimum
216        length of subject string that was needed in order to match a given pattern.
217        (It was back references and recursion that I had previously got hung up
218        on.) This code has now been added to pcre_study(); it finds a lower bound
219        to the length of subject needed. It is not necessarily the greatest lower
220        bound, but using it to avoid searching strings that are too short does give
221        some useful speed-ups. The value is available to calling programs via
222        pcre_fullinfo().
223    
224    26. While implementing 25, I discovered to my embarrassment that pcretest had
225        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
226        study optimizations had never been tested with that matching function.
227        Oops. What is worse, even when it was passed study data, there was a bug in
228        pcre_dfa_exec() that meant it never actually used it. Double oops. There
229        were also very few tests of studied patterns with pcre_dfa_exec().
230    
231    27. If (?| is used to create subpatterns with duplicate numbers, they are now
232        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
233        on the other side of the coin, they are no longer allowed to have different
234        names, because these cannot be distinguished in PCRE, and this has caused
235        confusion. (This is a difference from Perl.)
236    
237    28. When duplicate subpattern names are present (necessarily with different
238        numbers, as required by 27 above), and a test is made by name in a
239        conditional pattern, either for a subpattern having been matched, or for
240        recursion in such a pattern, all the associated numbered subpatterns are
241        tested, and the overall condition is true if the condition is true for any
242        one of them. This is the way Perl works, and is also more like the way
243        testing by number works.
244    
245    
246    Version 7.9 11-Apr-09
247    ---------------------
248    
249    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
250        (pcretest), all targets were linked against these libraries. This included
251        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
252        libraries. This caused unwanted dependencies to be created. This problem
253        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
254        pcretest is linked with readline.
255    
256    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
257        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
258        moved outside it again, because FALSE and TRUE are already defined in AIX,
259        but BOOL is not.
260    
261    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
262        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
263    
264    4.  The pcregrep documentation said spaces were inserted as well as colons (or
265        hyphens) following file names and line numbers when outputting matching
266        lines. This is not true; no spaces are inserted. I have also clarified the
267        wording for the --colour (or --color) option.
268    
269    5.  In pcregrep, when --colour was used with -o, the list of matching strings
270        was not coloured; this is different to GNU grep, so I have changed it to be
271        the same.
272    
273    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
274        each matching line was coloured. Now it goes on to look for further matches
275        of any of the test patterns, which is the same behaviour as GNU grep.
276    
277    7.  A pattern that could match an empty string could cause pcregrep to loop; it
278        doesn't make sense to accept an empty string match in pcregrep, so I have
279        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
280        seems to be how GNU grep behaves.
281    
282    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
283        start or after a newline", because the conditional assertion was not being
284        correctly handled. The rule now is that both the assertion and what follows
285        in the first alternative must satisfy the test.
286    
287    9.  If auto-callout was enabled in a pattern with a conditional group whose
288        condition was an assertion, PCRE could crash during matching, both with
289        pcre_exec() and pcre_dfa_exec().
290    
291    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
292        used for matching.
293    
294    11. Unicode property support in character classes was not working for
295        characters (bytes) greater than 127 when not in UTF-8 mode.
296    
297    12. Added the -M command line option to pcretest.
298    
299    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
300    
301    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
302    
303    16. Added comments and documentation about mis-use of no_arg in the C++
304        wrapper.
305    
306    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
307        from Martin Jerabek that uses macro names for all relevant character and
308        string constants.
309    
310    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
311        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
312        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
313        these, but not everybody uses configure.
314    
315    19. A conditional group that had only one branch was not being correctly
316        recognized as an item that could match an empty string. This meant that an
317        enclosing group might also not be so recognized, causing infinite looping
318        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
319        with the subject "ab", where knowledge that the repeated group can match
320        nothing is needed in order to break the loop.
321    
322    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
323        exec(), but without supplying a callout function, matching went wrong.
324    
325    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
326        leak if the size of the offset vector was greater than 30. When the vector
327        is smaller, the saved offsets during recursion go onto a local stack
328        vector, but for larger vectors malloc() is used. It was failing to free
329        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
330        error, in fact).
331    
332    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
333        heapframe that is used only when UTF-8 support is enabled. This caused no
334        problem, but was untidy.
335    
336    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
337        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
338        included within another project.
339    
340    24. Steven Van Ingelgem's patches to add more options to the CMake support,
341        slightly modified by me:
342    
343          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
344              not building pcregrep.
345    
346          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
347              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
348    
349    25. Forward references, both numeric and by name, in patterns that made use of
350        duplicate group numbers, could behave incorrectly or give incorrect errors,
351        because when scanning forward to find the reference group, PCRE was not
352        taking into account the duplicate group numbers. A pattern such as
353        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
354    
355    26. Changed a few more instances of "const unsigned char *" to USPTR, making
356        the feature of a custom pointer more persuasive (as requested by a user).
357    
358    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
359        pcretest.c, inside #ifndefs, because it seems they are sometimes already
360        pre-defined.
361    
362    28. Added support for (*UTF8) at the start of a pattern.
363    
364    29. Arrange for flags added by the "release type" setting in CMake to be shown
365        in the configuration summary.
366    
367    
368    Version 7.8 05-Sep-08
369    ---------------------
370    
371    1.  Replaced UCP searching code with optimized version as implemented for Ad
372        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
373        stage table and inline lookup instead of a function, giving speed ups of 2
374        to 5 times on some simple patterns that I tested. Permission was given to
375        distribute the MultiStage2.py script that generates the tables (it's not in
376        the tarball, but is in the Subversion repository).
377    
378    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
379        scripts.
380    
381    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
382        a group with a zero qualifier. The result of the study could be incorrect,
383        or the function might crash, depending on the pattern.
384    
385    4.  Caseless matching was not working for non-ASCII characters in back
386        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
387        It now works when Unicode Property Support is available.
388    
389    5.  In pcretest, an escape such as \x{de} in the data was always generating
390        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
391        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
392        truncation.
393    
394    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
395    
396    7.  Added two (int) casts to pcregrep when printing the difference of two
397        pointers, in case they are 64-bit values.
398    
399    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
400        test 2 if it fails.
401    
402    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
403        and a #define of that name to empty if it is not externally set. This is to
404        allow users of MSVC to set it if necessary.
405    
406    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
407        the convenience functions in the pcre_get.c source file.
408    
409    11. An option change at the start of a pattern that had top-level alternatives
410        could cause overwriting and/or a crash. This command provoked a crash in
411        some environments:
412    
413          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
414    
415        This potential security problem was recorded as CVE-2008-2371.
416    
417    12. For a pattern where the match had to start at the beginning or immediately
418        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
419        pcre_dfa_exec() could read past the end of the passed subject if there was
420        no match. To help with detecting such bugs (e.g. with valgrind), I modified
421        pcretest so that it places the subject at the end of its malloc-ed buffer.
422    
423    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
424        exec() might read past the end of the data buffer in UTF-8 mode.
425    
426    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
427        the data contained the byte 0x85 as part of a UTF-8 character within its
428        first line. This applied both to normal and DFA matching.
429    
430    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
431        /^[^d]*?$/8 failed to match "abc".
432    
433    16. Added a missing copyright notice to pcrecpp_internal.h.
434    
435    17. Make it more clear in the documentation that values returned from
436        pcre_exec() in ovector are byte offsets, not character counts.
437    
438    18. Tidied a few places to stop certain compilers from issuing warnings.
439    
440    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
441        supplied by Stefan Weber. I made a further small update for 7.8 because
442        there is a change of source arrangements: the pcre_searchfuncs.c module is
443        replaced by pcre_ucd.c.
444    
445    
446    Version 7.7 07-May-08
447    ---------------------
448    
449    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
450        a string to a long long, pretend we don't even have a long long." This is
451        done by checking for the strtoq, strtoll, and _strtoi64 functions.
452    
453    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
454        pre-7.6 versions, which defined a global no_arg variable instead of putting
455        it in the RE class. (See also #8 below.)
456    
457    3.  Remove a line of dead code, identified by coverity and reported by Nuno
458        Lopes.
459    
460    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
461    
462        (1) The include/exclude patterns were being applied to the whole pathnames
463            of files, instead of just to the final components.
464    
465        (2) If there was more than one level of directory, the subdirectories were
466            skipped unless they satisfied the include/exclude conditions. This is
467            inconsistent with GNU grep (and could even be seen as contrary to the
468            pcregrep specification - which I improved to make it absolutely clear).
469            The action now is always to scan all levels of directory, and just
470            apply the include/exclude patterns to regular files.
471    
472    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
473        --exclude_dir in the tests to avoid scanning .svn directories.
474    
475    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
476        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
477        doesn't support NULs in patterns.
478    
479    7.  Added some missing "const"s to declarations of static tables in
480        pcre_compile.c and pcre_dfa_exec.c.
481    
482    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
483        caused by fix #2  above. (Subsequently also a second patch to fix the
484        first patch. And a third patch - this was a messy problem.)
485    
486    9.  Applied Craig's patch to remove the use of push_back().
487    
488    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
489        matching function regexec().
490    
491    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
492        which, however, unlike Perl's \g{...}, are subroutine calls, not back
493        references. PCRE supports relative numbers with this syntax (I don't think
494        Oniguruma does).
495    
496    12. Previously, a group with a zero repeat such as (...){0} was completely
497        omitted from the compiled regex. However, this means that if the group
498        was called as a subroutine from elsewhere in the pattern, things went wrong
499        (an internal error was given). Such groups are now left in the compiled
500        pattern, with a new opcode that causes them to be skipped at execution
501        time.
502    
503    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
504        to the way PCRE behaves:
505    
506        (a) A lone ] character is dis-allowed (Perl treats it as data).
507    
508        (b) A back reference to an unmatched subpattern matches an empty string
509            (Perl fails the current match path).
510    
511        (c) A data ] in a character class must be notated as \] because if the
512            first data character in a class is ], it defines an empty class. (In
513            Perl it is not possible to have an empty class.) The empty class []
514            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
515            The negative empty class [^] matches any one character, independently
516            of the DOTALL setting.
517    
518    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
519        non-existent subpattern following a character class starting with ']' and
520        containing () gave an internal compiling error instead of "reference to
521        non-existent subpattern". Fortunately, when the pattern did exist, the
522        compiled code was correct. (When scanning forwards to check for the
523        existencd of the subpattern, it was treating the data ']' as terminating
524        the class, so got the count wrong. When actually compiling, the reference
525        was subsequently set up correctly.)
526    
527    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
528        it was being rejected as not supported by pcre_dfa_exec(), even though
529        other assertions are supported. I have made pcre_dfa_exec() support
530        (*FAIL).
531    
532    16. The implementation of 13c above involved the invention of a new opcode,
533        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
534        cannot be changed at match time, I realized I could make a small
535        improvement to matching performance by compiling OP_ALLANY instead of
536        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
537        on the OP_ANY path.
538    
539    17. Compiling pcretest on Windows with readline support failed without the
540        following two fixes: (1) Make the unistd.h include conditional on
541        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
542    
543    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
544        ncurses library to be included for pcretest when ReadLine support is
545        requested, but also to allow for it to be overridden. This patch came from
546        Daniel Bergström.
547    
548    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
549        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
550        any errors with the current Unicode tables. Thanks to Peter Kankowski for
551        spotting this.
552    
553    
554    Version 7.6 28-Jan-08
555    ---------------------
556    
557    1.  A character class containing a very large number of characters with
558        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
559        overflow.
560    
561    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
562        HAVE_LONG_LONG is not defined.
563    
564    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
565        bring them up to date and include new features. This patch includes:
566    
567        - Fixed PH's badly added libz and libbz2 support.
568        - Fixed a problem with static linking.
569        - Added pcredemo. [But later removed - see 7 below.]
570        - Fixed dftables problem and added an option.
571        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
572            HAVE_LONG_LONG.
573        - Added readline support for pcretest.
574        - Added an listing of the option settings after cmake has run.
575    
576    4.  A user submitted a patch to Makefile that makes it easy to create
577        "pcre.dll" under mingw when using Configure/Make. I added stuff to
578        Makefile.am that cause it to include this special target, without
579        affecting anything else. Note that the same mingw target plus all
580        the other distribution libraries and programs are now supported
581        when configuring with CMake (see 6 below) instead of with
582        Configure/Make.
583    
584    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
585        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
586        exported in the Windows port". It has not yet been confirmed that the patch
587        solves the problem, but it does no harm.
588    
589    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
590        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
591        with CMake, and also correct the comment about stack recursion.
592    
593    7.  Remove the automatic building of pcredemo from the ./configure system and
594        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
595        of a program that users should build themselves after PCRE is installed, so
596        building it automatically is not really right. What is more, it gave
597        trouble in some build environments.
598    
599    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
600    
601    
602    Version 7.5 10-Jan-08
603    ---------------------
604    
605    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
606        values in parens when parsing an RE using the C++ wrapper."
607    
608    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
609        Characters greater than 255 were excluded from the class instead of being
610        included.
611    
612    3.  The same bug as (2) above applied to negated POSIX classes such as
613        [:^space:].
614    
615    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
616        defined or documented. It seems to have been a typo for PCRE_STATIC, so
617        I have changed it.
618    
619    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
620        first named subpattern) and a construct such as (?&a) would reference the
621        first named subpattern whose name started with "a" (in other words, the
622        length check was missing). Both these problems are fixed. "Subpattern name
623        expected" is now given for (?&) (a zero-length name), and this patch also
624        makes it give the same error for \k'' (previously it complained that that
625        was a reference to a non-existent subpattern).
626    
627    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
628        this is right because (?- can be followed by option settings as well as by
629        digits. I have, however, made the messages clearer.
630    
631    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
632        than the number used in the conditional) now cause a compile-time error.
633        This is actually not compatible with Perl, which accepts such patterns, but
634        treats the conditional as always being FALSE (as PCRE used to), but it
635        seems to me that giving a diagnostic is better.
636    
637    8.  Change "alphameric" to the more common word "alphanumeric" in comments
638        and messages.
639    
640    9.  Fix two occurrences of "backslash" in comments that should have been
641        "backspace".
642    
643    10. Remove two redundant lines of code that can never be obeyed (their function
644        was moved elsewhere).
645    
646    11. The program that makes PCRE's Unicode character property table had a bug
647        which caused it to generate incorrect table entries for sequences of
648        characters that have the same character type, but are in different scripts.
649        It amalgamated them into a single range, with the script of the first of
650        them. In other words, some characters were in the wrong script. There were
651        thirteen such cases, affecting characters in the following ranges:
652    
653          U+002b0 - U+002c1
654          U+0060c - U+0060d
655          U+0061e - U+00612
656          U+0064b - U+0065e
657          U+0074d - U+0076d
658          U+01800 - U+01805
659          U+01d00 - U+01d77
660          U+01d9b - U+01dbf
661          U+0200b - U+0200f
662          U+030fc - U+030fe
663          U+03260 - U+0327f
664          U+0fb46 - U+0fbb1
665          U+10450 - U+1049d
666    
667    12. The -o option (show only the matching part of a line) for pcregrep was not
668        compatible with GNU grep in that, if there was more than one match in a
669        line, it showed only the first of them. It now behaves in the same way as
670        GNU grep.
671    
672    13. If the -o and -v options were combined for pcregrep, it printed a blank
673        line for every non-matching line. GNU grep prints nothing, and pcregrep now
674        does the same. The return code can be used to tell if there were any
675        non-matching lines.
676    
677    14. Added --file-offsets and --line-offsets to pcregrep.
678    
679    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
680        infinitely looping recursion. The bug was that positive lookaheads were not
681        being skipped when checking for a possible empty match (negative lookaheads
682        and both kinds of lookbehind were skipped).
683    
684    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
685        inclusion of <windows.h> to before rather than after the definition of
686        INVALID_FILE_ATTRIBUTES (patch from David Byron).
687    
688    17. Specifying a possessive quantifier with a specific limit for a Unicode
689        character property caused pcre_compile() to compile bad code, which led at
690        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
691        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
692        caused the error; without that there was no problem.
693    
694    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
695    
696    19. Added --enable-pcretest-libreadline.
697    
698    20. In pcrecpp.cc, the variable 'count' was incremented twice in
699        RE::GlobalReplace(). As a result, the number of replacements returned was
700        double what it should be. I removed one of the increments, but Craig sent a
701        later patch that removed the other one (the right fix) and added unit tests
702        that check the return values (which was not done before).
703    
704    21. Several CMake things:
705    
706        (1) Arranged that, when cmake is used on Unix, the libraries end up with
707            the names libpcre and libpcreposix, not just pcre and pcreposix.
708    
709        (2) The above change means that pcretest and pcregrep are now correctly
710            linked with the newly-built libraries, not previously installed ones.
711    
712        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
713    
714    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
715        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
716        UTF-8 newline character). The key issue is that the pattern starts .*;
717        this means that the match must be either at the beginning, or after a
718        newline. The bug was in the code for advancing after a failed match and
719        checking that the new position followed a newline. It was not taking
720        account of UTF-8 characters correctly.
721    
722    23. PCRE was behaving differently from Perl in the way it recognized POSIX
723        character classes. PCRE was not treating the sequence [:...:] as a
724        character class unless the ... were all letters. Perl, however, seems to
725        allow any characters between [: and :], though of course it rejects as
726        unknown any "names" that contain non-letters, because all the known class
727        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
728        for example, whereas PCRE did not - it did not recognize a POSIX character
729        class. This seemed a bit dangerous, so the code has been changed to be
730        closer to Perl. The behaviour is not identical to Perl, because PCRE will
731        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
732        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
733        Perl does, and where it didn't before.
734    
735    24. Rewrite so as to remove the single use of %n from pcregrep because in some
736        Windows environments %n is disabled by default.
737    
738    
739    Version 7.4 21-Sep-07
740    ---------------------
741    
742    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
743        means that a class such as [\s] counted as "explicit reference to CR or
744        LF". That isn't really right - the whole point of the change was to try to
745        help when there was an actual mention of one of the two characters. So now
746        the change happens only if \r or \n (or a literal CR or LF) character is
747        encountered.
748    
749    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
750        of both had grown to the point where there were only 3 bits left.
751        Fortunately, there was spare space in the data structure, and so I have
752        moved the internal flags into a new 16-bit field to free up more option
753        bits.
754    
755    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
756        but did not set the internal JCHANGED flag - either of these is enough to
757        control the way the "get" function works - but the PCRE_INFO_JCHANGED
758        facility is supposed to tell if (?J) was ever used, so now (?J) at the
759        start sets both bits.
760    
761    4.  Added options (at build time, compile time, exec time) to change \R from
762        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
763    
764    5.  doc/pcresyntax.html was missing from the distribution.
765    
766    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
767        compatibility, even though it is no longer used.
768    
769    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
770        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
771        windows.h file is present (where different names are used). [This was
772        reversed later after testing - see 16 below.]
773    
774    8.  Changed all #include <config.h> to #include "config.h". There were also
775        some further <pcre.h> cases that I changed to "pcre.h".
776    
777    9.  When pcregrep was used with the --colour option, it missed the line ending
778        sequence off the lines that it output.
779    
780    10. It was pointed out to me that arrays of string pointers cause lots of
781        relocations when a shared library is dynamically loaded. A technique of
782        using a single long string with a table of offsets can drastically reduce
783        these. I have refactored PCRE in four places to do this. The result is
784        dramatic:
785    
786          Originally:                          290
787          After changing UCP table:            187
788          After changing error message table:   43
789          After changing table of "verbs"       36
790          After changing table of Posix names   22
791    
792        Thanks to the folks working on Gregex for glib for this insight.
793    
794    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
795        unicode-properties was also set.
796    
797    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
798    
799    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
800        checked only for CRLF.
801    
802    14. Added casts to pcretest.c to avoid compiler warnings.
803    
804    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
805    
806    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
807        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
808        entirely. This removes changes made in 7 above.
809    
810    17. The CMake files have been updated, and there is now more information about
811        building with CMake in the NON-UNIX-USE document.
812    
813    
814    Version 7.3 28-Aug-07
815    ---------------------
816    
817     1. In the rejigging of the build system that eventually resulted in 7.1, the
818        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
819        brackets there is not right, since it causes compilers to look for an
820        installed pcre.h, not the version that is in the source that is being
821        compiled (which of course may be different). I have changed it back to:
822    
823          #include "pcre.h"
824    
825        I have a vague recollection that the change was concerned with compiling in
826        different directories, but in the new build system, that is taken care of
827        by the VPATH setting the Makefile.
828    
829     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
830        when the subject happened to end in the byte 0x85 (e.g. if the last
831        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
832        characters but of course it shouldn't be taken as a newline when it is part
833        of another character. The bug was that, for an unlimited repeat of . in
834        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
835        characters when looking for a newline.
836    
837     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
838    
839     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
840        in debug output.
841    
842     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
843        long printing in the pcrecpp unittest when running under MinGW.
844    
845     6. ESC_K was left out of the EBCDIC table.
846    
847     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
848        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
849        limit also applies to "virtual nesting" when a pattern is recursive, and in
850        this case 1000 isn't so big. I have been able to remove this limit at the
851        expense of backing off one optimization in certain circumstances. Normally,
852        when pcre_exec() would call its internal match() function recursively and
853        immediately return the result unconditionally, it uses a "tail recursion"
854        feature to save stack. However, when a subpattern that can match an empty
855        string has an unlimited repetition quantifier, it no longer makes this
856        optimization. That gives it a stack frame in which to save the data for
857        checking that an empty string has been matched. Previously this was taken
858        from the 1000-entry workspace that had been reserved. So now there is no
859        explicit limit, but more stack is used.
860    
861     8. Applied Daniel's patches to solve problems with the import/export magic
862        syntax that is required for Windows, and which was going wrong for the
863        pcreposix and pcrecpp parts of the library. These were overlooked when this
864        problem was solved for the main library.
865    
866     9. There were some crude static tests to avoid integer overflow when computing
867        the size of patterns that contain repeated groups with explicit upper
868        limits. As the maximum quantifier is 65535, the maximum group length was
869        set at 30,000 so that the product of these two numbers did not overflow a
870        32-bit integer. However, it turns out that people want to use groups that
871        are longer than 30,000 bytes (though not repeat them that many times).
872        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
873        made it possible to implement the integer overflow checks in a much more
874        dynamic way, which I have now done. The artificial limitation on group
875        length has been removed - we now have only the limit on the total length of
876        the compiled pattern, which depends on the LINK_SIZE setting.
877    
878    10. Fixed a bug in the documentation for get/copy named substring when
879        duplicate names are permitted. If none of the named substrings are set, the
880        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
881        empty string.
882    
883    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
884        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
885        because the ] is interpreted as the first data character and the
886        terminating ] is not found. PCRE has been made compatible with Perl in this
887        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
888        cause memory overwriting.
889    
890    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
891        string has been matched (to stop an infinite loop). It was not recognizing
892        a conditional subpattern that could match an empty string if that
893        subpattern was within another subpattern. For example, it looped when
894        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
895        condition was not nested. This bug has been fixed.
896    
897    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
898        past the start of the subject in the presence of bytes with the top bit
899        set, for example "\x8aBCD".
900    
901    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
902        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
903    
904    14. Optimized (?!) to (*FAIL).
905    
906    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
907        This restricts code points to be within the range 0 to 0x10FFFF, excluding
908        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
909        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
910        does: it's just the validity check that is more restrictive.
911    
912    16. Inserted checks for integer overflows during escape sequence (backslash)
913        processing, and also fixed erroneous offset values for syntax errors during
914        backslash processing.
915    
916    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
917        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
918    
919    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
920        caused an overrun.
921    
922    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
923        something other than just ASCII characters) inside a group that had an
924        unlimited repeat caused a loop at compile time (while checking to see
925        whether the group could match an empty string).
926    
927    20. Debugging a pattern containing \p or \P could cause a crash. For example,
928        [\P{Any}] did so. (Error in the code for printing property names.)
929    
930    21. An orphan \E inside a character class could cause a crash.
931    
932    22. A repeated capturing bracket such as (A)? could cause a wild memory
933        reference during compilation.
934    
935    23. There are several functions in pcre_compile() that scan along a compiled
936        expression for various reasons (e.g. to see if it's fixed length for look
937        behind). There were bugs in these functions when a repeated \p or \P was
938        present in the pattern. These operators have additional parameters compared
939        with \d, etc, and these were not being taken into account when moving along
940        the compiled data. Specifically:
941    
942        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
943            length.
944    
945        (b) An item such as \pL+ within a repeated group could cause crashes or
946            loops.
947    
948        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
949            "reference to non-existent subpattern" error.
950    
951        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
952    
953    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
954        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
955    
956    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
957    
958    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
959        character were causing crashes (broken optimization).
960    
961    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
962        \p or \P) caused a compile-time loop.
963    
964    28. More problems have arisen in unanchored patterns when CRLF is a valid line
965        break. For example, the unstudied pattern [\r\n]A does not match the string
966        "\r\nA" because change 7.0/46 below moves the current point on by two
967        characters after failing to match at the start. However, the pattern \nA
968        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
969        the same is true. There doesn't seem any very clean way out of this, but
970        what I have chosen to do makes the common cases work: PCRE now takes note
971        of whether there can be an explicit match for \r or \n anywhere in the
972        pattern, and if so, 7.0/46 no longer applies. As part of this change,
973        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
974        pattern has explicit CR or LF references.
975    
976    29. Added (*CR) etc for changing newline setting at start of pattern.
977    
978    
979    Version 7.2 19-Jun-07
980    ---------------------
981    
982     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
983        which is apparently normally available under Windows.
984    
985     2. Re-jig the pcregrep tests with different newline settings in an attempt
986        to make them independent of the local environment's newline setting.
987    
988     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
989    
990     4. Some of the "internals" tests were previously cut out when the link size
991        was not 2, because the output contained actual offsets. The recent new
992        "Z" feature of pcretest means that these can be cut out, making the tests
993        usable with all link sizes.
994    
995     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
996        stack recursion. This gives a massive performance boost under BSD, but just
997        a small improvement under Linux. However, it saves one field in the frame
998        in all cases.
999    
1000     6. Added more features from the forthcoming Perl 5.10:
1001    
1002        (a) (?-n) (where n is a string of digits) is a relative subroutine or
1003            recursion call. It refers to the nth most recently opened parentheses.
1004    
1005        (b) (?+n) is also a relative subroutine call; it refers to the nth next
1006            to be opened parentheses.
1007    
1008        (c) Conditions that refer to capturing parentheses can be specified
1009            relatively, for example, (?(-2)... or (?(+3)...
1010    
1011        (d) \K resets the start of the current match so that everything before
1012            is not part of it.
1013    
1014        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1015    
1016        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1017            reference syntax.
1018    
1019        (g) (?| introduces a group in which the numbering of parentheses in each
1020            alternative starts with the same number.
1021    
1022        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1023    
1024     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1025        PCRE_INFO_JCHANGED.
1026    
1027     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1028        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1029        for detecting groups that can match an empty string.
1030    
1031     9. A pattern with a very large number of alternatives (more than several
1032        hundred) was running out of internal workspace during the pre-compile
1033        phase, where pcre_compile() figures out how much memory will be needed. A
1034        bit of new cunning has reduced the workspace needed for groups with
1035        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1036        workspace instead of running out of the 4096 that are available.
1037    
1038    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1039    
1040    11. Applied patch from Google to remove an optimization that didn't quite work.
1041        The report of the bug said:
1042    
1043          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1044          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1045          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1046    
1047    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1048        it matched the wrong number of bytes.
1049    
1050    
1051    Version 7.1 24-Apr-07
1052  ---------------------  ---------------------
1053    
1054   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 143  Version 7.1 12-Mar-07 Line 1190  Version 7.1 12-Mar-07
1190  21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or  21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1191      CRLF as a newline sequence.      CRLF as a newline sequence.
1192    
1193    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1194        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1195        I have nevertheless tidied it up.
1196    
1197    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1198    
1199    24. Added a man page for pcre-config.
1200    
1201    
1202  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
1203  ---------------------  ---------------------

Legend:
Removed from v.150  
changed lines
  Added in v.479

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12