Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Useful errors for Moose and MooseX::Declare

Tags:

perl

moose

Moose is very lovely, but sometimes simple typos can cause hair-raisingly exciting long stacktraces with, from my point of view, zero useful content.

So, are there any tools to interpret this exploding into something helpful?

In particular for classes using plain Moose, Moose+MooseX::Method::Signatures, and MooseX::Declare.

The tools only need to be helpful while developing to catch those typo or thinko problems that make things just not work.

=========================

Following suggestion below, I'm using this not-quite-a-module-yet which is reducing my headaches a little, more ideas welcome, though:

package MooseX::QuietCarping;
# Not actually a Moose thing, but helpful for Moose.
# calm Moose-internal stacktraces down a little
use Carp;

my %retain = ();
sub import {
    my $class = shift;
    $retain{$_}++ for @_;
}

CHECK {
    for (sort keys %INC) {
    s{\.pm$}{};
    s{[/\\]}{::}g; # CROSS PLATFORM MY ARSE
    next if $retain{$_};
    $Carp::Internal{$_}++ if /^(?:Class::MOP|Moose|MooseX)\b/
    }
    %retain = (); # don't need this no more
}

1;
like image 902
Alex Avatar asked May 29 '11 23:05

Alex


1 Answers

One way I experimented with some time ago is putting Moose related classes into %Carp::Internal hash, something like this:

$Carp::Internal{$_}++ for qw{
    Class::MOP
    Class::MOP::Attribute
    Class::MOP::Class
    ...
};

Such classes will be skipped in stack trace, making it more compact and emphasizing your own code.

You can find them by traversing %INC variable:

package Dummy;
use Moose;
use MooseX::Declare;
# use ....;

for (sort keys %INC) {
    s{\.pm$}{};
    s{/}{::}g;
    print "$_\n" if /^(Class::MOP|Moose|MooseX)\b/;
}
like image 96
bvr Avatar answered Oct 04 '22 15:10

bvr