[Pcre-svn] [524] code/trunk: Fix comment describing returns …

Top Page
Delete this message
Author: Subversion repository
Date:  
To: pcre-svn
Subject: [Pcre-svn] [524] code/trunk: Fix comment describing returns from find_fixedlength().
Revision: 524
          http://www.exim.org/viewvc/pcre2?view=rev&revision=524
Author:   ph10
Date:     2016-06-14 16:12:07 +0100 (Tue, 14 Jun 2016)
Log Message:
-----------
Fix comment describing returns from find_fixedlength().


Modified Paths:
--------------
    code/trunk/ChangeLog
    code/trunk/src/pcre2_compile.c


Modified: code/trunk/ChangeLog
===================================================================
--- code/trunk/ChangeLog    2016-06-14 09:19:24 UTC (rev 523)
+++ code/trunk/ChangeLog    2016-06-14 15:12:07 UTC (rev 524)
@@ -132,7 +132,9 @@


33. Fix typo that gave a compiler error when JIT not supported.

+34. Fix comment describing the returns from find_fixedlength().

+
Version 10.21 12-January-2016
-----------------------------


Modified: code/trunk/src/pcre2_compile.c
===================================================================
--- code/trunk/src/pcre2_compile.c    2016-06-14 09:19:24 UTC (rev 523)
+++ code/trunk/src/pcre2_compile.c    2016-06-14 15:12:07 UTC (rev 524)
@@ -879,9 +879,10 @@
 Returns:   if non-negative, the fixed length,
              or -1 if an OP_RECURSE item was encountered and atend is FALSE
              or -2 if there is no fixed length,
-             or -3 if \C was encountered (in UTF-8 mode only)
-             or -4 length is too long
-             or -5 if an unknown opcode was encountered (internal error)
+             or -3 if \C was encountered (in UTF mode only)
+             or -4 if length is too long
+             or -5 if regex is too complicated 
+             or -6 if an unknown opcode was encountered (internal error)
 */


 #define FFL_LATER           (-1)
@@ -1116,7 +1117,7 @@
     cc++;
     break;


-    /* The single-byte matcher isn't allowed. This only happens in UTF-8 mode;
+    /* The single-byte matcher isn't allowed. This only happens in UTF mode;
     otherwise \C is coded as OP_ALLANY. */


     case OP_ANYBYTE: