Searched refs:EXACTFUP (Results 1 – 8 of 8) sorted by relevance
3 EXACTFUP # Z added by devel/scanprov
594 case EXACTFUP: in Perl_make_trie() 700 || OP(noper) == EXACTFUP)))) in Perl_make_trie() 713 if (OP( noper ) == EXACTFUP) { in Perl_make_trie() 926 || OP(noper) == EXACTFUP)))) in Perl_make_trie() 1160 || OP(noper) == EXACTFUP)))) in Perl_make_trie()
651 #define EXACTFUP 49 /* 0x31 Like EXACT, but match macro
953 * that hopefully generally solves the problem generates an EXACTFUP node in Perl_is_ssc_worth_it() 974 * EXACTFUP, indicating it is problematic, and needs careful handling. in Perl_ssc_finalize() 982 * EXACTFUP has been created as a grab-bag for (hopefully uncommon) in Perl_ssc_finalize() 988 * regex matching. By using an EXACTFUP node when it is not possible to in Perl_ssc_finalize() 993 * is because its fold requires UTF-8 to represent. Thus EXACTFUP nodes in Perl_ssc_finalize() 1439 OP(scan) = EXACTFUP; in Perl_join_exact() 1906 EXACTFUP | EXACTFU in Perl_study_chunk() 1919 || EXACTFUP == (X) ) \ in Perl_study_chunk()
171 EXACTFUP EXACT, str ; Like EXACT, but match using /iu rules; (string not UTF-8, folded ex…
7187 case EXACTFUP: /* /foo/iu, and something is problematic in in S_regmatch() 7233 || state_num == EXACTFUP in S_regmatch()
7433 node_type = EXACTFUP; in S_regatom() 11702 { /* EXACTFUP is a special node for this character */ in S_optimize_regclass() 11705 : EXACTFUP; in S_optimize_regclass()
700 EXACTFUP str Like EXACT, but match using /iu rules;