Thanks, posted to https://github.com/lme4/lme4/issues/412 for further
discussion ...
On Wed, Feb 22, 2017 at 10:03 AM, Therneau, Terry M., Ph.D.
wrote:
> I found this by accident yesterday. The program that crashes is the first
> two lines of the example from the help page for nlmer. That exampl
I found this by accident yesterday. The program that crashes is the first two lines of
the example from the help page for nlmer. That example hasn't changed in a long time, so I
assumed that it is an R-devel issue. It could also be a long latent nlmer bug. The second
run with valgrind is puzzl
On Tue, Feb 14, 2017 at 5:25 PM, Prof Brian Ripley
wrote:
>
> Registration has similar benefits to name spaces in R code:
>
> - it ensures that the routines used by .C, .Call etc are those in your
> package (without needing a PACKAGE argument).
> - it avoids polluting the search space for native
On Wed, 22 Feb 2017 12:22:45 +0200,
Mikko Korpela wrote:
[...]
> When trying to build the vignette from the git version of your package
> (as part of R CMD build), I see the same error message. Investigating
> further, the "tangled" file diveMove.R from
> 'tools::buildVignette("diveMove.Rnw")' h
On 2017-02-19 09:19, Prof Brian Ripley wrote:
On 14/02/2017 16:25, Prof Brian Ripley wrote:
Registration of 'native routines' (entry points in compiled code loaded
into R) has been available for over 14 years,
...
(There are reports that the check in 'R CMD check' on Windows sometimes
fails
On 21/02/17 19:06, Sebastian P. Luque wrote:
Hello,
I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31))
that has not seen any changes since it was last built without problems
in previous R versions. It fails during vignette building with:
---
