From 167e651f9a7445679df315ec089c3adf7b383552 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sat, 31 Dec 2011 21:48:53 -0700 Subject: regcomp.c: remove invalid assertion It turns out that a node can be an EXACTFU_SS upon entry to join_exact() contrary to what I thought. One way, anyway, for this to happen, is through the (?&NAME) construct which copies a pre-existing node. --- regcomp.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/regcomp.c b/regcomp.c index b408ec099c..021169d4f3 100644 --- a/regcomp.c +++ b/regcomp.c @@ -2631,10 +2631,9 @@ S_join_exact(pTHX_ RExC_state_t *pRExC_state, regnode *scan, IV *min_change, boo #endif DEBUG_PEEP("join",scan,depth); - /* These opcode should only be on output from this routine, never on input + /* This opcode should only be on output from this routine, never on input */ assert(OP(scan) != EXACTFU_NO_TRIE); - assert(OP(scan) != EXACTFU_SS); /* Look through the subsequent nodes in the chain. Skip NOTHING, merge * EXACT ones that are mergeable to the current one. */ -- cgit v1.2.1