This kind of thing can be okay for progressive checking. I normal dislike this style of code/logic but it seems a good fit for this kind of problem.
if ( $range > 500 )
{
WAT_OP();
}
elsif ( $range >= 425 )
{
some_op();
}
elsif ( $range > 400 )
{
some_other_op();
}
elsif ( $range > 300 )
{
exit 0;
}
else
{
complete_tree_op();
}
You can also do something more dispatchy–
my @action_tree = ( { test => sub { $_[0] >= 300 && $_[0] <= 400 },
action => sub { print "GUDNITES\n"; CORE::exit(0
+) } },
{ test => sub { $_[0] >= 425 && $_[0] <= 500 },
action => sub { print "OHAI\n" } } );
while ( my $signal = <SIGNAL_SOURCE> )
{
$_->{test}->($signal) && $_->{action}->() for @action_tree;
}
I'm not advocating either, or that second style of terseness, or any style or approach for that matter. Just expanding the library of options. :P
-
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.
|