Unless you can't compile XS, I would recommend Text::CSV_XS or Text::CSV::Simple (which uses Text::CSV_XS) you may not need the performance now but, I find I use it enough that you'll run into those situations.

Also Text::xSV looks good

These modules get around the problems with using split. The big problem being, escaped seperators in the data. Unless you are dead certain that the data has been cleaned of |'s avoid split.

Even if you can get by with split and don't really need Text::CSV_XS now you'll be better off learning the module. This type of thing comes up a lot and split can really bite you.



grep
Mynd you, mønk bites Kan be pretti nasti...

In reply to Re^2: Parse a pipe-delimited list by grep
in thread Parse a pipe-delimited list by jhs3

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.