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

Diff of /code/trunk/ChangeLog

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

revision 91 by nigel, Sat Feb 24 21:41:34 2007 UTC revision 360 by ph10, Wed Jul 9 20:00:28 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    Version 8.0 02 Jul-08
5    ---------------------
6    
7    1.  Replaced UCP searching code with optimized version as implemented for Ad
8        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
9        stage table and inline lookup instead of a function, giving speed ups of 2
10        to 5 times on some simple patterns that I tested. Permission was given to
11        distribute the MultiStage2.py script that generates the tables (it's not in
12        the tarball, but is in the Subversion repository).
13    
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
16    
17    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
18        a group with a zero qualifier. The result of the study could be incorrect,
19        or the function might crash, depending on the pattern.
20    
21    4.  Caseless matching was not working for non-ASCII characters in back
22        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
23        It now works when Unicode Property Support is available.
24    
25    5.  In pcretest, an escape such as \x{de} in the data was always generating
26        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
27        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
28        truncation.
29    
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
31    
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
34    
35    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
36        test 2 if it fails.
37    
38    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
39        and a #define of that name to empty if it is not externally set. This is to
40        allow users of MSVC to set it if necessary.
41    
42    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
43        the convenience functions in the pcre_get.c source file.
44    
45    11. An option change at the start of a pattern that had top-level alternatives
46        could cause overwriting and/or a crash. This command provoked a crash in
47        some environments:
48    
49          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
50    
51        This potential security problem was recorded as CVE-2008-2371.
52    
53    
54    Version 7.7 07-May-08
55    ---------------------
56    
57    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
58        a string to a long long, pretend we don't even have a long long." This is
59        done by checking for the strtoq, strtoll, and _strtoi64 functions.
60    
61    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
62        pre-7.6 versions, which defined a global no_arg variable instead of putting
63        it in the RE class. (See also #8 below.)
64    
65    3.  Remove a line of dead code, identified by coverity and reported by Nuno
66        Lopes.
67    
68    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
69    
70        (1) The include/exclude patterns were being applied to the whole pathnames
71            of files, instead of just to the final components.
72    
73        (2) If there was more than one level of directory, the subdirectories were
74            skipped unless they satisfied the include/exclude conditions. This is
75            inconsistent with GNU grep (and could even be seen as contrary to the
76            pcregrep specification - which I improved to make it absolutely clear).
77            The action now is always to scan all levels of directory, and just
78            apply the include/exclude patterns to regular files.
79    
80    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
81        --exclude_dir in the tests to avoid scanning .svn directories.
82    
83    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
84        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
85        doesn't support NULs in patterns.
86    
87    7.  Added some missing "const"s to declarations of static tables in
88        pcre_compile.c and pcre_dfa_exec.c.
89    
90    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
91        caused by fix #2  above. (Subsequently also a second patch to fix the
92        first patch. And a third patch - this was a messy problem.)
93    
94    9.  Applied Craig's patch to remove the use of push_back().
95    
96    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
97        matching function regexec().
98    
99    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
100        which, however, unlike Perl's \g{...}, are subroutine calls, not back
101        references. PCRE supports relative numbers with this syntax (I don't think
102        Oniguruma does).
103    
104    12. Previously, a group with a zero repeat such as (...){0} was completely
105        omitted from the compiled regex. However, this means that if the group
106        was called as a subroutine from elsewhere in the pattern, things went wrong
107        (an internal error was given). Such groups are now left in the compiled
108        pattern, with a new opcode that causes them to be skipped at execution
109        time.
110    
111    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
112        to the way PCRE behaves:
113    
114        (a) A lone ] character is dis-allowed (Perl treats it as data).
115    
116        (b) A back reference to an unmatched subpattern matches an empty string
117            (Perl fails the current match path).
118    
119        (c) A data ] in a character class must be notated as \] because if the
120            first data character in a class is ], it defines an empty class. (In
121            Perl it is not possible to have an empty class.) The empty class []
122            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
123            The negative empty class [^] matches any one character, independently
124            of the DOTALL setting.
125    
126    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
127        non-existent subpattern following a character class starting with ']' and
128        containing () gave an internal compiling error instead of "reference to
129        non-existent subpattern". Fortunately, when the pattern did exist, the
130        compiled code was correct. (When scanning forwards to check for the
131        existencd of the subpattern, it was treating the data ']' as terminating
132        the class, so got the count wrong. When actually compiling, the reference
133        was subsequently set up correctly.)
134    
135    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
136        it was being rejected as not supported by pcre_dfa_exec(), even though
137        other assertions are supported. I have made pcre_dfa_exec() support
138        (*FAIL).
139    
140    16. The implementation of 13c above involved the invention of a new opcode,
141        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
142        cannot be changed at match time, I realized I could make a small
143        improvement to matching performance by compiling OP_ALLANY instead of
144        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
145        on the OP_ANY path.
146    
147    17. Compiling pcretest on Windows with readline support failed without the
148        following two fixes: (1) Make the unistd.h include conditional on
149        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
150    
151    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
152        ncurses library to be included for pcretest when ReadLine support is
153        requested, but also to allow for it to be overridden. This patch came from
154        Daniel Bergström.
155    
156    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
157        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
158        any errors with the current Unicode tables. Thanks to Peter Kankowski for
159        spotting this.
160    
161    
162    Version 7.6 28-Jan-08
163    ---------------------
164    
165    1.  A character class containing a very large number of characters with
166        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
167        overflow.
168    
169    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
170        HAVE_LONG_LONG is not defined.
171    
172    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
173        bring them up to date and include new features. This patch includes:
174    
175        - Fixed PH's badly added libz and libbz2 support.
176        - Fixed a problem with static linking.
177        - Added pcredemo. [But later removed - see 7 below.]
178        - Fixed dftables problem and added an option.
179        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
180            HAVE_LONG_LONG.
181        - Added readline support for pcretest.
182        - Added an listing of the option settings after cmake has run.
183    
184    4.  A user submitted a patch to Makefile that makes it easy to create
185        "pcre.dll" under mingw when using Configure/Make. I added stuff to
186        Makefile.am that cause it to include this special target, without
187        affecting anything else. Note that the same mingw target plus all
188        the other distribution libraries and programs are now supported
189        when configuring with CMake (see 6 below) instead of with
190        Configure/Make.
191    
192    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
193        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
194        exported in the Windows port". It has not yet been confirmed that the patch
195        solves the problem, but it does no harm.
196    
197    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
198        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
199        with CMake, and also correct the comment about stack recursion.
200    
201    7.  Remove the automatic building of pcredemo from the ./configure system and
202        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
203        of a program that users should build themselves after PCRE is installed, so
204        building it automatically is not really right. What is more, it gave
205        trouble in some build environments.
206    
207    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
208    
209    
210    Version 7.5 10-Jan-08
211    ---------------------
212    
213    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
214        values in parens when parsing an RE using the C++ wrapper."
215    
216    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
217        Characters greater than 255 were excluded from the class instead of being
218        included.
219    
220    3.  The same bug as (2) above applied to negated POSIX classes such as
221        [:^space:].
222    
223    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
224        defined or documented. It seems to have been a typo for PCRE_STATIC, so
225        I have changed it.
226    
227    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
228        first named subpattern) and a construct such as (?&a) would reference the
229        first named subpattern whose name started with "a" (in other words, the
230        length check was missing). Both these problems are fixed. "Subpattern name
231        expected" is now given for (?&) (a zero-length name), and this patch also
232        makes it give the same error for \k'' (previously it complained that that
233        was a reference to a non-existent subpattern).
234    
235    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
236        this is right because (?- can be followed by option settings as well as by
237        digits. I have, however, made the messages clearer.
238    
239    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
240        than the number used in the conditional) now cause a compile-time error.
241        This is actually not compatible with Perl, which accepts such patterns, but
242        treats the conditional as always being FALSE (as PCRE used to), but it
243        seems to me that giving a diagnostic is better.
244    
245    8.  Change "alphameric" to the more common word "alphanumeric" in comments
246        and messages.
247    
248    9.  Fix two occurrences of "backslash" in comments that should have been
249        "backspace".
250    
251    10. Remove two redundant lines of code that can never be obeyed (their function
252        was moved elsewhere).
253    
254    11. The program that makes PCRE's Unicode character property table had a bug
255        which caused it to generate incorrect table entries for sequences of
256        characters that have the same character type, but are in different scripts.
257        It amalgamated them into a single range, with the script of the first of
258        them. In other words, some characters were in the wrong script. There were
259        thirteen such cases, affecting characters in the following ranges:
260    
261          U+002b0 - U+002c1
262          U+0060c - U+0060d
263          U+0061e - U+00612
264          U+0064b - U+0065e
265          U+0074d - U+0076d
266          U+01800 - U+01805
267          U+01d00 - U+01d77
268          U+01d9b - U+01dbf
269          U+0200b - U+0200f
270          U+030fc - U+030fe
271          U+03260 - U+0327f
272          U+0fb46 - U+0fbb1
273          U+10450 - U+1049d
274    
275    12. The -o option (show only the matching part of a line) for pcregrep was not
276        compatible with GNU grep in that, if there was more than one match in a
277        line, it showed only the first of them. It now behaves in the same way as
278        GNU grep.
279    
280    13. If the -o and -v options were combined for pcregrep, it printed a blank
281        line for every non-matching line. GNU grep prints nothing, and pcregrep now
282        does the same. The return code can be used to tell if there were any
283        non-matching lines.
284    
285    14. Added --file-offsets and --line-offsets to pcregrep.
286    
287    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
288        infinitely looping recursion. The bug was that positive lookaheads were not
289        being skipped when checking for a possible empty match (negative lookaheads
290        and both kinds of lookbehind were skipped).
291    
292    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
293        inclusion of <windows.h> to before rather than after the definition of
294        INVALID_FILE_ATTRIBUTES (patch from David Byron).
295    
296    17. Specifying a possessive quantifier with a specific limit for a Unicode
297        character property caused pcre_compile() to compile bad code, which led at
298        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
299        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
300        caused the error; without that there was no problem.
301    
302    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
303    
304    19. Added --enable-pcretest-libreadline.
305    
306    20. In pcrecpp.cc, the variable 'count' was incremented twice in
307        RE::GlobalReplace(). As a result, the number of replacements returned was
308        double what it should be. I removed one of the increments, but Craig sent a
309        later patch that removed the other one (the right fix) and added unit tests
310        that check the return values (which was not done before).
311    
312    21. Several CMake things:
313    
314        (1) Arranged that, when cmake is used on Unix, the libraries end up with
315            the names libpcre and libpcreposix, not just pcre and pcreposix.
316    
317        (2) The above change means that pcretest and pcregrep are now correctly
318            linked with the newly-built libraries, not previously installed ones.
319    
320        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
321    
322    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
323        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
324        UTF-8 newline character). The key issue is that the pattern starts .*;
325        this means that the match must be either at the beginning, or after a
326        newline. The bug was in the code for advancing after a failed match and
327        checking that the new position followed a newline. It was not taking
328        account of UTF-8 characters correctly.
329    
330    23. PCRE was behaving differently from Perl in the way it recognized POSIX
331        character classes. PCRE was not treating the sequence [:...:] as a
332        character class unless the ... were all letters. Perl, however, seems to
333        allow any characters between [: and :], though of course it rejects as
334        unknown any "names" that contain non-letters, because all the known class
335        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
336        for example, whereas PCRE did not - it did not recognize a POSIX character
337        class. This seemed a bit dangerous, so the code has been changed to be
338        closer to Perl. The behaviour is not identical to Perl, because PCRE will
339        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
340        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
341        Perl does, and where it didn't before.
342    
343    24. Rewrite so as to remove the single use of %n from pcregrep because in some
344        Windows environments %n is disabled by default.
345    
346    
347    Version 7.4 21-Sep-07
348    ---------------------
349    
350    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
351        means that a class such as [\s] counted as "explicit reference to CR or
352        LF". That isn't really right - the whole point of the change was to try to
353        help when there was an actual mention of one of the two characters. So now
354        the change happens only if \r or \n (or a literal CR or LF) character is
355        encountered.
356    
357    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
358        of both had grown to the point where there were only 3 bits left.
359        Fortunately, there was spare space in the data structure, and so I have
360        moved the internal flags into a new 16-bit field to free up more option
361        bits.
362    
363    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
364        but did not set the internal JCHANGED flag - either of these is enough to
365        control the way the "get" function works - but the PCRE_INFO_JCHANGED
366        facility is supposed to tell if (?J) was ever used, so now (?J) at the
367        start sets both bits.
368    
369    4.  Added options (at build time, compile time, exec time) to change \R from
370        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
371    
372    5.  doc/pcresyntax.html was missing from the distribution.
373    
374    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
375        compatibility, even though it is no longer used.
376    
377    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
378        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
379        windows.h file is present (where different names are used). [This was
380        reversed later after testing - see 16 below.]
381    
382    8.  Changed all #include <config.h> to #include "config.h". There were also
383        some further <pcre.h> cases that I changed to "pcre.h".
384    
385    9.  When pcregrep was used with the --colour option, it missed the line ending
386        sequence off the lines that it output.
387    
388    10. It was pointed out to me that arrays of string pointers cause lots of
389        relocations when a shared library is dynamically loaded. A technique of
390        using a single long string with a table of offsets can drastically reduce
391        these. I have refactored PCRE in four places to do this. The result is
392        dramatic:
393    
394          Originally:                          290
395          After changing UCP table:            187
396          After changing error message table:   43
397          After changing table of "verbs"       36
398          After changing table of Posix names   22
399    
400        Thanks to the folks working on Gregex for glib for this insight.
401    
402    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
403        unicode-properties was also set.
404    
405    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
406    
407    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
408        checked only for CRLF.
409    
410    14. Added casts to pcretest.c to avoid compiler warnings.
411    
412    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
413    
414    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
415        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
416        entirely. This removes changes made in 7 above.
417    
418    17. The CMake files have been updated, and there is now more information about
419        building with CMake in the NON-UNIX-USE document.
420    
421    
422    Version 7.3 28-Aug-07
423    ---------------------
424    
425     1. In the rejigging of the build system that eventually resulted in 7.1, the
426        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
427        brackets there is not right, since it causes compilers to look for an
428        installed pcre.h, not the version that is in the source that is being
429        compiled (which of course may be different). I have changed it back to:
430    
431          #include "pcre.h"
432    
433        I have a vague recollection that the change was concerned with compiling in
434        different directories, but in the new build system, that is taken care of
435        by the VPATH setting the Makefile.
436    
437     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
438        when the subject happened to end in the byte 0x85 (e.g. if the last
439        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
440        characters but of course it shouldn't be taken as a newline when it is part
441        of another character. The bug was that, for an unlimited repeat of . in
442        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
443        characters when looking for a newline.
444    
445     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
446    
447     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
448        in debug output.
449    
450     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
451        long printing in the pcrecpp unittest when running under MinGW.
452    
453     6. ESC_K was left out of the EBCDIC table.
454    
455     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
456        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
457        limit also applies to "virtual nesting" when a pattern is recursive, and in
458        this case 1000 isn't so big. I have been able to remove this limit at the
459        expense of backing off one optimization in certain circumstances. Normally,
460        when pcre_exec() would call its internal match() function recursively and
461        immediately return the result unconditionally, it uses a "tail recursion"
462        feature to save stack. However, when a subpattern that can match an empty
463        string has an unlimited repetition quantifier, it no longer makes this
464        optimization. That gives it a stack frame in which to save the data for
465        checking that an empty string has been matched. Previously this was taken
466        from the 1000-entry workspace that had been reserved. So now there is no
467        explicit limit, but more stack is used.
468    
469     8. Applied Daniel's patches to solve problems with the import/export magic
470        syntax that is required for Windows, and which was going wrong for the
471        pcreposix and pcrecpp parts of the library. These were overlooked when this
472        problem was solved for the main library.
473    
474     9. There were some crude static tests to avoid integer overflow when computing
475        the size of patterns that contain repeated groups with explicit upper
476        limits. As the maximum quantifier is 65535, the maximum group length was
477        set at 30,000 so that the product of these two numbers did not overflow a
478        32-bit integer. However, it turns out that people want to use groups that
479        are longer than 30,000 bytes (though not repeat them that many times).
480        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
481        made it possible to implement the integer overflow checks in a much more
482        dynamic way, which I have now done. The artificial limitation on group
483        length has been removed - we now have only the limit on the total length of
484        the compiled pattern, which depends on the LINK_SIZE setting.
485    
486    10. Fixed a bug in the documentation for get/copy named substring when
487        duplicate names are permitted. If none of the named substrings are set, the
488        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
489        empty string.
490    
491    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
492        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
493        because the ] is interpreted as the first data character and the
494        terminating ] is not found. PCRE has been made compatible with Perl in this
495        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
496        cause memory overwriting.
497    
498    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
499        string has been matched (to stop an infinite loop). It was not recognizing
500        a conditional subpattern that could match an empty string if that
501        subpattern was within another subpattern. For example, it looped when
502        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
503        condition was not nested. This bug has been fixed.
504    
505    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
506        past the start of the subject in the presence of bytes with the top bit
507        set, for example "\x8aBCD".
508    
509    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
510        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
511    
512    14. Optimized (?!) to (*FAIL).
513    
514    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
515        This restricts code points to be within the range 0 to 0x10FFFF, excluding
516        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
517        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
518        does: it's just the validity check that is more restrictive.
519    
520    16. Inserted checks for integer overflows during escape sequence (backslash)
521        processing, and also fixed erroneous offset values for syntax errors during
522        backslash processing.
523    
524    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
525        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
526    
527    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
528        caused an overrun.
529    
530    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
531        something other than just ASCII characters) inside a group that had an
532        unlimited repeat caused a loop at compile time (while checking to see
533        whether the group could match an empty string).
534    
535    20. Debugging a pattern containing \p or \P could cause a crash. For example,
536        [\P{Any}] did so. (Error in the code for printing property names.)
537    
538    21. An orphan \E inside a character class could cause a crash.
539    
540    22. A repeated capturing bracket such as (A)? could cause a wild memory
541        reference during compilation.
542    
543    23. There are several functions in pcre_compile() that scan along a compiled
544        expression for various reasons (e.g. to see if it's fixed length for look
545        behind). There were bugs in these functions when a repeated \p or \P was
546        present in the pattern. These operators have additional parameters compared
547        with \d, etc, and these were not being taken into account when moving along
548        the compiled data. Specifically:
549    
550        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
551            length.
552    
553        (b) An item such as \pL+ within a repeated group could cause crashes or
554            loops.
555    
556        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
557            "reference to non-existent subpattern" error.
558    
559        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
560    
561    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
562        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
563    
564    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
565    
566    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
567        character were causing crashes (broken optimization).
568    
569    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
570        \p or \P) caused a compile-time loop.
571    
572    28. More problems have arisen in unanchored patterns when CRLF is a valid line
573        break. For example, the unstudied pattern [\r\n]A does not match the string
574        "\r\nA" because change 7.0/46 below moves the current point on by two
575        characters after failing to match at the start. However, the pattern \nA
576        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
577        the same is true. There doesn't seem any very clean way out of this, but
578        what I have chosen to do makes the common cases work: PCRE now takes note
579        of whether there can be an explicit match for \r or \n anywhere in the
580        pattern, and if so, 7.0/46 no longer applies. As part of this change,
581        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
582        pattern has explicit CR or LF references.
583    
584    29. Added (*CR) etc for changing newline setting at start of pattern.
585    
586    
587    Version 7.2 19-Jun-07
588    ---------------------
589    
590     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
591        which is apparently normally available under Windows.
592    
593     2. Re-jig the pcregrep tests with different newline settings in an attempt
594        to make them independent of the local environment's newline setting.
595    
596     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
597    
598     4. Some of the "internals" tests were previously cut out when the link size
599        was not 2, because the output contained actual offsets. The recent new
600        "Z" feature of pcretest means that these can be cut out, making the tests
601        usable with all link sizes.
602    
603     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
604        stack recursion. This gives a massive performance boost under BSD, but just
605        a small improvement under Linux. However, it saves one field in the frame
606        in all cases.
607    
608     6. Added more features from the forthcoming Perl 5.10:
609    
610        (a) (?-n) (where n is a string of digits) is a relative subroutine or
611            recursion call. It refers to the nth most recently opened parentheses.
612    
613        (b) (?+n) is also a relative subroutine call; it refers to the nth next
614            to be opened parentheses.
615    
616        (c) Conditions that refer to capturing parentheses can be specified
617            relatively, for example, (?(-2)... or (?(+3)...
618    
619        (d) \K resets the start of the current match so that everything before
620            is not part of it.
621    
622        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
623    
624        (f) \g{name} is another synonym - part of Perl 5.10's unification of
625            reference syntax.
626    
627        (g) (?| introduces a group in which the numbering of parentheses in each
628            alternative starts with the same number.
629    
630        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
631    
632     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
633        PCRE_INFO_JCHANGED.
634    
635     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
636        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
637        for detecting groups that can match an empty string.
638    
639     9. A pattern with a very large number of alternatives (more than several
640        hundred) was running out of internal workspace during the pre-compile
641        phase, where pcre_compile() figures out how much memory will be needed. A
642        bit of new cunning has reduced the workspace needed for groups with
643        alternatives. The 1000-alternative test pattern now uses 12 bytes of
644        workspace instead of running out of the 4096 that are available.
645    
646    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
647    
648    11. Applied patch from Google to remove an optimization that didn't quite work.
649        The report of the bug said:
650    
651          pcrecpp::RE("a*").FullMatch("aaa") matches, while
652          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
653          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
654    
655    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
656        it matched the wrong number of bytes.
657    
658    
659    Version 7.1 24-Apr-07
660    ---------------------
661    
662     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
663        that is more "standard", making use of automake and other Autotools. There
664        is some re-arrangement of the files and adjustment of comments consequent
665        on this.
666    
667     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
668        for recursive directory scanning broke on some systems because the files
669        are not scanned in any specific order and on different systems the order
670        was different. A call to "sort" has been inserted into RunGrepTest for the
671        approprate test as a short-term fix. In the longer term there may be an
672        alternative.
673    
674     3. I had an email from Eric Raymond about problems translating some of PCRE's
675        man pages to HTML (despite the fact that I distribute HTML pages, some
676        people do their own conversions for various reasons). The problems
677        concerned the use of low-level troff macros .br and .in. I have therefore
678        removed all such uses from the man pages (some were redundant, some could
679        be replaced by .nf/.fi pairs). The 132html script that I use to generate
680        HTML has been updated to handle .nf/.fi and to complain if it encounters
681        .br or .in.
682    
683     4. Updated comments in configure.ac that get placed in config.h.in and also
684        arranged for config.h to be included in the distribution, with the name
685        config.h.generic, for the benefit of those who have to compile without
686        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
687    
688     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
689        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
690        makevp.bat for the current PCRE, using the additional files
691        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
692    
693     6. A Windows user reported a minor discrepancy with test 2, which turned out
694        to be caused by a trailing space on an input line that had got lost in his
695        copy. The trailing space was an accident, so I've just removed it.
696    
697     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
698        that is needed.
699    
700     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
701        as "const" (a) because they are and (b) because it helps the PHP
702        maintainers who have recently made a script to detect big data structures
703        in the php code that should be moved to the .rodata section. I remembered
704        to update Builducptable as well, so it won't revert if ucptable.h is ever
705        re-created.
706    
707     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
708        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
709        order to be able to cut out the UTF-8 tables in the latter when UTF-8
710        support is not required. This saves 1.5-2K of code, which is important in
711        some applications.
712    
713        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
714        so as not to refer to the tables, even though these functions will never be
715        called when UTF-8 support is disabled. Otherwise there are problems with a
716        shared library.
717    
718    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
719    
720        (a) It was defining its arguments as char * instead of void *.
721    
722        (b) It was assuming that all moves were upwards in memory; this was true
723            a long time ago when I wrote it, but is no longer the case.
724    
725        The emulated memove() is provided for those environments that have neither
726        memmove() nor bcopy(). I didn't think anyone used it these days, but that
727        is clearly not the case, as these two bugs were recently reported.
728    
729    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
730        and Detrail to create the HTML documentation, the .txt form of the man
731        pages, and it removes trailing spaces from listed files. It also creates
732        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
733        case, it wraps all the #defines with #ifndefs. This script should be run
734        before "make dist".
735    
736    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
737        with Unicode property support.
738    
739        (a) For a maximizing quantifier, if the two different cases of the
740            character were of different lengths in their UTF-8 codings (there are
741            some cases like this - I found 11), and the matching function had to
742            back up over a mixture of the two cases, it incorrectly assumed they
743            were both the same length.
744    
745        (b) When PCRE was configured to use the heap rather than the stack for
746            recursion during matching, it was not correctly preserving the data for
747            the other case of a UTF-8 character when checking ahead for a match
748            while processing a minimizing repeat. If the check also involved
749            matching a wide character, but failed, corruption could cause an
750            erroneous result when trying to check for a repeat of the original
751            character.
752    
753    13. Some tidying changes to the testing mechanism:
754    
755        (a) The RunTest script now detects the internal link size and whether there
756            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
757            values substituted by "configure". (The RunGrepTest script already did
758            this for UTF-8.) The configure.ac script no longer substitutes the
759            relevant variables.
760    
761        (b) The debugging options /B and /D in pcretest show the compiled bytecode
762            with length and offset values. This means that the output is different
763            for different internal link sizes. Test 2 is skipped for link sizes
764            other than 2 because of this, bypassing the problem. Unfortunately,
765            there was also a test in test 3 (the locale tests) that used /B and
766            failed for link sizes other than 2. Rather than cut the whole test out,
767            I have added a new /Z option to pcretest that replaces the length and
768            offset values with spaces. This is now used to make test 3 independent
769            of link size. (Test 2 will be tidied up later.)
770    
771    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
772        segmentation fault instead of returning the appropriate error message.
773    
774    15. In multiline mode when the newline sequence was set to "any", the pattern
775        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
776        This doesn't seem right; it now treats the CRLF combination as the line
777        ending, and so does not match in that case. It's only a pattern such as ^$
778        that would hit this one: something like ^ABC$ would have failed after \r
779        and then tried again after \r\n.
780    
781    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
782        in an attempt to make files that differ only in their line terminators
783        compare equal. This works on Linux.
784    
785    17. Under certain error circumstances pcregrep might try to free random memory
786        as it exited. This is now fixed, thanks to valgrind.
787    
788    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
789        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
790        was because its rules for how to advance for /g after matching an empty
791        string at the end of a line did not allow for this case. They now check for
792        it specially.
793    
794    20. pcretest is supposed to handle patterns and data of any length, by
795        extending its buffers when necessary. It was getting this wrong when the
796        buffer for a data line had to be extended.
797    
798    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
799        CRLF as a newline sequence.
800    
801    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
802        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
803        I have nevertheless tidied it up.
804    
805    23. Added some casts to kill warnings from HP-UX ia64 compiler.
806    
807    24. Added a man page for pcre-config.
808    
809    
810    Version 7.0 19-Dec-06
811    ---------------------
812    
813     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
814        moving to gcc 4.1.1.
815    
816     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
817        sys/time.h, which is documented as needed for this function. It doesn't
818        seem to matter on Linux, but it showed up on some releases of OS X.
819    
820     3. It seems that there are systems where bytes whose values are greater than
821        127 match isprint() in the "C" locale. The "C" locale should be the
822        default when a C program starts up. In most systems, only ASCII printing
823        characters match isprint(). This difference caused the output from pcretest
824        to vary, making some of the tests fail. I have changed pcretest so that:
825    
826        (a) When it is outputting text in the compiled version of a pattern, bytes
827            other than 32-126 are always shown as hex escapes.
828    
829        (b) When it is outputting text that is a matched part of a subject string,
830            it does the same, unless a different locale has been set for the match
831            (using the /L modifier). In this case, it uses isprint() to decide.
832    
833     4. Fixed a major bug that caused incorrect computation of the amount of memory
834        required for a compiled pattern when options that changed within the
835        pattern affected the logic of the preliminary scan that determines the
836        length. The relevant options are -x, and -i in UTF-8 mode. The result was
837        that the computed length was too small. The symptoms of this bug were
838        either the PCRE error "internal error: code overflow" from pcre_compile(),
839        or a glibc crash with a message such as "pcretest: free(): invalid next
840        size (fast)". Examples of patterns that provoked this bug (shown in
841        pcretest format) are:
842    
843          /(?-x: )/x
844          /(?x)(?-x: \s*#\s*)/
845          /((?i)[\x{c0}])/8
846          /(?i:[\x{c0}])/8
847    
848        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
849        is now done differently.
850    
851     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
852        wrapper classes; (b) implement a new function in the C++ scanner that is
853        more efficient than the old way of doing things because it avoids levels of
854        recursion in the regex matching; (c) add a paragraph to the documentation
855        for the FullMatch() function.
856    
857     6. The escape sequence \n was being treated as whatever was defined as
858        "newline". Not only was this contrary to the documentation, which states
859        that \n is character 10 (hex 0A), but it also went horribly wrong when
860        "newline" was defined as CRLF. This has been fixed.
861    
862     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
863        was being set to -1 for the "end of line" case (supposedly a value that no
864        character can have). Though this value is never used (the check for end of
865        line is "zero bytes in current character"), it caused compiler complaints.
866        I've changed it to 0xffffffff.
867    
868     8. In pcre_version.c, the version string was being built by a sequence of
869        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
870        string (as it is for production releases) called a macro with an empty
871        argument. The C standard says the result of this is undefined. The gcc
872        compiler treats it as an empty string (which was what was wanted) but it is
873        reported that Visual C gives an error. The source has been hacked around to
874        avoid this problem.
875    
876     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
877        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
878        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
879        of them did).
880    
881    10. Originally, pcretest opened its input and output without "b"; then I was
882        told that "b" was needed in some environments, so it was added for release
883        5.0 to both the input and output. (It makes no difference on Unix-like
884        systems.) Later I was told that it is wrong for the input on Windows. I've
885        now abstracted the modes into two macros, to make it easier to fiddle with
886        them, and removed "b" from the input mode under Windows.
887    
888    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
889    
890    12. Added -help and --help to pcretest as an official way of being reminded
891        of the options.
892    
893    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
894        and pcrecpp.cc because they annoy compilers at high warning levels.
895    
896    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
897    
898    15. Fixed an occurrence of == in configure.ac that should have been = (shell
899        scripts are not C programs :-) and which was not noticed because it works
900        on Linux.
901    
902    16. pcretest is supposed to handle any length of pattern and data line (as one
903        line or as a continued sequence of lines) by extending its input buffer if
904        necessary. This feature was broken for very long pattern lines, leading to
905        a string of junk being passed to pcre_compile() if the pattern was longer
906        than about 50K.
907    
908    17. I have done a major re-factoring of the way pcre_compile() computes the
909        amount of memory needed for a compiled pattern. Previously, there was code
910        that made a preliminary scan of the pattern in order to do this. That was
911        OK when PCRE was new, but as the facilities have expanded, it has become
912        harder and harder to keep it in step with the real compile phase, and there
913        have been a number of bugs (see for example, 4 above). I have now found a
914        cunning way of running the real compile function in a "fake" mode that
915        enables it to compute how much memory it would need, while actually only
916        ever using a few hundred bytes of working memory and without too many
917        tests of the mode. This should make future maintenance and development
918        easier. A side effect of this work is that the limit of 200 on the nesting
919        depth of parentheses has been removed (though this was never a serious
920        limitation, I suspect). However, there is a downside: pcre_compile() now
921        runs more slowly than before (30% or more, depending on the pattern). I
922        hope this isn't a big issue. There is no effect on runtime performance.
923    
924    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
925        newline (only possible for the last line of a file) and it was a
926        pattern that set a locale (followed by /Lsomething), pcretest crashed.
927    
928    19. Added additional timing features to pcretest. (1) The -tm option now times
929        matching only, not compiling. (2) Both -t and -tm can be followed, as a
930        separate command line item, by a number that specifies the number of
931        repeats to use when timing. The default is 50000; this gives better
932        precision, but takes uncomfortably long for very large patterns.
933    
934    20. Extended pcre_study() to be more clever in cases where a branch of a
935        subpattern has no definite first character. For example, (a*|b*)[cd] would
936        previously give no result from pcre_study(). Now it recognizes that the
937        first character must be a, b, c, or d.
938    
939    21. There was an incorrect error "recursive call could loop indefinitely" if
940        a subpattern (or the entire pattern) that was being tested for matching an
941        empty string contained only one non-empty item after a nested subpattern.
942        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
943        incorrectly, because the \d was being skipped in the check.
944    
945    22. The pcretest program now has a new pattern option /B and a command line
946        option -b, which is equivalent to adding /B to every pattern. This causes
947        it to show the compiled bytecode, without the additional information that
948        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
949        is the same as /B/I).
950    
951    23. A new optimization is now able automatically to treat some sequences such
952        as a*b as a*+b. More specifically, if something simple (such as a character
953        or a simple class like \d) has an unlimited quantifier, and is followed by
954        something that cannot possibly match the quantified thing, the quantifier
955        is automatically "possessified".
956    
957    24. A recursive reference to a subpattern whose number was greater than 39
958        went wrong under certain circumstances in UTF-8 mode. This bug could also
959        have affected the operation of pcre_study().
960    
961    25. Realized that a little bit of performance could be had by replacing
962        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
963    
964    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
965    
966    27. Possessive quantifiers such as a++ were previously implemented by turning
967        them into atomic groups such as ($>a+). Now they have their own opcodes,
968        which improves performance. This includes the automatically created ones
969        from 23 above.
970    
971    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
972        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
973        the first matched character to be a colon. This applied both to named and
974        numbered groups.
975    
976    29. The ucpinternal.h header file was missing its idempotency #ifdef.
977    
978    30. I was sent a "project" file called libpcre.a.dev which I understand makes
979        building PCRE on Windows easier, so I have included it in the distribution.
980    
981    31. There is now a check in pcretest against a ridiculously large number being
982        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
983        loop, the loop is abandoned.
984    
985    32. Forward references to subpatterns in conditions such as (?(2)...) where
986        subpattern 2 is defined later cause pcre_compile() to search forwards in
987        the pattern for the relevant set of parentheses. This search went wrong
988        when there were unescaped parentheses in a character class, parentheses
989        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
990    
991    33. "Subroutine" calls and backreferences were previously restricted to
992        referencing subpatterns earlier in the regex. This restriction has now
993        been removed.
994    
995    34. Added a number of extra features that are going to be in Perl 5.10. On the
996        whole, these are just syntactic alternatives for features that PCRE had
997        previously implemented using the Python syntax or my own invention. The
998        other formats are all retained for compatibility.
999    
1000        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
1001            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
1002            also .NET compatible.
1003    
1004        (b) A recursion or subroutine call to a named group can now be defined as
1005            (?&name) as well as (?P>name).
1006    
1007        (c) A backreference to a named group can now be defined as \k<name> or
1008            \k'name' as well as (?P=name). The new forms, as well as being in Perl
1009            5.10, are also .NET compatible.
1010    
1011        (d) A conditional reference to a named group can now use the syntax
1012            (?(<name>) or (?('name') as well as (?(name).
1013    
1014        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
1015            groups (named and numbered) that are never evaluated inline, but can be
1016            called as "subroutines" from elsewhere. In effect, the DEFINE condition
1017            is always false. There may be only one alternative in such a group.
1018    
1019        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
1020            as the simple (?(R). The condition is true only if the most recent
1021            recursion is that of the given number or name. It does not search out
1022            through the entire recursion stack.
1023    
1024        (g) The escape \gN or \g{N} has been added, where N is a positive or
1025            negative number, specifying an absolute or relative reference.
1026    
1027    35. Tidied to get rid of some further signed/unsigned compiler warnings and
1028        some "unreachable code" warnings.
1029    
1030    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
1031        things, this adds five new scripts.
1032    
1033    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
1034        There were also incompatibilities regarding the handling of \Q..\E inside
1035        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
1036        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
1037    
1038    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
1039        matches an empty string, and forcibly breaks the loop. There were bugs in
1040        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
1041        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
1042        separate and independent bugs (that affected different cases) have been
1043        fixed.
1044    
1045    39. Refactored the code to abolish the use of different opcodes for small
1046        capturing bracket numbers. This is a tidy that I avoided doing when I
1047        removed the limit on the number of capturing brackets for 3.5 back in 2001.
1048        The new approach is not only tidier, it makes it possible to reduce the
1049        memory needed to fix the previous bug (38).
1050    
1051    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
1052        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
1053        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
1054        mode.
1055    
1056    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
1057        report.
1058    
1059    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
1060        copy construction and assignment in the C++ wrapper.
1061    
1062    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
1063        couple of bugs that could have given wrong results in the "--newline=crlf"
1064        case.
1065    
1066    44. Added a number of casts and did some reorganization of signed/unsigned int
1067        variables following suggestions from Dair Grant. Also renamed the variable
1068        "this" as "item" because it is a C++ keyword.
1069    
1070    45. Arranged for dftables to add
1071    
1072          #include "pcre_internal.h"
1073    
1074        to pcre_chartables.c because without it, gcc 4.x may remove the array
1075        definition from the final binary if PCRE is built into a static library and
1076        dead code stripping is activated.
1077    
1078    46. For an unanchored pattern, if a match attempt fails at the start of a
1079        newline sequence, and the newline setting is CRLF or ANY, and the next two
1080        characters are CRLF, advance by two characters instead of one.
1081    
1082    
1083  Version 6.7 04-Jul-06  Version 6.7 04-Jul-06
1084  ---------------------  ---------------------
1085    

Legend:
Removed from v.91  
changed lines
  Added in v.360

  ViewVC Help
Powered by ViewVC 1.1.5