ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.207  
changed lines
  Added in v.513

  ViewVC Help
Powered by ViewVC 1.1.5