Interestingly, the GNU convention is "When you split an expression into multiple lines, split it before an operator, not after one." but GNU style apparently does not treat commas as operators — those are still left at the end of a line.

if (($foo && $bar && ...) || ($baz && $quux && ...)) { ... } # but function_call_with_many_lengthy_args (very_long_arg1, very_long_arg2, and_on_and_on_and_on);

GNU style is specifically for C, but Perl syntax is reasonably similar. I suppose the point is that this really is a matter of style, except in Awk, where if I remember correctly, an operator at the end of a line also implies line continuation; the GNU convention requires backslash-newline in Awk.


In reply to Re^4: Adding items to arrays: best approach? by jcb
in thread Adding items to arrays: best approach? by geertvc

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.