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
java.lang.NullPointerException from incomplete regex on the REPL #3254
Comments
From @moritzmoritz@pat:~/p6/json>perl6-j
at perl6.main(gen/jvm/main.nqp) needless to say, this is not the level of error reporting that we aspire to. |
From @usev6This no longer gives a NullPointerException: $ perl6-j
$ perl6-j --version Is this closeable or do we need a test for the rakudo.jvm REPL? |
1 similar comment
From @usev6This no longer gives a NullPointerException: $ perl6-j
$ perl6-j --version Is this closeable or do we need a test for the rakudo.jvm REPL? |
@usev6 - Status changed from 'new' to 'open' |
As described in Raku/old-issue-tracker#3254 the following evaluation used to fail badly in the REPL (on the JVM backend) a couple of years ago: 'asa' ~~ /:s ^a* % java.lang.NullPointerException java.lang.NullPointerException [...] Exception in thread "main" org.perl6.nqp.runtime.UnwindException [...] The problem has been fixed a long time ago (the exact commit is unknown) and the incomplete regex results in a sane error message, but we didn't have a regression test, yet.
As described in Raku/old-issue-tracker#3254 the following evaluation used to fail badly in the REPL (on the JVM backend) a couple of years ago: 'asa' ~~ /:s ^a* % java.lang.NullPointerException java.lang.NullPointerException [...] Exception in thread "main" org.perl6.nqp.runtime.UnwindException [...] The problem has been fixed a long time ago (the exact commit is unknown) and the incomplete regex results in a sane error message, but we didn't have a regression test, yet.
Test added with rakudo/rakudo@cbf12d22e1. I'm closing this issue. |
Migrated from rt.perl.org#120379 (status was 'open')
Searchable as RT120379$
The text was updated successfully, but these errors were encountered: