ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 75 by nigel, Sat Feb 24 21:40:37 2007 UTC revision 83 by nigel, Sat Feb 24 21:41:06 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 6.3 15-Aug-05
5    ---------------------
7     1. The file libpcre.pc.in did not have general read permission in the tarball.
9     2. There were some problems when building without C++ support:
11        (a) If C++ support was not built, "make install" and "make test" still
12            tried to test it.
14        (b) There were problems when the value of CXX was explicitly set. Some
15            changes have been made to try to fix these, and ...
17        (c) --disable-cpp can now be used to explicitly disable C++ support.
19        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
20            backslash in a target when C++ was disabled. This confuses some
21            versions of "make", apparently. Using an intermediate variable solves
22            this. (Same for CPP_LOBJ.)
24     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
25        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
26        necessary on certain architectures.
28     4. Added a setting of -export-symbols-regex to the link command to remove
29        those symbols that are exported in the C sense, but actually are local
30        within the library, and not documented. Their names all begin with
31        "_pcre_". This is not a perfect job, because (a) we have to except some
32        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
33        available (and never for static libraries). I have made a note to try to
34        find a way round (a) in the future.
37    Version 6.2 01-Aug-05
38    ---------------------
40     1. There was no test for integer overflow of quantifier values. A construction
41        such as {1111111111111111} would give undefined results. What is worse, if
42        a minimum quantifier for a parenthesized subpattern overflowed and became
43        negative, the calculation of the memory size went wrong. This could have
44        led to memory overwriting.
46     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
48     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
49        operating environments where this matters.
51     4. Applied Giuseppe Maxia's patch to add additional features for controlling
52        PCRE options from within the C++ wrapper.
54     5. Named capturing subpatterns were not being correctly counted when a pattern
55        was compiled. This caused two problems: (a) If there were more than 100
56        such subpatterns, the calculation of the memory needed for the whole
57        compiled pattern went wrong, leading to an overflow error. (b) Numerical
58        back references of the form \12, where the number was greater than 9, were
59        not recognized as back references, even though there were sufficient
60        previous subpatterns.
62     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
63        versions of gcc, e.g. 2.95.4.
66    Version 6.1 21-Jun-05
67    ---------------------
69     1. There was one reference to the variable "posix" in pcretest.c that was not
70        surrounded by "#if !defined NOPOSIX".
72     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
73        the cross-check on the old pcre_info() function, for the benefit of the
74        cut-down version of PCRE that is currently imported into Exim.
76     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
77        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
78        patterns that start (?i) but I don't think that matters. The use of (?i) is
79        just an example; this all applies to the other options as well.
81     4. Since libtool seems to echo the compile commands it is issuing, the output
82        from "make" can be reduced a bit by putting "@" in front of each libtool
83        compile command.
85     5. Patch from the folks at Google for configure.in to be a bit more thorough
86        in checking for a suitable C++ installation before trying to compile the
87        C++ stuff. This should fix a reported problem when a compiler was present,
88        but no suitable headers.
90     6. The man pages all had just "PCRE" as their title. I have changed them to
91        be the relevant file name. I have also arranged that these names are
92        retained in the file doc/pcre.txt, which is a concatenation in text format
93        of all the man pages except the little individual ones for each function.
95     7. The NON-UNIX-USE file had not been updated for the different set of source
96        files that come with release 6. I also added a few comments about the C++
97        wrapper.
100    Version 6.0 07-Jun-05
101    ---------------------
103     1. Some minor internal re-organization to help with my DFA experiments.
105     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
106        didn't matter for the library itself when fully configured, but did matter
107        when compiling without UCP support, or within Exim, where the ucp files are
108        not imported.
110     3. Refactoring of the library code to split up the various functions into
111        different source modules. The addition of the new DFA matching code (see
112        below) to a single monolithic source would have made it really too
113        unwieldy, quite apart from causing all the code to be include in a
114        statically linked application, when only some functions are used. This is
115        relevant even without the DFA addition now that patterns can be compiled in
116        one application and matched in another.
118        The downside of splitting up is that there have to be some external
119        functions and data tables that are used internally in different modules of
120        the library but which are not part of the API. These have all had their
121        names changed to start with "_pcre_" so that they are unlikely to clash
122        with other external names.
124     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
125        a different (DFA) algorithm. Although it is slower than the original
126        function, it does have some advantages for certain types of matching
127        problem.
129     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
130        including restarting after a partial match.
132     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
133        defined when compiling for Windows was sent to me. I have put it into the
134        code, though I have no means of testing or verifying it.
136     7. Added the pcre_refcount() auxiliary function.
138     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
139        match before or at the first newline in the subject string. In pcretest,
140        the /f option on a pattern can be used to set this.
142     9. A repeated \w when used in UTF-8 mode with characters greater than 256
143        would behave wrongly. This has been present in PCRE since release 4.0.
145    10. A number of changes to the pcregrep command:
147        (a) Refactored how -x works; insert ^(...)$ instead of setting
148            PCRE_ANCHORED and checking the length, in preparation for adding
149            something similar for -w.
151        (b) Added the -w (match as a word) option.
153        (c) Refactored the way lines are read and buffered so as to have more
154            than one at a time available.
156        (d) Implemented a pcregrep test script.
158        (e) Added the -M (multiline match) option. This allows patterns to match
159            over several lines of the subject. The buffering ensures that at least
160            8K, or the rest of the document (whichever is the shorter) is available
161            for matching (and similarly the previous 8K for lookbehind assertions).
163        (f) Changed the --help output so that it now says
165              -w, --word-regex(p)
167            instead of two lines, one with "regex" and the other with "regexp"
168            because that confused at least one person since the short forms are the
169            same. (This required a bit of code, as the output is generated
170            automatically from a table. It wasn't just a text change.)
172        (g) -- can be used to terminate pcregrep options if the next thing isn't an
173            option but starts with a hyphen. Could be a pattern or a path name
174            starting with a hyphen, for instance.
176        (h) "-" can be given as a file name to represent stdin.
178        (i) When file names are being printed, "(standard input)" is used for
179            the standard input, for compatibility with GNU grep. Previously
180            "<stdin>" was used.
182        (j) The option --label=xxx can be used to supply a name to be used for
183            stdin when file names are being printed. There is no short form.
185        (k) Re-factored the options decoding logic because we are going to add
186            two more options that take data. Such options can now be given in four
187            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
189        (l) Added the -A, -B, and -C options for requesting that lines of context
190            around matches be printed.
192        (m) Added the -L option to print the names of files that do not contain
193            any matching lines, that is, the complement of -l.
195        (n) The return code is 2 if any file cannot be opened, but pcregrep does
196            continue to scan other files.
198        (o) The -s option was incorrectly implemented. For compatibility with other
199            greps, it now suppresses the error message for a non-existent or non-
200            accessible file (but not the return code). There is a new option called
201            -q that suppresses the output of matching lines, which was what -s was
202            previously doing.
204        (p) Added --include and --exclude options to specify files for inclusion
205            and exclusion when recursing.
207    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
208        Hopefully, it now does.
210    12. Missing cast in pcre_study().
212    13. Added an "uninstall" target to the makefile.
214    14. Replaced "extern" in the function prototypes in Makefile.in with
215        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
216        world, but is set differently for Windows.
218    15. Added a second compiling function called pcre_compile2(). The only
219        difference is that it has an extra argument, which is a pointer to an
220        integer error code. When there is a compile-time failure, this is set
221        non-zero, in addition to the error test pointer being set to point to an
222        error message. The new argument may be NULL if no error number is required
223        (but then you may as well call pcre_compile(), which is now just a
224        wrapper). This facility is provided because some applications need a
225        numeric error indication, but it has also enabled me to tidy up the way
226        compile-time errors are handled in the POSIX wrapper.
228    16. Added VPATH=.libs to the makefile; this should help when building with one
229        prefix path and installing with another. (Or so I'm told by someone who
230        knows more about this stuff than I do.)
232    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
233        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
234        match everything, including newlines. This is not POSIX-compatible, but
235        somebody wanted the feature. From pcretest it can be activated by using
236        both the P and the s flags.
238    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
240    19. libpcre.pc was being incorrectly installed as executable.
242    20. A couple of places in pcretest check for end-of-line by looking for '\n';
243        it now also looks for '\r' so that it will work unmodified on Windows.
245    21. Added Google's contributed C++ wrapper to the distribution.
247    22. Added some untidy missing memory free() calls in pcretest, to keep
248        Electric Fence happy when testing.
252  Version 5.0 13-Sep-04  Version 5.0 13-Sep-04
253  ---------------------  ---------------------

Removed from v.75  
changed lines
  Added in v.83

  ViewVC Help
Powered by ViewVC 1.1.5