Ah, like this? 
use threads;
use threads::shared;

my @file_list :shared = @ARGV;
my $num_workers = 2;

my %MSG :shared;

sub process {
   my ($file) = @_;
   print "Opening $file\n";
   if(some condition){
      lock(%MSG);
      #write stuff to hash
   }
   print "Closing $file\n";
}

for (1..$num_workers) {
   async {
      for (;;) {
          my $file = do {
              lock @file_list;
              return if !@file_list;
              shift(@file_list)
          };
          process($file);
      }
   }
}

$_->join() for threads::list();

[download]

This will work as long as you never add anything to the file list once the threads have started. (If you do, you might have worker threads exiting prematurely.)

Thread::Queue does the same, but hides a couple of the details.

In reply to Re^2: wait for threads to end in parallel by ikegami
in thread wait for threads to end in parallel by pmarcoen

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.