Just to add a bit to clarify and keep history, as Corion asked me in /msg: the $csv object is used for both input/getline/parse and output/print/combine. Most of the questions I get are for parsing, and most of my own scripts are parsing CSV data.

The parsing code works better when not setting eol, as it then allows more "default" values (to be mixed) and works faster (but probably not measurable).

Setting eol to $/ by default would most likely break a lot of parser scripts. Setting eol to $/ on output only makes some sense, but also makes the documentation harder and I wonder if it would be worth breaking backward compatibility.

What does make sense in breaking backward compatibility is to make binary default to a true value, as I can't think of a modern situation where it would break a parser.


Enjoy, Have FUN! H.Merijn
cc

In reply to Re^3: CSV_XS issue by Tux
in thread CSV_XS issue by anaconda_wly

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.