similar to: R-devel Digest, Vol 179, Issue 7

You can legally cast a function pointer to another function pointer, where the signatures differ. (It is not legal to cast between data and function pointers.) I would make typedefs for the various signatures, as the casting syntax is more readable then. Bill Dunlap TIBCO Software wdunlap tibco.com On Fri, Dec 29, 2017 at 10:13 AM, Therneau, Terry M., Ph.D. < therneau at mayo.edu> wrote:

As things stand now, package tarballs with vignettes that are built with R-devel will not install in R 3.4.x, so CRAN can't accept them and someone running R CMD check --as-cran should be told that. A WARNING is appropriate. Most likely what will change soon is that build/version.rds will be saved with serialization version = 2 and this warning will not be triggered just by having a vignette.

On 10/01/2018 1:26 PM, Neal Richardson wrote: > Hi, > Since yesterday I'm seeing `R CMD check --as-cran` failures on the > R-devel daily build (specifically, R Under development (unstable) > (2018-01-09 r74100)) for multiple packages: > > * checking serialized R objects in the sources ... WARNING > Found file(s) with version 3 serialization: > ?build/vignette.rds? >

Try changing static void (*fun)() = NULL; to DL_FUNC fun = NULL; Bill Dunlap TIBCO Software wdunlap tibco.com On Fri, Dec 29, 2017 at 5:14 AM, Therneau, Terry M., Ph.D. < therneau at mayo.edu> wrote: > I've recently updated the coxme package, which calls internal routines > from the bdsmatrix package. (It is in fact mentioned as an example of this > in the Extensions

And remove the cast on the return value of R_GETCCallable. And check that your function is found before using it. #include <R.h> #include <Rinternals.h> #include <R_ext/Rdynload.h> void bdsmatrix_prod4(int nrow, int nblock, int *bsize, double *bmat, double *rmat, int nfrail, double *y) { DL_FUNC fun = NULL; if (fun==NULL)

To reduce difficulties for people relying on automated tests set up to build&"check --as-cran" using R-devel (e.g. travis-ci), the default serialization version has been temporarily switched back to 2. Thank you for your patience - according to svn history, the last change of the serialization format happened 16 years ago, and unsurprisingly some practices that developed since

This change poses difficulties for automated build systems such as travis-ci, which is widely used in the R community. In particular because this is a WARNING and not a NOTE this causes all R-devel builds with vignettes to fail, as the default settings fail the build if R CMD check issues a WARNING. The simplest change would be for R-core to change this message to be a NOTE rather than a WARNING,

> On Apr 16, 2018, at 3:20 PM, David Winsemius <dwinsemius at comcast.net> wrote: > >> >> On Apr 16, 2018, at 2:58 PM, Therneau, Terry M., Ph.D. via R-devel <r-devel at r-project.org> wrote: >> >> A user asked me about this and I can't figure it out. >> >> tmt% R >> R Under development (unstable) (2018-04-09 r74565) --

> In general, as a package user, I don't want people to be able to > suppress checks on CRAN. I want things fixed. > > So I am pretty sure there won't ever be a reliable "CRAN-detector" put > into R. It would devalue the brand. > > Duncan Murdoch My problem is that CRAN demands that I suppress a large fraction of my checks, in order to fit within time

I am not in favor of the change, which is a choice of rigor over usability. When I am developing code or functions I agree with this, and I view any warnings from R CMD check about shortened arguments as positive feedback. But 90% of my usage of R is day to day data analysis, interactive, at the keyboard. A lot of data sets that come to me have long variable names. What this change will mean

Hi, Since yesterday I'm seeing `R CMD check --as-cran` failures on the R-devel daily build (specifically, R Under development (unstable) (2018-01-09 r74100)) for multiple packages: * checking serialized R objects in the sources ... WARNING Found file(s) with version 3 serialization: ?build/vignette.rds? Such files are only readable in R >= 3.5.0. Recreate them with R < 3.5.0 or

I've recently updated the coxme package, which calls internal routines from the bdsmatrix package.? (It is in fact mentioned as an example of this in the Extensions manual.) The call connections are a blocks like this, one for each of the 9 called C routines. void bdsmatrix_prod4(int nrow,??? int nblock,?? int *bsize, ??????????????????? double *bmat, double *rmat, ??????????????????? int

?I ended up finding the issue by a focused code review. Once in the past, I had a version that would fail under one architecture but not another, in that case some help from Brian Ripley pointed me to the offending line of C code.?? That line read, but did not write, at an invalid memory location.?? Starting with the question of "what C routines have I added or modified most

Could this be related to "SIGNIFICANT USER-VISIBLE CHANGES The default method for generating from a discrete uniform distribution (used in sample(), for instance) has been changed. This addresses the fact, pointed out by Ottoboni and Stark, that the previous method made sample() noticeably non-uniform on large populations. See PR#17494 for a discussion. The previous method can be requested

FWIW Microsoft provides evaluation version of Windows that can be easily installed using VirtualBox and runs for 180 days. One that I believe is the closest to the CRAN setup (Windows 2008) is: https://www.microsoft.com/en-nz/download/details.aspx?id=11093 You just tell VB to setup a Windows 2008 VM then, select the downloaded ISO as CD-ROM drive and install from it. The installation is fairly

I think it would be a good idea. Several versions of the survival package had a duplicate line in the S3methods, and were missing a line that should have been there, due to a cut/paste error. Terry T. On 03/13/2013 06:00 AM, r-devel-request at r-project.org wrote: > Circa 80 CRAN and core-R packages have duplicate export entries in their NAMESPACE files. E.g., > bit 1.1.9 :

It's hard to diagnose this without your package sources / a reproducible example. Shot in the dark: one thing worth checking is that you don't have an entry in your `.Rbuildignore` that's removing files you don't expect it to (maybe that's causing R to strip out the 'doc/index.html' file) Kevin On Fri, May 15, 2015 at 12:54 PM, Therneau, Terry M., Ph.D. <therneau

On 05/04/2019 10:46 a.m., Therneau, Terry M., Ph.D. wrote: > > > On 4/5/19 9:39 AM, Duncan Murdoch wrote: >> On 05/04/2019 10:19 a.m., Therneau, Terry M., Ph.D. wrote: >>> Duncan, >>> ?? I should have included it in my original note, but >>> >>> ??? ? all.equal(unclass(t0x), unclass(t1x)) >>> >>> returns TRUE as well.? I had

>>> strongly disagree. I'm appalled to see that sentence here. >> > >> > Come on! >> > >>> >> The overhead is significant for any large vector and it is in particular unnecessary since in .C you have to allocate*and copy* space even for results (twice!). Also it is very error-prone, because you have no information about the length of

I don't know of one. If building your own you could use rpart with the "maxdepth=1" as the tool to find the best split at each node. Terry Therneau On 12/20/2012 05:00 AM, r-help-request at r-project.org wrote: > Hi, > > I've searched R-help and haven't found an answer. I have a set of data from which I can create a classification tree using > rpart. However,