There's more than one way to do things | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Caveat: I know nothing about RSPerl, other than it embeds one interpretter in the other.
Since each Perl thread starts a new interpretter, its unclear whether an R interpretter created in the main thread will get cloned into all the children, or each child will get a brand new R interpretter instance. Assuming you revert to the original approach, you might try cranking up the per-thread stack size, and see if that corrects the error message. Note that doing so will reduce the number of threads you can start. Perl Contrarian & SQL fanboy In reply to Re: RSperl & threads
by renodino
|
|