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

Diff of /code/trunk/ChangeLog

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

revision 323 by ph10, Wed Mar 5 17:23:42 2008 UTC revision 484 by ph10, Mon Jan 4 17:11:54 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 05-Mar-08  Version 8.01 11-Dec-09
5    ----------------------
6    
7    1.  If a pattern contained a conditional subpattern with only one branch (in
8        particular, this includes all (DEFINE) patterns), a call to pcre_study()
9        computed the wrong minimum data length (which is of course zero for such
10        subpatterns).
11    
12    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
13        the pattern is reset in the first branch, pcre_compile() failed with
14        "internal error: code overflow at offset...". This happened only when
15        the reset was to the original external option setting. (An optimization
16        abstracts leading options settings into an external setting, which was the
17        cause of this.)
18    
19    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
20        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
21        assertion pattern did not match (meaning that the assertion was true), it
22        was incorrectly treated as false if the SKIP had been reached during the
23        matching. This also applied to assertions used as conditions.
24    
25    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
26        assertion subpattern, including such a pattern used as a condition,
27        unpredictable results occurred, instead of the error return
28        PCRE_ERROR_DFA_UITEM.
29    
30    5.  The C++ GlobalReplace function was not working like Perl for the special
31        situation when an empty string is matched. It now does the fancy magic
32        stuff that is necessary.
33    
34    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
35        removed. (These were left over from very, very early versions of PCRE.)
36    
37    7.  Some cosmetic changes to the code to make life easier when compiling it
38        as part of something else:
39    
40        (a) Change DEBUG to PCRE_DEBUG.
41    
42        (b) In pcre_compile(), rename the member of the "branch_chain" structure
43            called "current" as "current_branch", to prevent a collision with the
44            Linux macro when compiled as a kernel module.
45    
46        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
47            prevent a collision with the Linux macro when compiled as a kernel
48            module.
49    
50    8.  In pcre_compile() there are some checks for integer overflows that used to
51        cast potentially large values to (double). This has been changed to that
52        when building, a check for int64_t is made, and if it is found, it is used
53        instead, thus avoiding the use of floating point arithmetic. (There is no
54        other use of FP in PCRE.) If int64_t is not found, the fallback is to
55        double.
56    
57    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
58        2005 (difference between two addresses compared to an unsigned value).
59    
60    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
61        custom one, because of the following reported problem in Windows:
62    
63          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
64            under Win32.
65          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
66            therefore missing the function definition.
67          - The compiler thus generates a "C" signature for the test function.
68          - The linker fails to find the "C" function.
69          - PCRE fails to configure if asked to do so against libbz2.
70    
71    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
72        messages were output:
73    
74          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
75          rerunning libtoolize, to keep the correct libtool macros in-tree.
76          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
77    
78        I have done both of these things.
79    
80    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
81        most of the time, it *can* run out if it is given a pattern that contains a
82        runaway infinite recursion. I updated the discussion in the pcrestack man
83        page.
84    
85    13. Now that we have gone to the x.xx style of version numbers, the minor
86        version may start with zero. Using 08 or 09 is a bad idea because users
87        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
88        interpreted as invalid octal numbers. I've updated the previous comment in
89        configure.ac, and also added a check that gives an error if 08 or 09 are
90        used.
91    
92    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
93        causing partial matching to fail when the end of the subject matched \W
94        in a UTF-8 pattern where \W was quantified with a minimum of 3.
95    
96    15. There were some discrepancies between the declarations in pcre_internal.h
97        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
98        their definitions. The declarations used "const uschar *" and the
99        definitions used USPTR. Even though USPTR is normally defined as "const
100        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
101        reported that: "This difference in casting confuses some C++ compilers, for
102        example, SunCC recognizes above declarations as different functions and
103        generates broken code for hbpcre." I have changed the declarations to use
104        USPTR.
105    
106    16. GNU libtool is named differently on some systems. The autogen.sh script now
107        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
108        (FreeBSD).
109    
110    
111    
112    Version 8.00 19-Oct-09
113    ----------------------
114    
115    1.  The table for translating pcre_compile() error codes into POSIX error codes
116        was out-of-date, and there was no check on the pcre_compile() error code
117        being within the table. This could lead to an OK return being given in
118        error.
119    
120    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
121        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
122        in a Windows environment.
123    
124    3.  The pcregrep --count option prints the count for each file even when it is
125        zero, as does GNU grep. However, pcregrep was also printing all files when
126        --files-with-matches was added. Now, when both options are given, it prints
127        counts only for those files that have at least one match. (GNU grep just
128        prints the file name in this circumstance, but including the count seems
129        more useful - otherwise, why use --count?) Also ensured that the
130        combination -clh just lists non-zero counts, with no names.
131    
132    4.  The long form of the pcregrep -F option was incorrectly implemented as
133        --fixed_strings instead of --fixed-strings. This is an incompatible change,
134        but it seems right to fix it, and I didn't think it was worth preserving
135        the old behaviour.
136    
137    5.  The command line items --regex=pattern and --regexp=pattern were not
138        recognized by pcregrep, which required --regex pattern or --regexp pattern
139        (with a space rather than an '='). The man page documented the '=' forms,
140        which are compatible with GNU grep; these now work.
141    
142    6.  No libpcreposix.pc file was created for pkg-config; there was just
143        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
144    
145    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
146        when UCP support is not needed, by modifying the Python script that
147        generates it from Unicode data files. This should not matter if the module
148        is correctly used as a library, but I received one complaint about 50K of
149        unwanted data. My guess is that the person linked everything into his
150        program rather than using a library. Anyway, it does no harm.
151    
152    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
153        was a minimum greater than 1 for a wide character in a possessive
154        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
155        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
156        character. Chaos in the form of incorrect output or a compiling loop could
157        result.
158    
159    9.  The restrictions on what a pattern can contain when partial matching is
160        requested for pcre_exec() have been removed. All patterns can now be
161        partially matched by this function. In addition, if there are at least two
162        slots in the offset vector, the offset of the earliest inspected character
163        for the match and the offset of the end of the subject are set in them when
164        PCRE_ERROR_PARTIAL is returned.
165    
166    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
167        synonymous with PCRE_PARTIAL, for backwards compatibility, and
168        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
169        and may be more useful for multi-segment matching.
170    
171    11. Partial matching with pcre_exec() is now more intuitive. A partial match
172        used to be given if ever the end of the subject was reached; now it is
173        given only if matching could not proceed because another character was
174        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
175        string "Z", which now yields "no match" instead of "partial match". In the
176        case of pcre_dfa_exec(), "no match" is given if every matching path for the
177        final character ended with (*FAIL).
178    
179    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
180        if the pattern had a "must contain" character that was already found in the
181        earlier partial match, unless partial matching was again requested. For
182        example, with the pattern /dog.(body)?/, the "must contain" character is
183        "g". If the first part-match was for the string "dog", restarting with
184        "sbody" failed. This bug has been fixed.
185    
186    13. The string returned by pcre_dfa_exec() after a partial match has been
187        changed so that it starts at the first inspected character rather than the
188        first character of the match. This makes a difference only if the pattern
189        starts with a lookbehind assertion or \b or \B (\K is not supported by
190        pcre_dfa_exec()). It's an incompatible change, but it makes the two
191        matching functions compatible, and I think it's the right thing to do.
192    
193    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
194        so that the demonstration program is easily available in environments where
195        PCRE has not been installed from source.
196    
197    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
198        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
199        library.
200    
201    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
202        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
203        is not the first non-POSIX option to be added. Clearly some people find
204        these options useful.
205    
206    17. If a caller to the POSIX matching function regexec() passes a non-zero
207        value for nmatch with a NULL value for pmatch, the value of
208        nmatch is forced to zero.
209    
210    18. RunGrepTest did not have a test for the availability of the -u option of
211        the diff command, as RunTest does. It now checks in the same way as
212        RunTest, and also checks for the -b option.
213    
214    19. If an odd number of negated classes containing just a single character
215        interposed, within parentheses, between a forward reference to a named
216        subpattern and the definition of the subpattern, compilation crashed with
217        an internal error, complaining that it could not find the referenced
218        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
219        [The bug was that it was starting one character too far in when skipping
220        over the character class, thus treating the ] as data rather than
221        terminating the class. This meant it could skip too much.]
222    
223    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
224        /g option in pcretest when the pattern contains \K, which makes it possible
225        to have an empty string match not at the start, even when the pattern is
226        anchored. Updated pcretest and pcredemo to use this option.
227    
228    21. If the maximum number of capturing subpatterns in a recursion was greater
229        than the maximum at the outer level, the higher number was returned, but
230        with unset values at the outer level. The correct (outer level) value is
231        now given.
232    
233    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
234        PCRE did not set those parentheses (unlike Perl). I have now found a way to
235        make it do so. The string so far is captured, making this feature
236        compatible with Perl.
237    
238    23. The tests have been re-organized, adding tests 11 and 12, to make it
239        possible to check the Perl 5.10 features against Perl 5.10.
240    
241    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
242        pattern matches a fixed length string. PCRE did not allow this; now it
243        does. Neither allows recursion.
244    
245    25. I finally figured out how to implement a request to provide the minimum
246        length of subject string that was needed in order to match a given pattern.
247        (It was back references and recursion that I had previously got hung up
248        on.) This code has now been added to pcre_study(); it finds a lower bound
249        to the length of subject needed. It is not necessarily the greatest lower
250        bound, but using it to avoid searching strings that are too short does give
251        some useful speed-ups. The value is available to calling programs via
252        pcre_fullinfo().
253    
254    26. While implementing 25, I discovered to my embarrassment that pcretest had
255        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
256        study optimizations had never been tested with that matching function.
257        Oops. What is worse, even when it was passed study data, there was a bug in
258        pcre_dfa_exec() that meant it never actually used it. Double oops. There
259        were also very few tests of studied patterns with pcre_dfa_exec().
260    
261    27. If (?| is used to create subpatterns with duplicate numbers, they are now
262        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
263        on the other side of the coin, they are no longer allowed to have different
264        names, because these cannot be distinguished in PCRE, and this has caused
265        confusion. (This is a difference from Perl.)
266    
267    28. When duplicate subpattern names are present (necessarily with different
268        numbers, as required by 27 above), and a test is made by name in a
269        conditional pattern, either for a subpattern having been matched, or for
270        recursion in such a pattern, all the associated numbered subpatterns are
271        tested, and the overall condition is true if the condition is true for any
272        one of them. This is the way Perl works, and is also more like the way
273        testing by number works.
274    
275    
276    Version 7.9 11-Apr-09
277    ---------------------
278    
279    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
280        (pcretest), all targets were linked against these libraries. This included
281        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
282        libraries. This caused unwanted dependencies to be created. This problem
283        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
284        pcretest is linked with readline.
285    
286    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
287        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
288        moved outside it again, because FALSE and TRUE are already defined in AIX,
289        but BOOL is not.
290    
291    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
292        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
293    
294    4.  The pcregrep documentation said spaces were inserted as well as colons (or
295        hyphens) following file names and line numbers when outputting matching
296        lines. This is not true; no spaces are inserted. I have also clarified the
297        wording for the --colour (or --color) option.
298    
299    5.  In pcregrep, when --colour was used with -o, the list of matching strings
300        was not coloured; this is different to GNU grep, so I have changed it to be
301        the same.
302    
303    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
304        each matching line was coloured. Now it goes on to look for further matches
305        of any of the test patterns, which is the same behaviour as GNU grep.
306    
307    7.  A pattern that could match an empty string could cause pcregrep to loop; it
308        doesn't make sense to accept an empty string match in pcregrep, so I have
309        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
310        seems to be how GNU grep behaves.
311    
312    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
313        start or after a newline", because the conditional assertion was not being
314        correctly handled. The rule now is that both the assertion and what follows
315        in the first alternative must satisfy the test.
316    
317    9.  If auto-callout was enabled in a pattern with a conditional group whose
318        condition was an assertion, PCRE could crash during matching, both with
319        pcre_exec() and pcre_dfa_exec().
320    
321    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
322        used for matching.
323    
324    11. Unicode property support in character classes was not working for
325        characters (bytes) greater than 127 when not in UTF-8 mode.
326    
327    12. Added the -M command line option to pcretest.
328    
329    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
330    
331    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
332    
333    16. Added comments and documentation about mis-use of no_arg in the C++
334        wrapper.
335    
336    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
337        from Martin Jerabek that uses macro names for all relevant character and
338        string constants.
339    
340    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
341        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
342        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
343        these, but not everybody uses configure.
344    
345    19. A conditional group that had only one branch was not being correctly
346        recognized as an item that could match an empty string. This meant that an
347        enclosing group might also not be so recognized, causing infinite looping
348        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
349        with the subject "ab", where knowledge that the repeated group can match
350        nothing is needed in order to break the loop.
351    
352    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
353        exec(), but without supplying a callout function, matching went wrong.
354    
355    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
356        leak if the size of the offset vector was greater than 30. When the vector
357        is smaller, the saved offsets during recursion go onto a local stack
358        vector, but for larger vectors malloc() is used. It was failing to free
359        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
360        error, in fact).
361    
362    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
363        heapframe that is used only when UTF-8 support is enabled. This caused no
364        problem, but was untidy.
365    
366    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
367        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
368        included within another project.
369    
370    24. Steven Van Ingelgem's patches to add more options to the CMake support,
371        slightly modified by me:
372    
373          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
374              not building pcregrep.
375    
376          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
377              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
378    
379    25. Forward references, both numeric and by name, in patterns that made use of
380        duplicate group numbers, could behave incorrectly or give incorrect errors,
381        because when scanning forward to find the reference group, PCRE was not
382        taking into account the duplicate group numbers. A pattern such as
383        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
384    
385    26. Changed a few more instances of "const unsigned char *" to USPTR, making
386        the feature of a custom pointer more persuasive (as requested by a user).
387    
388    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
389        pcretest.c, inside #ifndefs, because it seems they are sometimes already
390        pre-defined.
391    
392    28. Added support for (*UTF8) at the start of a pattern.
393    
394    29. Arrange for flags added by the "release type" setting in CMake to be shown
395        in the configuration summary.
396    
397    
398    Version 7.8 05-Sep-08
399    ---------------------
400    
401    1.  Replaced UCP searching code with optimized version as implemented for Ad
402        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
403        stage table and inline lookup instead of a function, giving speed ups of 2
404        to 5 times on some simple patterns that I tested. Permission was given to
405        distribute the MultiStage2.py script that generates the tables (it's not in
406        the tarball, but is in the Subversion repository).
407    
408    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
409        scripts.
410    
411    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
412        a group with a zero qualifier. The result of the study could be incorrect,
413        or the function might crash, depending on the pattern.
414    
415    4.  Caseless matching was not working for non-ASCII characters in back
416        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
417        It now works when Unicode Property Support is available.
418    
419    5.  In pcretest, an escape such as \x{de} in the data was always generating
420        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
421        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
422        truncation.
423    
424    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
425    
426    7.  Added two (int) casts to pcregrep when printing the difference of two
427        pointers, in case they are 64-bit values.
428    
429    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
430        test 2 if it fails.
431    
432    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
433        and a #define of that name to empty if it is not externally set. This is to
434        allow users of MSVC to set it if necessary.
435    
436    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
437        the convenience functions in the pcre_get.c source file.
438    
439    11. An option change at the start of a pattern that had top-level alternatives
440        could cause overwriting and/or a crash. This command provoked a crash in
441        some environments:
442    
443          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
444    
445        This potential security problem was recorded as CVE-2008-2371.
446    
447    12. For a pattern where the match had to start at the beginning or immediately
448        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
449        pcre_dfa_exec() could read past the end of the passed subject if there was
450        no match. To help with detecting such bugs (e.g. with valgrind), I modified
451        pcretest so that it places the subject at the end of its malloc-ed buffer.
452    
453    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
454        exec() might read past the end of the data buffer in UTF-8 mode.
455    
456    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
457        the data contained the byte 0x85 as part of a UTF-8 character within its
458        first line. This applied both to normal and DFA matching.
459    
460    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
461        /^[^d]*?$/8 failed to match "abc".
462    
463    16. Added a missing copyright notice to pcrecpp_internal.h.
464    
465    17. Make it more clear in the documentation that values returned from
466        pcre_exec() in ovector are byte offsets, not character counts.
467    
468    18. Tidied a few places to stop certain compilers from issuing warnings.
469    
470    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
471        supplied by Stefan Weber. I made a further small update for 7.8 because
472        there is a change of source arrangements: the pcre_searchfuncs.c module is
473        replaced by pcre_ucd.c.
474    
475    
476    Version 7.7 07-May-08
477  ---------------------  ---------------------
478    
479  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
480      a string to a long long, pretend we don't even have a long long." This is      a string to a long long, pretend we don't even have a long long." This is
481      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
482    
483  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
484      pre-7.6 versions, which defined a global no_arg variable instead of putting      pre-7.6 versions, which defined a global no_arg variable instead of putting
485      it in the RE class.      it in the RE class. (See also #8 below.)
486    
487  3.  Remove a line of dead code, identified by coverity and reported by Nuno  3.  Remove a line of dead code, identified by coverity and reported by Nuno
488      Lopes.      Lopes.
489    
490    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
491    
492        (1) The include/exclude patterns were being applied to the whole pathnames
493            of files, instead of just to the final components.
494    
495        (2) If there was more than one level of directory, the subdirectories were
496            skipped unless they satisfied the include/exclude conditions. This is
497            inconsistent with GNU grep (and could even be seen as contrary to the
498            pcregrep specification - which I improved to make it absolutely clear).
499            The action now is always to scan all levels of directory, and just
500            apply the include/exclude patterns to regular files.
501    
502    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
503        --exclude_dir in the tests to avoid scanning .svn directories.
504    
505    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
506        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
507        doesn't support NULs in patterns.
508    
509    7.  Added some missing "const"s to declarations of static tables in
510        pcre_compile.c and pcre_dfa_exec.c.
511    
512    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
513        caused by fix #2  above. (Subsequently also a second patch to fix the
514        first patch. And a third patch - this was a messy problem.)
515    
516    9.  Applied Craig's patch to remove the use of push_back().
517    
518    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
519        matching function regexec().
520    
521    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
522        which, however, unlike Perl's \g{...}, are subroutine calls, not back
523        references. PCRE supports relative numbers with this syntax (I don't think
524        Oniguruma does).
525    
526    12. Previously, a group with a zero repeat such as (...){0} was completely
527        omitted from the compiled regex. However, this means that if the group
528        was called as a subroutine from elsewhere in the pattern, things went wrong
529        (an internal error was given). Such groups are now left in the compiled
530        pattern, with a new opcode that causes them to be skipped at execution
531        time.
532    
533    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
534        to the way PCRE behaves:
535    
536        (a) A lone ] character is dis-allowed (Perl treats it as data).
537    
538        (b) A back reference to an unmatched subpattern matches an empty string
539            (Perl fails the current match path).
540    
541        (c) A data ] in a character class must be notated as \] because if the
542            first data character in a class is ], it defines an empty class. (In
543            Perl it is not possible to have an empty class.) The empty class []
544            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
545            The negative empty class [^] matches any one character, independently
546            of the DOTALL setting.
547    
548    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
549        non-existent subpattern following a character class starting with ']' and
550        containing () gave an internal compiling error instead of "reference to
551        non-existent subpattern". Fortunately, when the pattern did exist, the
552        compiled code was correct. (When scanning forwards to check for the
553        existencd of the subpattern, it was treating the data ']' as terminating
554        the class, so got the count wrong. When actually compiling, the reference
555        was subsequently set up correctly.)
556    
557    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
558        it was being rejected as not supported by pcre_dfa_exec(), even though
559        other assertions are supported. I have made pcre_dfa_exec() support
560        (*FAIL).
561    
562    16. The implementation of 13c above involved the invention of a new opcode,
563        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
564        cannot be changed at match time, I realized I could make a small
565        improvement to matching performance by compiling OP_ALLANY instead of
566        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
567        on the OP_ANY path.
568    
569    17. Compiling pcretest on Windows with readline support failed without the
570        following two fixes: (1) Make the unistd.h include conditional on
571        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
572    
573    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
574        ncurses library to be included for pcretest when ReadLine support is
575        requested, but also to allow for it to be overridden. This patch came from
576        Daniel Bergström.
577    
578    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
579        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
580        any errors with the current Unicode tables. Thanks to Peter Kankowski for
581        spotting this.
582    
583    
584  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08

Legend:
Removed from v.323  
changed lines
  Added in v.484

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12