Hello,
Inline.
On 3/1/2018 6:44 PM, Eric Berger wrote:
Good question Rolf.
Rui, thanks for pointing out dyn.unload.
When I started using Rcpp a couple of years ago I got burned by stale
.so enough times that I adopted a policy of recompile-then-start new R
session.
My workflow does not includ
Good question Rolf.
Rui, thanks for pointing out dyn.unload.
When I started using Rcpp a couple of years ago I got burned by stale .so
enough times that I adopted a policy of recompile-then-start new R session.
My workflow does not include Rolf's "brazillion" repeats, so the overhead
of this approa
Hello,
In such cases, with C code, I call dyn.unload before loading the
modified shared lib again.
I don't know if this changed recently, but it used to be needed or else
R wouldn't load the new lib. When I call dyn.unload followed by dyn.load
I never had problems.
(Or the other way around, c
I am working with a function "foo" that explicitly dynamically loads a
shared object library or "DLL", doing something like dyn.load("bar.so").
This is a debugging exercise so I make changes to the underlying
Fortran code (yes, I acknowledge that I am a dinosaur) remake the DLL
"bar.so" and
4 matches
Mail list logo