i would strongly agree with others who have recommended use of a standard, well tested csv-parsing module.

however, if you really have to go commando (and do it on the command line to boot), the following (tested) code should work.

note that:

perl -wlpe "use strict; my $quo = qq(\042); my $esc = qq(\\\\); my $body = qr/[^$quo$esc]/; my $escaped = qr/$esc ./x; my $sep = qr/ \s* , \s* | \s* \Z /x; my $quoted = qr( $quo $body* (?: $escaped $body* )* $quo )x; my $number = qr(\d+); $_ = join '|', m/( $quoted | $number ) (?= $sep )/gx" NSRLFile.csv > NSRLfile.psv

In reply to Re: swapping PIPE for comma in CSV file by Anonymous Monk
in thread swapping PIPE for comma in CSV file by dwhite20899

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.