<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#3333FF">
Dear Dirk,<br>
<br>
I have now written a patch which incorporates your answer to Hadley
in the Rcpp-package manual. I am attaching the complete *Rnw file.
The diff is below.<br>
<br>
Please let me know your preferred channel for me to submit future
patch suggestions.<br>
<br>
Kind regards,<br>
<br>
+glenn<br>
<br>
########## begin diff output ##################<br>
<br>
233,244d232<br>
< <br>
< \subsubsection{\proglang{C++} development workflow}<br>
< \proglang{R}'s package framework elegantly supports rapid
prototyping and experimental code development. One suggested
workflow tests changes to \proglange{C++} code via<br>
< <<echo=FALSE>>=<br>
< $ R CMD INSTALL mypkg && r -lmypkg -e
'someFunctionToTickle(3.14)'<br>
< @<br>
< <br>
< The second command calls 'r' (littler), not 'R'. Littler is an
alternative front end to GNU R for '#!' (hashbang) scripting. It has
fast start-up times and gives a guaranteed clean slate. The -l
option calls 'library(mypkg)' before executing the \proglang{R}
expression. Littler is available via most Linux distribution's
package management systems. The project homepage is
\href{<a class="moz-txt-link-freetext" href="http://code.google.com/p/littler/">http://code.google.com/p/littler/</a>.}<br>
< <br>
< Alternately, rapid prototyping can be conducted using the
inline package and \Sexpr{cxxfunction}.<br>
< <br>
< <br>
<br>
########## end diff output ##################<br>
<br>
<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th>
<td>Re: [Rcpp-devel] devtools load_all() and modules</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Tue, 20 Mar 2012 12:38:37 -0500</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Dirk Eddelbuettel <a class="moz-txt-link-rfc2396E" href="mailto:edd@debian.org"><edd@debian.org></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td>Hadley Wickham <a class="moz-txt-link-rfc2396E" href="mailto:hadley@rice.edu"><hadley@rice.edu></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:rcpp-devel@r-forge.wu-wien.ac.at">rcpp-devel@r-forge.wu-wien.ac.at</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>On 20 March 2012 at 12:22, Hadley Wickham wrote:
| > For usage beyond what we document and test, you're on your own. If you want
| > to explore usage with devtools and other means, go for it.
| >
| > But I will be unlikely to have time to work this out for you, unfortunately.
|
| Let me flip this around on you - when you're developing a package that
| uses Rcpp, could you outline your workflow? After modifying your R
| and C++ code, what sequence of steps do you take so that you can try
| out the code in an R session? It would be really useful to hear what
| workflow that you (and others) find most helpful.
Sure, very valid question. I tend to do two things:
a) at times experiment/try/play with the inline package and cxxfunction
b) much more often, work with a package where, for force of habit, my
typical workflow often is
$ R CMD INSTALL mypkg && r -lmypkg -e 'someFunctionToTickle(3.14)'
which does a 'library(mypkg)' for me (which is how r resolves the -l
arguments) and then executes the R expression
as I never got really happy with any of the unloading attempts. Littler's r
starts very quickly and gives me a guaranteed clean slate, so I tend to work
from there.
Dirk
--
"Outside of a dog, a book is a man's best friend. Inside of a dog, it is too
dark to read." -- Groucho Marx
_______________________________________________
Rcpp-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rcpp-devel@lists.r-forge.r-project.org">Rcpp-devel@lists.r-forge.r-project.org</a>
<a class="moz-txt-link-freetext" href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel</a>
</pre>
</body>
</html>