From c10713345de01e923289c756b4a97e41147dac26 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Thu, 3 Sep 2015 10:27:39 -0600 Subject: regcomp.h: SSC no longer has to be strict ANYOF Since commit a0bd1a30d379f2625c307657d63fc50173d7a56d, a synthetic start class node can be just an ANYOF-type node. I don't think this causes a bug, just misses a potential optimisation. --- regcomp.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'regcomp.h') diff --git a/regcomp.h b/regcomp.h index 0f2617b022..f338b35967 100644 --- a/regcomp.h +++ b/regcomp.h @@ -261,7 +261,7 @@ struct regnode_ssc { #define set_ANYOF_SYNTHETIC(n) STMT_START{ OP(n) = ANYOF; \ NEXT_OFF(n) = 1; \ } STMT_END -#define is_ANYOF_SYNTHETIC(n) (OP(n) == ANYOF && NEXT_OFF(n) == 1) +#define is_ANYOF_SYNTHETIC(n) (PL_regkind[OP(n)] == ANYOF && NEXT_OFF(n) == 1) /* XXX fix this description. Impose a limit of REG_INFTY on various pattern matching operations -- cgit v1.2.1