I'm not sure that what you have is a Windows vs Unix problem. Standard network termination is 0D0A (like how a Windows box likes to do). So even if 2 Unix boxes were talking in a text mode over a socket, the data over the socket would be CRLF terminated instead of the normal LF like to a terminal/local file. So, on the Unix box, print() does different things depending upon whether it is talking to a network connection or a local file on a Unix box.

I think you are going to wind up using read() and write() instead of print() if you want absolute control of exactly what is sent over the socket. In that case, you would be taking on the job of figuring out what a "line" is.

In reply to Re: Remove extra carriage return (0D) on socket communications by Marshall
in thread Remove extra carriage return (0D) on socket communications by PhillyR

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.