The easiest thing to do is to have &get_info return undef on failure. Then you can check to see if you have good $info back, in &do_something. If not, then recall &get_info with another arg to see if that works. You don't really need to get too complicated with this.
sub do_something
{
my $param = shift;
# just add a test for success here:
my $info = get_info($param) || get_info('option 1');
# more things happen
do_something_else($param, $info);
}
sub get_info
{
my $param = shift;
my $info;
if($param eq 'option 1')
{
$info = 'blah';
}
elsif($param eq 'option 2')
{
return unless # <-- test whether a failure occurred; return undef
do_something_that_might_fail($param) #POINT A
$info = 'foo';
}
else
{
$info = 'bar''
}
return $info;
}
I hope that's clear.
I'm not sure HOW the failure occurs. Maybe by dying, maybe by returning false from &do_something_that_might_fail ... I chose the latter for this example. Please put in a test that works for you.
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.