Thanks, Duncan,
> It is a mixture of two things. Yes, R is not thread safe so if
> two system threads were to access R concurrently, bad things would
> happen a.s.
That's clear, yes. :-/ And a pity, but so be it.
> It is also an issue when Python is compiled and linked with
> threaded options
Since Python has been mentioned in this context: Could not Python's
threading model and implementation serve as a guideline?
>From a few simple benchmarks I've run, it seems as if the Python
interpreter itself is thread-safe but not threadable. That is, when I
run something "pure Python" like a re
> But it still remains to be seen whether the extra work to introduce
> threads is warranted. Will people actually use them in R and will it
> have a significant impact on the computations or simply make writing
> GUIs within R slightly easier to manage?
If threads can be set up easily, why not?
I don't want to keep hammering on the possible interest of python in
this context... but have you seen this?
http://ipython.scipy.org/moin/Parallel_Computing
I know, not exactly the same as multithreading ;)
__
R-devel@r-project.org mailing list
https:
