New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
empty groups in regexes should throw "Null pattern not allowed at" errors #1462
Comments
From @masakThis be Rakudo db84bc on Parrot r43174. $ perl6 -e '/[ ]/' $ perl6 -e '/( )/' Really a PGE bug, but it affects Rakudo. (Cause: The .perl6exp traversal nulls the PGE::Exp::WS node when it |
From @moritzNow does nothing, but should complain that "Null pattern not allowed" |
The RT System itself - Status changed from 'new' to 'open' |
From @bbkrrelated issue to also put in test suite (Moscow build): perl6 -e 'say /[]/.WHAT' |
From @bbkrNOM: still no warning, good point is that it does not divide by zero anymore bbkr:nom bbkr$ ./perl6 -e '/[ ]/' |
From @bbkrIn all those cases STD returns "Null pattern not allowed" error. 2012.10 behavior is incorrect in all of those ceses: bbkrimac:~ ppabian$ perl6 -e '/ [] /' bbkrimac:~ ppabian$ perl6 -e '/ () /' bbkrimac:~ ppabian$ perl6 -e '/ [ ] /.WHAT.say' |
From @usev6Now all of these die with X::Syntax::Regex::NullRegex. There are tests in S32-exceptions/misc.t. |
1 similar comment
From @usev6Now all of these die with X::Syntax::Regex::NullRegex. There are tests in S32-exceptions/misc.t. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#71800 (status was 'resolved')
Searchable as RT71800$
The text was updated successfully, but these errors were encountered: