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

Diff of /code/trunk/ChangeLog

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

revision 459 by ph10, Sun Oct 4 09:21:39 2009 UTC revision 512 by ph10, Tue Mar 30 11:11:52 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.00 ??-???-??  Version 8.03 26-Mar-2010
5    ------------------------
6    
7    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
8        THEN.
9    
10    2.  (*ACCEPT) was not working when inside an atomic group.
11    
12    
13    Version 8.02 19-Mar-2010
14    ------------------------
15    
16    1.  The Unicode data tables have been updated to Unicode 5.2.0.
17    
18    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
19        configured.
20    
21    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
22        original author of that file, following a query about its status.
23    
24    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
25        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
26    
27    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
28        quantifier applied to a forward-referencing subroutine call, could compile
29        incorrect code or give the error "internal error: previously-checked
30        referenced subpattern not found".
31    
32    6.  Both MS Visual Studio and Symbian OS have problems with initializing
33        variables to point to external functions. For these systems, therefore,
34        pcre_malloc etc. are now initialized to local functions that call the
35        relevant global functions.
36    
37    7.  There were two entries missing in the vectors called coptable and poptable
38        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
39        I've fixed the data, and added a kludgy way of testing at compile time that
40        the lengths are correct (equal to the number of opcodes).
41    
42    8.  Following on from 7, I added a similar kludge to check the length of the
43        eint vector in pcreposix.c.
44    
45    9.  Error texts for pcre_compile() are held as one long string to avoid too
46        much relocation at load time. To find a text, the string is searched,
47        counting zeros. There was no check for running off the end of the string,
48        which could happen if a new error number was added without updating the
49        string.
50    
51    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
52    
53    11. \K was not working if it appeared in an atomic group or in a group that
54        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
55        \K is "not well defined" if used in an assertion. PCRE now accepts it if
56        the assertion is positive, but not if it is negative.
57    
58    12. Change 11 fortuitously reduced the size of the stack frame used in the
59        "match()" function of pcre_exec.c by one pointer. Forthcoming
60        implementation of support for (*MARK) will need an extra pointer on the
61        stack; I have reserved it now, so that the stack frame size does not
62        decrease.
63    
64    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
65        item in branch that calls a recursion is a subroutine call - as in the
66        second branch in the above example - was incorrectly given the compile-
67        time error "recursive call could loop indefinitely" because pcre_compile()
68        was not correctly checking the subroutine for matching a non-empty string.
69    
70    14. The checks for overrunning compiling workspace could trigger after an
71        overrun had occurred. This is a "should never occur" error, but it can be
72        triggered by pathological patterns such as hundreds of nested parentheses.
73        The checks now trigger 100 bytes before the end of the workspace.
74    
75    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
76    
77    
78    Version 8.01 19-Jan-2010
79    ------------------------
80    
81    1.  If a pattern contained a conditional subpattern with only one branch (in
82        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
83        computed the wrong minimum data length (which is of course zero for such
84        subpatterns). This could cause incorrect "no match" results.
85    
86    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
87        the pattern is reset in the first branch, pcre_compile() failed with
88        "internal error: code overflow at offset...". This happened only when
89        the reset was to the original external option setting. (An optimization
90        abstracts leading options settings into an external setting, which was the
91        cause of this.)
92    
93    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
94        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
95        assertion pattern did not match (meaning that the assertion was true), it
96        was incorrectly treated as false if the SKIP had been reached during the
97        matching. This also applied to assertions used as conditions.
98    
99    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
100        assertion subpattern, including such a pattern used as a condition,
101        unpredictable results occurred, instead of the error return
102        PCRE_ERROR_DFA_UITEM.
103    
104    5.  The C++ GlobalReplace function was not working like Perl for the special
105        situation when an empty string is matched. It now does the fancy magic
106        stuff that is necessary.
107    
108    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
109        removed. (These were left over from very, very early versions of PCRE.)
110    
111    7.  Some cosmetic changes to the code to make life easier when compiling it
112        as part of something else:
113    
114        (a) Change DEBUG to PCRE_DEBUG.
115    
116        (b) In pcre_compile(), rename the member of the "branch_chain" structure
117            called "current" as "current_branch", to prevent a collision with the
118            Linux macro when compiled as a kernel module.
119    
120        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
121            prevent a collision with the Linux macro when compiled as a kernel
122            module.
123    
124    8.  In pcre_compile() there are some checks for integer overflows that used to
125        cast potentially large values to (double). This has been changed to that
126        when building, a check for int64_t is made, and if it is found, it is used
127        instead, thus avoiding the use of floating point arithmetic. (There is no
128        other use of FP in PCRE.) If int64_t is not found, the fallback is to
129        double.
130    
131    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
132        2005 (difference between two addresses compared to an unsigned value).
133    
134    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
135        custom one, because of the following reported problem in Windows:
136    
137          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
138              under Win32.
139          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
140              therefore missing the function definition.
141          - The compiler thus generates a "C" signature for the test function.
142          - The linker fails to find the "C" function.
143          - PCRE fails to configure if asked to do so against libbz2.
144    
145    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
146        messages were output:
147    
148          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
149          rerunning libtoolize, to keep the correct libtool macros in-tree.
150          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
151    
152        I have done both of these things.
153    
154    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
155        most of the time, it *can* run out if it is given a pattern that contains a
156        runaway infinite recursion. I updated the discussion in the pcrestack man
157        page.
158    
159    13. Now that we have gone to the x.xx style of version numbers, the minor
160        version may start with zero. Using 08 or 09 is a bad idea because users
161        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
162        interpreted as invalid octal numbers. I've updated the previous comment in
163        configure.ac, and also added a check that gives an error if 08 or 09 are
164        used.
165    
166    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
167        causing partial matching to fail when the end of the subject matched \W
168        in a UTF-8 pattern where \W was quantified with a minimum of 3.
169    
170    15. There were some discrepancies between the declarations in pcre_internal.h
171        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
172        their definitions. The declarations used "const uschar *" and the
173        definitions used USPTR. Even though USPTR is normally defined as "const
174        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
175        reported that: "This difference in casting confuses some C++ compilers, for
176        example, SunCC recognizes above declarations as different functions and
177        generates broken code for hbpcre." I have changed the declarations to use
178        USPTR.
179    
180    16. GNU libtool is named differently on some systems. The autogen.sh script now
181        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
182        (FreeBSD).
183    
184    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
185        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
186        comment: "Figure out how to create a longlong from a string: strtoll and
187        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
188        instance, but it only takes 2 args instead of 3!"
189    
190    18. A subtle bug concerned with back references has been fixed by a change of
191        specification, with a corresponding code fix. A pattern such as
192        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
193        refers, was giving matches when it shouldn't. For example, xa=xaaa would
194        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
195        same bug. Such groups have to be quantified to be useful, or contained
196        inside another quantified group. (If there's no repetition, the reference
197        can never match.) The problem arises because, having left the group and
198        moved on to the rest of the pattern, a later failure that backtracks into
199        the group uses the captured value from the final iteration of the group
200        rather than the correct earlier one. I have fixed this in PCRE by forcing
201        any group that contains a reference to itself to be an atomic group; that
202        is, there cannot be any backtracking into it once it has completed. This is
203        similar to recursive and subroutine calls.
204    
205    
206    Version 8.00 19-Oct-09
207  ----------------------  ----------------------
208    
209  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
210      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
211      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
212      error.      error.
213    
214  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,
215      "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
216      in a Windows environment.      in a Windows environment.
217    
218  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
219      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
220      --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
221      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
222      prints the file name in this circumstance, but including the count seems      prints the file name in this circumstance, but including the count seems
223      more useful - otherwise, why use --count?) Also ensured that the      more useful - otherwise, why use --count?) Also ensured that the
224      combination -clh just lists non-zero counts, with no names.      combination -clh just lists non-zero counts, with no names.
225    
226  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
227      --fixed_strings instead of --fixed-strings. This is an incompatible change,      --fixed_strings instead of --fixed-strings. This is an incompatible change,
228      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
229      the old behaviour.      the old behaviour.
230    
231  5.  The command line items --regex=pattern and --regexp=pattern were not  5.  The command line items --regex=pattern and --regexp=pattern were not
232      recognized by pcregrep, which required --regex pattern or --regexp pattern      recognized by pcregrep, which required --regex pattern or --regexp pattern
233      (with a space rather than an '='). The man page documented the '=' forms,      (with a space rather than an '='). The man page documented the '=' forms,
234      which are compatible with GNU grep; these now work.      which are compatible with GNU grep; these now work.
235    
236  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
237      libpcre.pc and libpcrecpp.pc. The omission has been rectified.      libpcre.pc and libpcrecpp.pc. The omission has been rectified.
238    
239  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
240      when UCP support is not needed, by modifying the Python script that      when UCP support is not needed, by modifying the Python script that
241      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
242      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
243      unwanted data. My guess is that the person linked everything into his      unwanted data. My guess is that the person linked everything into his
244      program rather than using a library. Anyway, it does no harm.      program rather than using a library. Anyway, it does no harm.
245    
246  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
247      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
248      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
249      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
250      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
251      result.      result.
252    
253  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
254      requested for pcre_exec() have been removed. All patterns can now be      requested for pcre_exec() have been removed. All patterns can now be
255      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
256      slots in the offset vector, the offset of the earliest inspected character      slots in the offset vector, the offset of the earliest inspected character
257      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
258      PCRE_ERROR_PARTIAL is returned.      PCRE_ERROR_PARTIAL is returned.
259    
260  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
261      synonymous with PCRE_PARTIAL, for backwards compatibility, and      synonymous with PCRE_PARTIAL, for backwards compatibility, and
262      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,
263      and may be more useful for multi-segment matching, especially with      and may be more useful for multi-segment matching.
264      pcre_exec().  
265    11. Partial matching with pcre_exec() is now more intuitive. A partial match
266  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
267      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
268      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
269      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
270      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
271      case of pcre_dfa_exec(), "no match" is given if every matching path for the      final character ended with (*FAIL).
272      final character ended with (*FAIL).  
   
