comment on

Yes, that is how it works (there's no point in catching the exception inside set_number because set_number is using the exception to signal failure to calling code).

To make it a bit nicer, you could use Exception::Class::TryCatch in tandem with Exception::Class -

use Exception::Class::TryCatch;

...

# try
eval { $obj->some_method('foo') };

# catch
if ( catch my $err ) {
  $err->isa('Bio::Phylo::Exceptions::BadNumber') and do { handle_this(
+$err) };
  $err->isa('Bio::Phylo::Exceptions::ObjectMismatch') and do { handle_
+that($err) };
}
[download]

In reply to Re: Exception::Class - how to use? by Arunbear
in thread Exception::Class - how to use? by rvosa

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks