Dis you test your code?! I made some tests for Thread too, but all the process stop when reading STDIN!!! :-/
Test Thread:
use threads;
use threads::shared;
my ($BUFFER) : shared ;
$thra = threads->new(\&read_stdin);
$thrb = threads->new(\&send_sock);
print "By!\n" ;
##############
# READ_STDIN #
##############
sub read_stdin {
1 while( read( \*STDIN , $BUFFER, 1 , length($BUFFER) ) ) ;
}
#############
# SEND_SOCK #
#############
sub send_sock {
my ($buf_lng) ;
for(;;) {
if ( length($BUFFER) > $buf_lng ) {
my $buf = substr($BUFFER , $buf_lng-1 ) ;
print "<$buf>\n" ;
}
$buf_lng = length($BUFFER) ;
print ".\n" ;
sleep(1) ;
}
}
But thanks for the reply!
Graciliano M. P.
"The creativity is the expression of the liberty".
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.