Hi, Is there an option for achieving a "thread-safe" build of plplot ?
On Win32, the use of the 'fork' function in the PDL::Graphics::PLplot (perl) module test script causes a problem - namely that, after the forked process has exited, there's still *something* hanging about that intereferes with the way that the remainder of the script behaves. On Win32 perls, fork() is implemented via multi-threading, and I suspect that this problem might go away if one (or more) plplot global(s) was instead assigned on a per-thread basis using TLS (thread local storage). My diagnosis might be quite wrong, but.... Cheers, Rob ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Plplot-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-general
