This should get you close to what you want..
>perl -e "my $x = qq['foo',123,'bar\\'cuz', 'comma,comma',,'void']; map { print qq[<$_;\n]; } $x=~m/((?:'[^']*'|[^'\s,]+|))(?:[$|,\s]|$ +)/g;" <'foo'; <123; <'cuz'; <; <'comma,comma'; <; <'void'; <;
There is an extra empty item returned. No easy way to avoid that, that I can think of.
'bar\'cuz' is an invalid text string, in this context, so only 'cuz' is returned.

Note the use of non-capturing parens "(?:" - quite useful in this context, so each iteration returns only a single capture, because the first paren IS a capturing paren.

     "As you get older three things happen. The first is your memory goes, and I can't remember the other two... " - Sir Norman Wisdom


In reply to Re: m//g in list and scalar context differences? by NetWallah
in thread m//g in list and scalar context differences? by oha

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.