True, but who cares. He has a freshly accepted socket, so all he needs is
sub new_inet_from_fd {
my ($fd, %arg) = @_;
my $timeout = delete $arg{Timeout};
my $blocking = exists $arg{Blocking} ? delete $arg{Blocking} : 1;
my $sock = IO::Socket::INET->IO::Handle::new_from_fd($fd, '+<');
${*$sock}{'io_socket_timeout'} = $timeout;
${*$sock}{io_sock_nonblocking} = !$blocking;
$sock->blocking($blocking);
$sock->autoflush(1);
return $sock;
}
It produces a socket whose operations don't timeout (unless one is specified), whose operations do block (unless otherwise specified), and that does autoflush. Everything in IO::Handle other than autoflush is at its default.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.