[Rcpp-devel] devtools load_all() and modules

[Dirk Eddelbuettel]

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