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
Not all error messages should include a stack trace #153
Comments
From @moritzError messages caused by programmer's mistakes shouldn't include stack Rakudo r29047: IMHO the stack trace is mostly unnecessary line noise, and shouldn't be Typical examples of error messages are "Type check failed", parse It might be a bit too early for this change because atm most users are Cheers, -- |
From gp@zimt.uni-siegen.deHello! There is a problem with the function "die" in Rakudo. I tried the function "die" under Windows and Linux. Under both OS it Gerd Pokorra [gz016@pgerd parrot]$ ./parrot languages/perl6/perl6.pbc -e die current instr.: 'die' pc 13123 (src/gen_builtins.pir:8122) [gz016@pgerd parrot]$ |
From @masakpgerd (>):
Looks perfectly normal to me. Are you concerned because you got a |
The RT System itself - Status changed from 'new' to 'open' |
From gp@zimt.uni-siegen.de
Yes, that is the reason why I am concerned. To see a stacktrace is not Gerd Pokorra |
From @jnthnOn Fri Jul 04 01:39:12 2008, moritz@casella.verplant.org wrote:
All stack trace into the compiler guts is now not shown at all now, and Type mismatch in assignment; expected something matching type Int but Thanks, Jonathan |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
From @masak<masak> I'd just like to report that the stacktraces in Rakudo are back Here's an example: $ perl6 lib/November/CGI.pm That's a record in insanity. :( |
@masak - Status changed from 'resolved' to 'open' |
From @moritzWe now have nice, Perl 6-level-only backtraces in Rakudo, so I'm closing |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#56604 (status was 'resolved')
Searchable as RT56604$
The text was updated successfully, but these errors were encountered: