On 8 October 2013 14:19, Dirk Eddelbuettel wrote:
>
> On 8 October 2013 at 13:53, Jon Clayden wrote:
> | I think I do... ;) I need the object to hold state and not be
> deallocated
> | between calls into the C++ code. I also want to allow for the
> possibility that
> | multiple Foo objects exist
On 8 October 2013 at 13:53, Jon Clayden wrote:
| Sure. And the memory allocated to "bar" (if it's a NumericVector) will be
| protected from the garbage collector until the Foo object is deleted?
Yes, R objects created by Rcpp, eg Rcpp::NumericVector and all the other
Rcpp::* objects mapping to st
Le 08/10/13 14:53, Jon Clayden a écrit :
Thanks Dirk and Romain for your helpful replies. To follow up briefly...
I'm defining a custom class, an object of which will need to survive
across various calls back and forth between R and C++, so I plan
to use
the XPtr
Thanks Dirk and Romain for your helpful replies. To follow up briefly...
I'm defining a custom class, an object of which will need to survive
>> across various calls back and forth between R and C++, so I plan to use
>> the XPtr class to wrap a pointer. My question is, what are the
>> advantages a
Le 08/10/13 13:04, Jon Clayden a écrit :
Dear all,
I'm new to Rcpp and this mailing list. I did look for a previous answer
to this question, but it's hard to summarise succinctly so I may have
missed something. Apologies if so.
I'm defining a custom class, an object of which will need to surviv
Hi Jon,
On 8 October 2013 at 12:04, Jon Clayden wrote:
| I'm new to Rcpp and this mailing list. I did look for a previous answer to
this
| question, but it's hard to summarise succinctly so I may have missed
something.
| Apologies if so.
|
| I'm defining a custom class, an object of which will
Dear all,
I'm new to Rcpp and this mailing list. I did look for a previous answer to
this question, but it's hard to summarise succinctly so I may have missed
something. Apologies if so.
I'm defining a custom class, an object of which will need to survive across
various calls back and forth betwe
