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

Diff of /code/trunk/ChangeLog

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

revision 71 by nigel, Sat Feb 24 21:40:24 2007 UTC revision 143 by ph10, Mon Apr 2 10:08:14 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    Version 7.1 12-Mar-07
5    ---------------------
6    
7     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
8        that is more "standard", making use of automake and other Autotools. There
9        is some re-arrangement of the files and adjustment of comments consequent
10        on this.
11    
12     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
13        for recursive directory scanning broke on some systems because the files
14        are not scanned in any specific order and on different systems the order
15        was different. A call to "sort" has been inserted into RunGrepTest for the
16        approprate test as a short-term fix. In the longer term there may be an
17        alternative.
18    
19     3. I had an email from Eric Raymond about problems translating some of PCRE's
20        man pages to HTML (despite the fact that I distribute HTML pages, some
21        people do their own conversions for various reasons). The problems
22        concerned the use of low-level troff macros .br and .in. I have therefore
23        removed all such uses from the man pages (some were redundant, some could
24        be replaced by .nf/.fi pairs). The 132html script that I use to generate
25        HTML has been updated to handle .nf/.fi and to complain if it encounters
26        .br or .in.
27    
28     4. Updated comments in configure.ac that get placed in config.h.in and also
29        arranged for config.h to be included in the distribution, with the name
30        config.h.generic, for the benefit of those who have to compile without
31        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
32    
33     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
34        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
35        makevp.bat for the current PCRE, using the additional files
36        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
37    
38     6. A Windows user reported a minor discrepancy with test 2, which turned out
39        to be caused by a trailing space on an input line that had got lost in his
40        copy. The trailing space was an accident, so I've just removed it.
41    
42     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
43        that is needed.
44    
45     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
46        as "const" (a) because they are and (b) because it helps the PHP
47        maintainers who have recently made a script to detect big data structures
48        in the php code that should be moved to the .rodata section. I remembered
49        to update Builducptable as well, so it won't revert if ucptable.h is ever
50        re-created.
51    
52     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
53        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
54        order to be able to cut out the UTF-8 tables in the latter when UTF-8
55        support is not required. This saves 1.5-2K of code, which is important in
56        some applications.
57    
58        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
59        so as not to refer to the tables, even though these functions will never be
60        called when UTF-8 support is disabled. Otherwise there are problems with a
61        shared library.
62    
63    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
64    
65        (a) It was defining its arguments as char * instead of void *.
66    
67        (b) It was assuming that all moves were upwards in memory; this was true
68            a long time ago when I wrote it, but is no longer the case.
69    
70        The emulated memove() is provided for those environments that have neither
71        memmove() nor bcopy(). I didn't think anyone used it these days, but that
72        is clearly not the case, as these two bugs were recently reported.
73    
74    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
75        and Detrail to create the HTML documentation, the .txt form of the man
76        pages, and it removes trailing spaces from listed files. It also creates
77        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
78        case, it wraps all the #defines with #ifndefs. This script should be run
79        before "make dist".
80    
81    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
82        with Unicode property support.
83    
84        (a) For a maximizing quantifier, if the two different cases of the
85            character were of different lengths in their UTF-8 codings (there are
86            some cases like this - I found 11), and the matching function had to
87            back up over a mixture of the two cases, it incorrectly assumed they
88            were both the same length.
89    
90        (b) When PCRE was configured to use the heap rather than the stack for
91            recursion during matching, it was not correctly preserving the data for
92            the other case of a UTF-8 character when checking ahead for a match
93            while processing a minimizing repeat. If the check also involved
94            matching a wide character, but failed, corruption could cause an
95            erroneous result when trying to check for a repeat of the original
96            character.
97    
98    13. Some tidying changes to the testing mechanism:
99    
100        (a) The RunTest script now detects the internal link size and whether there
101            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
102            values substituted by "configure". (The RunGrepTest script already did
103            this for UTF-8.) The configure.ac script no longer substitutes the
104            relevant variables.
105    
106        (b) The debugging options /B and /D in pcretest show the compiled bytecode
107            with length and offset values. This means that the output is different
108            for different internal link sizes. Test 2 is skipped for link sizes
109            other than 2 because of this, bypassing the problem. Unfortunately,
110            there was also a test in test 3 (the locale tests) that used /B and
111            failed for link sizes other than 2. Rather than cut the whole test out,
112            I have added a new /Z option to pcretest that replaces the length and
113            offset values with spaces. This is now used to make test 3 independent
114            of link size. (Test 2 will be tidied up later.)
115    
116    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
117        segmentation fault instead of returning the appropriate error message.
118    
119    15. In multiline mode when the newline sequence was set to "any", the pattern
120        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
121        This doesn't seem right; it now treats the CRLF combination as the line
122        ending, and so does not match in that case. It's only a pattern such as ^$
123        that would hit this one: something like ^ABC$ would have failed after \r
124        and then tried again after \r\n.
125    
126    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
127        in an attempt to make files that differ only in their line terminators
128        compare equal. This works on Linux.
129    
130    17. Under certain error circumstances pcregrep might try to free random memory
131        as it exited. This is now fixed, thanks to valgrind.
132    
133    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
134        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
135        was because its rules for how to advance for /g after matching an empty
136        string at the end of a line did not allow for this case. They now check for
137        it specially.
138    
139    
140    Version 7.0 19-Dec-06
141    ---------------------
142    
143     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
144        moving to gcc 4.1.1.
145    
146     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
147        sys/time.h, which is documented as needed for this function. It doesn't
148        seem to matter on Linux, but it showed up on some releases of OS X.
149    
150     3. It seems that there are systems where bytes whose values are greater than
151        127 match isprint() in the "C" locale. The "C" locale should be the
152        default when a C program starts up. In most systems, only ASCII printing
153        characters match isprint(). This difference caused the output from pcretest
154        to vary, making some of the tests fail. I have changed pcretest so that:
155    
156        (a) When it is outputting text in the compiled version of a pattern, bytes
157            other than 32-126 are always shown as hex escapes.
158    
159        (b) When it is outputting text that is a matched part of a subject string,
160            it does the same, unless a different locale has been set for the match
161            (using the /L modifier). In this case, it uses isprint() to decide.
162    
163     4. Fixed a major bug that caused incorrect computation of the amount of memory
164        required for a compiled pattern when options that changed within the
165        pattern affected the logic of the preliminary scan that determines the
166        length. The relevant options are -x, and -i in UTF-8 mode. The result was
167        that the computed length was too small. The symptoms of this bug were
168        either the PCRE error "internal error: code overflow" from pcre_compile(),
169        or a glibc crash with a message such as "pcretest: free(): invalid next
170        size (fast)". Examples of patterns that provoked this bug (shown in
171        pcretest format) are:
172    
173          /(?-x: )/x
174          /(?x)(?-x: \s*#\s*)/
175          /((?i)[\x{c0}])/8
176          /(?i:[\x{c0}])/8
177    
178        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
179        is now done differently.
180    
181     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
182        wrapper classes; (b) implement a new function in the C++ scanner that is
183        more efficient than the old way of doing things because it avoids levels of
184        recursion in the regex matching; (c) add a paragraph to the documentation
185        for the FullMatch() function.
186    
187     6. The escape sequence \n was being treated as whatever was defined as
188        "newline". Not only was this contrary to the documentation, which states
189        that \n is character 10 (hex 0A), but it also went horribly wrong when
190        "newline" was defined as CRLF. This has been fixed.
191    
192     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
193        was being set to -1 for the "end of line" case (supposedly a value that no
194        character can have). Though this value is never used (the check for end of
195        line is "zero bytes in current character"), it caused compiler complaints.
196        I've changed it to 0xffffffff.
197    
198     8. In pcre_version.c, the version string was being built by a sequence of
199        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
200        string (as it is for production releases) called a macro with an empty
201        argument. The C standard says the result of this is undefined. The gcc
202        compiler treats it as an empty string (which was what was wanted) but it is
203        reported that Visual C gives an error. The source has been hacked around to
204        avoid this problem.
205    
206     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
207        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
208        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
209        of them did).
210    
211    10. Originally, pcretest opened its input and output without "b"; then I was
212        told that "b" was needed in some environments, so it was added for release
213        5.0 to both the input and output. (It makes no difference on Unix-like
214        systems.) Later I was told that it is wrong for the input on Windows. I've
215        now abstracted the modes into two macros, to make it easier to fiddle with
216        them, and removed "b" from the input mode under Windows.
217    
218    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
219    
220    12. Added -help and --help to pcretest as an official way of being reminded
221        of the options.
222    
223    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
224        and pcrecpp.cc because they annoy compilers at high warning levels.
225    
226    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
227    
228    15. Fixed an occurrence of == in configure.ac that should have been = (shell
229        scripts are not C programs :-) and which was not noticed because it works
230        on Linux.
231    
232    16. pcretest is supposed to handle any length of pattern and data line (as one
233        line or as a continued sequence of lines) by extending its input buffer if
234        necessary. This feature was broken for very long pattern lines, leading to
235        a string of junk being passed to pcre_compile() if the pattern was longer
236        than about 50K.
237    
238    17. I have done a major re-factoring of the way pcre_compile() computes the
239        amount of memory needed for a compiled pattern. Previously, there was code
240        that made a preliminary scan of the pattern in order to do this. That was
241        OK when PCRE was new, but as the facilities have expanded, it has become
242        harder and harder to keep it in step with the real compile phase, and there
243        have been a number of bugs (see for example, 4 above). I have now found a
244        cunning way of running the real compile function in a "fake" mode that
245        enables it to compute how much memory it would need, while actually only
246        ever using a few hundred bytes of working memory and without too many
247        tests of the mode. This should make future maintenance and development
248        easier. A side effect of this work is that the limit of 200 on the nesting
249        depth of parentheses has been removed (though this was never a serious
250        limitation, I suspect). However, there is a downside: pcre_compile() now
251        runs more slowly than before (30% or more, depending on the pattern). I
252        hope this isn't a big issue. There is no effect on runtime performance.
253    
254    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
255        newline (only possible for the last line of a file) and it was a
256        pattern that set a locale (followed by /Lsomething), pcretest crashed.
257    
258    19. Added additional timing features to pcretest. (1) The -tm option now times
259        matching only, not compiling. (2) Both -t and -tm can be followed, as a
260        separate command line item, by a number that specifies the number of
261        repeats to use when timing. The default is 50000; this gives better
262        precision, but takes uncomfortably long for very large patterns.
263    
264    20. Extended pcre_study() to be more clever in cases where a branch of a
265        subpattern has no definite first character. For example, (a*|b*)[cd] would
266        previously give no result from pcre_study(). Now it recognizes that the
267        first character must be a, b, c, or d.
268    
269    21. There was an incorrect error "recursive call could loop indefinitely" if
270        a subpattern (or the entire pattern) that was being tested for matching an
271        empty string contained only one non-empty item after a nested subpattern.
272        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
273        incorrectly, because the \d was being skipped in the check.
274    
275    22. The pcretest program now has a new pattern option /B and a command line
276        option -b, which is equivalent to adding /B to every pattern. This causes
277        it to show the compiled bytecode, without the additional information that
278        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
279        is the same as /B/I).
280    
281    23. A new optimization is now able automatically to treat some sequences such
282        as a*b as a*+b. More specifically, if something simple (such as a character
283        or a simple class like \d) has an unlimited quantifier, and is followed by
284        something that cannot possibly match the quantified thing, the quantifier
285        is automatically "possessified".
286    
287    24. A recursive reference to a subpattern whose number was greater than 39
288        went wrong under certain circumstances in UTF-8 mode. This bug could also
289        have affected the operation of pcre_study().
290    
291    25. Realized that a little bit of performance could be had by replacing
292        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
293    
294    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
295    
296    27. Possessive quantifiers such as a++ were previously implemented by turning
297        them into atomic groups such as ($>a+). Now they have their own opcodes,
298        which improves performance. This includes the automatically created ones
299        from 23 above.
300    
301    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
302        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
303        the first matched character to be a colon. This applied both to named and
304        numbered groups.
305    
306    29. The ucpinternal.h header file was missing its idempotency #ifdef.
307    
308    30. I was sent a "project" file called libpcre.a.dev which I understand makes
309        building PCRE on Windows easier, so I have included it in the distribution.
310    
311    31. There is now a check in pcretest against a ridiculously large number being
312        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
313        loop, the loop is abandoned.
314    
315    32. Forward references to subpatterns in conditions such as (?(2)...) where
316        subpattern 2 is defined later cause pcre_compile() to search forwards in
317        the pattern for the relevant set of parentheses. This search went wrong
318        when there were unescaped parentheses in a character class, parentheses
319        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
320    
321    33. "Subroutine" calls and backreferences were previously restricted to
322        referencing subpatterns earlier in the regex. This restriction has now
323        been removed.
324    
325    34. Added a number of extra features that are going to be in Perl 5.10. On the
326        whole, these are just syntactic alternatives for features that PCRE had
327        previously implemented using the Python syntax or my own invention. The
328        other formats are all retained for compatibility.
329    
330        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
331            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
332            also .NET compatible.
333    
334        (b) A recursion or subroutine call to a named group can now be defined as
335            (?&name) as well as (?P>name).
336    
337        (c) A backreference to a named group can now be defined as \k<name> or
338            \k'name' as well as (?P=name). The new forms, as well as being in Perl
339            5.10, are also .NET compatible.
340    
341        (d) A conditional reference to a named group can now use the syntax
342            (?(<name>) or (?('name') as well as (?(name).
343    
344        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
345            groups (named and numbered) that are never evaluated inline, but can be
346            called as "subroutines" from elsewhere. In effect, the DEFINE condition
347            is always false. There may be only one alternative in such a group.
348    
349        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
350            as the simple (?(R). The condition is true only if the most recent
351            recursion is that of the given number or name. It does not search out
352            through the entire recursion stack.
353    
354        (g) The escape \gN or \g{N} has been added, where N is a positive or
355            negative number, specifying an absolute or relative reference.
356    
357    35. Tidied to get rid of some further signed/unsigned compiler warnings and
358        some "unreachable code" warnings.
359    
360    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
361        things, this adds five new scripts.
362    
363    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
364        There were also incompatibilities regarding the handling of \Q..\E inside
365        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
366        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
367    
368    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
369        matches an empty string, and forcibly breaks the loop. There were bugs in
370        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
371        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
372        separate and independent bugs (that affected different cases) have been
373        fixed.
374    
375    39. Refactored the code to abolish the use of different opcodes for small
376        capturing bracket numbers. This is a tidy that I avoided doing when I
377        removed the limit on the number of capturing brackets for 3.5 back in 2001.
378        The new approach is not only tidier, it makes it possible to reduce the
379        memory needed to fix the previous bug (38).
380    
381    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
382        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
383        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
384        mode.
385    
386    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
387        report.
388    
389    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
390        copy construction and assignment in the C++ wrapper.
391    
392    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
393        couple of bugs that could have given wrong results in the "--newline=crlf"
394        case.
395    
396    44. Added a number of casts and did some reorganization of signed/unsigned int
397        variables following suggestions from Dair Grant. Also renamed the variable
398        "this" as "item" because it is a C++ keyword.
399    
400    45. Arranged for dftables to add
401    
402          #include "pcre_internal.h"
403    
404        to pcre_chartables.c because without it, gcc 4.x may remove the array
405        definition from the final binary if PCRE is built into a static library and
406        dead code stripping is activated.
407    
408    46. For an unanchored pattern, if a match attempt fails at the start of a
409        newline sequence, and the newline setting is CRLF or ANY, and the next two
410        characters are CRLF, advance by two characters instead of one.
411    
412    
413    Version 6.7 04-Jul-06
414    ---------------------
415    
416     1. In order to handle tests when input lines are enormously long, pcretest has
417        been re-factored so that it automatically extends its buffers when
418        necessary. The code is crude, but this _is_ just a test program. The
419        default size has been increased from 32K to 50K.
420    
421     2. The code in pcre_study() was using the value of the re argument before
422        testing it for NULL. (Of course, in any sensible call of the function, it
423        won't be NULL.)
424    
425     3. The memmove() emulation function in pcre_internal.h, which is used on
426        systems that lack both memmove() and bcopy() - that is, hardly ever -
427        was missing a "static" storage class specifier.
428    
429     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
430        containing an extended class (one that cannot be represented by a bitmap
431        because it contains high-valued characters or Unicode property items, e.g.
432        [\pZ]). Almost always one would set UTF-8 mode when processing such a
433        pattern, but PCRE should not loop if you do not (it no longer does).
434        [Detail: two cases were found: (a) a repeated subpattern containing an
435        extended class; (b) a recursive reference to a subpattern that followed a
436        previous extended class. It wasn't skipping over the extended class
437        correctly when UTF-8 mode was not set.]
438    
439     5. A negated single-character class was not being recognized as fixed-length
440        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
441        compile error "lookbehind assertion is not fixed length".
442    
443     6. The RunPerlTest auxiliary script was showing an unexpected difference
444        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
445        write a Perl script that can interpret lines of an input file either as
446        byte characters or as UTF-8, which is what "perltest" was being required to
447        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
448        can't do is switch easily at run time between having the "use utf8;" pragma
449        or not. In the end, I fudged it by using the RunPerlTest script to insert
450        "use utf8;" explicitly for the UTF-8 tests.
451    
452     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
453        the end of the subject string, contrary to the documentation and to what
454        Perl does. This was true of both matching functions. Now it matches only at
455        the start of the subject and immediately after *internal* newlines.
456    
457     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
458        a pointer to an int instead of a pointer to an unsigned long int. This
459        caused problems on 64-bit systems.
460    
461     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
462        instance of the 'standard' template library not being so standard".
463    
464    10. There was no check on the number of named subpatterns nor the maximum
465        length of a subpattern name. The product of these values is used to compute
466        the size of the memory block for a compiled pattern. By supplying a very
467        long subpattern name and a large number of named subpatterns, the size
468        computation could be caused to overflow. This is now prevented by limiting
469        the length of names to 32 characters, and the number of named subpatterns
470        to 10,000.
471    
472    11. Subpatterns that are repeated with specific counts have to be replicated in
473        the compiled pattern. The size of memory for this was computed from the
474        length of the subpattern and the repeat count. The latter is limited to
475        65535, but there was no limit on the former, meaning that integer overflow
476        could in principle occur. The compiled length of a repeated subpattern is
477        now limited to 30,000 bytes in order to prevent this.
478    
479    12. Added the optional facility to have named substrings with the same name.
480    
481    13. Added the ability to use a named substring as a condition, using the
482        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
483        are numbers (not recommended). Forward references are permitted.
484    
485    14. Added forward references in named backreferences (if you see what I mean).
486    
487    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
488        pattern could run off the end of the subject. For example, the pattern
489        "(?s)(.{1,5})"8 did this with the subject "ab".
490    
491    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
492        PCRE_CASELESS was set when matching characters that were quantified with ?
493        or *.
494    
495    17. A character class other than a single negated character that had a minimum
496        but no maximum quantifier - for example [ab]{6,} - was not handled
497        correctly by pce_dfa_exec(). It would match only one character.
498    
499    18. A valid (though odd) pattern that looked like a POSIX character
500        class but used an invalid character after [ (for example [[,abc,]]) caused
501        pcre_compile() to give the error "Failed: internal error: code overflow" or
502        in some cases to crash with a glibc free() error. This could even happen if
503        the pattern terminated after [[ but there just happened to be a sequence of
504        letters, a binary zero, and a closing ] in the memory that followed.
505    
506    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
507        over the years. Originally (before any Unicode support), just the bottom 8
508        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
509        output from "man perlunicode" includes this:
510    
511          The regular expression compiler produces polymorphic opcodes.  That
512          is, the pattern adapts to the data and automatically switches to
513          the Unicode character scheme when presented with Unicode data--or
514          instead uses a traditional byte scheme when presented with byte
515          data.
516    
517        Sadly, a wide octal escape does not cause a switch, and in a string with
518        no other multibyte characters, these octal escapes are treated as before.
519        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
520        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
521        Unicode string.
522    
523        I have not perpetrated such confusion in PCRE. Up till now, it took just
524        the bottom 8 bits, as in old Perl. I have now made octal escapes with
525        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
526        translate to the appropriate multibyte character.
527    
528    29. Applied some refactoring to reduce the number of warnings from Microsoft
529        and Borland compilers. This has included removing the fudge introduced
530        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
531        a warning about an unused variable.
532    
533    21. PCRE has not included VT (character 0x0b) in the set of whitespace
534        characters since release 4.0, because Perl (from release 5.004) does not.
535        [Or at least, is documented not to: some releases seem to be in conflict
536        with the documentation.] However, when a pattern was studied with
537        pcre_study() and all its branches started with \s, PCRE still included VT
538        as a possible starting character. Of course, this did no harm; it just
539        caused an unnecessary match attempt.
540    
541    22. Removed a now-redundant internal flag bit that recorded the fact that case
542        dependency changed within the pattern. This was once needed for "required
543        byte" processing, but is no longer used. This recovers a now-scarce options
544        bit. Also moved the least significant internal flag bit to the most-
545        significant bit of the word, which was not previously used (hangover from
546        the days when it was an int rather than a uint) to free up another bit for
547        the future.
548    
549    23. Added support for CRLF line endings as well as CR and LF. As well as the
550        default being selectable at build time, it can now be changed at runtime
551        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
552        specify that it is scanning data with non-default line endings.
553    
554    24. Changed the definition of CXXLINK to make it agree with the definition of
555        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
556    
557    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
558        recursions. This makes a big different to stack usage for some patterns.
559    
560    26. If a subpattern containing a named recursion or subroutine reference such
561        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
562        the space required for the compiled pattern went wrong and gave too small a
563        value. Depending on the environment, this could lead to "Failed: internal
564        error: code overflow at offset 49" or "glibc detected double free or
565        corruption" errors.
566    
567    27. Applied patches from Google (a) to support the new newline modes and (b) to
568        advance over multibyte UTF-8 characters in GlobalReplace.
569    
570    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
571        difference for some implementation of PCRE in some Windows version.
572    
573    29. Added some extra testing facilities to pcretest:
574    
575        \q<number>   in a data line sets the "match limit" value
576        \Q<number>   in a data line sets the "match recursion limt" value
577        -S <number>  sets the stack size, where <number> is in megabytes
578    
579        The -S option isn't available for Windows.
580    
581    
582    Version 6.6 06-Feb-06
583    ---------------------
584    
585     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
586        in pcreposix.h. I have copied the definition from pcre.h.
587    
588     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
589        because pcre.h is no longer a built file.
590    
591     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
592        not normally included in the compiled code.
593    
594    
595    Version 6.5 01-Feb-06
596    ---------------------
597    
598     1. When using the partial match feature with pcre_dfa_exec(), it was not
599        anchoring the second and subsequent partial matches at the new starting
600        point. This could lead to incorrect results. For example, with the pattern
601        /1234/, partially matching against "123" and then "a4" gave a match.
602    
603     2. Changes to pcregrep:
604    
605        (a) All non-match returns from pcre_exec() were being treated as failures
606            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
607            error message is output. Some extra information is given for the
608            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
609            probably the only errors that are likely to be caused by users (by
610            specifying a regex that has nested indefinite repeats, for instance).
611            If there are more than 20 of these errors, pcregrep is abandoned.
612    
613        (b) A binary zero was treated as data while matching, but terminated the
614            output line if it was written out. This has been fixed: binary zeroes
615            are now no different to any other data bytes.
616    
617        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
618            used to set a locale for matching. The --locale=xxxx long option has
619            been added (no short equivalent) to specify a locale explicitly on the
620            pcregrep command, overriding the environment variables.
621    
622        (d) When -B was used with -n, some line numbers in the output were one less
623            than they should have been.
624    
625        (e) Added the -o (--only-matching) option.
626    
627        (f) If -A or -C was used with -c (count only), some lines of context were
628            accidentally printed for the final match.
629    
630        (g) Added the -H (--with-filename) option.
631    
632        (h) The combination of options -rh failed to suppress file names for files
633            that were found from directory arguments.
634    
635        (i) Added the -D (--devices) and -d (--directories) options.
636    
637        (j) Added the -F (--fixed-strings) option.
638    
639        (k) Allow "-" to be used as a file name for -f as well as for a data file.
640    
641        (l) Added the --colo(u)r option.
642    
643        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
644            is not present by default.
645    
646     3. A nasty bug was discovered in the handling of recursive patterns, that is,
647        items such as (?R) or (?1), when the recursion could match a number of
648        alternatives. If it matched one of the alternatives, but subsequently,
649        outside the recursion, there was a failure, the code tried to back up into
650        the recursion. However, because of the way PCRE is implemented, this is not
651        possible, and the result was an incorrect result from the match.
652    
653        In order to prevent this happening, the specification of recursion has
654        been changed so that all such subpatterns are automatically treated as
655        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
656    
657     4. I had overlooked the fact that, in some locales, there are characters for
658        which isalpha() is true but neither isupper() nor islower() are true. In
659        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
660        and ordfeminine) are like this. This affected the treatment of \w and \W
661        when they appeared in character classes, but not when they appeared outside
662        a character class. The bit map for "word" characters is now created
663        separately from the results of isalnum() instead of just taking it from the
664        upper, lower, and digit maps. (Plus the underscore character, of course.)
665    
666     5. The above bug also affected the handling of POSIX character classes such as
667        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
668        permanent tables. Instead, the bit maps for such a class were previously
669        created as the appropriate unions of the upper, lower, and digit bitmaps.
670        Now they are created by subtraction from the [[:word:]] class, which has
671        its own bitmap.
672    
673     6. The [[:blank:]] character class matches horizontal, but not vertical space.
674        It is created by subtracting the vertical space characters (\x09, \x0a,
675        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
676        subtraction was done in the overall bitmap for a character class, meaning
677        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
678        be recognized. This bug has been fixed.
679    
680     7. Patches from the folks at Google:
681    
682          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
683          real life, but is still worth protecting against".
684    
685          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
686          regular expressions".
687    
688          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
689          have it.
690    
691          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
692          "configure" and the latter not, in order to fix a problem somebody had
693          with compiling the Arg class on HP-UX.
694    
695          (e) Improve the error-handling of the C++ wrapper a little bit.
696    
697          (f) New tests for checking recursion limiting.
698    
699     8. The pcre_memmove() function, which is used only if the environment does not
700        have a standard memmove() function (and is therefore rarely compiled),
701        contained two bugs: (a) use of int instead of size_t, and (b) it was not
702        returning a result (though PCRE never actually uses the result).
703    
704     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
705        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
706        returned instead of calling malloc() with an overflowing number that would
707        most likely cause subsequent chaos.
708    
709    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
710    
711    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
712        with this option is matched, the nmatch and pmatch options of regexec() are
713        ignored.
714    
715    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
716        provided in case anyone wants to the the POSIX interface with UTF-8
717        strings.
718    
719    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
720        C++ linking (needed for some HP-UX environments).
721    
722    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
723        (unused parameter) and in the pcre_printint() function (omitted "default"
724        switch label when the default is to do nothing).
725    
726    15. Added some code to make it possible, when PCRE is compiled as a C++
727        library, to replace subject pointers for pcre_exec() with a smart pointer
728        class, thus making it possible to process discontinuous strings.
729    
730    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
731        much the same function. They were added by different people who were trying
732        to make PCRE easy to compile on non-Unix systems. It has been suggested
733        that PCRE_EXPORT be abolished now that there is more automatic apparatus
734        for compiling on Windows systems. I have therefore replaced it with
735        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
736        defaults to "extern" for C or "extern C" for C++, which works fine on
737        Unix-like systems. It is now possible to override the value of PCRE_DATA_
738        SCOPE with something explicit in config.h. In addition:
739    
740        (a) pcreposix.h still had just "extern" instead of either of these macros;
741            I have replaced it with PCRE_DATA_SCOPE.
742    
743        (b) Functions such as _pcre_xclass(), which are internal to the library,
744            but external in the C sense, all had PCRE_EXPORT in their definitions.
745            This is apparently wrong for the Windows case, so I have removed it.
746            (It makes no difference on Unix-like systems.)
747    
748    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
749        of recursive calls to match(). This is different to MATCH_LIMIT because
750        that limits the total number of calls to match(), not all of which increase
751        the depth of recursion. Limiting the recursion depth limits the amount of
752        stack (or heap if NO_RECURSE is set) that is used. The default can be set
753        when PCRE is compiled, and changed at run time. A patch from Google adds
754        this functionality to the C++ interface.
755    
756    18. Changes to the handling of Unicode character properties:
757    
758        (a) Updated the table to Unicode 4.1.0.
759    
760        (b) Recognize characters that are not in the table as "Cn" (undefined).
761    
762        (c) I revised the way the table is implemented to a much improved format
763            which includes recognition of ranges. It now supports the ranges that
764            are defined in UnicodeData.txt, and it also amalgamates other
765            characters into ranges. This has reduced the number of entries in the
766            table from around 16,000 to around 3,000, thus reducing its size
767            considerably. I realized I did not need to use a tree structure after
768            all - a binary chop search is just as efficient. Having reduced the
769            number of entries, I extended their size from 6 bytes to 8 bytes to
770            allow for more data.
771    
772        (d) Added support for Unicode script names via properties such as \p{Han}.
773    
774    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
775        matching that character.
776    
777    20. When matching a repeated Unicode property with a minimum greater than zero,
778        (for example \pL{2,}), PCRE could look past the end of the subject if it
779        reached it while seeking the minimum number of characters. This could
780        happen only if some of the characters were more than one byte long, because
781        there is a check for at least the minimum number of bytes.
782    
783    21. Refactored the implementation of \p and \P so as to be more general, to
784        allow for more different types of property in future. This has changed the
785        compiled form incompatibly. Anybody with saved compiled patterns that use
786        \p or \P will have to recompile them.
787    
788    22. Added "Any" and "L&" to the supported property types.
789    
790    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
791        but give a compile time error if the value is greater than 0xff.
792    
793    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
794        accidentally not being installed or uninstalled.
795    
796    25. The pcre.h file was built from pcre.h.in, but the only changes that were
797        made were to insert the current release number. This seemed silly, because
798        it made things harder for people building PCRE on systems that don't run
799        "configure". I have turned pcre.h into a distributed file, no longer built
800        by "configure", with the version identification directly included. There is
801        no longer a pcre.h.in file.
802    
803        However, this change necessitated a change to the pcre-config script as
804        well. It is built from pcre-config.in, and one of the substitutions was the
805        release number. I have updated configure.ac so that ./configure now finds
806        the release number by grepping pcre.h.
807    
808    26. Added the ability to run the tests under valgrind.
809    
810    
811    Version 6.4 05-Sep-05
812    ---------------------
813    
814     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
815        "--" to be printed when multiple files were scanned, even when none of the
816        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
817        consider it to be a bug, and have restored the previous behaviour.
818    
819     2. A couple of code tidies to get rid of compiler warnings.
820    
821     3. The pcretest program used to cheat by referring to symbols in the library
822        whose names begin with _pcre_. These are internal symbols that are not
823        really supposed to be visible externally, and in some environments it is
824        possible to suppress them. The cheating is now confined to including
825        certain files from the library's source, which is a bit cleaner.
826    
827     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
828        file's purpose clearer.
829    
830     5. Reorganized pcre_ucp_findchar().
831    
832    
833    Version 6.3 15-Aug-05
834    ---------------------
835    
836     1. The file libpcre.pc.in did not have general read permission in the tarball.
837    
838     2. There were some problems when building without C++ support:
839    
840        (a) If C++ support was not built, "make install" and "make test" still
841            tried to test it.
842    
843        (b) There were problems when the value of CXX was explicitly set. Some
844            changes have been made to try to fix these, and ...
845    
846        (c) --disable-cpp can now be used to explicitly disable C++ support.
847    
848        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
849            backslash in a target when C++ was disabled. This confuses some
850            versions of "make", apparently. Using an intermediate variable solves
851            this. (Same for CPP_LOBJ.)
852    
853     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
854        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
855        necessary on certain architectures.
856    
857     4. Added a setting of -export-symbols-regex to the link command to remove
858        those symbols that are exported in the C sense, but actually are local
859        within the library, and not documented. Their names all begin with
860        "_pcre_". This is not a perfect job, because (a) we have to except some
861        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
862        available (and never for static libraries). I have made a note to try to
863        find a way round (a) in the future.
864    
865    
866    Version 6.2 01-Aug-05
867    ---------------------
868    
869     1. There was no test for integer overflow of quantifier values. A construction
870        such as {1111111111111111} would give undefined results. What is worse, if
871        a minimum quantifier for a parenthesized subpattern overflowed and became
872        negative, the calculation of the memory size went wrong. This could have
873        led to memory overwriting.
874    
875     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
876    
877     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
878        operating environments where this matters.
879    
880     4. Applied Giuseppe Maxia's patch to add additional features for controlling
881        PCRE options from within the C++ wrapper.
882    
883     5. Named capturing subpatterns were not being correctly counted when a pattern
884        was compiled. This caused two problems: (a) If there were more than 100
885        such subpatterns, the calculation of the memory needed for the whole
886        compiled pattern went wrong, leading to an overflow error. (b) Numerical
887        back references of the form \12, where the number was greater than 9, were
888        not recognized as back references, even though there were sufficient
889        previous subpatterns.
890    
891     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
892        versions of gcc, e.g. 2.95.4.
893    
894    
895    Version 6.1 21-Jun-05
896    ---------------------
897    
898     1. There was one reference to the variable "posix" in pcretest.c that was not
899        surrounded by "#if !defined NOPOSIX".
900    
901     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
902        the cross-check on the old pcre_info() function, for the benefit of the
903        cut-down version of PCRE that is currently imported into Exim.
904    
905     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
906        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
907        patterns that start (?i) but I don't think that matters. The use of (?i) is
908        just an example; this all applies to the other options as well.
909    
910     4. Since libtool seems to echo the compile commands it is issuing, the output
911        from "make" can be reduced a bit by putting "@" in front of each libtool
912        compile command.
913    
914     5. Patch from the folks at Google for configure.in to be a bit more thorough
915        in checking for a suitable C++ installation before trying to compile the
916        C++ stuff. This should fix a reported problem when a compiler was present,
917        but no suitable headers.
918    
919     6. The man pages all had just "PCRE" as their title. I have changed them to
920        be the relevant file name. I have also arranged that these names are
921        retained in the file doc/pcre.txt, which is a concatenation in text format
922        of all the man pages except the little individual ones for each function.
923    
924     7. The NON-UNIX-USE file had not been updated for the different set of source
925        files that come with release 6. I also added a few comments about the C++
926        wrapper.
927    
928    
929    Version 6.0 07-Jun-05
930    ---------------------
931    
932     1. Some minor internal re-organization to help with my DFA experiments.
933    
934     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
935        didn't matter for the library itself when fully configured, but did matter
936        when compiling without UCP support, or within Exim, where the ucp files are
937        not imported.
938    
939     3. Refactoring of the library code to split up the various functions into
940        different source modules. The addition of the new DFA matching code (see
941        below) to a single monolithic source would have made it really too
942        unwieldy, quite apart from causing all the code to be include in a
943        statically linked application, when only some functions are used. This is
944        relevant even without the DFA addition now that patterns can be compiled in
945        one application and matched in another.
946    
947        The downside of splitting up is that there have to be some external
948        functions and data tables that are used internally in different modules of
949        the library but which are not part of the API. These have all had their
950        names changed to start with "_pcre_" so that they are unlikely to clash
951        with other external names.
952    
953     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
954        a different (DFA) algorithm. Although it is slower than the original
955        function, it does have some advantages for certain types of matching
956        problem.
957    
958     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
959        including restarting after a partial match.
960    
961     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
962        defined when compiling for Windows was sent to me. I have put it into the
963        code, though I have no means of testing or verifying it.
964    
965     7. Added the pcre_refcount() auxiliary function.
966    
967     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
968        match before or at the first newline in the subject string. In pcretest,
969        the /f option on a pattern can be used to set this.
970    
971     9. A repeated \w when used in UTF-8 mode with characters greater than 256
972        would behave wrongly. This has been present in PCRE since release 4.0.
973    
974    10. A number of changes to the pcregrep command:
975    
976        (a) Refactored how -x works; insert ^(...)$ instead of setting
977            PCRE_ANCHORED and checking the length, in preparation for adding
978            something similar for -w.
979    
980        (b) Added the -w (match as a word) option.
981    
982        (c) Refactored the way lines are read and buffered so as to have more
983            than one at a time available.
984    
985        (d) Implemented a pcregrep test script.
986    
987        (e) Added the -M (multiline match) option. This allows patterns to match
988            over several lines of the subject. The buffering ensures that at least
989            8K, or the rest of the document (whichever is the shorter) is available
990            for matching (and similarly the previous 8K for lookbehind assertions).
991    
992        (f) Changed the --help output so that it now says
993    
994              -w, --word-regex(p)
995    
996            instead of two lines, one with "regex" and the other with "regexp"
997            because that confused at least one person since the short forms are the
998            same. (This required a bit of code, as the output is generated
999            automatically from a table. It wasn't just a text change.)
1000    
1001        (g) -- can be used to terminate pcregrep options if the next thing isn't an
1002            option but starts with a hyphen. Could be a pattern or a path name
1003            starting with a hyphen, for instance.
1004    
1005        (h) "-" can be given as a file name to represent stdin.
1006    
1007        (i) When file names are being printed, "(standard input)" is used for
1008            the standard input, for compatibility with GNU grep. Previously
1009            "<stdin>" was used.
1010    
1011        (j) The option --label=xxx can be used to supply a name to be used for
1012            stdin when file names are being printed. There is no short form.
1013    
1014        (k) Re-factored the options decoding logic because we are going to add
1015            two more options that take data. Such options can now be given in four
1016            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
1017    
1018        (l) Added the -A, -B, and -C options for requesting that lines of context
1019            around matches be printed.
1020    
1021        (m) Added the -L option to print the names of files that do not contain
1022            any matching lines, that is, the complement of -l.
1023    
1024        (n) The return code is 2 if any file cannot be opened, but pcregrep does
1025            continue to scan other files.
1026    
1027        (o) The -s option was incorrectly implemented. For compatibility with other
1028            greps, it now suppresses the error message for a non-existent or non-
1029            accessible file (but not the return code). There is a new option called
1030            -q that suppresses the output of matching lines, which was what -s was
1031            previously doing.
1032    
1033        (p) Added --include and --exclude options to specify files for inclusion
1034            and exclusion when recursing.
1035    
1036    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
1037        Hopefully, it now does.
1038    
1039    12. Missing cast in pcre_study().
1040    
1041    13. Added an "uninstall" target to the makefile.
1042    
1043    14. Replaced "extern" in the function prototypes in Makefile.in with
1044        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
1045        world, but is set differently for Windows.
1046    
1047    15. Added a second compiling function called pcre_compile2(). The only
1048        difference is that it has an extra argument, which is a pointer to an
1049        integer error code. When there is a compile-time failure, this is set
1050        non-zero, in addition to the error test pointer being set to point to an
1051        error message. The new argument may be NULL if no error number is required
1052        (but then you may as well call pcre_compile(), which is now just a
1053        wrapper). This facility is provided because some applications need a
1054        numeric error indication, but it has also enabled me to tidy up the way
1055        compile-time errors are handled in the POSIX wrapper.
1056    
1057    16. Added VPATH=.libs to the makefile; this should help when building with one
1058        prefix path and installing with another. (Or so I'm told by someone who
1059        knows more about this stuff than I do.)
1060    
1061    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
1062        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
1063        match everything, including newlines. This is not POSIX-compatible, but
1064        somebody wanted the feature. From pcretest it can be activated by using
1065        both the P and the s flags.
1066    
1067    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
1068    
1069    19. libpcre.pc was being incorrectly installed as executable.
1070    
1071    20. A couple of places in pcretest check for end-of-line by looking for '\n';
1072        it now also looks for '\r' so that it will work unmodified on Windows.
1073    
1074    21. Added Google's contributed C++ wrapper to the distribution.
1075    
1076    22. Added some untidy missing memory free() calls in pcretest, to keep
1077        Electric Fence happy when testing.
1078    
1079    
1080    
1081    Version 5.0 13-Sep-04
1082    ---------------------
1083    
1084     1. Internal change: literal characters are no longer packed up into items
1085        containing multiple characters in a single byte-string. Each character
1086        is now matched using a separate opcode. However, there may be more than one
1087        byte in the character in UTF-8 mode.
1088    
1089     2. The pcre_callout_block structure has two new fields: pattern_position and
1090        next_item_length. These contain the offset in the pattern to the next match
1091        item, and its length, respectively.
1092    
1093     3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
1094        insertion of callouts before each pattern item. Added the /C option to
1095        pcretest to make use of this.
1096    
1097     4. On the advice of a Windows user, the lines
1098    
1099          #if defined(_WIN32) || defined(WIN32)
1100          _setmode( _fileno( stdout ), 0x8000 );
1101          #endif  /* defined(_WIN32) || defined(WIN32) */
1102    
1103        have been added to the source of pcretest. This apparently does useful
1104        magic in relation to line terminators.
1105    
1106     5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
1107        for the benefit of those environments where the "b" makes a difference.
1108    
1109     6. The icc compiler has the same options as gcc, but "configure" doesn't seem
1110        to know about it. I have put a hack into configure.in that adds in code
1111        to set GCC=yes if CC=icc. This seems to end up at a point in the
1112        generated configure script that is early enough to affect the setting of
1113        compiler options, which is what is needed, but I have no means of testing
1114        whether it really works. (The user who reported this had patched the
1115        generated configure script, which of course I cannot do.)
1116    
1117        LATER: After change 22 below (new libtool files), the configure script
1118        seems to know about icc (and also ecc). Therefore, I have commented out
1119        this hack in configure.in.
1120    
1121     7. Added support for pkg-config (2 patches were sent in).
1122    
1123     8. Negated POSIX character classes that used a combination of internal tables
1124        were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
1125        [[:^ascii]]. Typically, they would match almost any characters. The other
1126        POSIX classes were not broken in this way.
1127    
1128     9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
1129        to find the match, as PCRE was deluded into thinking that the match had to
1130        start at the start point or following a newline. The same bug applied to
1131        patterns with negative forward assertions or any backward assertions
1132        preceding ".*" at the start, unless the pattern required a fixed first
1133        character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
1134    
1135    10. In UTF-8 mode, when moving forwards in the subject after a failed match
1136        starting at the last subject character, bytes beyond the end of the subject
1137        string were read.
1138    
1139    11. Renamed the variable "class" as "classbits" to make life easier for C++
1140        users. (Previously there was a macro definition, but it apparently wasn't
1141        enough.)
1142    
1143    12. Added the new field "tables" to the extra data so that tables can be passed
1144        in at exec time, or the internal tables can be re-selected. This allows
1145        a compiled regex to be saved and re-used at a later time by a different
1146        program that might have everything at different addresses.
1147    
1148    13. Modified the pcre-config script so that, when run on Solaris, it shows a
1149        -R library as well as a -L library.
1150    
1151    14. The debugging options of pcretest (-d on the command line or D on a
1152        pattern) showed incorrect output for anything following an extended class
1153        that contained multibyte characters and which was followed by a quantifier.
1154    
1155    15. Added optional support for general category Unicode character properties
1156        via the \p, \P, and \X escapes. Unicode property support implies UTF-8
1157        support. It adds about 90K to the size of the library. The meanings of the
1158        inbuilt class escapes such as \d and \s have NOT been changed.
1159    
1160    16. Updated pcredemo.c to include calls to free() to release the memory for the
1161        compiled pattern.
1162    
1163    17. The generated file chartables.c was being created in the source directory
1164        instead of in the building directory. This caused the build to fail if the
1165        source directory was different from the building directory, and was
1166        read-only.
1167    
1168    18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
1169        file. No doubt somebody will tell me if they don't make sense... Also added
1170        Dan Mooney's comments about building on OpenVMS.
1171    
1172    19. Added support for partial matching via the PCRE_PARTIAL option for
1173        pcre_exec() and the \P data escape in pcretest.
1174    
1175    20. Extended pcretest with 3 new pattern features:
1176    
1177        (i)   A pattern option of the form ">rest-of-line" causes pcretest to
1178              write the compiled pattern to the file whose name is "rest-of-line".
1179              This is a straight binary dump of the data, with the saved pointer to
1180              the character tables forced to be NULL. The study data, if any, is
1181              written too. After writing, pcretest reads a new pattern.
1182    
1183        (ii)  If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
1184              compiled pattern from the given file. There must not be any
1185              occurrences of "<" in the file name (pretty unlikely); if there are,
1186              pcretest will instead treat the initial "<" as a pattern delimiter.
1187              After reading in the pattern, pcretest goes on to read data lines as
1188              usual.
1189    
1190        (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
1191              and 16-bit fields in a compiled pattern, to simulate a pattern that
1192              was compiled on a host of opposite endianness.
1193    
1194    21. The pcre-exec() function can now cope with patterns that were compiled on
1195        hosts of opposite endianness, with this restriction:
1196    
1197          As for any compiled expression that is saved and used later, the tables
1198          pointer field cannot be preserved; the extra_data field in the arguments
1199          to pcre_exec() should be used to pass in a tables address if a value
1200          other than the default internal tables were used at compile time.
1201    
1202    22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
1203        now diagnosed as an error. Previously, most of the time, a negative number
1204        would have been treated as zero, but if in addition "ovector" was passed as
1205        NULL, a crash could occur.
1206    
1207    23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
1208        new versions from the libtool 1.5 distribution (the last one is a copy of
1209        a file called libtool.m4). This seems to have fixed the need to patch
1210        "configure" to support Darwin 1.3 (which I used to do). However, I still
1211        had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
1212        workstation).
1213    
1214    24. Changed the PCRE licence to be the more standard "BSD" licence.
1215    
1216    
1217    Version 4.5 01-Dec-03
1218    ---------------------
1219    
1220     1. There has been some re-arrangement of the code for the match() function so
1221        that it can be compiled in a version that does not call itself recursively.
1222        Instead, it keeps those local variables that need separate instances for
1223        each "recursion" in a frame on the heap, and gets/frees frames whenever it
1224        needs to "recurse". Keeping track of where control must go is done by means
1225        of setjmp/longjmp. The whole thing is implemented by a set of macros that
1226        hide most of the details from the main code, and operates only if
1227        NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
1228        "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
1229        operating.
1230    
1231        To make it easier for callers to provide specially tailored get/free
1232        functions for this usage, two new functions, pcre_stack_malloc, and
1233        pcre_stack_free, are used. They are always called in strict stacking order,
1234        and the size of block requested is always the same.
1235    
1236        The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
1237        PCRE has been compiled to use the stack or the heap for recursion. The
1238        -C option of pcretest uses this to show which version is compiled.
1239    
1240        A new data escape \S, is added to pcretest; it causes the amounts of store
1241        obtained and freed by both kinds of malloc/free at match time to be added
1242        to the output.
1243    
1244     2. Changed the locale test to use "fr_FR" instead of "fr" because that's
1245        what's available on my current Linux desktop machine.
1246    
1247     3. When matching a UTF-8 string, the test for a valid string at the start has
1248        been extended. If start_offset is not zero, PCRE now checks that it points
1249        to a byte that is the start of a UTF-8 character. If not, it returns
1250        PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
1251        this is necessary because there may be backward assertions in the pattern.
1252        When matching the same subject several times, it may save resources to use
1253        PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
1254    
1255     4. The code for checking the validity of UTF-8 strings has been tightened so
1256        that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
1257        containing "overlong sequences".
1258    
1259     5. Fixed a bug (appearing twice) that I could not find any way of exploiting!
1260        I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
1261        should have been "&", but it just so happened that all the cases this let
1262        through by mistake were picked up later in the function.
1263    
1264     6. I had used a variable called "isblank" - this is a C99 function, causing
1265        some compilers to warn. To avoid this, I renamed it (as "blankclass").
1266    
1267     7. Cosmetic: (a) only output another newline at the end of pcretest if it is
1268        prompting; (b) run "./pcretest /dev/null" at the start of the test script
1269        so the version is shown; (c) stop "make test" echoing "./RunTest".
1270    
1271     8. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
1272    
1273     9. The prototype for memmove() for systems that don't have it was using
1274        size_t, but the inclusion of the header that defines size_t was later. I've
1275        moved the #includes for the C headers earlier to avoid this.
1276    
1277    10. Added some adjustments to the code to make it easier to compiler on certain
1278        special systems:
1279    
1280          (a) Some "const" qualifiers were missing.
1281          (b) Added the macro EXPORT before all exported functions; by default this
1282              is defined to be empty.
1283          (c) Changed the dftables auxiliary program (that builds chartables.c) so
1284              that it reads its output file name as an argument instead of writing
1285              to the standard output and assuming this can be redirected.
1286    
1287    11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
1288        class containing characters with values greater than 255, PCRE compilation
1289        went into a loop.
1290    
1291    12. A recursive reference to a subpattern that was within another subpattern
1292        that had a minimum quantifier of zero caused PCRE to crash. For example,
1293        (x(y(?2))z)? provoked this bug with a subject that got as far as the
1294        recursion. If the recursively-called subpattern itself had a zero repeat,
1295        that was OK.
1296    
1297    13. In pcretest, the buffer for reading a data line was set at 30K, but the
1298        buffer into which it was copied (for escape processing) was still set at
1299        1024, so long lines caused crashes.
1300    
1301    14. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
1302        "internal error: code overflow...". This applied to any character class
1303        that was followed by a possessive quantifier.
1304    
1305    15. Modified the Makefile to add libpcre.la as a prerequisite for
1306        libpcreposix.la because I was told this is needed for a parallel build to
1307        work.
1308    
1309    16. If a pattern that contained .* following optional items at the start was
1310        studied, the wrong optimizing data was generated, leading to matching
1311        errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
1312        matching string must start with a or b or c. The correct conclusion for
1313        this pattern is that a match can start with any character.
1314    
1315    
1316  Version 4.4 13-Aug-03  Version 4.4 13-Aug-03
1317  ---------------------  ---------------------
1318    

Legend:
Removed from v.71  
changed lines
  Added in v.143

  ViewVC Help
Powered by ViewVC 1.1.5