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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.201  
changed lines
  Added in v.503

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12