Ah, I spoke too soon. I started putting the demo code into a test suite and ran
one check with valgrind and — sure enough — there's def more issues (a cpl
functions) than the overt/easy ones (and, I went back to the check results page
and, also sure enough, they're there, too). They look to be f
Or, a crazy person (me) cld volunteer to keep this running and get it back on
CRAN.
I fixed the severe warning and also added C-side registration code.
The pkg is monolithic but the C code is super straightforward (a is the R code).
Unless someone can think of a reason not to, I can submit thi
On 2019-09-25 3:26 a.m., Martin Maechler wrote:
>> Ben Bolker
>> on Tue, 24 Sep 2019 20:09:55 -0400 writes:
>
> > SuppDists is orphaned on CRAN (and has been since 2013).
> > https://cran.r-project.org/web/checks/check_results_.html
>
> > Oddly, the simulate method for
On 29/09/2019 12:12 p.m., nos...@altfeld-im.de wrote:
Thanks a lot for pointing out the reason
(and yes, I am testing quite to stringent in this case - it's my old testing
disease ;-)
For other readers:
The R-devel NEWS is a good source to find possible change reasons:
https://stat.ethz.ch/R-
Thanks a lot for pointing out the reason
(and yes, I am testing quite to stringent in this case - it's my old testing
disease ;-)
For other readers:
The R-devel NEWS is a good source to find possible change reasons:
https://stat.ethz.ch/R-manual/R-devel/doc/html/NEWS.html
On Sun, 2019-09-29 a
On 29/09/2019 7:55 a.m., nos...@altfeld-im.de wrote:
Hi,
I have a failing unit test in my package tryCatchLog on the CRAN build
infrastructure
(https://cran.r-project.org/web/checks/check_results_tryCatchLog.html)
with "R Under development (unstable) (2019-09-27 r77229)"
and the unit tests just
Hi,
I have a failing unit test in my package tryCatchLog on the CRAN build
infrastructure
(https://cran.r-project.org/web/checks/check_results_tryCatchLog.html)
with "R Under development (unstable) (2019-09-27 r77229)"
and the unit tests just ensures consistent behaviour of R (not of my package)
Dear R developers,
I spotted that R_isNA and R_IsNaN could be improved when applied on a
vector where we could take out small part of their logic, run it once,
and then reuse inside the loop.
I setup tiny plain-C experiment. Taking R_IsNA, R_IsNaN from R's
arithmetic.c, and building R_vIsNA and R_