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

Diff of /code/trunk/ChangeLog

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

revision 67 by nigel, Sat Feb 24 21:40:13 2007 UTC revision 89 by nigel, Sat Feb 24 21:41:27 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    Version 6.6 06-Feb-06
5    ---------------------
6    
7     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
8        in pcreposix.h. I have copied the definition from pcre.h.
9    
10     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
11        because pcre.h is no longer a built file.
12    
13     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
14        not normally included in the compiled code.
15    
16    
17    Version 6.5 01-Feb-06
18    ---------------------
19    
20     1. When using the partial match feature with pcre_dfa_exec(), it was not
21        anchoring the second and subsequent partial matches at the new starting
22        point. This could lead to incorrect results. For example, with the pattern
23        /1234/, partially matching against "123" and then "a4" gave a match.
24    
25     2. Changes to pcregrep:
26    
27        (a) All non-match returns from pcre_exec() were being treated as failures
28            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
29            error message is output. Some extra information is given for the
30            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
31            probably the only errors that are likely to be caused by users (by
32            specifying a regex that has nested indefinite repeats, for instance).
33            If there are more than 20 of these errors, pcregrep is abandoned.
34    
35        (b) A binary zero was treated as data while matching, but terminated the
36            output line if it was written out. This has been fixed: binary zeroes
37            are now no different to any other data bytes.
38    
39        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
40            used to set a locale for matching. The --locale=xxxx long option has
41            been added (no short equivalent) to specify a locale explicitly on the
42            pcregrep command, overriding the environment variables.
43    
44        (d) When -B was used with -n, some line numbers in the output were one less
45            than they should have been.
46    
47        (e) Added the -o (--only-matching) option.
48    
49        (f) If -A or -C was used with -c (count only), some lines of context were
50            accidentally printed for the final match.
51    
52        (g) Added the -H (--with-filename) option.
53    
54        (h) The combination of options -rh failed to suppress file names for files
55            that were found from directory arguments.
56    
57        (i) Added the -D (--devices) and -d (--directories) options.
58    
59        (j) Added the -F (--fixed-strings) option.
60    
61        (k) Allow "-" to be used as a file name for -f as well as for a data file.
62    
63        (l) Added the --colo(u)r option.
64    
65        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
66            is not present by default.
67    
68     3. A nasty bug was discovered in the handling of recursive patterns, that is,
69        items such as (?R) or (?1), when the recursion could match a number of
70        alternatives. If it matched one of the alternatives, but subsequently,
71        outside the recursion, there was a failure, the code tried to back up into
72        the recursion. However, because of the way PCRE is implemented, this is not
73        possible, and the result was an incorrect result from the match.
74    
75        In order to prevent this happening, the specification of recursion has
76        been changed so that all such subpatterns are automatically treated as
77        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
78    
79     4. I had overlooked the fact that, in some locales, there are characters for
80        which isalpha() is true but neither isupper() nor islower() are true. In
81        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
82        and ordfeminine) are like this. This affected the treatment of \w and \W
83        when they appeared in character classes, but not when they appeared outside
84        a character class. The bit map for "word" characters is now created
85        separately from the results of isalnum() instead of just taking it from the
86        upper, lower, and digit maps. (Plus the underscore character, of course.)
87    
88     5. The above bug also affected the handling of POSIX character classes such as
89        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
90        permanent tables. Instead, the bit maps for such a class were previously
91        created as the appropriate unions of the upper, lower, and digit bitmaps.
92        Now they are created by subtraction from the [[:word:]] class, which has
93        its own bitmap.
94    
95     6. The [[:blank:]] character class matches horizontal, but not vertical space.
96        It is created by subtracting the vertical space characters (\x09, \x0a,
97        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
98        subtraction was done in the overall bitmap for a character class, meaning
99        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
100        be recognized. This bug has been fixed.
101    
102     7. Patches from the folks at Google:
103    
104          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
105          real life, but is still worth protecting against".
106    
107          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
108          regular expressions".
109    
110          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
111          have it.
112    
113          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
114          "configure" and the latter not, in order to fix a problem somebody had
115          with compiling the Arg class on HP-UX.
116    
117          (e) Improve the error-handling of the C++ wrapper a little bit.
118    
119          (f) New tests for checking recursion limiting.
120    
121     8. The pcre_memmove() function, which is used only if the environment does not
122        have a standard memmove() function (and is therefore rarely compiled),
123        contained two bugs: (a) use of int instead of size_t, and (b) it was not
124        returning a result (though PCRE never actually uses the result).
125    
126     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
127        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
128        returned instead of calling malloc() with an overflowing number that would
129        most likely cause subsequent chaos.
130    
131    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
132    
133    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
134        with this option is matched, the nmatch and pmatch options of regexec() are
135        ignored.
136    
137    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
138        provided in case anyone wants to the the POSIX interface with UTF-8
139        strings.
140    
141    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
142        C++ linking (needed for some HP-UX environments).
143    
144    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
145        (unused parameter) and in the pcre_printint() function (omitted "default"
146        switch label when the default is to do nothing).
147    
148    15. Added some code to make it possible, when PCRE is compiled as a C++
149        library, to replace subject pointers for pcre_exec() with a smart pointer
150        class, thus making it possible to process discontinuous strings.
151    
152    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
153        much the same function. They were added by different people who were trying
154        to make PCRE easy to compile on non-Unix systems. It has been suggested
155        that PCRE_EXPORT be abolished now that there is more automatic apparatus
156        for compiling on Windows systems. I have therefore replaced it with
157        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
158        defaults to "extern" for C or "extern C" for C++, which works fine on
159        Unix-like systems. It is now possible to override the value of PCRE_DATA_
160        SCOPE with something explicit in config.h. In addition:
161    
162        (a) pcreposix.h still had just "extern" instead of either of these macros;
163            I have replaced it with PCRE_DATA_SCOPE.
164    
165        (b) Functions such as _pcre_xclass(), which are internal to the library,
166            but external in the C sense, all had PCRE_EXPORT in their definitions.
167            This is apparently wrong for the Windows case, so I have removed it.
168            (It makes no difference on Unix-like systems.)
169    
170    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
171        of recursive calls to match(). This is different to MATCH_LIMIT because
172        that limits the total number of calls to match(), not all of which increase
173        the depth of recursion. Limiting the recursion depth limits the amount of
174        stack (or heap if NO_RECURSE is set) that is used. The default can be set
175        when PCRE is compiled, and changed at run time. A patch from Google adds
176        this functionality to the C++ interface.
177    
178    18. Changes to the handling of Unicode character properties:
179    
180        (a) Updated the table to Unicode 4.1.0.
181    
182        (b) Recognize characters that are not in the table as "Cn" (undefined).
183    
184        (c) I revised the way the table is implemented to a much improved format
185            which includes recognition of ranges. It now supports the ranges that
186            are defined in UnicodeData.txt, and it also amalgamates other
187            characters into ranges. This has reduced the number of entries in the
188            table from around 16,000 to around 3,000, thus reducing its size
189            considerably. I realized I did not need to use a tree structure after
190            all - a binary chop search is just as efficient. Having reduced the
191            number of entries, I extended their size from 6 bytes to 8 bytes to
192            allow for more data.
193    
194        (d) Added support for Unicode script names via properties such as \p{Han}.
195    
196    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
197        matching that character.
198    
199    20. When matching a repeated Unicode property with a minimum greater than zero,
200        (for example \pL{2,}), PCRE could look past the end of the subject if it
201        reached it while seeking the minimum number of characters. This could
202        happen only if some of the characters were more than one byte long, because
203        there is a check for at least the minimum number of bytes.
204    
205    21. Refactored the implementation of \p and \P so as to be more general, to
206        allow for more different types of property in future. This has changed the
207        compiled form incompatibly. Anybody with saved compiled patterns that use
208        \p or \P will have to recompile them.
209    
210    22. Added "Any" and "L&" to the supported property types.
211    
212    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
213        but give a compile time error if the value is greater than 0xff.
214    
215    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
216        accidentally not being installed or uninstalled.
217    
218    25. The pcre.h file was built from pcre.h.in, but the only changes that were
219        made were to insert the current release number. This seemed silly, because
220        it made things harder for people building PCRE on systems that don't run
221        "configure". I have turned pcre.h into a distributed file, no longer built
222        by "configure", with the version identification directly included. There is
223        no longer a pcre.h.in file.
224    
225        However, this change necessitated a change to the pcre-config script as
226        well. It is built from pcre-config.in, and one of the substitutions was the
227        release number. I have updated configure.ac so that ./configure now finds
228        the release number by grepping pcre.h.
229    
230    26. Added the ability to run the tests under valgrind.
231    
232    
233    Version 6.4 05-Sep-05
234    ---------------------
235    
236     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
237        "--" to be printed when multiple files were scanned, even when none of the
238        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
239        consider it to be a bug, and have restored the previous behaviour.
240    
241     2. A couple of code tidies to get rid of compiler warnings.
242    
243     3. The pcretest program used to cheat by referring to symbols in the library
244        whose names begin with _pcre_. These are internal symbols that are not
245        really supposed to be visible externally, and in some environments it is
246        possible to suppress them. The cheating is now confined to including
247        certain files from the library's source, which is a bit cleaner.
248    
249     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
250        file's purpose clearer.
251    
252     5. Reorganized pcre_ucp_findchar().
253    
254    
255    Version 6.3 15-Aug-05
256    ---------------------
257    
258     1. The file libpcre.pc.in did not have general read permission in the tarball.
259    
260     2. There were some problems when building without C++ support:
261    
262        (a) If C++ support was not built, "make install" and "make test" still
263            tried to test it.
264    
265        (b) There were problems when the value of CXX was explicitly set. Some
266            changes have been made to try to fix these, and ...
267    
268        (c) --disable-cpp can now be used to explicitly disable C++ support.
269    
270        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
271            backslash in a target when C++ was disabled. This confuses some
272            versions of "make", apparently. Using an intermediate variable solves
273            this. (Same for CPP_LOBJ.)
274    
275     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
276        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
277        necessary on certain architectures.
278    
279     4. Added a setting of -export-symbols-regex to the link command to remove
280        those symbols that are exported in the C sense, but actually are local
281        within the library, and not documented. Their names all begin with
282        "_pcre_". This is not a perfect job, because (a) we have to except some
283        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
284        available (and never for static libraries). I have made a note to try to
285        find a way round (a) in the future.
286    
287    
288    Version 6.2 01-Aug-05
289    ---------------------
290    
291     1. There was no test for integer overflow of quantifier values. A construction
292        such as {1111111111111111} would give undefined results. What is worse, if
293        a minimum quantifier for a parenthesized subpattern overflowed and became
294        negative, the calculation of the memory size went wrong. This could have
295        led to memory overwriting.
296    
297     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
298    
299     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
300        operating environments where this matters.
301    
302     4. Applied Giuseppe Maxia's patch to add additional features for controlling
303        PCRE options from within the C++ wrapper.
304    
305     5. Named capturing subpatterns were not being correctly counted when a pattern
306        was compiled. This caused two problems: (a) If there were more than 100
307        such subpatterns, the calculation of the memory needed for the whole
308        compiled pattern went wrong, leading to an overflow error. (b) Numerical
309        back references of the form \12, where the number was greater than 9, were
310        not recognized as back references, even though there were sufficient
311        previous subpatterns.
312    
313     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
314        versions of gcc, e.g. 2.95.4.
315    
316    
317    Version 6.1 21-Jun-05
318    ---------------------
319    
320     1. There was one reference to the variable "posix" in pcretest.c that was not
321        surrounded by "#if !defined NOPOSIX".
322    
323     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
324        the cross-check on the old pcre_info() function, for the benefit of the
325        cut-down version of PCRE that is currently imported into Exim.
326    
327     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
328        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
329        patterns that start (?i) but I don't think that matters. The use of (?i) is
330        just an example; this all applies to the other options as well.
331    
332     4. Since libtool seems to echo the compile commands it is issuing, the output
333        from "make" can be reduced a bit by putting "@" in front of each libtool
334        compile command.
335    
336     5. Patch from the folks at Google for configure.in to be a bit more thorough
337        in checking for a suitable C++ installation before trying to compile the
338        C++ stuff. This should fix a reported problem when a compiler was present,
339        but no suitable headers.
340    
341     6. The man pages all had just "PCRE" as their title. I have changed them to
342        be the relevant file name. I have also arranged that these names are
343        retained in the file doc/pcre.txt, which is a concatenation in text format
344        of all the man pages except the little individual ones for each function.
345    
346     7. The NON-UNIX-USE file had not been updated for the different set of source
347        files that come with release 6. I also added a few comments about the C++
348        wrapper.
349    
350    
351    Version 6.0 07-Jun-05
352    ---------------------
353    
354     1. Some minor internal re-organization to help with my DFA experiments.
355    
356     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
357        didn't matter for the library itself when fully configured, but did matter
358        when compiling without UCP support, or within Exim, where the ucp files are
359        not imported.
360    
361     3. Refactoring of the library code to split up the various functions into
362        different source modules. The addition of the new DFA matching code (see
363        below) to a single monolithic source would have made it really too
364        unwieldy, quite apart from causing all the code to be include in a
365        statically linked application, when only some functions are used. This is
366        relevant even without the DFA addition now that patterns can be compiled in
367        one application and matched in another.
368    
369        The downside of splitting up is that there have to be some external
370        functions and data tables that are used internally in different modules of
371        the library but which are not part of the API. These have all had their
372        names changed to start with "_pcre_" so that they are unlikely to clash
373        with other external names.
374    
375     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
376        a different (DFA) algorithm. Although it is slower than the original
377        function, it does have some advantages for certain types of matching
378        problem.
379    
380     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
381        including restarting after a partial match.
382    
383     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
384        defined when compiling for Windows was sent to me. I have put it into the
385        code, though I have no means of testing or verifying it.
386    
387     7. Added the pcre_refcount() auxiliary function.
388    
389     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
390        match before or at the first newline in the subject string. In pcretest,
391        the /f option on a pattern can be used to set this.
392    
393     9. A repeated \w when used in UTF-8 mode with characters greater than 256
394        would behave wrongly. This has been present in PCRE since release 4.0.
395    
396    10. A number of changes to the pcregrep command:
397    
398        (a) Refactored how -x works; insert ^(...)$ instead of setting
399            PCRE_ANCHORED and checking the length, in preparation for adding
400            something similar for -w.
401    
402        (b) Added the -w (match as a word) option.
403    
404        (c) Refactored the way lines are read and buffered so as to have more
405            than one at a time available.
406    
407        (d) Implemented a pcregrep test script.
408    
409        (e) Added the -M (multiline match) option. This allows patterns to match
410            over several lines of the subject. The buffering ensures that at least
411            8K, or the rest of the document (whichever is the shorter) is available
412            for matching (and similarly the previous 8K for lookbehind assertions).
413    
414        (f) Changed the --help output so that it now says
415    
416              -w, --word-regex(p)
417    
418            instead of two lines, one with "regex" and the other with "regexp"
419            because that confused at least one person since the short forms are the
420            same. (This required a bit of code, as the output is generated
421            automatically from a table. It wasn't just a text change.)
422    
423        (g) -- can be used to terminate pcregrep options if the next thing isn't an
424            option but starts with a hyphen. Could be a pattern or a path name
425            starting with a hyphen, for instance.
426    
427        (h) "-" can be given as a file name to represent stdin.
428    
429        (i) When file names are being printed, "(standard input)" is used for
430            the standard input, for compatibility with GNU grep. Previously
431            "<stdin>" was used.
432    
433        (j) The option --label=xxx can be used to supply a name to be used for
434            stdin when file names are being printed. There is no short form.
435    
436        (k) Re-factored the options decoding logic because we are going to add
437            two more options that take data. Such options can now be given in four
438            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
439    
440        (l) Added the -A, -B, and -C options for requesting that lines of context
441            around matches be printed.
442    
443        (m) Added the -L option to print the names of files that do not contain
444            any matching lines, that is, the complement of -l.
445    
446        (n) The return code is 2 if any file cannot be opened, but pcregrep does
447            continue to scan other files.
448    
449        (o) The -s option was incorrectly implemented. For compatibility with other
450            greps, it now suppresses the error message for a non-existent or non-
451            accessible file (but not the return code). There is a new option called
452            -q that suppresses the output of matching lines, which was what -s was
453            previously doing.
454    
455        (p) Added --include and --exclude options to specify files for inclusion
456            and exclusion when recursing.
457    
458    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
459        Hopefully, it now does.
460    
461    12. Missing cast in pcre_study().
462    
463    13. Added an "uninstall" target to the makefile.
464    
465    14. Replaced "extern" in the function prototypes in Makefile.in with
466        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
467        world, but is set differently for Windows.
468    
469    15. Added a second compiling function called pcre_compile2(). The only
470        difference is that it has an extra argument, which is a pointer to an
471        integer error code. When there is a compile-time failure, this is set
472        non-zero, in addition to the error test pointer being set to point to an
473        error message. The new argument may be NULL if no error number is required
474        (but then you may as well call pcre_compile(), which is now just a
475        wrapper). This facility is provided because some applications need a
476        numeric error indication, but it has also enabled me to tidy up the way
477        compile-time errors are handled in the POSIX wrapper.
478    
479    16. Added VPATH=.libs to the makefile; this should help when building with one
480        prefix path and installing with another. (Or so I'm told by someone who
481        knows more about this stuff than I do.)
482    
483    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
484        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
485        match everything, including newlines. This is not POSIX-compatible, but
486        somebody wanted the feature. From pcretest it can be activated by using
487        both the P and the s flags.
488    
489    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
490    
491    19. libpcre.pc was being incorrectly installed as executable.
492    
493    20. A couple of places in pcretest check for end-of-line by looking for '\n';
494        it now also looks for '\r' so that it will work unmodified on Windows.
495    
496    21. Added Google's contributed C++ wrapper to the distribution.
497    
498    22. Added some untidy missing memory free() calls in pcretest, to keep
499        Electric Fence happy when testing.
500    
501    
502    
503    Version 5.0 13-Sep-04
504    ---------------------
505    
506     1. Internal change: literal characters are no longer packed up into items
507        containing multiple characters in a single byte-string. Each character
508        is now matched using a separate opcode. However, there may be more than one
509        byte in the character in UTF-8 mode.
510    
511     2. The pcre_callout_block structure has two new fields: pattern_position and
512        next_item_length. These contain the offset in the pattern to the next match
513        item, and its length, respectively.
514    
515     3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
516        insertion of callouts before each pattern item. Added the /C option to
517        pcretest to make use of this.
518    
519     4. On the advice of a Windows user, the lines
520    
521          #if defined(_WIN32) || defined(WIN32)
522          _setmode( _fileno( stdout ), 0x8000 );
523          #endif  /* defined(_WIN32) || defined(WIN32) */
524    
525        have been added to the source of pcretest. This apparently does useful
526        magic in relation to line terminators.
527    
528     5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
529        for the benefit of those environments where the "b" makes a difference.
530    
531     6. The icc compiler has the same options as gcc, but "configure" doesn't seem
532        to know about it. I have put a hack into configure.in that adds in code
533        to set GCC=yes if CC=icc. This seems to end up at a point in the
534        generated configure script that is early enough to affect the setting of
535        compiler options, which is what is needed, but I have no means of testing
536        whether it really works. (The user who reported this had patched the
537        generated configure script, which of course I cannot do.)
538    
539        LATER: After change 22 below (new libtool files), the configure script
540        seems to know about icc (and also ecc). Therefore, I have commented out
541        this hack in configure.in.
542    
543     7. Added support for pkg-config (2 patches were sent in).
544    
545     8. Negated POSIX character classes that used a combination of internal tables
546        were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
547        [[:^ascii]]. Typically, they would match almost any characters. The other
548        POSIX classes were not broken in this way.
549    
550     9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
551        to find the match, as PCRE was deluded into thinking that the match had to
552        start at the start point or following a newline. The same bug applied to
553        patterns with negative forward assertions or any backward assertions
554        preceding ".*" at the start, unless the pattern required a fixed first
555        character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
556    
557    10. In UTF-8 mode, when moving forwards in the subject after a failed match
558        starting at the last subject character, bytes beyond the end of the subject
559        string were read.
560    
561    11. Renamed the variable "class" as "classbits" to make life easier for C++
562        users. (Previously there was a macro definition, but it apparently wasn't
563        enough.)
564    
565    12. Added the new field "tables" to the extra data so that tables can be passed
566        in at exec time, or the internal tables can be re-selected. This allows
567        a compiled regex to be saved and re-used at a later time by a different
568        program that might have everything at different addresses.
569    
570    13. Modified the pcre-config script so that, when run on Solaris, it shows a
571        -R library as well as a -L library.
572    
573    14. The debugging options of pcretest (-d on the command line or D on a
574        pattern) showed incorrect output for anything following an extended class
575        that contained multibyte characters and which was followed by a quantifier.
576    
577    15. Added optional support for general category Unicode character properties
578        via the \p, \P, and \X escapes. Unicode property support implies UTF-8
579        support. It adds about 90K to the size of the library. The meanings of the
580        inbuilt class escapes such as \d and \s have NOT been changed.
581    
582    16. Updated pcredemo.c to include calls to free() to release the memory for the
583        compiled pattern.
584    
585    17. The generated file chartables.c was being created in the source directory
586        instead of in the building directory. This caused the build to fail if the
587        source directory was different from the building directory, and was
588        read-only.
589    
590    18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
591        file. No doubt somebody will tell me if they don't make sense... Also added
592        Dan Mooney's comments about building on OpenVMS.
593    
594    19. Added support for partial matching via the PCRE_PARTIAL option for
595        pcre_exec() and the \P data escape in pcretest.
596    
597    20. Extended pcretest with 3 new pattern features:
598    
599        (i)   A pattern option of the form ">rest-of-line" causes pcretest to
600              write the compiled pattern to the file whose name is "rest-of-line".
601              This is a straight binary dump of the data, with the saved pointer to
602              the character tables forced to be NULL. The study data, if any, is
603              written too. After writing, pcretest reads a new pattern.
604    
605        (ii)  If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
606              compiled pattern from the given file. There must not be any
607              occurrences of "<" in the file name (pretty unlikely); if there are,
608              pcretest will instead treat the initial "<" as a pattern delimiter.
609              After reading in the pattern, pcretest goes on to read data lines as
610              usual.
611    
612        (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
613              and 16-bit fields in a compiled pattern, to simulate a pattern that
614              was compiled on a host of opposite endianness.
615    
616    21. The pcre-exec() function can now cope with patterns that were compiled on
617        hosts of opposite endianness, with this restriction:
618    
619          As for any compiled expression that is saved and used later, the tables
620          pointer field cannot be preserved; the extra_data field in the arguments
621          to pcre_exec() should be used to pass in a tables address if a value
622          other than the default internal tables were used at compile time.
623    
624    22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
625        now diagnosed as an error. Previously, most of the time, a negative number
626        would have been treated as zero, but if in addition "ovector" was passed as
627        NULL, a crash could occur.
628    
629    23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
630        new versions from the libtool 1.5 distribution (the last one is a copy of
631        a file called libtool.m4). This seems to have fixed the need to patch
632        "configure" to support Darwin 1.3 (which I used to do). However, I still
633        had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
634        workstation).
635    
636    24. Changed the PCRE licence to be the more standard "BSD" licence.
637    
638    
639    Version 4.5 01-Dec-03
640    ---------------------
641    
642     1. There has been some re-arrangement of the code for the match() function so
643        that it can be compiled in a version that does not call itself recursively.
644        Instead, it keeps those local variables that need separate instances for
645        each "recursion" in a frame on the heap, and gets/frees frames whenever it
646        needs to "recurse". Keeping track of where control must go is done by means
647        of setjmp/longjmp. The whole thing is implemented by a set of macros that
648        hide most of the details from the main code, and operates only if
649        NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
650        "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
651        operating.
652    
653        To make it easier for callers to provide specially tailored get/free
654        functions for this usage, two new functions, pcre_stack_malloc, and
655        pcre_stack_free, are used. They are always called in strict stacking order,
656        and the size of block requested is always the same.
657    
658        The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
659        PCRE has been compiled to use the stack or the heap for recursion. The
660        -C option of pcretest uses this to show which version is compiled.
661    
662        A new data escape \S, is added to pcretest; it causes the amounts of store
663        obtained and freed by both kinds of malloc/free at match time to be added
664        to the output.
665    
666     2. Changed the locale test to use "fr_FR" instead of "fr" because that's
667        what's available on my current Linux desktop machine.
668    
669     3. When matching a UTF-8 string, the test for a valid string at the start has
670        been extended. If start_offset is not zero, PCRE now checks that it points
671        to a byte that is the start of a UTF-8 character. If not, it returns
672        PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
673        this is necessary because there may be backward assertions in the pattern.
674        When matching the same subject several times, it may save resources to use
675        PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
676    
677     4. The code for checking the validity of UTF-8 strings has been tightened so
678        that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
679        containing "overlong sequences".
680    
681     5. Fixed a bug (appearing twice) that I could not find any way of exploiting!
682        I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
683        should have been "&", but it just so happened that all the cases this let
684        through by mistake were picked up later in the function.
685    
686     6. I had used a variable called "isblank" - this is a C99 function, causing
687        some compilers to warn. To avoid this, I renamed it (as "blankclass").
688    
689     7. Cosmetic: (a) only output another newline at the end of pcretest if it is
690        prompting; (b) run "./pcretest /dev/null" at the start of the test script
691        so the version is shown; (c) stop "make test" echoing "./RunTest".
692    
693     8. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
694    
695     9. The prototype for memmove() for systems that don't have it was using
696        size_t, but the inclusion of the header that defines size_t was later. I've
697        moved the #includes for the C headers earlier to avoid this.
698    
699    10. Added some adjustments to the code to make it easier to compiler on certain
700        special systems:
701    
702          (a) Some "const" qualifiers were missing.
703          (b) Added the macro EXPORT before all exported functions; by default this
704              is defined to be empty.
705          (c) Changed the dftables auxiliary program (that builds chartables.c) so
706              that it reads its output file name as an argument instead of writing
707              to the standard output and assuming this can be redirected.
708    
709    11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
710        class containing characters with values greater than 255, PCRE compilation
711        went into a loop.
712    
713    12. A recursive reference to a subpattern that was within another subpattern
714        that had a minimum quantifier of zero caused PCRE to crash. For example,
715        (x(y(?2))z)? provoked this bug with a subject that got as far as the
716        recursion. If the recursively-called subpattern itself had a zero repeat,
717        that was OK.
718    
719    13. In pcretest, the buffer for reading a data line was set at 30K, but the
720        buffer into which it was copied (for escape processing) was still set at
721        1024, so long lines caused crashes.
722    
723    14. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
724        "internal error: code overflow...". This applied to any character class
725        that was followed by a possessive quantifier.
726    
727    15. Modified the Makefile to add libpcre.la as a prerequisite for
728        libpcreposix.la because I was told this is needed for a parallel build to
729        work.
730    
731    16. If a pattern that contained .* following optional items at the start was
732        studied, the wrong optimizing data was generated, leading to matching
733        errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
734        matching string must start with a or b or c. The correct conclusion for
735        this pattern is that a match can start with any character.
736    
737    
738    Version 4.4 13-Aug-03
739    ---------------------
740    
741     1. In UTF-8 mode, a character class containing characters with values between
742        127 and 255 was not handled correctly if the compiled pattern was studied.
743        In fixing this, I have also improved the studying algorithm for such
744        classes (slightly).
745    
746     2. Three internal functions had redundant arguments passed to them. Removal
747        might give a very teeny performance improvement.
748    
749     3. Documentation bug: the value of the capture_top field in a callout is *one
750        more than* the number of the hightest numbered captured substring.
751    
752     4. The Makefile linked pcretest and pcregrep with -lpcre, which could result
753        in incorrectly linking with a previously installed version. They now link
754        explicitly with libpcre.la.
755    
756     5. configure.in no longer needs to recognize Cygwin specially.
757    
758     6. A problem in pcre.in for Windows platforms is fixed.
759    
760     7. If a pattern was successfully studied, and the -d (or /D) flag was given to
761        pcretest, it used to include the size of the study block as part of its
762        output. Unfortunately, the structure contains a field that has a different
763        size on different hardware architectures. This meant that the tests that
764        showed this size failed. As the block is currently always of a fixed size,
765        this information isn't actually particularly useful in pcretest output, so
766        I have just removed it.
767    
768     8. Three pre-processor statements accidentally did not start in column 1.
769        Sadly, there are *still* compilers around that complain, even though
770        standard C has not required this for well over a decade. Sigh.
771    
772     9. In pcretest, the code for checking callouts passed small integers in the
773        callout_data field, which is a void * field. However, some picky compilers
774        complained about the casts involved for this on 64-bit systems. Now
775        pcretest passes the address of the small integer instead, which should get
776        rid of the warnings.
777    
778    10. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
779        both compile and run time, and gives an error if an invalid UTF-8 sequence
780        is found. There is a option for disabling this check in cases where the
781        string is known to be correct and/or the maximum performance is wanted.
782    
783    11. In response to a bug report, I changed one line in Makefile.in from
784    
785            -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
786        to
787            -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \
788    
789        to look similar to other lines, but I have no way of telling whether this
790        is the right thing to do, as I do not use Windows. No doubt I'll get told
791        if it's wrong...
792    
793    
794    Version 4.3 21-May-03
795    ---------------------
796    
797    1. Two instances of @WIN_PREFIX@ omitted from the Windows targets in the
798       Makefile.
799    
800    2. Some refactoring to improve the quality of the code:
801    
802       (i)   The utf8_table... variables are now declared "const".
803    
804       (ii)  The code for \cx, which used the "case flipping" table to upper case
805             lower case letters, now just substracts 32. This is ASCII-specific,
806             but the whole concept of \cx is ASCII-specific, so it seems
807             reasonable.
808    
809       (iii) PCRE was using its character types table to recognize decimal and
810             hexadecimal digits in the pattern. This is silly, because it handles
811             only 0-9, a-f, and A-F, but the character types table is locale-
812             specific, which means strange things might happen. A private
813             table is now used for this - though it costs 256 bytes, a table is
814             much faster than multiple explicit tests. Of course, the standard
815             character types table is still used for matching digits in subject
816             strings against \d.
817    
818       (iv)  Strictly, the identifier ESC_t is reserved by POSIX (all identifiers
819             ending in _t are). So I've renamed it as ESC_tee.
820    
821    3. The first argument for regexec() in the POSIX wrapper should have been
822       defined as "const".
823    
824    4. Changed pcretest to use malloc() for its buffers so that they can be
825       Electric Fenced for debugging.
826    
827    5. There were several places in the code where, in UTF-8 mode, PCRE would try
828       to read one or more bytes before the start of the subject string. Often this
829       had no effect on PCRE's behaviour, but in some circumstances it could
830       provoke a segmentation fault.
831    
832    6. A lookbehind at the start of a pattern in UTF-8 mode could also cause PCRE
833       to try to read one or more bytes before the start of the subject string.
834    
835    7. A lookbehind in a pattern matched in non-UTF-8 mode on a PCRE compiled with
836       UTF-8 support could misbehave in various ways if the subject string
837       contained bytes with the 0x80 bit set and the 0x40 bit unset in a lookbehind
838       area. (PCRE was not checking for the UTF-8 mode flag, and trying to move
839       back over UTF-8 characters.)
840    
841    
842  Version 4.2 14-Apr-03  Version 4.2 14-Apr-03
843  ---------------------  ---------------------
844    

Legend:
Removed from v.67  
changed lines
  Added in v.89

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12