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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.65  
changed lines
  Added in v.87

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12