[Rcpp-commits] r584 - papers/rjournal

[noreply at r-forge.r-project.org]

Author: romain
Date: 2010-02-05 17:40:38 +0100 (Fri, 05 Feb 2010)
New Revision: 584

Modified:
   papers/rjournal/EddelbuettelFrancois.tex
Log:
chatting around

Modified: papers/rjournal/EddelbuettelFrancois.tex
===================================================================
--- papers/rjournal/EddelbuettelFrancois.tex	2010-02-05 16:19:02 UTC (rev 583)
+++ papers/rjournal/EddelbuettelFrancois.tex	2010-02-05 16:40:38 UTC (rev 584)
@@ -14,7 +14,10 @@
 \pkg{Rcpp} substantially lowers the language barrier for programmers
 wanting to combine compiled code with R.}
 
-\section{Introduction}  % [Dirk] I am a tradionalist here ...
+\section{Introduction} 
+% [Dirk] I am a tradionalist here ...
+% [Romain] fine. should we then remove the background section
+% and just let its contents be part of 'introduction'
 
 R is an extensible system. The 'Writing R Extensions' manual \citep{R:exts}
 describes in great detail the various ways to augment R with compiled code,
@@ -33,7 +36,9 @@
 APIs. The first---which we call `classic Rcpp API'---exists since 
 the first version of \pkg{Rcpp}. The second API, enclosed in the 
 \code{Rcpp} C++ namespace is a newer codebase, which we started to develop
-more recently. This article %mostly concerns the newer API, and  %% [Dirk] Really?
+more recently. This article 
+% mostly concerns the newer API, and  %% [Dirk] Really?
+% [Romain] based on relative lengths of coverage ... 
 highlights some of the key design and implementation choices: 
 lightweight encapsulation of R object in C++ classes, automatic
 garbage collection strategy, code inlining, data interchange between