On 2/22/06, Martin Voelkle <[EMAIL PROTECTED]> wrote: > > from http://www.boost.org/libs/python/doc/v2/faq.html > > > > == > > > > Is Boost.Python thread-aware/compatible with multiple interpreters? > > > > Niall Douglas provides these notes: > > > > The quick answer to this is: no. > > > > The longer answer is that it can be patched to be so, but it's complex. You > > will need to add custom lock/unlock wrapping of every time your code enters > > Boost.Python (particularly every virtual function override) plus heavily > > modify boost/python/detail/invoke.hpp with custom unlock/lock wrapping of > > every time Boost.Python enters your code. You must furthermore take care to > > not unlock/lock when Boost.Python is invoking iterator changes via > > invoke.hpp. > > There is a patched invoke.hpp posted on the C++-SIG mailing list archives > > and > > you can find a real implementation of all the machinery necessary to fully > > implement this in the TnFOX project at this SourceForge project location. > > > > == > > > > The project they talk about is there : > > http://sourceforge.net/projects/tnfox > > But the CVS looks empty :-( > > The problem described there is about real multithreading with > preemption. Coroutines don't have this problem. > > Martin > > > _______________________________________________ > glob2-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/glob2-devel >
I'm not exactly sure what "coroutines" are? Could you give some background information? It sounds like a different way of representing parralellism, but i'm unsure. _______________________________________________ glob2-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/glob2-devel
