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
Exception subclasses without a message method aren't handled well by the top level exception handler #4405
Comments
From @hoelzroFor example: $ perl6 -e 'class CustomException is Exception {}; CustomException.new.throw' This results in the following error output: Unhandled exception: concatenate requires a concrete string, but got null Adding a message method to CustomException causes the exception handler to print out more normal-looking output. |
From @jnthnOn Wed Jul 15 20:57:03 2015, rob@hoelz.ro wrote:
It's actually the gist method on such an exception that is rather busted. Fixed it so now you get: $ perl6-m -e "class CustomException is Exception {}; CustomException.new.throw" Which is somewhat more informative. :-) Added tests in S32-exceptions/misc.t. |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125620 (status was 'resolved')
Searchable as RT125620$
The text was updated successfully, but these errors were encountered: