A common misconception in socket programming is that \n eq \012 everywhere. When using protocols such as common Internet protocols, \012 and \015 are called for specifically, and the values of the logical \n and \r (carriage return) are not reliable.

 print SOCKET "Hi there, client!\r\n";      # WRONG
 print SOCKET "Hi there, client!\015\012";  # RIGHT <- also wrong!
[download]

print SOCKET "Hi there, client!\n"; #WORKS, on Unix or Windows!!
                                    #sends CR/LF: \015\012
[download]

Thank you for making my point. If you click on your own link, you will see the below.

And incredibly, in the line right after the one you quoted it says

    print SOCKET "Hi there, client!\r\n";      # WRONG
    print SOCKET "Hi there, client!\015\012";  # RIGHT
[download]

Keep reading smartalec

Before this escalates, please step back, make your point with code and data, and don't resort to names. They do nothing to prove your point.

--MidLifeXis

So anonymous smartalec, post some code that proves your point.

I think that it is beyond discussion that Perl prints LF for \n on a Unix system and Perl prints CRLF for \n on a Windows system. I further claim that Perl will print CRLF for \n on a Network socket.

Hi Marshall, please mark your updates , thank you. How do I change/delete my post?