Hello Fernando,
For sure there will be better ideas, but sometimes I use serialized
protocol buffers (RProtoBuf) for persistence, or even to treat data structures
(or "classes") between R, C++, python or even C#. You can store serialized
protobuf on the file system or using databases (sql or not).
But for sure there are better ideas.
Kind regards
David Ibarra Gómez
-----Mensaje original-----
De: rcpp-devel-boun...@lists.r-forge.r-project.org
[mailto:rcpp-devel-boun...@lists.r-forge.r-project.org] En nombre de F.Tusell
Enviado el: jueves, 20 de marzo de 2014 18:40
Para: rcpp-devel@lists.r-forge.r-project.org
Asunto: [Rcpp-devel] Making objects in the C++ "side" persistent
I have been reading "Exposing C++ functions and classes with Rcpp modules" and
find the idea interesting. However, I read in Section 5 that objects created
using an external pointer are not persistent from session to session.
For my purposes, I think I could use S4 objects that make C++ copies of
themselves at creation time, accessible via an external pointer. All methods
would then make use of the C++ copies for speed, and at the end of the session
the S4 copies that live in the R side would be saved.
I am thinking of writing code which at the start of a session checks all
(S4) objects in the workspace and recreate the C++ copies. Is this the way to
go? Has someone with a similar problem devised an alternative solution? If
anyone can offer some hints (or better yet, point to some package that I can
use for inspiration) I would be grateful.
Best,
F.Tusell <fernando.tus...@ehu.es>
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
Disclaimer: http://disclaimer.aqualogy.net/
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
