Hmmm... that's odd. I found that the close STDIN did the job perfectly. I note you are using ActiveState perl v5.8.8 on a dual core machine -- while I have 5.10.0, single core... but have no way of knowing whether either accounts for the difference.

Just in case: it's not necessary to have the sleep in the input thread and the close together... the close on its own does the trick (here).

I wondered whether it made a difference if the input thread was blocked on the <STDIN> at the time the main thread did the close STDIN in the main thread to block or fail... which would be more likely on a dual core machine. However, I tried a threads->yield() before the close, and that didn't make any difference. (The input loop was definitely waiting for <STDIN> but the close completed successfully.)I suppose this could be different on 5.8.8 ?

If you wanted to play with semaphores you could do:

# Create terminal watcher

print "Create terminal watcher...\n";

my $Q_stdin = Thread::Queue->new ;
my $S_stdin = Thread::Semaphore->new(0) ;

print "fileno(STDIN) = ", fileno(STDIN), "\n" ;

async {
  $S_stdin->down() ;
  print "Reading STDIN, fileno=", fileno(STDIN), "\n" ;
  while (defined( $_ = <STDIN> )) {
    chomp ;
    print "\n+IN : '$_'   " ;
    $Q_stdin->enqueue( $_ ) ;
    print "*" ;
  } ;

}->detach;

close STDIN ;                          ### no longer our business     
+  <<<<
print "STDIN is: ", defined(fileno(STDIN)) ? 'open' : 'closed', "\n" ;

$S_stdin->up() ;
[download]

which guarantees that the main thread has closed STDIN before the input thread touches it.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.