273  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
274      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
275      earlier partial match, unless partial matching was again requested. For      earlier partial match, unless partial matching was again requested. For
276      example, with the pattern /dog.(body)?/, the "must contain" character is      example, with the pattern /dog.(body)?/, the "must contain" character is
277      "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
278      "sbody" failed. This bug has been fixed.      "sbody" failed. This bug has been fixed.
279    
280  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
281      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
282      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
283      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
284      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
285      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.
286    
287  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,
288      so that the demonstration program is easily available in environments where      so that the demonstration program is easily available in environments where
289      PCRE has not been installed from source.      PCRE has not been installed from source.
290    
291  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,
292      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
293      library.      library.
294    
295  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.
296      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
297      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
298      these options useful.      these options useful.
299    
300  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
301      value for nmatch with a NULL value for pmatch, the value of      value for nmatch with a NULL value for pmatch, the value of
302      nmatch is forced to zero.      nmatch is forced to zero.
303    
304  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
305      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
306      RunTest, and also checks for the -b option.      RunTest, and also checks for the -b option.
307    
308  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
309      interposed, within parentheses, between a forward reference to a named      interposed, within parentheses, between a forward reference to a named
310      subpattern and the definition of the subpattern, compilation crashed with      subpattern and the definition of the subpattern, compilation crashed with
311      an internal error, complaining that it could not find the referenced      an internal error, complaining that it could not find the referenced
312      subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.      subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
313      [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
314      over the character class, thus treating the ] as data rather than      over the character class, thus treating the ] as data rather than
315      terminating the class. This meant it could skip too much.]      terminating the class. This meant it could skip too much.]
316    
317  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
318      /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
319      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
320      anchored. Updated pcretest and pcredemo to use this option.      anchored. Updated pcretest and pcredemo to use this option.
321    
322  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
323      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
324      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
325      now given.      now given.
326    
327  22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of  22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
328      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
329      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
330      compatible with Perl.      compatible with Perl.
331    
332  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
333      possible to check the Perl 5.10 features against Perl 5.10.      possible to check the Perl 5.10 features against Perl 5.10.
334    
335  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
336      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
337      does. Neither allows recursion.      does. Neither allows recursion.
338    
339  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
340      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.
341      (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
342      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
343      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
344      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
345      some useful speed-ups. The value is available to calling programs via      some useful speed-ups. The value is available to calling programs via
346      pcre_fullinfo().      pcre_fullinfo().
347    
348  26. While implementing 25, I discovered to my embarrassment that pcretest had  26. While implementing 25, I discovered to my embarrassment that pcretest had
349      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
350      study optimizations had never been tested with that matching function.      study optimizations had never been tested with that matching function.
351      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
352      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
353      were also very few tests of studied patterns with pcre_dfa_exec().      were also very few tests of studied patterns with pcre_dfa_exec().
354    
355  27. If (?| is used to create subpatterns with duplicate numbers, they are now  27. If (?| is used to create subpatterns with duplicate numbers, they are now
356      allowed to have the same name, even if PCRE_DUPNAMES is not set. However,      allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
357      on the other side of the coin, they are no longer allowed to have different      on the other side of the coin, they are no longer allowed to have different
358      names, because these cannot be distinguished in PCRE, and this has caused      names, because these cannot be distinguished in PCRE, and this has caused
359      confusion. (This is a difference from Perl.)      confusion. (This is a difference from Perl.)
360    
361  28. When duplicate subpattern names are present (necessarily with different  28. When duplicate subpattern names are present (necessarily with different
362      numbers, as required by 27 above), and a test is made by name in a      numbers, as required by 27 above), and a test is made by name in a
363      conditional pattern, either for a subpattern having been matched, or for      conditional pattern, either for a subpattern having been matched, or for
364      recursion in such a pattern, all the associated numbered subpatterns are      recursion in such a pattern, all the associated numbered subpatterns are
365      tested, and the overall condition is true if the condition is true for any      tested, and the overall condition is true if the condition is true for any
366      one of them. This is the way Perl works, and is also more like the way      one of them. This is the way Perl works, and is also more like the way
367      testing by number works.      testing by number works.
368    
369    
370  Version 7.9 11-Apr-09  Version 7.9 11-Apr-09
371  ---------------------  ---------------------

Legend:
Removed from v.459  
changed lines
  Added in v.512

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12