The other thread will use PHYSFS_getCdRomDirs() (and possibly its file-listing methods later, if I intent to implement recursive file listing)<br><br><div class="gmail_quote">2009/7/5 Matheus Izvekov <span dir="ltr"><<a href="mailto:mizvekov@gmail.com">mizvekov@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">On 13:27 Sun 05 Jul , Tim Čas wrote:<br>
> Hey, this is one of my first mails (if not the first), but I've been a<br>
> member of the list for a few months now.<br>
><br>
> I am working on a game engine with an interchangeable backend - one of the<br>
> features is quake-like file handling.<br>
><br>
> I am working on a PHYSFS backend for file I/O and I have a question:<br>
> Is PHYSFS_getCdRomDirs() thread-safe?<br>
> I mean, can I use it from a different thread to create a "non-blocking"<br>
> listing - so that the program doesn't get blocked while the CD unit spins up<br>
<br>
</div></div>Physfs is not thread-safe. But are you sure you need thread safety?<br>
>From your description of the problem, it seems that the other thread<br>
will not use physfs, right?<br>
Thread safety is not needed just because you are using threads in your<br>
program. It's needed if you intend to use it from<br>
different threads at the same time.<br>
<br>
> _______________________________________________<br>
> physfs mailing list<br>
> <a href="mailto:physfs@icculus.org">physfs@icculus.org</a><br>
> <a href="http://icculus.org/mailman/listinfo/physfs" target="_blank">http://icculus.org/mailman/listinfo/physfs</a><br>
<br>
_______________________________________________<br>
physfs mailing list<br>
<a href="mailto:physfs@icculus.org">physfs@icculus.org</a><br>
<a href="http://icculus.org/mailman/listinfo/physfs" target="_blank">http://icculus.org/mailman/listinfo/physfs</a><br>
</blockquote></div><br>