That can still be helped by better formatting rules. The way I write complex conditionals that would be too long to fit on one line is to treat the parens like curlies and line them up the same way, indenting the content.

See what your mistake would look like then:

if(
    ( $flag1 or $flag2 )
    and ( length( $string )
) {
    # ...
}

[download]

It still isn't perfectly obvious, but it's much easier to see now.

It also helps to have an editor that will match brackets/parens/curlies for you; go through your delimiters one by one and check that there is a matching one where you expect it.

Makeshifts last the longest.

In reply to Re^3: Grokking Compile Error Messages by Aristotle
in thread Grokking Compile Error Messages by QM

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.