When using Perl's default I/O layer, print "\n" will emit <LF> on Unix and <CR><LF> on Windows.

Yes, you're just repeating back to me what I said several times now.

When reading a text line (Unix or Windows), the <CR> will be deleted, if it exists.

For *NIX that is once again wrong.

$ hexdump -C test.txt 
00000000  46 6f 6f 0d 0a                                    |Foo..|
$ perl -wMstrict -MData::Dump -e 'dd <>' test.txt 
"Foo\r\n"
[download]

Update: When using "standard default I/O methods"

But that's not the only thing this discussion iswas about. It's also about you insisting that (essentially) $ matches before \r, insisting that (essentially) "\n" eq "\r\n" and that somehow all network communication magically uses CRLF, or stuff like the above. Sorry, but all the evidence appears to point to a fundamental misunderstanding of the topic.

That is not completely correct.

Are you just trolling now? You clearly still haven't studied the subject matter enough, I'm not sure if you're even reading my posts, and I'm tired of repeating myself and running tests that you could be running, so for now, I'm out.

At this point, I need to get a Unix account and run some tests and compare Windows vs Unix. This will take some weeks.

I did look at Re^7: How do I display only matches and I am perplexed.

Somehow, print $sock "foo\n\0\0"; produces 66:6f:6f:0a:00:00. On both Windows and Unix? That does indeed surprise me! But, if true, that does indeed indicate that on Windows, printing to a socket is different than printing to a file.

let's stop this subthread. I will investigate further.