The alternative the grandparent suggested
print("error message\n"), next if /^>>/;
could easily be confused for
print("error message\n"); next if /^>>/;
I don't think it's a very good idea.

At least what you used is well established. It is quite ugly, though. I usually fall back to if/elsif. if/elsif even produces shorter lines: 

foreach (@w) {
  print "working with $_... ";
  if    (/^>>/               ) { print "error message\n"            }
  elsif (/^\s*([<>])\s*(\S+)/) { print "separated '$1' from '$2'\n" }
  elsif (/^\s*\|/            ) { print "pipefront\n"                }
  elsif (/\|\s*$/            ) { print "pipeend\n"                  }
  else                         { print "\n"                         }
}

[download]

In reply to Re^4: searching the strings by ikegami
in thread searching the strings by singam

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.