[Rcpp-commits] r581 - papers/rjournal

noreply at r-forge.r-project.org noreply at r-forge.r-project.org
Fri Feb 5 16:11:51 CET 2010


Author: romain
Date: 2010-02-05 16:11:50 +0100 (Fri, 05 Feb 2010)
New Revision: 581

Modified:
   papers/rjournal/EddelbuettelFrancois.tex
Log:
some more text

Modified: papers/rjournal/EddelbuettelFrancois.tex
===================================================================
--- papers/rjournal/EddelbuettelFrancois.tex	2010-02-05 15:07:31 UTC (rev 580)
+++ papers/rjournal/EddelbuettelFrancois.tex	2010-02-05 15:11:50 UTC (rev 581)
@@ -195,11 +195,17 @@
 The \code{Rcpp::RObject} class is the basic class of the new Rcpp API. 
 An instance of the \code{RObject} class encapsulates an R object
 (\code{SEXP}), exposes methods that are appropriate for all types 
-of objects and transparently manage garbage collection.
+of objects and transparently manages garbage collection.
 
 The most important aspect of the \code{RObject} class is that it is 
 a very thin wrapper around the \code{SEXP} it encapsulates, the 
-\code{SEXP} is indeed the only data member of an \code{RObject}.
+\code{SEXP} is indeed the only data member of an \code{RObject}. The 
+\code{RObject} class does not interfere with the way R manages its 
+memory, does not perform copies of the object into a suboptimal 
+C++ representation, but instead merely acts as a proxy to the 
+object it encapsulates, so that methods applied to the \code{RObject}
+instance are relayed back to the \code{SEXP} in terms of the standard
+R API.
 
 The \code{RObject} class takes advantage of the explicit life cycle of 
 c++ objects to manage exposure of the underlying R object to the 



More information about the Rcpp-commits mailing list