--linuxkid

No.

\n will mean 0x0D 0x0A in a CR LF environment (DOS), 0x0D in a CR environment (Mac Classic), and 0x0A in a NL environment (pretty much everything else). You mean \015\012 (or \x0d\x0a if you’re a hexed person) when dealing with sockets, but even that’s not true, because it’s 0x0D 0x0A only in protocols that define new lines as a CR LF sequence. Even so, most of the time, receiving NL-separated messages in such protocols is generally okay, as per “(Be strict in what you send), but forgiving in what you receive”.

But cygwin and windows are different OS, they have different defaults for \n, and you need to deal with them. Read binmode, read perlport#Newlines, and deal with the newlines

eol

EOL - This module aids in the conversion of text file newline characters within the context of other perl code; includes command line executable.

PerlIO::eol - PerlIO layer for normalizing line endings

Text::FixEOL - Canonicalizes text to a specified EOL/EOF convention, repairing any 'mixed' usages

s/\s+$//;

newline

Encode::Newlines

File::LocalizeNewlines

?node_id=3989;HIT=newline;re=N, ?node_id=3989;HIT=\n;re=N

Quick and portable way to determine line-ending string?

\r\n at end of line

use

s/\s+$//;

don't

dos2unix, its silly to use it between cygwin and windows :)