01-05-04 16.16, skrev Alan Burlison p� [EMAIL PROTECTED] f�ljande: > Artur Bergman wrote: > >> But that is pretty easy to fix by using thread local storage (like perl does >> for the current perl-interpreter). > > And how exactly will you do this for a third-party binary-only library? My bad, I meant for user supplied C code on CPAN. >> Maybe it would be possible to add a option to XS to automaticly add code to >> mutex protect an entire library. (This won't solve the problem with stored >> state, but my belief is it would help in most cases). > > This is distinctly non-trivial. I don't know XS well enough to say it isn't so I take your word on it. Artur
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Nicholas Clark
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Chris Stith
- Re: our :shared $foo / iThreads Benjamin Sugars
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Alan Burlison
- Re: our :shared $foo / iThreads Artur Bergman
- Re: our :shared $foo / iThreads Jarkko Hietaniemi
- Re: our :shared $foo / iThreads Alan Burlison
- Re: our :shared $foo / iThreads Artur Bergman
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Benjamin Sugars
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Gurusamy Sarathy
- Re: our :shared $foo / iThreads Dan Sugalski
- Re: our :shared $foo / iThreads Alan Burlison
- Re: our :shared $foo / iThreads Jens-Uwe Mager
- Re: our :shared $foo / iThreads Alan Burlison
- Re: our :shared $foo / iThreads Jens-Uwe Mager
- Re: our :shared $foo / iThreads Alan Burlison
