Hi monks,
I am trying to use try catch from Try::Tiny module to catch and exception class object.
use Try::Tiny;
use Exception::Class (
'MyException',
'Commands' => { isa => 'MyException' },
'Timeout' => {
isa => 'Commands',
description => 'These exceptions are resulted from running t
+he naviseccli commands'
}
);
try{
MyException->throw( error => 'I feel funny. custom string based on
+error' ) ;
} catch{
my $e=$_;
if ( $e == Exception::Class->caught('MyException') ) {
warn $e->error, "\n", $e->trace->as_string, "\n";
warn join ' ', $e->euid, $e->egid, $e->uid, $e->gid, $e->pid, $e
+->time;
#exit;
}
};
I see that try did not throw the error. Any ideas why?. Try::Tiny documentation says that $_ should contain the error. Is try of Try::Tiny module capable of throwing exception class object and can it be stored in $_?
I do not want to use die in the try block because I do not want the program to exit but retry after some time or for some exceptions just ignore them after printing a log message.
Thanks in advance!
-
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.