I'm not in the habit of submitting posts (correct or otherwise) to perlmonks that I believe to be inapplicable to the current thread

Unfortunately, my 2nd reply to you included "it [is] unlikely to apply in this situation", which is not correct. Sorry. What you describe is certainly a part of the process here. It was mostly that you replied to my question about why his code breaks in the face of certain line endings with a reply that had absolutely nothing to do with why his code cares about line endings.

I understand how CPAN practices make it easy for Unix line endings to end up in Windows text files. But I find Unix line endings in text files in Windows quite frequently anyway so I don't need any CPAN-specific reasons to motivate making Perl code not care about such, especially since his module surely needs to work on text files in Windows other than the ones that people download from CPAN.

And he had already gotten his code to work in the face of different line endings. I just felt that it was very likely that he was "doing it the hard way". So I was talking even more about how he should get his code to not care about line endings, which made talk of how which types of line endings come to be even further from that point.

So, to be clear, I am not questioning the validity of any of the information that you posted. I am not even questioning the appropriateness of where you posted it.

I just wanted to restate the kernel of my point in hopes of clarifying it and that it still stands, just because it wasn't obvious to me that this was clear to you or would be clear to readers of the thread.

Sorry about flubbing my 2nd attempt to clarify.

- tye        

In reply to Re^7: CPAN module unit test issues: OS line endings (topic) by tye
in thread CPAN module unit test issues: OS line endings by stevieb

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.