Hi Derek-

That has been on my list to fix for a while now.  I'll add it to the final
push for 2.4.10 for pdl2.  In the meantime, here is a modified execute
sub for your Devel/REPL.pm file.  Just replace the existing execute
code with the following (it is line 132 in my version):

sub execute {
  my ($self, $to_exec, @args) = @_;
  my @ret = eval { $to_exec->(@args) };
  return $self->error_return("Runtime error", clean_error_string($@)) if $@;
  return @ret;
}

sub clean_error_string {
   my $bigerr = $_[0];
   $bigerr =~ s/^\s+Devel::REPL.*$//ms;
   $bigerr =~ s/^\s+Class::MOP.*$//ms;
   $bigerr =~ s/^\s+Lexical::Persistence.*$//ms;
   $bigerr =~ s/^\s+main::.*$//ms;
   $bigerr =~ s/^\s+eval {.*$//ms;
   $bigerr =~ s/^\s+PDL::Core::barf.*$//ms;
   return $bigerr;
 }


Now that I have the code working, I'll get it added in a cleaner way
for the upcoming release.  Thanks for the push....

Enjoy!
Chris


On Fri, Dec 16, 2011 at 1:22 PM, Derek Lamb <[email protected]> wrote:
> I've been using the pdl2 shell because perldl isn't telling me when I have a 
> syntax error, etc.  But pdl2 goes too far the other way, giving me 36 lines 
> of error messages whenever I do something stupid like zeroes(3) + zeroes(4).  
> Probably only 3 of those lines are actually needed--I don't need a full stack 
> trace through Lexical::Persistence, Devel::REPL, Moose, etc.  Is there a way 
> to tone it down a bit?
>
> Derek

_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to