[Rcpp-commits] r574 - papers/rjournal
noreply at r-forge.r-project.org
noreply at r-forge.r-project.org
Fri Feb 5 11:53:25 CET 2010
Author: romain
Date: 2010-02-05 11:53:24 +0100 (Fri, 05 Feb 2010)
New Revision: 574
Modified:
papers/rjournal/EddelbuettelFrancois.bib
papers/rjournal/EddelbuettelFrancois.tex
Log:
having a go at the abstract, remove the explicit section 'introduction' and 'overview'
Modified: papers/rjournal/EddelbuettelFrancois.bib
===================================================================
--- papers/rjournal/EddelbuettelFrancois.bib 2010-02-05 10:19:37 UTC (rev 573)
+++ papers/rjournal/EddelbuettelFrancois.bib 2010-02-05 10:53:24 UTC (rev 574)
@@ -114,3 +114,12 @@
url = {http://CRAN.R-project.org/package=RcppTemplate}
}
+ at Manual{cran:rprotobuf,
+ title = {RProtoBuf: R Interface to the Protocol Buffers API},
+ author = {Romain Francois and Dirk Eddelbuettel},
+ year = {2010},
+ note = {R package version 0.1-0},
+ url = {http://r-forge.r-project.org/projects/rprotobuf/, http://code.google.com/p/protobuf/},
+}
+
+
Modified: papers/rjournal/EddelbuettelFrancois.tex
===================================================================
--- papers/rjournal/EddelbuettelFrancois.tex 2010-02-05 10:19:37 UTC (rev 573)
+++ papers/rjournal/EddelbuettelFrancois.tex 2010-02-05 10:53:24 UTC (rev 574)
@@ -5,9 +5,16 @@
\maketitle
-\abstract{TBD}
+\abstract{The \pkg{Rcpp} package dramatically simplifies the
+process of integrating C++ code with R. It provides a
+consistent C++ class hierarchy that map various types of
+R objects (vectors, functions, environments, ...) to
+dedicated C++ class. Data interchange between R and C++
+is managed by simple, flexible and extensible concepts.
+\pkg{Rcpp} substancially lowers the language barrier for programmers
+who want to plug compiled code in an R package.}
-\section{Introduction}
+% \section{Introduction}
TBD, probably close to last
@@ -17,7 +24,12 @@
also significantly eases access from C++ itself (and to the C++
representation of R objects). Does that make sense?
-\section{Overview}
+% \section{Overview}
+% [Romain:] we don't need introduction and overview, one should be enough
+% also some articles don't have anything. For example
+% the party on article in the last issue directly start with
+% text after the abstract. I like that. Also is the case of the
+% "new R help system" article
% [Romain:] the overview is really messy and probably
% needs a complete rewrite when all other sections are finished
@@ -730,8 +742,8 @@
of the code, which improves code readability and maintainability.
The redesign of \code{Rcpp} was motivated by the needs of other
projects such as \code{RInside} for easy embedding
-of R in a c++ application and \code{RProtoBuf} that interfaces
-with the protocol buffer library.
+of R in a c++ application and \code{RProtoBuf} \citep{cran:rprotobuf}
+that interfaces with the protocol buffer library.
\bibliography{EddelbuettelFrancois}
More information about the Rcpp-commits
mailing list