[perl #56604] Not all error messages should include a stack trace

2010-03-31 Thread Carl Mäsak via RT
I'd just like to report that the stacktraces in Rakudo are back to being insanely long. I think they're even longer than when people were complaining about them being far too long last time, and someone fixed it. and are also back to be totally useless yes. * masak submits rakudobug Here's

[perl #56604] Not all error messages should include a stack trace

2009-05-15 Thread jn...@jnthn.net via RT
On Fri Jul 04 01:39:12 2008, mor...@casella.verplant.org wrote: > Error messages caused by programmer's mistakes shouldn't include stack > traces. > > Rakudo r29047: > ../../parrot perl6.pbc -e 'my Int $x; $x = "str"' > Type check failed > current instr.: 'parrot;Perl6Object;infix:=' pc 59 (src/ge

[perl #56604] Not all error messages should include a stack trace

2008-07-04 Thread via RT
# New Ticket Created by Moritz Lenz # Please include the string: [perl #56604] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=56604 > Error messages caused by programmer's mistakes shouldn't include stack traces. Rakudo r2