I have settled on reducing horizontal indentation (code creeping across the screen) by using more vertical indentation. 
if (
  condition1 or
  condition2 or
  condition3
)
{
  # do something
}
elsif (
  condition4 or
  condition5
)
{
  # do something else
}

[download]
I like the top down feel this approach gives me.

As has been mentioned already, if the code does start creeping across more than, say, 3 'levels of indentation' it almost certainly means it'd be better off being rewritten. I can't hold that many levels of a process/sub processes in my head at a time.

I often take a similar approach to functions/objects. An extreme example:

open(
  my $fh,
  '<',
  'text.txt',
) or die "died";

[download]
Down is better than across :-)

 

In reply to Re: bloated 'if' formatting by wfsp
in thread bloated 'if' formatting by eff_i_g

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.