Skip Menu |

This queue is for tickets about the Unexpected CPAN distribution.

Report information
The Basics
Id: 86121
Status: resolved
Priority: 0/
Queue: Unexpected

People
Owner: Support [...] RoxSoft.co.uk
Requestors: mst [...] shadowcat.co.uk
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Why not using Throwable directly?
Date: Thu, 13 Jun 2013 20:52:38 +0000
To: bugs-Unexpected [...] rt.cpan.org
From: Matt S Trout <mst [...] shadowcat.co.uk>
The version of the stack trace filter you're using seems to be the one I wrote in the process of getting Throwable ported to Moo - so it seems odd to have lifted that code rather than simply depending on it. Not that I'm assuming you don't have a good reason - just it seems like you could use StackTrace::Auto directly at a quick glance so it's maybe worth documenting why you didn't :) -- Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ Email me now on mst (at) shadowcat.co.uk and let's chat about how our CPAN commercial support, training and consultancy packages could help your team.
Fixed in v0.3.11 L<Throwable> did not let me use the stack trace filter directly, it's wrapped inside an attribute constructor. There was nothing else in L<Throwable> that would not have been overridden