The recipes I've seen have an inner eval block and a second alarm(0). Paraphrasing, the inner eval is to trap any exception from your long process, which otherwise might pop you out of the outer eval with the alarm still pending; and the second alarm reset is for the slim chance of an exception occurring after the inner eval, but before the first alarm reset.
See the three new lines below. I haven't tested this, but does it work?
use strict;
use warnings;
use XML::LibXML;
my $html = do { local $/; <> };
my $libxml = XML::LibXML->new();
#$libxml->recover(2);
eval {
local $SIG{ALRM} = sub { die "TIMEOUT\n" };
alarm(10);
eval { ######
$libxml->parse_html_string($html);
}; ######
alarm(0);
};
alarm(0); ######
if ($@ and $@ eq "TIMEOUT\n") {
warn "Timed out ok.\n";
} elsif ($@) {
die $@;
}
-
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.
|