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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.189  
changed lines
  Added in v.492

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12