A flag can be useful in these situations. Now the method could return something useful without getting tangled up in success/failure issues.
my $account_data = $ssh->add_account( login => q{bob}, uid => 123 ); if ($ssh->success){ print qq{success: user added\n}; # do something with $account_data } else{ printf qq{failed: %s\n}, $ssh->error_msg; # try next user } sub add_account{ my $account_data; # ... $ssh->{success} = 0; if (condition){ $ssh->{success} = 1; } elsif (condition){ $ssh->{error_msg} = qq{uid not unique}; } else { $ssh->{error_msg} = qq{unknown error}; } return $account_data; } sub success {shift->{success} }; sub error_msg {shift->{error_msg} };

In reply to Re: Dealing with errors in subroutines by wfsp
in thread Dealing with errors in subroutines by walkingthecow

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.