I changed my code so filedescriptor will be closed before threads starts and it works , so why this strange behavier ? i thought that filedescriptors r duped per thread on windows
use strict; use warnings; use threads; mxu_install(); sub mxu_install { my $count=0; my $kit_temp=$ARGV[0]; if(!opendir(MXU_DIR,"$kit_temp/MXU")) { print "Can't open $kit_temp/MXU: $!"; } while( defined (my $file = readdir MXU_DIR) ) { next if $file =~ /^\.\.?$/; } closedir(MXU_DIR); install_mxu_comp(); return; } sub install_mxu_comp { my $count=0; $|=1; my $thread1 = threads->new(\&blah); my $thread2=threads->new(\&blah); $thread1->join(); $thread2->join(); print "Father exiting\n"; return 0; } sub blah { print "inthread\n"; sleep(5); }

In reply to Re: threads problem by Anonymous Monk
in thread threads problem by vlingvo

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.