I don't see a check to see how much can be written without blocking. You can have a write in one direction blocking writes in the other direction, which can lead to a deadlock.
As for golfing, this bit:
139: socket($c,AF_INET,SOCK_STREAM,0)&&connect($c,sockaddr_in$ARGV[1],
+inet_aton$ARGV[0])||die$!;fcntl$_,F_SETFL,O_NONBLOCK|fcntl$_,F_GETFL,
+0 for
(whose only space is not needed) can be reduced to:
100: -MIO::Socket::INET $c=IO::Socket::INET->new(PeerHost=>"$ARGV[0]:$
+ARGV[1]")||die$!;$_->blocking(0)for
By the way, if you hardcoded the host and port, you could save a bunch more.
Update:
99: -MIO::Socket::INET $c=IO::Socket::INET->new(PeerHost,"$ARGV[0]:$A
+RGV[1]")||die$!;$_->blocking(0)for
95: -MIO::Socket::INET $c=new IO::Socket::INET PeerHost,"$ARGV[0]:$AR
+GV[1]"or die$!;blocking$_ 0for
85: -MIO::Socket::INET $c=new IO::Socket::INET"$ARGV[0]:$ARGV[1]"or d
+ie$!;blocking$_ 0for
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.