Displaying 3 results from an estimated 3 matches for "preserveobject".
Did you mean:
  r_preserveobject
  
2008 Feb 22
1
Calling R_PreserveObject from embedded R
.... I've followed up 
the examples of the documentation showing how to run R embedded, and I got 
it partially working. However, I have a problem with the reference handling 
of the R objects.
I've followed this strategy: every time I call a function in R and it 
answers me a SEXP, I called R_PreserveObject(sexp), and wrap it with a 
Smalltalk object. Whenever the Smalltalk object dies, I release the R object 
by calling R_ReleaseObject(sexp).
This seems to handle well the life cycle, but makes the running process to 
use a growing and a never ending amount of memory. Actually, after 
experimenting a...
2014 Mar 07
0
Repost: (apologies for HTML post) A question about multiple(?) out of order ReleaseObject
Apologies, I am resending this because my emails seem to go in HTML form.
Hello,
This  is a question that probably reveals my lack of understanding.
In a C function (call it cfunc), i created a SEXP, called S, and then
called R_PreserveObject on S.
I returned the SEXP to the calling R function (call it rfunc). Note, I
didn't call
R_ReleaseObject on S.
v <- .Call("cfunc")
So, are the following  statements correct
1.  S is 'doubly' protected from the GC by  being associated both with 'v'
and because it...
2014 Mar 07
0
Many apologies: last post: A question about multiple(?) out of order ReleaseObject
Apologies, I am resending this because my emails seem to go in HTML form.
(I haven't as yet figured gmail web interface)
 Hello,
This  is a question that probably reveals my lack of understanding.
In a C function (call it cfunc), i created a SEXP, called S, and then
called R_PreserveObject on S.
I returned the SEXP to the calling R function (call it rfunc). Note, I
didn't call
R_ReleaseObject on S.
v <- .Call("cfunc")
So, are the following  statements correct
1.  S is 'doubly' protected from the GC by  being associated both with 'v'
and because it...