Results for regex.test.sh

casebashzshdescription
0pass pass Match is unanchored at both ends
1pass pass Failed match
2pass pass Regex quoted with \ -- preferred in bash
3ok pass Regex quoted with single quotes
details
4ok pass Regex quoted with double quotes
details
5pass pass Fix single quotes by storing in variable
6pass pass Fix single quotes by storing in variable
7ok pass Double quoting pat variable -- again bash doesn't like it.
details
8pass ok Regex with == and not =~ is parse error, different lexer mode required
details
9pass pass Omitting ( )
10pass ok Malformed regex
details
11pass pass Regex with char class
12pass N-I Operators lose meaning in () in regex state (BASH_REGEX_CAHRS)
details
13pass N-I Regex with |
details

21 passed, 5 ok, 2 known unimplemented, 0 known bugs, 0 failed, 0 skipped

Details on runs that didn't PASS

bash3 Regex quoted with single quotes

stdout:
stderr: 
bash4 Regex quoted with double quotes

stdout:
stderr: 
bash7 Double quoting pat variable -- again bash doesn't like it.

stdout:
stderr: 
zsh8 Regex with == and not =~ is parse error, different lexer mode required

stdout:
stderr: 
zsh10 Malformed regex

stdout:
stderr: 
zsh: parse error near `)'
zsh12 Operators lose meaning in () in regex state (BASH_REGEX_CAHRS)

stdout:
stderr: 
zsh: parse error near `<'
zsh13 Regex with |

stdout:
stderr: 
zsh: parse error near `|'