ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.197  
changed lines
  Added in v.511

  ViewVC Help
Powered by ViewVC 1.1.5