[bug] /[\x{0}-X]/i doesn't match properly when UTF-16/32 is used.

This bug occurs when a code range already includes \x{0} and adding a new code range to it. We must also care about 0xffffffff.
k-takata · Nov 16, 2011 · b5fec0b · b5fec0b
1 parent 13a5849
commit b5fec0b
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/regparse.c b/regparse.c
@@ -1741,9 +1741,10 @@ add_code_range_to_buf(BBuf** pbuf, OnigCodePoint from, OnigCodePoint to)
       bound = x;
   }
 
-  for (high = low, bound = n; high < bound; ) {
+  high = (to == ~((OnigCodePoint )0)) ? n : low;
+  for (bound = n; high < bound; ) {
     x = (high + bound) >> 1;
-    if (to >= data[x*2] - 1)
+    if (to + 1 >= data[x*2])
       high = x + 1;
     else
       bound = x;