Dear monks,

I've got another question regarding the same topic of "handling errors" and your help would be really appreciated. This time I'm thinking about the best way of passing the stacktrace from the deepest bottom to the top caller.

I'd better explain my question by some example. Let's assume, we have some some classes and some methods:

package ClassB;

sub method_y {
  if($something_has_gone_wrong) {
    confess("Something has gone wrong!");
  }
}



package ClassA;

sub method_x {
  try {
    $class_b_object->method_y;
  } catch {
    confess($_);
  }
}



package main;

try {
  $class_a_object->method_x
} catch {
  $log->error($_);
}
[download]

I need to have a stack-trace to be delivered to the main module, but, obviously, when something goes wrong, I have 2 stack-traces instead of 1 (one is from ClassA::method_x and another - from ClassB::method_y), which is really ugly. I need only the stack-trace from the bottom, but I don't want to decide whenever I shall die() or confess() in every catch-block.

As a solution, I imagine something like that:

package Error;

sub new {
  my($self, $class, $parameter)
  if(ref($parameter) eq 'Error') {
    return($parameter);
  } else {
    bless($self, $class);
    $self->stacktrace(Devel::StackTrace->new->as_string);
    $self->message($parameter);
    $self->timestamp(time);
    $self->whatever("Blah-blah");
    return($self);
  }
}


package ClassB;

sub method_y {
  if($something_has_gone_wrong) {
    die(Error->new("Something has gone wrong"));
  }
}



package ClassA;

sub method_x {
  try {
    $class_b_object->method_y
  } catch {
    die(Error->new($_));
  }
}



package main;

try {
  $class_a_object->method_x;
} catch {
  if(ref($_) eq Error) {
    print(SOMEWHERE "The worst has happened at " . $_->timestamp . "\n
+");
    print(SOMEWHERE $_->message . "\n");
    print(SOMEWHERE $_->backtrace . "\n");
  } else {
    $log->error($_);
  }
}
[download]

So, the deepest subroutine (ClassB::method_y) dies and creates a new Error-object, which has a stacktrace and everything else we need. This object is being passed as $_ to the constructor of another Error-object inside of ClassA::method_x, but it won't add anything to this object, because it will understand that it have got an Error-object, not just an error-message. Then the main module will do something with that object.

I'm not sure about this idea, so I'll be glad to know your opinion on that.

Thank you very much!

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.