You'll get the same problem with using any code that relies upon global state if you try to use it in threads. You'll likely get a similar problem if you try to use File::Find in an event driven environment like POE.

There was a recent thread about what is wrong with File::Find. For me, it's this dependancy upon global state that is it's biggest failing. It's not just the Perlish global vars that form the interface that is a problem--ithreads heroically attempts and mostly succeeds in defending you against that--it's also the way it changes the state of the process by changing the process' current working directory. I'm not sure of the case under pthreads, but on Win32, the CWD is a process-wide state at the OS level, so running File::Find in threads whilst it has this behaviour will never succeed.

You should be able to use opendir/readdir/closedir successfully in a threaded environment.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: File::Find in a thread safe fashion by BrowserUk
in thread File::Find in a thread safe fashion by Preceptor

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.