From f6eaa562638a777c6c2e56637898eb90a0f40412 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Tue, 4 Jun 2019 11:43:17 -0600 Subject: Use inRANGE for seeing if node is an ANYOFH type This is easier to read, especially when a third type is added a few commits ahead. --- regcomp.sym | 3 +++ 1 file changed, 3 insertions(+) (limited to 'regcomp.sym') diff --git a/regcomp.sym b/regcomp.sym index e432ae5cd1..4b8885d0b3 100644 --- a/regcomp.sym +++ b/regcomp.sym @@ -62,8 +62,11 @@ ANYOF ANYOF, sv charclass S ; Match character in (or not in) this ANYOFD ANYOF, sv charclass S ; Like ANYOF, but /d is in effect ANYOFL ANYOF, sv charclass S ; Like ANYOF, but /l is in effect ANYOFPOSIXL ANYOF, sv charclass_posixl S ; Like ANYOFL, but matches [[:posix:]] classes + +# Must be sequential ANYOFH ANYOF, sv 1 S ; Like ANYOF, but only has "High" matches, none in the bitmap; ANYOFHb ANYOF, sv 1 S ; Like ANYOFH, but all matches share the same UTF-8 start byte, given in the flags field + ANYOFM ANYOFM byte 1 S ; Like ANYOF, but matches an invariant byte as determined by the mask and arg NANYOFM ANYOFM byte 1 S ; complement of ANYOFM -- cgit v1.2.1