[Rprotobuf-commits] r835 - papers/jss

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

Author: murray
Date: 2014-01-23 04:01:59 +0100 (Thu, 23 Jan 2014)
New Revision: 835

Modified:
   papers/jss/article.Rnw
Log:
Note at the end of section 2 that the reflection based API is slightly
slower for some operations, but that its much more convenient for
interactive data analysis.

I want to tone down the implication that protocol buffers are the
best/fastest thing out there, and I always thought the 'particularly
well-suited' was a tad vague here.



Modified: papers/jss/article.Rnw
===================================================================
--- papers/jss/article.Rnw	2014-01-23 02:45:35 UTC (rev 834)
+++ papers/jss/article.Rnw	2014-01-23 03:01:59 UTC (rev 835)
@@ -426,8 +426,10 @@
 Buffer schema description file (ending in \texttt{.proto}) into
 language-specific classes that can be used to create, read, write, and
 manipulate Protocol Buffer messages.  The \proglang{R} interface, in contrast,
-uses a reflection-based API that is particularly well-suited for
-interactive data analysis.  
+uses a reflection-based API that makes some operations slightly
+slower but which is much more convenient for interactive data analysis.
+%particularly well-suited for
+%interactive data analysis.  
 All messages in \proglang{R} have a single class
 structure, but different accessor methods are created at runtime based
 on the named fields of the specified message type, as described in the
@@ -554,7 +556,7 @@
 <<>>=
 p[["name"]] <- "Murray Stokely"
 p[[ 2 ]] <- 3
-p[[ "email" ]]
+p[["email"]]
 @
 
 Protocol Buffers include a 64-bit integer type, but \proglang{R} lacks native