Results for ysh-regex-bytes-chars.test.sh

status	osh
pass	14
FAIL	1
total	15

case	osh	description
0	pass	Match tab character with [\t]
1	pass	Match newline with [\n]
2	pass	ERE: 'dot' matches newline
3	pass	ERE: 'dot' matches code point represented with multiple bytes (mu = 0xce 0xbe)
4	pass	$'\xff' is disallowed in Eggex, because it's disallowed in YSH
5	pass	Match low ASCII with [\x01]
6	pass	Match low ASCII with \u{7f} - translates to valid ERE
7	pass	non-ASCII bytes must be singleton terms, e.g. b'\y7f\yff' is disallowed
8	pass	Bytes are denoted \y01 in Eggex char classes (not \x01)
9	pass	NUL byte can be expressed in Eggex, but not in ERE
10	pass	High bytes 0x80 0xff usually can't be matched - Eggex is UTF-8
11	pass	High bytes 0x80 0xff can be matched with plain ERE and LC_ALL=C
12	pass	Code points like \u{3bc} can be matched
13	pass	Code point ranges work in limited cases
14	FAIL	Max code point is disallowed at parse time
	details

14 passed, 0 OK, 0 not implemented, 0 BUG, 1 failed, 0 timeouts, 0 cases skipped
1 failed under osh

Details on runs that didn't PASS

osh

14 Max code point is disallowed at parse time

[osh stdout] Expected '(Bool) false\n(Bool) true\n\n(Bool) false\n(Bool) true\n' Got '<Eggex>\n<Eggex>\n'

stdout:

<Eggex>
<Eggex>

stderr: