On 30 November 2016 at 10:23, Whit Armstrong wrote:
| My point regarding the clang parser is that one really shouldn't have to write
| any R or Rcpp wrappers at all.
Did anybody keep tabs on the related projects by Duncan Temple Lang?
https://github.com/omegahat/RClangSimple
https://github.c
My point regarding the clang parser is that one really shouldn't have to
write any R or Rcpp wrappers at all.
If one directly parses the c++ class then both the R6/RefClass/List (or
whatever implementation one chooses to use) and the C wrappers (which we
will still need as we can't expose the c++
On Mon, Nov 28, 2016 at 9:40 PM, Christian Gunning wrote:
>
> B) Are there any *gotchas* with using Rcpp "modify-in-place" functions
> inside RefClass methods?
>
After some reading, I'm going to answer my own question and point to one
possible *gotcha* that wasn't clear to me at first.
* From h
Whit,
I see that this could be useful in similar situations where Rcpp modules
excels (generating R bindings to existing C++ classes). Language preference
aside, it's less clear to me what advantage this approach (or Rcpp modules)
offers average users over RefClasses + Rcpp functions, where the Re
