First thing I'd check if it worked with ActiveState but not Cygwin, was the 'chomp'.

Check so it isn't confused about 1 or 2 chars end-of-lines. (See what you have after the chomp, either one char to little or an extra \n.)

(It is a potential mess. You can configure Cygwin for how it should treat eol:s. Also, if you wrote the data file in Unix and copied over the file in bin format, you'd get a single \n.)

Update:
Should add some code that do reading w/out extra chars in Cygwin, as bart did. This works for me in fixing up mixed files (I use an old version of Ultraedit that mixes line endings! Don't use Win much). 

while(<$fh>) {
   chop;
   chop              if /\015$/;
   print UT $_;
   print UT "\012";
}
close $fh;

[download]

In reply to Re: Doesn't work in Cygwin by BerntB
in thread Doesn't work in Cygwin by maybeD

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.