> 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.
Hmmmm, interesting. But R CMD install is still fairly slow, right? I guess because you're installing directly from the package dir (and not from a tarball built via R CMD build) it's a bit faster, and only changed files need to be recompiled. You introduce a slight risk of problems caused by build artefacts left by previous runs, but that's probably worth it for the speed (and you know much more about the tradeoffs here than I do). Hadley -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/ _______________________________________________ Rcpp-devel mailing list [email protected] https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
