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
Rakudo hangs or crashes on ranges of large \x character specifications in a regex #1112
Comments
From @masak<masak> rakudo: / <[\x10000..\xEFFFF]> /; say "alive" |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/t/spec/S05-metasyntax/charset.t |
The RT System itself - Status changed from 'new' to 'open' |
From @bbkr[16:21] <bbkr> rakudo: / <[\x10000..\xEFFFF]> /; say "alive" # testing 67122 |
From @bbkrNOM still broken (no output) bbkr:nom bbkr$ ./perl6 -e 'say "\x[10001]" ~~ /<[\x10000..\xEFFFF]>/' bbkr:nom bbkr$ |
From @bbkrOn 2012.04: $ ./perl6 -e 'say "\x[10001]" ~~ /<[\x10000..\xEFFFF]>/' |
From @cokeOn Fri Apr 20 02:54:24 2012, bbkr wrote:
Isn't this correct behavior now? -- |
From @FROGGSOn all platforms it built a string with every codepoint of the given range, and when :i was in effect it built that string with uppercase and lowercase codepoint. This is probably fixed for MoarVM (branch charrange in MoarVM and nqp). About that invalid character message: This also popped up when an invalid codepoint was withing that range, since every codepoint of that range was turned into a char and concatenated to a string. The changed code only would complain if the lower and upper bounds were invalid codepoints. Hopefully the charrange branches can be merged this weekend. |
From @FROGGSFixed in Raku/nqp@a0842ef500 |
@FROGGS - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#67122 (status was 'resolved')
Searchable as RT67122$
The text was updated successfully, but these errors were encountered: