Re: [Rd] Running R embedded in an mpiexec spawned process - Fatal error: you must specify '--save', '--no-save' or '--vanilla'

Thanks for that. It does confirm what I was starting to suspect: that the R engine initialization in R.NET needs a change to use the R embedding API functions, though mindful that the R.NET author did settle on the current arrangement for a pragmatic reason. I also shamefully missed a recent pos

[Rd] Running R embedded in an mpiexec spawned process - Fatal error: you must specify '--save', '--no-save' or '--vanilla'

I'd like someone familiar with the R options initialization to comment on a difference of behavior within/without mpiexec I have a (.NET) application with embedded R that is proven to run in a single process: ./Sample1.exe on a Debian Linux with R 3.0.2 Running the same code with mpiexec,

[Rd] Different behavior of the "showArgs" example (R extension manual) between gcc and Visual C++ compiled code

Hi, I am trying to implement on a Win7 box the showArgs example of section 5.10.2 "Calling .External" of the R extension manual. I am using interchangeably gcc (RTools) and Visual C++ (via Makefile.win) to build a package. I get a couple of runtime oddities when the dll compiled with Visual C++