I would probably go about this differently: 
# starting point
sub start {
   eval {
       call1();
       call2();
   };
   return 0 if $@;
   return 1;
}

sub call1 {
   # code here
   die "Error in call1" if $something_nasty;
   call3();
   # more code
}

sub call2 {
   # code here
   die "Error in call2" if $something_nasty;
   # more code here..
}

sub call3 {
   # code here
   die "Error in call3" if $something_nasty;
   # more code here..
}

[download]

In other words use die and eval BLOCK to trow and catch exceptions, and you won't have to check every subroutine call, just catch the error at the place you want to process it.

See the die and eval entries in perlfunc for more info. 

-- 
Joost       downtime n. The period during which a system
            is error-free and immune from user input.

[download]

In reply to Re: Managing errors in subroutines by Joost
in thread Managing errors in subroutines by rbi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.