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

Diff of /code/trunk/ChangeLog

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

revision 455 by ph10, Sat Sep 26 19:12:32 2009 UTC revision 471 by ph10, Fri Dec 11 15:11:55 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.00 ??-???-??  Version 8.01 11-Dec-09
5    ----------------------
6    
7    1.  If a pattern contained a conditional subpattern with only one branch (in
8        particular, this includes all (DEFINE) patterns), a call to pcre_study()
9        computed the wrong minimum data length (which is of course zero for such
10        subpatterns).
11    
12    
13    Version 8.00 19-Oct-09
14  ----------------------  ----------------------
15    
16  1.  The table for translating pcre_compile() error codes into POSIX error codes  1.  The table for translating pcre_compile() error codes into POSIX error codes
17      was out-of-date, and there was no check on the pcre_compile() error code      was out-of-date, and there was no check on the pcre_compile() error code
18      being within the table. This could lead to an OK return being given in      being within the table. This could lead to an OK return being given in
19      error.      error.
20    
21  2.  Changed the call to open a subject file in pcregrep from fopen(pathname,  2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
22      "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests      "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
23      in a Windows environment.      in a Windows environment.
24    
25  3.  The pcregrep --count option prints the count for each file even when it is  3.  The pcregrep --count option prints the count for each file even when it is
26      zero, as does GNU grep. However, pcregrep was also printing all files when      zero, as does GNU grep. However, pcregrep was also printing all files when
27      --files-with-matches was added. Now, when both options are given, it prints      --files-with-matches was added. Now, when both options are given, it prints
28      counts only for those files that have at least one match. (GNU grep just      counts only for those files that have at least one match. (GNU grep just
29      prints the file name in this circumstance, but including the count seems      prints the file name in this circumstance, but including the count seems
30      more useful - otherwise, why use --count?) Also ensured that the      more useful - otherwise, why use --count?) Also ensured that the
31      combination -clh just lists non-zero counts, with no names.      combination -clh just lists non-zero counts, with no names.
32    
33  4.  The long form of the pcregrep -F option was incorrectly implemented as  4.  The long form of the pcregrep -F option was incorrectly implemented as
34      --fixed_strings instead of --fixed-strings. This is an incompatible change,      --fixed_strings instead of --fixed-strings. This is an incompatible change,
35      but it seems right to fix it, and I didn't think it was worth preserving      but it seems right to fix it, and I didn't think it was worth preserving
36      the old behaviour.      the old behaviour.
37    
38  5.  The command line items --regex=pattern and --regexp=pattern were not  5.  The command line items --regex=pattern and --regexp=pattern were not
39      recognized by pcregrep, which required --regex pattern or --regexp pattern      recognized by pcregrep, which required --regex pattern or --regexp pattern
40      (with a space rather than an '='). The man page documented the '=' forms,      (with a space rather than an '='). The man page documented the '=' forms,
41      which are compatible with GNU grep; these now work.      which are compatible with GNU grep; these now work.
42    
43  6.  No libpcreposix.pc file was created for pkg-config; there was just  6.  No libpcreposix.pc file was created for pkg-config; there was just
44      libpcre.pc and libpcrecpp.pc. The omission has been rectified.      libpcre.pc and libpcrecpp.pc. The omission has been rectified.
45    
46  7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size  7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
47      when UCP support is not needed, by modifying the Python script that      when UCP support is not needed, by modifying the Python script that
48      generates it from Unicode data files. This should not matter if the module      generates it from Unicode data files. This should not matter if the module
49      is correctly used as a library, but I received one complaint about 50K of      is correctly used as a library, but I received one complaint about 50K of
50      unwanted data. My guess is that the person linked everything into his      unwanted data. My guess is that the person linked everything into his
51      program rather than using a library. Anyway, it does no harm.      program rather than using a library. Anyway, it does no harm.
52    
53  8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger  8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
54      was a minimum greater than 1 for a wide character in a possessive      was a minimum greater than 1 for a wide character in a possessive
55      repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8      repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
56      which had an unlimited repeat of a nested, fixed maximum repeat of a wide      which had an unlimited repeat of a nested, fixed maximum repeat of a wide
57      character. Chaos in the form of incorrect output or a compiling loop could      character. Chaos in the form of incorrect output or a compiling loop could
58      result.      result.
59    
60  9.  The restrictions on what a pattern can contain when partial matching is  9.  The restrictions on what a pattern can contain when partial matching is
61      requested for pcre_exec() have been removed. All patterns can now be      requested for pcre_exec() have been removed. All patterns can now be
62      partially matched by this function. In addition, if there are at least two      partially matched by this function. In addition, if there are at least two
63      slots in the offset vector, the offset of the earliest inspected character      slots in the offset vector, the offset of the earliest inspected character
64      for the match and the offset of the end of the subject are set in them when      for the match and the offset of the end of the subject are set in them when
65      PCRE_ERROR_PARTIAL is returned.      PCRE_ERROR_PARTIAL is returned.
66    
67  10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is  10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
68      synonymous with PCRE_PARTIAL, for backwards compatibility, and      synonymous with PCRE_PARTIAL, for backwards compatibility, and
69      PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,      PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
70      and may be more useful for multi-segment matching, especially with      and may be more useful for multi-segment matching.
71      pcre_exec().  
72    11. Partial matching with pcre_exec() is now more intuitive. A partial match
73  11. Partial matching with pcre_exec() is now more intuitive. A partial match      used to be given if ever the end of the subject was reached; now it is
74      used to be given if ever the end of the subject was reached; now it is      given only if matching could not proceed because another character was
75      given only if matching could not proceed because another character was      needed. This makes a difference in some odd cases such as Z(*FAIL) with the
76      needed. This makes a difference in some odd cases such as Z(*FAIL) with the      string "Z", which now yields "no match" instead of "partial match". In the
77      string "Z", which now yields "no match" instead of "partial match". In the      case of pcre_dfa_exec(), "no match" is given if every matching path for the
78      case of pcre_dfa_exec(), "no match" is given if every matching path for the      final character ended with (*FAIL).
79      final character ended with (*FAIL).  
   
80  12. Restarting a match using pcre_dfa_exec() after a partial match did not work  12. Restarting a match using pcre_dfa_exec() after a partial match did not work
81      if the pattern had a "must contain" character that was already found in the      if the pattern had a "must contain" character that was already found in the
82      earlier partial match, unless partial matching was again requested. For      earlier partial match, unless partial matching was again requested. For
83      example, with the pattern /dog.(body)?/, the "must contain" character is      example, with the pattern /dog.(body)?/, the "must contain" character is
84      "g". If the first part-match was for the string "dog", restarting with      "g". If the first part-match was for the string "dog", restarting with
85      "sbody" failed. This bug has been fixed.      "sbody" failed. This bug has been fixed.
86    
87  13. The string returned by pcre_dfa_exec() after a partial match has been  13. The string returned by pcre_dfa_exec() after a partial match has been
88      changed so that it starts at the first inspected character rather than the      changed so that it starts at the first inspected character rather than the
89      first character of the match. This makes a difference only if the pattern      first character of the match. This makes a difference only if the pattern
90      starts with a lookbehind assertion or \b or \B (\K is not supported by      starts with a lookbehind assertion or \b or \B (\K is not supported by
91      pcre_dfa_exec()). It's an incompatible change, but it makes the two      pcre_dfa_exec()). It's an incompatible change, but it makes the two
92      matching functions compatible, and I think it's the right thing to do.      matching functions compatible, and I think it's the right thing to do.
93    
94  14. Added a pcredemo man page, created automatically from the pcredemo.c file,  14. Added a pcredemo man page, created automatically from the pcredemo.c file,
95      so that the demonstration program is easily available in environments where      so that the demonstration program is easily available in environments where
96      PCRE has not been installed from source.      PCRE has not been installed from source.
97    
98  15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,  15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
99      libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared      libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
100      library.      library.
101    
102  16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.  16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
103      It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it      It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
104      is not the first non-POSIX option to be added. Clearly some people find      is not the first non-POSIX option to be added. Clearly some people find
105      these options useful.      these options useful.
106    
107  17. If a caller to the POSIX matching function regexec() passes a non-zero  17. If a caller to the POSIX matching function regexec() passes a non-zero
108      value for nmatch with a NULL value for pmatch, the value of      value for nmatch with a NULL value for pmatch, the value of
109      nmatch is forced to zero.      nmatch is forced to zero.
110    
111  18. RunGrepTest did not have a test for the availability of the -u option of  18. RunGrepTest did not have a test for the availability of the -u option of
112      the diff command, as RunTest does. It now checks in the same way as      the diff command, as RunTest does. It now checks in the same way as
113      RunTest, and also checks for the -b option.      RunTest, and also checks for the -b option.
114    
115  19. If an odd number of negated classes containing just a single character  19. If an odd number of negated classes containing just a single character
116      interposed, within parentheses, between a forward reference to a named      interposed, within parentheses, between a forward reference to a named
117      subpattern and the definition of the subpattern, compilation crashed with      subpattern and the definition of the subpattern, compilation crashed with
118      an internal error, complaining that it could not find the referenced      an internal error, complaining that it could not find the referenced
119      subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.      subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
120      [The bug was that it was starting one character too far in when skipping      [The bug was that it was starting one character too far in when skipping
121      over the character class, thus treating the ] as data rather than      over the character class, thus treating the ] as data rather than
122      terminating the class. This meant it could skip too much.]      terminating the class. This meant it could skip too much.]
123    
124  20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the  20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
125      /g option in pcretest when the pattern contains \K, which makes it possible      /g option in pcretest when the pattern contains \K, which makes it possible
126      to have an empty string match not at the start, even when the pattern is      to have an empty string match not at the start, even when the pattern is
127      anchored. Updated pcretest and pcredemo to use this option.      anchored. Updated pcretest and pcredemo to use this option.
128    
129  21. If the maximum number of capturing subpatterns in a recursion was greater  21. If the maximum number of capturing subpatterns in a recursion was greater
130      than the maximum at the outer level, the higher number was returned, but      than the maximum at the outer level, the higher number was returned, but
131      with unset values at the outer level. The correct (outer level) value is      with unset values at the outer level. The correct (outer level) value is
132      now given.      now given.
133    
134  22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of  22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
135      PCRE did not set those parentheses (unlike Perl). I have now found a way to      PCRE did not set those parentheses (unlike Perl). I have now found a way to
136      make it do so. The string so far is captured, making this feature      make it do so. The string so far is captured, making this feature
137      compatible with Perl.      compatible with Perl.
138    
139  23. The tests have been re-organized, adding tests 11 and 12, to make it  23. The tests have been re-organized, adding tests 11 and 12, to make it
140      possible to check the Perl 5.10 features against Perl 5.10.      possible to check the Perl 5.10 features against Perl 5.10.
141    
142  24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine  24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
143      pattern matches a fixed length string. PCRE did not allow this; now it      pattern matches a fixed length string. PCRE did not allow this; now it
144      does. Neither allows recursion.      does. Neither allows recursion.
145    
146  25. I finally figured out how to implement a request to provide the minimum  25. I finally figured out how to implement a request to provide the minimum
147      length of subject string that was needed in order to match a given pattern.      length of subject string that was needed in order to match a given pattern.
148      (It was back references and recursion that I had previously got hung up      (It was back references and recursion that I had previously got hung up
149      on.) This code has now been added to pcre_study(); it finds a lower bound      on.) This code has now been added to pcre_study(); it finds a lower bound
150      to the length of subject needed. It is not necessarily the greatest lower      to the length of subject needed. It is not necessarily the greatest lower
151      bound, but using it to avoid searching strings that are too short does give      bound, but using it to avoid searching strings that are too short does give
152      some useful speed-ups. The value is available to calling programs via      some useful speed-ups. The value is available to calling programs via
153      pcre_fullinfo().      pcre_fullinfo().
154    
155  26. While implementing 25, I discovered to my embarrassment that pcretest had  26. While implementing 25, I discovered to my embarrassment that pcretest had
156      not been passing the result of pcre_study() to pcre_dfa_exec(), so the      not been passing the result of pcre_study() to pcre_dfa_exec(), so the
157      study optimizations had never been tested with that matching function.      study optimizations had never been tested with that matching function.
158      Oops. What is worse, even when it was passed study data, there was a bug in      Oops. What is worse, even when it was passed study data, there was a bug in
159      pcre_dfa_exec() that meant it never actually used it. Double oops. There      pcre_dfa_exec() that meant it never actually used it. Double oops. There
160      were also very few tests of studied patterns with pcre_dfa_exec().      were also very few tests of studied patterns with pcre_dfa_exec().
161    
162    27. If (?| is used to create subpatterns with duplicate numbers, they are now
163        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
164        on the other side of the coin, they are no longer allowed to have different
165        names, because these cannot be distinguished in PCRE, and this has caused
166        confusion. (This is a difference from Perl.)
167    
168    28. When duplicate subpattern names are present (necessarily with different
169        numbers, as required by 27 above), and a test is made by name in a
170        conditional pattern, either for a subpattern having been matched, or for
171        recursion in such a pattern, all the associated numbered subpatterns are
172        tested, and the overall condition is true if the condition is true for any
173        one of them. This is the way Perl works, and is also more like the way
174        testing by number works.
175    
176    
177  Version 7.9 11-Apr-09  Version 7.9 11-Apr-09
178  ---------------------  ---------------------

Legend:
Removed from v.455  
changed lines
  Added in v.471

  ViewVC Help
Powered by ViewVC 1.1.5