[Rcpp-commits] r613 - papers/rjournal

noreply at r-forge.r-project.org noreply at r-forge.r-project.org
Sat Feb 6 21:57:20 CET 2010


Author: romain
Date: 2010-02-06 21:57:20 +0100 (Sat, 06 Feb 2010)
New Revision: 613

Modified:
   papers/rjournal/EddelbuettelFrancois.tex
Log:
let the reader breathe

Modified: papers/rjournal/EddelbuettelFrancois.tex
===================================================================
--- papers/rjournal/EddelbuettelFrancois.tex	2010-02-06 20:51:08 UTC (rev 612)
+++ papers/rjournal/EddelbuettelFrancois.tex	2010-02-06 20:57:20 UTC (rev 613)
@@ -381,6 +381,8 @@
 Whether an object is wrappable is resolved at compile time, and the 
 dispatch of the appropriate implementation is performed by the compiler
 using modern techniques of template meta programming and class traits.
+
+% [Romain] : should we put the explanation after the code ?
 The design allows composition, so for example objects of the class
 \code{std::vector< std::map<std::string,int> >} are wrappable. This is 
 because \code{int} is wrappable (as a primitive type), consequently 



More information about the Rcpp-commits mailing list