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

Diff of /code/trunk/ChangeLog

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

revision 79 by nigel, Sat Feb 24 21:40:52 2007 UTC revision 340 by ph10, Fri Apr 18 20:00:21 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    Version 7.7 05-Mar-08
5    ---------------------
6    
7    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
8        a string to a long long, pretend we don't even have a long long." This is
9        done by checking for the strtoq, strtoll, and _strtoi64 functions.
10    
11    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
12        pre-7.6 versions, which defined a global no_arg variable instead of putting
13        it in the RE class. (See also #8 below.)
14    
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
17    
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
19    
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
22    
23        (2) If there was more than one level of directory, the subdirectories were
24            skipped unless they satisfied the include/exclude conditions. This is
25            inconsistent with GNU grep (and could even be seen as contrary to the
26            pcregrep specification - which I improved to make it absolutely clear).
27            The action now is always to scan all levels of directory, and just
28            apply the include/exclude patterns to regular files.
29    
30    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
31        --exclude_dir in the tests to avoid scanning .svn directories.
32    
33    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
34        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
35        doesn't support NULs in patterns.
36    
37    7.  Added some missing "const"s to declarations of static tables in
38        pcre_compile.c and pcre_dfa_exec.c.
39    
40    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
41        caused by fix #2  above. (Subsequently also a second patch to fix the
42        first patch. And a third patch - this was a messy problem.)
43    
44    9.  Applied Craig's patch to remove the use of push_back().
45    
46    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
47        matching function regexec().
48    
49    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
50        which, however, unlike Perl's \g{...}, are subroutine calls, not back
51        references. PCRE supports relative numbers with this syntax (I don't think
52        Oniguruma does).
53    
54    12. Previously, a group with a zero repeat such as (...){0} was completely
55        omitted from the compiled regex. However, this means that if the group
56        was called as a subroutine from elsewhere in the pattern, things went wrong
57        (an internal error was given). Such groups are now left in the compiled
58        pattern, with a new opcode that causes them to be skipped at execution
59        time.
60    
61    13. Added the PCRE_JAVASCRIPT_COMPAT option. This currently does two things:
62        (a) A lone ] character is dis-allowed (Perl treats it as data).
63        (b) A back reference to an unmatched subpattern matches an empty string
64            (Perl fails the current match path).
65    
66    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
67        non-existent subpattern following a character class starting with ']' and
68        containing () gave an internal compiling error instead of "reference to
69        non-existent subpattern". Fortunately, when the pattern did exist, the
70        compiled code was correct. (When scanning forwards to check for the
71        existencd of the subpattern, it was treating the data ']' as terminating
72        the class, so got the count wrong. When actually compiling, the reference
73        was subsequently set up correctly.)
74    
75    
76    Version 7.6 28-Jan-08
77    ---------------------
78    
79    1.  A character class containing a very large number of characters with
80        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
81        overflow.
82    
83    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
84        HAVE_LONG_LONG is not defined.
85    
86    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
87        bring them up to date and include new features. This patch includes:
88    
89        - Fixed PH's badly added libz and libbz2 support.
90        - Fixed a problem with static linking.
91        - Added pcredemo. [But later removed - see 7 below.]
92        - Fixed dftables problem and added an option.
93        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
94            HAVE_LONG_LONG.
95        - Added readline support for pcretest.
96        - Added an listing of the option settings after cmake has run.
97    
98    4.  A user submitted a patch to Makefile that makes it easy to create
99        "pcre.dll" under mingw when using Configure/Make. I added stuff to
100        Makefile.am that cause it to include this special target, without
101        affecting anything else. Note that the same mingw target plus all
102        the other distribution libraries and programs are now supported
103        when configuring with CMake (see 6 below) instead of with
104        Configure/Make.
105    
106    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
107        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
108        exported in the Windows port". It has not yet been confirmed that the patch
109        solves the problem, but it does no harm.
110    
111    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
112        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
113        with CMake, and also correct the comment about stack recursion.
114    
115    7.  Remove the automatic building of pcredemo from the ./configure system and
116        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
117        of a program that users should build themselves after PCRE is installed, so
118        building it automatically is not really right. What is more, it gave
119        trouble in some build environments.
120    
121    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
122    
123    
124    Version 7.5 10-Jan-08
125    ---------------------
126    
127    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
128        values in parens when parsing an RE using the C++ wrapper."
129    
130    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
131        Characters greater than 255 were excluded from the class instead of being
132        included.
133    
134    3.  The same bug as (2) above applied to negated POSIX classes such as
135        [:^space:].
136    
137    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
138        defined or documented. It seems to have been a typo for PCRE_STATIC, so
139        I have changed it.
140    
141    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
142        first named subpattern) and a construct such as (?&a) would reference the
143        first named subpattern whose name started with "a" (in other words, the
144        length check was missing). Both these problems are fixed. "Subpattern name
145        expected" is now given for (?&) (a zero-length name), and this patch also
146        makes it give the same error for \k'' (previously it complained that that
147        was a reference to a non-existent subpattern).
148    
149    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
150        this is right because (?- can be followed by option settings as well as by
151        digits. I have, however, made the messages clearer.
152    
153    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
154        than the number used in the conditional) now cause a compile-time error.
155        This is actually not compatible with Perl, which accepts such patterns, but
156        treats the conditional as always being FALSE (as PCRE used to), but it
157        seems to me that giving a diagnostic is better.
158    
159    8.  Change "alphameric" to the more common word "alphanumeric" in comments
160        and messages.
161    
162    9.  Fix two occurrences of "backslash" in comments that should have been
163        "backspace".
164    
165    10. Remove two redundant lines of code that can never be obeyed (their function
166        was moved elsewhere).
167    
168    11. The program that makes PCRE's Unicode character property table had a bug
169        which caused it to generate incorrect table entries for sequences of
170        characters that have the same character type, but are in different scripts.
171        It amalgamated them into a single range, with the script of the first of
172        them. In other words, some characters were in the wrong script. There were
173        thirteen such cases, affecting characters in the following ranges:
174    
175          U+002b0 - U+002c1
176          U+0060c - U+0060d
177          U+0061e - U+00612
178          U+0064b - U+0065e
179          U+0074d - U+0076d
180          U+01800 - U+01805
181          U+01d00 - U+01d77
182          U+01d9b - U+01dbf
183          U+0200b - U+0200f
184          U+030fc - U+030fe
185          U+03260 - U+0327f
186          U+0fb46 - U+0fbb1
187          U+10450 - U+1049d
188    
189    12. The -o option (show only the matching part of a line) for pcregrep was not
190        compatible with GNU grep in that, if there was more than one match in a
191        line, it showed only the first of them. It now behaves in the same way as
192        GNU grep.
193    
194    13. If the -o and -v options were combined for pcregrep, it printed a blank
195        line for every non-matching line. GNU grep prints nothing, and pcregrep now
196        does the same. The return code can be used to tell if there were any
197        non-matching lines.
198    
199    14. Added --file-offsets and --line-offsets to pcregrep.
200    
201    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
202        infinitely looping recursion. The bug was that positive lookaheads were not
203        being skipped when checking for a possible empty match (negative lookaheads
204        and both kinds of lookbehind were skipped).
205    
206    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
207        inclusion of <windows.h> to before rather than after the definition of
208        INVALID_FILE_ATTRIBUTES (patch from David Byron).
209    
210    17. Specifying a possessive quantifier with a specific limit for a Unicode
211        character property caused pcre_compile() to compile bad code, which led at
212        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
213        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
214        caused the error; without that there was no problem.
215    
216    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
217    
218    19. Added --enable-pcretest-libreadline.
219    
220    20. In pcrecpp.cc, the variable 'count' was incremented twice in
221        RE::GlobalReplace(). As a result, the number of replacements returned was
222        double what it should be. I removed one of the increments, but Craig sent a
223        later patch that removed the other one (the right fix) and added unit tests
224        that check the return values (which was not done before).
225    
226    21. Several CMake things:
227    
228        (1) Arranged that, when cmake is used on Unix, the libraries end up with
229            the names libpcre and libpcreposix, not just pcre and pcreposix.
230    
231        (2) The above change means that pcretest and pcregrep are now correctly
232            linked with the newly-built libraries, not previously installed ones.
233    
234        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
235    
236    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
237        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
238        UTF-8 newline character). The key issue is that the pattern starts .*;
239        this means that the match must be either at the beginning, or after a
240        newline. The bug was in the code for advancing after a failed match and
241        checking that the new position followed a newline. It was not taking
242        account of UTF-8 characters correctly.
243    
244    23. PCRE was behaving differently from Perl in the way it recognized POSIX
245        character classes. PCRE was not treating the sequence [:...:] as a
246        character class unless the ... were all letters. Perl, however, seems to
247        allow any characters between [: and :], though of course it rejects as
248        unknown any "names" that contain non-letters, because all the known class
249        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
250        for example, whereas PCRE did not - it did not recognize a POSIX character
251        class. This seemed a bit dangerous, so the code has been changed to be
252        closer to Perl. The behaviour is not identical to Perl, because PCRE will
253        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
254        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
255        Perl does, and where it didn't before.
256    
257    24. Rewrite so as to remove the single use of %n from pcregrep because in some
258        Windows environments %n is disabled by default.
259    
260    
261    Version 7.4 21-Sep-07
262    ---------------------
263    
264    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
265        means that a class such as [\s] counted as "explicit reference to CR or
266        LF". That isn't really right - the whole point of the change was to try to
267        help when there was an actual mention of one of the two characters. So now
268        the change happens only if \r or \n (or a literal CR or LF) character is
269        encountered.
270    
271    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
272        of both had grown to the point where there were only 3 bits left.
273        Fortunately, there was spare space in the data structure, and so I have
274        moved the internal flags into a new 16-bit field to free up more option
275        bits.
276    
277    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
278        but did not set the internal JCHANGED flag - either of these is enough to
279        control the way the "get" function works - but the PCRE_INFO_JCHANGED
280        facility is supposed to tell if (?J) was ever used, so now (?J) at the
281        start sets both bits.
282    
283    4.  Added options (at build time, compile time, exec time) to change \R from
284        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
285    
286    5.  doc/pcresyntax.html was missing from the distribution.
287    
288    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
289        compatibility, even though it is no longer used.
290    
291    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
292        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
293        windows.h file is present (where different names are used). [This was
294        reversed later after testing - see 16 below.]
295    
296    8.  Changed all #include <config.h> to #include "config.h". There were also
297        some further <pcre.h> cases that I changed to "pcre.h".
298    
299    9.  When pcregrep was used with the --colour option, it missed the line ending
300        sequence off the lines that it output.
301    
302    10. It was pointed out to me that arrays of string pointers cause lots of
303        relocations when a shared library is dynamically loaded. A technique of
304        using a single long string with a table of offsets can drastically reduce
305        these. I have refactored PCRE in four places to do this. The result is
306        dramatic:
307    
308          Originally:                          290
309          After changing UCP table:            187
310          After changing error message table:   43
311          After changing table of "verbs"       36
312          After changing table of Posix names   22
313    
314        Thanks to the folks working on Gregex for glib for this insight.
315    
316    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
317        unicode-properties was also set.
318    
319    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
320    
321    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
322        checked only for CRLF.
323    
324    14. Added casts to pcretest.c to avoid compiler warnings.
325    
326    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
327    
328    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
329        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
330        entirely. This removes changes made in 7 above.
331    
332    17. The CMake files have been updated, and there is now more information about
333        building with CMake in the NON-UNIX-USE document.
334    
335    
336    Version 7.3 28-Aug-07
337    ---------------------
338    
339     1. In the rejigging of the build system that eventually resulted in 7.1, the
340        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
341        brackets there is not right, since it causes compilers to look for an
342        installed pcre.h, not the version that is in the source that is being
343        compiled (which of course may be different). I have changed it back to:
344    
345          #include "pcre.h"
346    
347        I have a vague recollection that the change was concerned with compiling in
348        different directories, but in the new build system, that is taken care of
349        by the VPATH setting the Makefile.
350    
351     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
352        when the subject happened to end in the byte 0x85 (e.g. if the last
353        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
354        characters but of course it shouldn't be taken as a newline when it is part
355        of another character. The bug was that, for an unlimited repeat of . in
356        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
357        characters when looking for a newline.
358    
359     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
360    
361     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
362        in debug output.
363    
364     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
365        long printing in the pcrecpp unittest when running under MinGW.
366    
367     6. ESC_K was left out of the EBCDIC table.
368    
369     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
370        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
371        limit also applies to "virtual nesting" when a pattern is recursive, and in
372        this case 1000 isn't so big. I have been able to remove this limit at the
373        expense of backing off one optimization in certain circumstances. Normally,
374        when pcre_exec() would call its internal match() function recursively and
375        immediately return the result unconditionally, it uses a "tail recursion"
376        feature to save stack. However, when a subpattern that can match an empty
377        string has an unlimited repetition quantifier, it no longer makes this
378        optimization. That gives it a stack frame in which to save the data for
379        checking that an empty string has been matched. Previously this was taken
380        from the 1000-entry workspace that had been reserved. So now there is no
381        explicit limit, but more stack is used.
382    
383     8. Applied Daniel's patches to solve problems with the import/export magic
384        syntax that is required for Windows, and which was going wrong for the
385        pcreposix and pcrecpp parts of the library. These were overlooked when this
386        problem was solved for the main library.
387    
388     9. There were some crude static tests to avoid integer overflow when computing
389        the size of patterns that contain repeated groups with explicit upper
390        limits. As the maximum quantifier is 65535, the maximum group length was
391        set at 30,000 so that the product of these two numbers did not overflow a
392        32-bit integer. However, it turns out that people want to use groups that
393        are longer than 30,000 bytes (though not repeat them that many times).
394        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
395        made it possible to implement the integer overflow checks in a much more
396        dynamic way, which I have now done. The artificial limitation on group
397        length has been removed - we now have only the limit on the total length of
398        the compiled pattern, which depends on the LINK_SIZE setting.
399    
400    10. Fixed a bug in the documentation for get/copy named substring when
401        duplicate names are permitted. If none of the named substrings are set, the
402        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
403        empty string.
404    
405    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
406        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
407        because the ] is interpreted as the first data character and the
408        terminating ] is not found. PCRE has been made compatible with Perl in this
409        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
410        cause memory overwriting.
411    
412    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
413        string has been matched (to stop an infinite loop). It was not recognizing
414        a conditional subpattern that could match an empty string if that
415        subpattern was within another subpattern. For example, it looped when
416        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
417        condition was not nested. This bug has been fixed.
418    
419    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
420        past the start of the subject in the presence of bytes with the top bit
421        set, for example "\x8aBCD".
422    
423    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
424        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
425    
426    14. Optimized (?!) to (*FAIL).
427    
428    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
429        This restricts code points to be within the range 0 to 0x10FFFF, excluding
430        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
431        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
432        does: it's just the validity check that is more restrictive.
433    
434    16. Inserted checks for integer overflows during escape sequence (backslash)
435        processing, and also fixed erroneous offset values for syntax errors during
436        backslash processing.
437    
438    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
439        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
440    
441    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
442        caused an overrun.
443    
444    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
445        something other than just ASCII characters) inside a group that had an
446        unlimited repeat caused a loop at compile time (while checking to see
447        whether the group could match an empty string).
448    
449    20. Debugging a pattern containing \p or \P could cause a crash. For example,
450        [\P{Any}] did so. (Error in the code for printing property names.)
451    
452    21. An orphan \E inside a character class could cause a crash.
453    
454    22. A repeated capturing bracket such as (A)? could cause a wild memory
455        reference during compilation.
456    
457    23. There are several functions in pcre_compile() that scan along a compiled
458        expression for various reasons (e.g. to see if it's fixed length for look
459        behind). There were bugs in these functions when a repeated \p or \P was
460        present in the pattern. These operators have additional parameters compared
461        with \d, etc, and these were not being taken into account when moving along
462        the compiled data. Specifically:
463    
464        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
465            length.
466    
467        (b) An item such as \pL+ within a repeated group could cause crashes or
468            loops.
469    
470        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
471            "reference to non-existent subpattern" error.
472    
473        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
474    
475    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
476        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
477    
478    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
479    
480    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
481        character were causing crashes (broken optimization).
482    
483    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
484        \p or \P) caused a compile-time loop.
485    
486    28. More problems have arisen in unanchored patterns when CRLF is a valid line
487        break. For example, the unstudied pattern [\r\n]A does not match the string
488        "\r\nA" because change 7.0/46 below moves the current point on by two
489        characters after failing to match at the start. However, the pattern \nA
490        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
491        the same is true. There doesn't seem any very clean way out of this, but
492        what I have chosen to do makes the common cases work: PCRE now takes note
493        of whether there can be an explicit match for \r or \n anywhere in the
494        pattern, and if so, 7.0/46 no longer applies. As part of this change,
495        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
496        pattern has explicit CR or LF references.
497    
498    29. Added (*CR) etc for changing newline setting at start of pattern.
499    
500    
501    Version 7.2 19-Jun-07
502    ---------------------
503    
504     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
505        which is apparently normally available under Windows.
506    
507     2. Re-jig the pcregrep tests with different newline settings in an attempt
508        to make them independent of the local environment's newline setting.
509    
510     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
511    
512     4. Some of the "internals" tests were previously cut out when the link size
513        was not 2, because the output contained actual offsets. The recent new
514        "Z" feature of pcretest means that these can be cut out, making the tests
515        usable with all link sizes.
516    
517     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
518        stack recursion. This gives a massive performance boost under BSD, but just
519        a small improvement under Linux. However, it saves one field in the frame
520        in all cases.
521    
522     6. Added more features from the forthcoming Perl 5.10:
523    
524        (a) (?-n) (where n is a string of digits) is a relative subroutine or
525            recursion call. It refers to the nth most recently opened parentheses.
526    
527        (b) (?+n) is also a relative subroutine call; it refers to the nth next
528            to be opened parentheses.
529    
530        (c) Conditions that refer to capturing parentheses can be specified
531            relatively, for example, (?(-2)... or (?(+3)...
532    
533        (d) \K resets the start of the current match so that everything before
534            is not part of it.
535    
536        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
537    
538        (f) \g{name} is another synonym - part of Perl 5.10's unification of
539            reference syntax.
540    
541        (g) (?| introduces a group in which the numbering of parentheses in each
542            alternative starts with the same number.
543    
544        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
545    
546     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
547        PCRE_INFO_JCHANGED.
548    
549     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
550        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
551        for detecting groups that can match an empty string.
552    
553     9. A pattern with a very large number of alternatives (more than several
554        hundred) was running out of internal workspace during the pre-compile
555        phase, where pcre_compile() figures out how much memory will be needed. A
556        bit of new cunning has reduced the workspace needed for groups with
557        alternatives. The 1000-alternative test pattern now uses 12 bytes of
558        workspace instead of running out of the 4096 that are available.
559    
560    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
561    
562    11. Applied patch from Google to remove an optimization that didn't quite work.
563        The report of the bug said:
564    
565          pcrecpp::RE("a*").FullMatch("aaa") matches, while
566          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
567          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
568    
569    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
570        it matched the wrong number of bytes.
571    
572    
573    Version 7.1 24-Apr-07
574    ---------------------
575    
576     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
577        that is more "standard", making use of automake and other Autotools. There
578        is some re-arrangement of the files and adjustment of comments consequent
579        on this.
580    
581     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
582        for recursive directory scanning broke on some systems because the files
583        are not scanned in any specific order and on different systems the order
584        was different. A call to "sort" has been inserted into RunGrepTest for the
585        approprate test as a short-term fix. In the longer term there may be an
586        alternative.
587    
588     3. I had an email from Eric Raymond about problems translating some of PCRE's
589        man pages to HTML (despite the fact that I distribute HTML pages, some
590        people do their own conversions for various reasons). The problems
591        concerned the use of low-level troff macros .br and .in. I have therefore
592        removed all such uses from the man pages (some were redundant, some could
593        be replaced by .nf/.fi pairs). The 132html script that I use to generate
594        HTML has been updated to handle .nf/.fi and to complain if it encounters
595        .br or .in.
596    
597     4. Updated comments in configure.ac that get placed in config.h.in and also
598        arranged for config.h to be included in the distribution, with the name
599        config.h.generic, for the benefit of those who have to compile without
600        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
601    
602     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
603        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
604        makevp.bat for the current PCRE, using the additional files
605        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
606    
607     6. A Windows user reported a minor discrepancy with test 2, which turned out
608        to be caused by a trailing space on an input line that had got lost in his
609        copy. The trailing space was an accident, so I've just removed it.
610    
611     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
612        that is needed.
613    
614     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
615        as "const" (a) because they are and (b) because it helps the PHP
616        maintainers who have recently made a script to detect big data structures
617        in the php code that should be moved to the .rodata section. I remembered
618        to update Builducptable as well, so it won't revert if ucptable.h is ever
619        re-created.
620    
621     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
622        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
623        order to be able to cut out the UTF-8 tables in the latter when UTF-8
624        support is not required. This saves 1.5-2K of code, which is important in
625        some applications.
626    
627        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
628        so as not to refer to the tables, even though these functions will never be
629        called when UTF-8 support is disabled. Otherwise there are problems with a
630        shared library.
631    
632    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
633    
634        (a) It was defining its arguments as char * instead of void *.
635    
636        (b) It was assuming that all moves were upwards in memory; this was true
637            a long time ago when I wrote it, but is no longer the case.
638    
639        The emulated memove() is provided for those environments that have neither
640        memmove() nor bcopy(). I didn't think anyone used it these days, but that
641        is clearly not the case, as these two bugs were recently reported.
642    
643    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
644        and Detrail to create the HTML documentation, the .txt form of the man
645        pages, and it removes trailing spaces from listed files. It also creates
646        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
647        case, it wraps all the #defines with #ifndefs. This script should be run
648        before "make dist".
649    
650    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
651        with Unicode property support.
652    
653        (a) For a maximizing quantifier, if the two different cases of the
654            character were of different lengths in their UTF-8 codings (there are
655            some cases like this - I found 11), and the matching function had to
656            back up over a mixture of the two cases, it incorrectly assumed they
657            were both the same length.
658    
659        (b) When PCRE was configured to use the heap rather than the stack for
660            recursion during matching, it was not correctly preserving the data for
661            the other case of a UTF-8 character when checking ahead for a match
662            while processing a minimizing repeat. If the check also involved
663            matching a wide character, but failed, corruption could cause an
664            erroneous result when trying to check for a repeat of the original
665            character.
666    
667    13. Some tidying changes to the testing mechanism:
668    
669        (a) The RunTest script now detects the internal link size and whether there
670            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
671            values substituted by "configure". (The RunGrepTest script already did
672            this for UTF-8.) The configure.ac script no longer substitutes the
673            relevant variables.
674    
675        (b) The debugging options /B and /D in pcretest show the compiled bytecode
676            with length and offset values. This means that the output is different
677            for different internal link sizes. Test 2 is skipped for link sizes
678            other than 2 because of this, bypassing the problem. Unfortunately,
679            there was also a test in test 3 (the locale tests) that used /B and
680            failed for link sizes other than 2. Rather than cut the whole test out,
681            I have added a new /Z option to pcretest that replaces the length and
682            offset values with spaces. This is now used to make test 3 independent
683            of link size. (Test 2 will be tidied up later.)
684    
685    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
686        segmentation fault instead of returning the appropriate error message.
687    
688    15. In multiline mode when the newline sequence was set to "any", the pattern
689        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
690        This doesn't seem right; it now treats the CRLF combination as the line
691        ending, and so does not match in that case. It's only a pattern such as ^$
692        that would hit this one: something like ^ABC$ would have failed after \r
693        and then tried again after \r\n.
694    
695    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
696        in an attempt to make files that differ only in their line terminators
697        compare equal. This works on Linux.
698    
699    17. Under certain error circumstances pcregrep might try to free random memory
700        as it exited. This is now fixed, thanks to valgrind.
701    
702    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
703        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
704        was because its rules for how to advance for /g after matching an empty
705        string at the end of a line did not allow for this case. They now check for
706        it specially.
707    
708    20. pcretest is supposed to handle patterns and data of any length, by
709        extending its buffers when necessary. It was getting this wrong when the
710        buffer for a data line had to be extended.
711    
712    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
713        CRLF as a newline sequence.
714    
715    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
716        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
717        I have nevertheless tidied it up.
718    
719    23. Added some casts to kill warnings from HP-UX ia64 compiler.
720    
721    24. Added a man page for pcre-config.
722    
723    
724    Version 7.0 19-Dec-06
725    ---------------------
726    
727     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
728        moving to gcc 4.1.1.
729    
730     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
731        sys/time.h, which is documented as needed for this function. It doesn't
732        seem to matter on Linux, but it showed up on some releases of OS X.
733    
734     3. It seems that there are systems where bytes whose values are greater than
735        127 match isprint() in the "C" locale. The "C" locale should be the
736        default when a C program starts up. In most systems, only ASCII printing
737        characters match isprint(). This difference caused the output from pcretest
738        to vary, making some of the tests fail. I have changed pcretest so that:
739    
740        (a) When it is outputting text in the compiled version of a pattern, bytes
741            other than 32-126 are always shown as hex escapes.
742    
743        (b) When it is outputting text that is a matched part of a subject string,
744            it does the same, unless a different locale has been set for the match
745            (using the /L modifier). In this case, it uses isprint() to decide.
746    
747     4. Fixed a major bug that caused incorrect computation of the amount of memory
748        required for a compiled pattern when options that changed within the
749        pattern affected the logic of the preliminary scan that determines the
750        length. The relevant options are -x, and -i in UTF-8 mode. The result was
751        that the computed length was too small. The symptoms of this bug were
752        either the PCRE error "internal error: code overflow" from pcre_compile(),
753        or a glibc crash with a message such as "pcretest: free(): invalid next
754        size (fast)". Examples of patterns that provoked this bug (shown in
755        pcretest format) are:
756    
757          /(?-x: )/x
758          /(?x)(?-x: \s*#\s*)/
759          /((?i)[\x{c0}])/8
760          /(?i:[\x{c0}])/8
761    
762        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
763        is now done differently.
764    
765     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
766        wrapper classes; (b) implement a new function in the C++ scanner that is
767        more efficient than the old way of doing things because it avoids levels of
768        recursion in the regex matching; (c) add a paragraph to the documentation
769        for the FullMatch() function.
770    
771     6. The escape sequence \n was being treated as whatever was defined as
772        "newline". Not only was this contrary to the documentation, which states
773        that \n is character 10 (hex 0A), but it also went horribly wrong when
774        "newline" was defined as CRLF. This has been fixed.
775    
776     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
777        was being set to -1 for the "end of line" case (supposedly a value that no
778        character can have). Though this value is never used (the check for end of
779        line is "zero bytes in current character"), it caused compiler complaints.
780        I've changed it to 0xffffffff.
781    
782     8. In pcre_version.c, the version string was being built by a sequence of
783        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
784        string (as it is for production releases) called a macro with an empty
785        argument. The C standard says the result of this is undefined. The gcc
786        compiler treats it as an empty string (which was what was wanted) but it is
787        reported that Visual C gives an error. The source has been hacked around to
788        avoid this problem.
789    
790     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
791        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
792        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
793        of them did).
794    
795    10. Originally, pcretest opened its input and output without "b"; then I was
796        told that "b" was needed in some environments, so it was added for release
797        5.0 to both the input and output. (It makes no difference on Unix-like
798        systems.) Later I was told that it is wrong for the input on Windows. I've
799        now abstracted the modes into two macros, to make it easier to fiddle with
800        them, and removed "b" from the input mode under Windows.
801    
802    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
803    
804    12. Added -help and --help to pcretest as an official way of being reminded
805        of the options.
806    
807    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
808        and pcrecpp.cc because they annoy compilers at high warning levels.
809    
810    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
811    
812    15. Fixed an occurrence of == in configure.ac that should have been = (shell
813        scripts are not C programs :-) and which was not noticed because it works
814        on Linux.
815    
816    16. pcretest is supposed to handle any length of pattern and data line (as one
817        line or as a continued sequence of lines) by extending its input buffer if
818        necessary. This feature was broken for very long pattern lines, leading to
819        a string of junk being passed to pcre_compile() if the pattern was longer
820        than about 50K.
821    
822    17. I have done a major re-factoring of the way pcre_compile() computes the
823        amount of memory needed for a compiled pattern. Previously, there was code
824        that made a preliminary scan of the pattern in order to do this. That was
825        OK when PCRE was new, but as the facilities have expanded, it has become
826        harder and harder to keep it in step with the real compile phase, and there
827        have been a number of bugs (see for example, 4 above). I have now found a
828        cunning way of running the real compile function in a "fake" mode that
829        enables it to compute how much memory it would need, while actually only
830        ever using a few hundred bytes of working memory and without too many
831        tests of the mode. This should make future maintenance and development
832        easier. A side effect of this work is that the limit of 200 on the nesting
833        depth of parentheses has been removed (though this was never a serious
834        limitation, I suspect). However, there is a downside: pcre_compile() now
835        runs more slowly than before (30% or more, depending on the pattern). I
836        hope this isn't a big issue. There is no effect on runtime performance.
837    
838    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
839        newline (only possible for the last line of a file) and it was a
840        pattern that set a locale (followed by /Lsomething), pcretest crashed.
841    
842    19. Added additional timing features to pcretest. (1) The -tm option now times
843        matching only, not compiling. (2) Both -t and -tm can be followed, as a
844        separate command line item, by a number that specifies the number of
845        repeats to use when timing. The default is 50000; this gives better
846        precision, but takes uncomfortably long for very large patterns.
847    
848    20. Extended pcre_study() to be more clever in cases where a branch of a
849        subpattern has no definite first character. For example, (a*|b*)[cd] would
850        previously give no result from pcre_study(). Now it recognizes that the
851        first character must be a, b, c, or d.
852    
853    21. There was an incorrect error "recursive call could loop indefinitely" if
854        a subpattern (or the entire pattern) that was being tested for matching an
855        empty string contained only one non-empty item after a nested subpattern.
856        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
857        incorrectly, because the \d was being skipped in the check.
858    
859    22. The pcretest program now has a new pattern option /B and a command line
860        option -b, which is equivalent to adding /B to every pattern. This causes
861        it to show the compiled bytecode, without the additional information that
862        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
863        is the same as /B/I).
864    
865    23. A new optimization is now able automatically to treat some sequences such
866        as a*b as a*+b. More specifically, if something simple (such as a character
867        or a simple class like \d) has an unlimited quantifier, and is followed by
868        something that cannot possibly match the quantified thing, the quantifier
869        is automatically "possessified".
870    
871    24. A recursive reference to a subpattern whose number was greater than 39
872        went wrong under certain circumstances in UTF-8 mode. This bug could also
873        have affected the operation of pcre_study().
874    
875    25. Realized that a little bit of performance could be had by replacing
876        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
877    
878    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
879    
880    27. Possessive quantifiers such as a++ were previously implemented by turning
881        them into atomic groups such as ($>a+). Now they have their own opcodes,
882        which improves performance. This includes the automatically created ones
883        from 23 above.
884    
885    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
886        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
887        the first matched character to be a colon. This applied both to named and
888        numbered groups.
889    
890    29. The ucpinternal.h header file was missing its idempotency #ifdef.
891    
892    30. I was sent a "project" file called libpcre.a.dev which I understand makes
893        building PCRE on Windows easier, so I have included it in the distribution.
894    
895    31. There is now a check in pcretest against a ridiculously large number being
896        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
897        loop, the loop is abandoned.
898    
899    32. Forward references to subpatterns in conditions such as (?(2)...) where
900        subpattern 2 is defined later cause pcre_compile() to search forwards in
901        the pattern for the relevant set of parentheses. This search went wrong
902        when there were unescaped parentheses in a character class, parentheses
903        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
904    
905    33. "Subroutine" calls and backreferences were previously restricted to
906        referencing subpatterns earlier in the regex. This restriction has now
907        been removed.
908    
909    34. Added a number of extra features that are going to be in Perl 5.10. On the
910        whole, these are just syntactic alternatives for features that PCRE had
911        previously implemented using the Python syntax or my own invention. The
912        other formats are all retained for compatibility.
913    
914        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
915            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
916            also .NET compatible.
917    
918        (b) A recursion or subroutine call to a named group can now be defined as
919            (?&name) as well as (?P>name).
920    
921        (c) A backreference to a named group can now be defined as \k<name> or
922            \k'name' as well as (?P=name). The new forms, as well as being in Perl
923            5.10, are also .NET compatible.
924    
925        (d) A conditional reference to a named group can now use the syntax
926            (?(<name>) or (?('name') as well as (?(name).
927    
928        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
929            groups (named and numbered) that are never evaluated inline, but can be
930            called as "subroutines" from elsewhere. In effect, the DEFINE condition
931            is always false. There may be only one alternative in such a group.
932    
933        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
934            as the simple (?(R). The condition is true only if the most recent
935            recursion is that of the given number or name. It does not search out
936            through the entire recursion stack.
937    
938        (g) The escape \gN or \g{N} has been added, where N is a positive or
939            negative number, specifying an absolute or relative reference.
940    
941    35. Tidied to get rid of some further signed/unsigned compiler warnings and
942        some "unreachable code" warnings.
943    
944    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
945        things, this adds five new scripts.
946    
947    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
948        There were also incompatibilities regarding the handling of \Q..\E inside
949        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
950        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
951    
952    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
953        matches an empty string, and forcibly breaks the loop. There were bugs in
954        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
955        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
956        separate and independent bugs (that affected different cases) have been
957        fixed.
958    
959    39. Refactored the code to abolish the use of different opcodes for small
960        capturing bracket numbers. This is a tidy that I avoided doing when I
961        removed the limit on the number of capturing brackets for 3.5 back in 2001.
962        The new approach is not only tidier, it makes it possible to reduce the
963        memory needed to fix the previous bug (38).
964    
965    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
966        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
967        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
968        mode.
969    
970    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
971        report.
972    
973    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
974        copy construction and assignment in the C++ wrapper.
975    
976    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
977        couple of bugs that could have given wrong results in the "--newline=crlf"
978        case.
979    
980    44. Added a number of casts and did some reorganization of signed/unsigned int
981        variables following suggestions from Dair Grant. Also renamed the variable
982        "this" as "item" because it is a C++ keyword.
983    
984    45. Arranged for dftables to add
985    
986          #include "pcre_internal.h"
987    
988        to pcre_chartables.c because without it, gcc 4.x may remove the array
989        definition from the final binary if PCRE is built into a static library and
990        dead code stripping is activated.
991    
992    46. For an unanchored pattern, if a match attempt fails at the start of a
993        newline sequence, and the newline setting is CRLF or ANY, and the next two
994        characters are CRLF, advance by two characters instead of one.
995    
996    
997    Version 6.7 04-Jul-06
998    ---------------------
999    
1000     1. In order to handle tests when input lines are enormously long, pcretest has
1001        been re-factored so that it automatically extends its buffers when
1002        necessary. The code is crude, but this _is_ just a test program. The
1003        default size has been increased from 32K to 50K.
1004    
1005     2. The code in pcre_study() was using the value of the re argument before
1006        testing it for NULL. (Of course, in any sensible call of the function, it
1007        won't be NULL.)
1008    
1009     3. The memmove() emulation function in pcre_internal.h, which is used on
1010        systems that lack both memmove() and bcopy() - that is, hardly ever -
1011        was missing a "static" storage class specifier.
1012    
1013     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
1014        containing an extended class (one that cannot be represented by a bitmap
1015        because it contains high-valued characters or Unicode property items, e.g.
1016        [\pZ]). Almost always one would set UTF-8 mode when processing such a
1017        pattern, but PCRE should not loop if you do not (it no longer does).
1018        [Detail: two cases were found: (a) a repeated subpattern containing an
1019        extended class; (b) a recursive reference to a subpattern that followed a
1020        previous extended class. It wasn't skipping over the extended class
1021        correctly when UTF-8 mode was not set.]
1022    
1023     5. A negated single-character class was not being recognized as fixed-length
1024        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
1025        compile error "lookbehind assertion is not fixed length".
1026    
1027     6. The RunPerlTest auxiliary script was showing an unexpected difference
1028        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
1029        write a Perl script that can interpret lines of an input file either as
1030        byte characters or as UTF-8, which is what "perltest" was being required to
1031        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
1032        can't do is switch easily at run time between having the "use utf8;" pragma
1033        or not. In the end, I fudged it by using the RunPerlTest script to insert
1034        "use utf8;" explicitly for the UTF-8 tests.
1035    
1036     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
1037        the end of the subject string, contrary to the documentation and to what
1038        Perl does. This was true of both matching functions. Now it matches only at
1039        the start of the subject and immediately after *internal* newlines.
1040    
1041     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
1042        a pointer to an int instead of a pointer to an unsigned long int. This
1043        caused problems on 64-bit systems.
1044    
1045     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
1046        instance of the 'standard' template library not being so standard".
1047    
1048    10. There was no check on the number of named subpatterns nor the maximum
1049        length of a subpattern name. The product of these values is used to compute
1050        the size of the memory block for a compiled pattern. By supplying a very
1051        long subpattern name and a large number of named subpatterns, the size
1052        computation could be caused to overflow. This is now prevented by limiting
1053        the length of names to 32 characters, and the number of named subpatterns
1054        to 10,000.
1055    
1056    11. Subpatterns that are repeated with specific counts have to be replicated in
1057        the compiled pattern. The size of memory for this was computed from the
1058        length of the subpattern and the repeat count. The latter is limited to
1059        65535, but there was no limit on the former, meaning that integer overflow
1060        could in principle occur. The compiled length of a repeated subpattern is
1061        now limited to 30,000 bytes in order to prevent this.
1062    
1063    12. Added the optional facility to have named substrings with the same name.
1064    
1065    13. Added the ability to use a named substring as a condition, using the
1066        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
1067        are numbers (not recommended). Forward references are permitted.
1068    
1069    14. Added forward references in named backreferences (if you see what I mean).
1070    
1071    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
1072        pattern could run off the end of the subject. For example, the pattern
1073        "(?s)(.{1,5})"8 did this with the subject "ab".
1074    
1075    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
1076        PCRE_CASELESS was set when matching characters that were quantified with ?
1077        or *.
1078    
1079    17. A character class other than a single negated character that had a minimum
1080        but no maximum quantifier - for example [ab]{6,} - was not handled
1081        correctly by pce_dfa_exec(). It would match only one character.
1082    
1083    18. A valid (though odd) pattern that looked like a POSIX character
1084        class but used an invalid character after [ (for example [[,abc,]]) caused
1085        pcre_compile() to give the error "Failed: internal error: code overflow" or
1086        in some cases to crash with a glibc free() error. This could even happen if
1087        the pattern terminated after [[ but there just happened to be a sequence of
1088        letters, a binary zero, and a closing ] in the memory that followed.
1089    
1090    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
1091        over the years. Originally (before any Unicode support), just the bottom 8
1092        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
1093        output from "man perlunicode" includes this:
1094    
1095          The regular expression compiler produces polymorphic opcodes.  That
1096          is, the pattern adapts to the data and automatically switches to
1097          the Unicode character scheme when presented with Unicode data--or
1098          instead uses a traditional byte scheme when presented with byte
1099          data.
1100    
1101        Sadly, a wide octal escape does not cause a switch, and in a string with
1102        no other multibyte characters, these octal escapes are treated as before.
1103        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
1104        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
1105        Unicode string.
1106    
1107        I have not perpetrated such confusion in PCRE. Up till now, it took just
1108        the bottom 8 bits, as in old Perl. I have now made octal escapes with
1109        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
1110        translate to the appropriate multibyte character.
1111    
1112    29. Applied some refactoring to reduce the number of warnings from Microsoft
1113        and Borland compilers. This has included removing the fudge introduced
1114        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
1115        a warning about an unused variable.
1116    
1117    21. PCRE has not included VT (character 0x0b) in the set of whitespace
1118        characters since release 4.0, because Perl (from release 5.004) does not.
1119        [Or at least, is documented not to: some releases seem to be in conflict
1120        with the documentation.] However, when a pattern was studied with
1121        pcre_study() and all its branches started with \s, PCRE still included VT
1122        as a possible starting character. Of course, this did no harm; it just
1123        caused an unnecessary match attempt.
1124    
1125    22. Removed a now-redundant internal flag bit that recorded the fact that case
1126        dependency changed within the pattern. This was once needed for "required
1127        byte" processing, but is no longer used. This recovers a now-scarce options
1128        bit. Also moved the least significant internal flag bit to the most-
1129        significant bit of the word, which was not previously used (hangover from
1130        the days when it was an int rather than a uint) to free up another bit for
1131        the future.
1132    
1133    23. Added support for CRLF line endings as well as CR and LF. As well as the
1134        default being selectable at build time, it can now be changed at runtime
1135        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1136        specify that it is scanning data with non-default line endings.
1137    
1138    24. Changed the definition of CXXLINK to make it agree with the definition of
1139        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1140    
1141    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1142        recursions. This makes a big different to stack usage for some patterns.
1143    
1144    26. If a subpattern containing a named recursion or subroutine reference such
1145        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1146        the space required for the compiled pattern went wrong and gave too small a
1147        value. Depending on the environment, this could lead to "Failed: internal
1148        error: code overflow at offset 49" or "glibc detected double free or
1149        corruption" errors.
1150    
1151    27. Applied patches from Google (a) to support the new newline modes and (b) to
1152        advance over multibyte UTF-8 characters in GlobalReplace.
1153    
1154    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1155        difference for some implementation of PCRE in some Windows version.
1156    
1157    29. Added some extra testing facilities to pcretest:
1158    
1159        \q<number>   in a data line sets the "match limit" value
1160        \Q<number>   in a data line sets the "match recursion limt" value
1161        -S <number>  sets the stack size, where <number> is in megabytes
1162    
1163        The -S option isn't available for Windows.
1164    
1165    
1166    Version 6.6 06-Feb-06
1167    ---------------------
1168    
1169     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1170        in pcreposix.h. I have copied the definition from pcre.h.
1171    
1172     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1173        because pcre.h is no longer a built file.
1174    
1175     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1176        not normally included in the compiled code.
1177    
1178    
1179    Version 6.5 01-Feb-06
1180    ---------------------
1181    
1182     1. When using the partial match feature with pcre_dfa_exec(), it was not
1183        anchoring the second and subsequent partial matches at the new starting
1184        point. This could lead to incorrect results. For example, with the pattern
1185        /1234/, partially matching against "123" and then "a4" gave a match.
1186    
1187     2. Changes to pcregrep:
1188    
1189        (a) All non-match returns from pcre_exec() were being treated as failures
1190            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
1191            error message is output. Some extra information is given for the
1192            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
1193            probably the only errors that are likely to be caused by users (by
1194            specifying a regex that has nested indefinite repeats, for instance).
1195            If there are more than 20 of these errors, pcregrep is abandoned.
1196    
1197        (b) A binary zero was treated as data while matching, but terminated the
1198            output line if it was written out. This has been fixed: binary zeroes
1199            are now no different to any other data bytes.
1200    
1201        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
1202            used to set a locale for matching. The --locale=xxxx long option has
1203            been added (no short equivalent) to specify a locale explicitly on the
1204            pcregrep command, overriding the environment variables.
1205    
1206        (d) When -B was used with -n, some line numbers in the output were one less
1207            than they should have been.
1208    
1209        (e) Added the -o (--only-matching) option.
1210    
1211        (f) If -A or -C was used with -c (count only), some lines of context were
1212            accidentally printed for the final match.
1213    
1214        (g) Added the -H (--with-filename) option.
1215    
1216        (h) The combination of options -rh failed to suppress file names for files
1217            that were found from directory arguments.
1218    
1219        (i) Added the -D (--devices) and -d (--directories) options.
1220    
1221        (j) Added the -F (--fixed-strings) option.
1222    
1223        (k) Allow "-" to be used as a file name for -f as well as for a data file.
1224    
1225        (l) Added the --colo(u)r option.
1226    
1227        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
1228            is not present by default.
1229    
1230     3. A nasty bug was discovered in the handling of recursive patterns, that is,
1231        items such as (?R) or (?1), when the recursion could match a number of
1232        alternatives. If it matched one of the alternatives, but subsequently,
1233        outside the recursion, there was a failure, the code tried to back up into
1234        the recursion. However, because of the way PCRE is implemented, this is not
1235        possible, and the result was an incorrect result from the match.
1236    
1237        In order to prevent this happening, the specification of recursion has
1238        been changed so that all such subpatterns are automatically treated as
1239        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1240    
1241     4. I had overlooked the fact that, in some locales, there are characters for
1242        which isalpha() is true but neither isupper() nor islower() are true. In
1243        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1244        and ordfeminine) are like this. This affected the treatment of \w and \W
1245        when they appeared in character classes, but not when they appeared outside
1246        a character class. The bit map for "word" characters is now created
1247        separately from the results of isalnum() instead of just taking it from the
1248        upper, lower, and digit maps. (Plus the underscore character, of course.)
1249    
1250     5. The above bug also affected the handling of POSIX character classes such as
1251        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
1252        permanent tables. Instead, the bit maps for such a class were previously
1253        created as the appropriate unions of the upper, lower, and digit bitmaps.
1254        Now they are created by subtraction from the [[:word:]] class, which has
1255        its own bitmap.
1256    
1257     6. The [[:blank:]] character class matches horizontal, but not vertical space.
1258        It is created by subtracting the vertical space characters (\x09, \x0a,
1259        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
1260        subtraction was done in the overall bitmap for a character class, meaning
1261        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
1262        be recognized. This bug has been fixed.
1263    
1264     7. Patches from the folks at Google:
1265    
1266          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
1267          real life, but is still worth protecting against".
1268    
1269          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
1270          regular expressions".
1271    
1272          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
1273          have it.
1274    
1275          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
1276          "configure" and the latter not, in order to fix a problem somebody had
1277          with compiling the Arg class on HP-UX.
1278    
1279          (e) Improve the error-handling of the C++ wrapper a little bit.
1280    
1281          (f) New tests for checking recursion limiting.
1282    
1283     8. The pcre_memmove() function, which is used only if the environment does not
1284        have a standard memmove() function (and is therefore rarely compiled),
1285        contained two bugs: (a) use of int instead of size_t, and (b) it was not
1286        returning a result (though PCRE never actually uses the result).
1287    
1288     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
1289        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
1290        returned instead of calling malloc() with an overflowing number that would
1291        most likely cause subsequent chaos.
1292    
1293    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
1294    
1295    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
1296        with this option is matched, the nmatch and pmatch options of regexec() are
1297        ignored.
1298    
1299    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
1300        provided in case anyone wants to the the POSIX interface with UTF-8
1301        strings.
1302    
1303    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1304        C++ linking (needed for some HP-UX environments).
1305    
1306    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1307        (unused parameter) and in the pcre_printint() function (omitted "default"
1308        switch label when the default is to do nothing).
1309    
1310    15. Added some code to make it possible, when PCRE is compiled as a C++
1311        library, to replace subject pointers for pcre_exec() with a smart pointer
1312        class, thus making it possible to process discontinuous strings.
1313    
1314    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1315        much the same function. They were added by different people who were trying
1316        to make PCRE easy to compile on non-Unix systems. It has been suggested
1317        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1318        for compiling on Windows systems. I have therefore replaced it with
1319        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1320        defaults to "extern" for C or "extern C" for C++, which works fine on
1321        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1322        SCOPE with something explicit in config.h. In addition:
1323    
1324        (a) pcreposix.h still had just "extern" instead of either of these macros;
1325            I have replaced it with PCRE_DATA_SCOPE.
1326    
1327        (b) Functions such as _pcre_xclass(), which are internal to the library,
1328            but external in the C sense, all had PCRE_EXPORT in their definitions.
1329            This is apparently wrong for the Windows case, so I have removed it.
1330            (It makes no difference on Unix-like systems.)
1331    
1332    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1333        of recursive calls to match(). This is different to MATCH_LIMIT because
1334        that limits the total number of calls to match(), not all of which increase
1335        the depth of recursion. Limiting the recursion depth limits the amount of
1336        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1337        when PCRE is compiled, and changed at run time. A patch from Google adds
1338        this functionality to the C++ interface.
1339    
1340    18. Changes to the handling of Unicode character properties:
1341    
1342        (a) Updated the table to Unicode 4.1.0.
1343    
1344        (b) Recognize characters that are not in the table as "Cn" (undefined).
1345    
1346        (c) I revised the way the table is implemented to a much improved format
1347            which includes recognition of ranges. It now supports the ranges that
1348            are defined in UnicodeData.txt, and it also amalgamates other
1349            characters into ranges. This has reduced the number of entries in the
1350            table from around 16,000 to around 3,000, thus reducing its size
1351            considerably. I realized I did not need to use a tree structure after
1352            all - a binary chop search is just as efficient. Having reduced the
1353            number of entries, I extended their size from 6 bytes to 8 bytes to
1354            allow for more data.
1355    
1356        (d) Added support for Unicode script names via properties such as \p{Han}.
1357    
1358    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1359        matching that character.
1360    
1361    20. When matching a repeated Unicode property with a minimum greater than zero,
1362        (for example \pL{2,}), PCRE could look past the end of the subject if it
1363        reached it while seeking the minimum number of characters. This could
1364        happen only if some of the characters were more than one byte long, because
1365        there is a check for at least the minimum number of bytes.
1366    
1367    21. Refactored the implementation of \p and \P so as to be more general, to
1368        allow for more different types of property in future. This has changed the
1369        compiled form incompatibly. Anybody with saved compiled patterns that use
1370        \p or \P will have to recompile them.
1371    
1372    22. Added "Any" and "L&" to the supported property types.
1373    
1374    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1375        but give a compile time error if the value is greater than 0xff.
1376    
1377    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1378        accidentally not being installed or uninstalled.
1379    
1380    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1381        made were to insert the current release number. This seemed silly, because
1382        it made things harder for people building PCRE on systems that don't run
1383        "configure". I have turned pcre.h into a distributed file, no longer built
1384        by "configure", with the version identification directly included. There is
1385        no longer a pcre.h.in file.
1386    
1387        However, this change necessitated a change to the pcre-config script as
1388        well. It is built from pcre-config.in, and one of the substitutions was the
1389        release number. I have updated configure.ac so that ./configure now finds
1390        the release number by grepping pcre.h.
1391    
1392    26. Added the ability to run the tests under valgrind.
1393    
1394    
1395    Version 6.4 05-Sep-05
1396    ---------------------
1397    
1398     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1399        "--" to be printed when multiple files were scanned, even when none of the
1400        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1401        consider it to be a bug, and have restored the previous behaviour.
1402    
1403     2. A couple of code tidies to get rid of compiler warnings.
1404    
1405     3. The pcretest program used to cheat by referring to symbols in the library
1406        whose names begin with _pcre_. These are internal symbols that are not
1407        really supposed to be visible externally, and in some environments it is
1408        possible to suppress them. The cheating is now confined to including
1409        certain files from the library's source, which is a bit cleaner.
1410    
1411     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1412        file's purpose clearer.
1413    
1414     5. Reorganized pcre_ucp_findchar().
1415    
1416    
1417    Version 6.3 15-Aug-05
1418    ---------------------
1419    
1420     1. The file libpcre.pc.in did not have general read permission in the tarball.
1421    
1422     2. There were some problems when building without C++ support:
1423    
1424        (a) If C++ support was not built, "make install" and "make test" still
1425            tried to test it.
1426    
1427        (b) There were problems when the value of CXX was explicitly set. Some
1428            changes have been made to try to fix these, and ...
1429    
1430        (c) --disable-cpp can now be used to explicitly disable C++ support.
1431    
1432        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
1433            backslash in a target when C++ was disabled. This confuses some
1434            versions of "make", apparently. Using an intermediate variable solves
1435            this. (Same for CPP_LOBJ.)
1436    
1437     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
1438        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
1439        necessary on certain architectures.
1440    
1441     4. Added a setting of -export-symbols-regex to the link command to remove
1442        those symbols that are exported in the C sense, but actually are local
1443        within the library, and not documented. Their names all begin with
1444        "_pcre_". This is not a perfect job, because (a) we have to except some
1445        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
1446        available (and never for static libraries). I have made a note to try to
1447        find a way round (a) in the future.
1448    
1449    
1450    Version 6.2 01-Aug-05
1451    ---------------------
1452    
1453     1. There was no test for integer overflow of quantifier values. A construction
1454        such as {1111111111111111} would give undefined results. What is worse, if
1455        a minimum quantifier for a parenthesized subpattern overflowed and became
1456        negative, the calculation of the memory size went wrong. This could have
1457        led to memory overwriting.
1458    
1459     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
1460    
1461     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
1462        operating environments where this matters.
1463    
1464     4. Applied Giuseppe Maxia's patch to add additional features for controlling
1465        PCRE options from within the C++ wrapper.
1466    
1467     5. Named capturing subpatterns were not being correctly counted when a pattern
1468        was compiled. This caused two problems: (a) If there were more than 100
1469        such subpatterns, the calculation of the memory needed for the whole
1470        compiled pattern went wrong, leading to an overflow error. (b) Numerical
1471        back references of the form \12, where the number was greater than 9, were
1472        not recognized as back references, even though there were sufficient
1473        previous subpatterns.
1474    
1475     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
1476        versions of gcc, e.g. 2.95.4.
1477    
1478    
1479  Version 6.1 21-Jun-05  Version 6.1 21-Jun-05
1480  ---------------------  ---------------------
1481    

Legend:
Removed from v.79  
changed lines
  Added in v.340

  ViewVC Help
Powered by ViewVC 1.1.5