Your post and your follow-up regarding your testing methodology suggest IO::Socket may be a bit lacking in tests of its own. In a perfect world, it would be loaded with tests that would tell you right away if your proposed change broke things.

The IO modules are on the Phalanx 100, so some additional tests might be welcome. Now I'm sure this would be biting off much more than you bargained for, but what about adopting the module and becoming a hoplite? Even if you're not up for that, it would be helpful to convert the test cases you came up with into module tests and submit them with your patch.

In reply to Re: IO::Socket doing getpeername twice on every send? by cbrandtbuffalo
in thread IO::Socket doing getpeername twice on every send? by cazz

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.