In general I lean towards less nesting. Less nesting makes the code easier to map into a model in my head. A lot of nesting in one place make me question if there should be a subroutine.

I have seen code with CLAIM comments that signal to the reader that something is true at that point in the program. (Well, that the programmer intended it to be and believes it to be true.) See the following example. 
sub foo
{
   my($self) = @_;
   my $authentication = $self->authenticate_user();
   if(! defined($authentication)){
      return {status=>0, error=>"Authentication Failed", external_id=>
+undef};
   }

   # CLAIM : the user is authenticated

   my $profile = $self->get_user_profile();
   if(! $profile->is_active()){
      return {status=>0, error=>"User is not active", external_id=>und
+ef};
   }

   # CLAIM : the user profile is active

   my($external_id) = $self->find_external_id($profile);
   if(! defined($external_id)){
        $external_id = $self->send_profile_to_partner($profile);
   }

   # CLAIM : the user profile has been sent to the partner

   return {status=>1, error=>undef, external_id=>$external_id};
}

[download]

In reply to Re: Control Flow - Multiple returns or nested conditionals by superfrink
in thread Control Flow - Multiple returns or nested conditionals by JediWizard

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.