I'm QUITE sure that using \012\015 is a bad idea ... \n\r has a chance of doing the right thing.

Um, I don't think so - Read the perlport man page under the heading "Newlines". To quote:

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.

[download]

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

[download]

This is equally applicable to the use of the literal \r and \n in general programming.

 

perl -le 'print+unpack"N",pack"B32","00000000000000000000001001111000"'

In reply to Re: Re: Re: An introduction to POE by rob_au
in thread An introduction to POE by RMGir

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.