On 7 November 2018 at 22:53, Barth Riley wrote:
| @Dirk: I didn’t want to overwhelm those on the list with tons of code. Below
is the full source for the function. What else would you need to see?
|
| After clearing my environment variables, I am now getting the following error:
|
| Error in l
On 7 November 2018 at 23:28, Qiang Kou wrote:
| Hi, William,
|
| I think you can send the PR first. It will trigger the unit tests on github.
And running 'R CMD build ...' followed by 'R CMD check ...' on your modified
sources tests them locally. There are equivalent GUI buttons in RStudio you
In my “stupid” (minimal) project, my namespace looks as follows:
useDynLib(StupidRCPP, .registration=TRUE)
exportPattern("^[[:alpha:]]+")
importFrom(Rcpp, evalCpp)
In my main project I include Rcpp in an import() statement in NAMESPACE.
One thing I’m noticing with the minimal project is that I c
Did you remove the .Rbuildignore file? Your problems should not be problems if
that file is configured.
On November 8, 2018 7:10:08 AM PST, Barth Riley wrote:
>In my “stupid” (minimal) project, my namespace looks as follows:
>
>useDynLib(StupidRCPP, .registration=TRUE)
>exportPattern("^[[:alpha:
Thanks. That did the trick. After testing w/my own test harness, I made
sure the unit tests work with a baseline cloned fork.
Then integrated my changes into the fork, re-built/checked with bumped-up
version # and tests all passed again. Pushed fork to github.
I have just created PR #920