Ohh, that brings back (bad) memories.

In $CPAN/src/unsupported/4.036/perl-4.036.tar.gz, you'll find a file named lib/chat2.pl, which contains: 

    unless (socket(S, 2, 1, 6)) {
        # XXX hardwired $AF_SOCKET, $SOCK_STREAM, 'tcp'
        # but who the heck would change these anyway? (:-)

[download]
Yes, these were the correct constants on BSD, but they were wrong for SysV, which meant that every SysV user sent me bug reports about why chat2 didn't work for them. {sigh}

Thankfully, that file was "retired" as of Perl5, being replaced by the Expect module.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

In reply to Re^2: RFC: Perl Second-Best Practices by merlyn
in thread RFC: Perl Second-Best Practices by dimar

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.