Re: [Rd] [External] exists, get and get0 accept silently inputs of length > 1

2020-11-23 Thread luke-tierney
Thanks for the suggestion. In R-devel (as of r79474) exists(), get(), and get0() now signal an error if the first argument has length > 1. This will cause about 30 CRAN packages and possibly a couple of Bioconductor packages to fail under R-devel. getS3method() now also signals an error if the c

Re: [Rd] Two ALTREP questions

2020-11-23 Thread Dirk Eddelbuettel
On 21 November 2020 at 20:56, Jiefei Wang wrote: | Hello, | | I have two related ALTREP questions. It seems like there is no way to | assign attributes to an ALTREP vector without using C++ code. To be more | specifically, I want to make an ALTREP matrix, I have tried the following R | code but

Re: [Rd] .Internal(quit(...)): system call failed: Cannot allocate memory

2020-11-23 Thread Bill Dunlap
The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'

Re: [Rd] .Internal(quit(...)): system call failed: Cannot allocate memory

2020-11-23 Thread Gregory Warnes
Try explicitly deleting large data objects by calling `rm`, then `gc`. On Mon, Nov 23, 2020 at 6:15 AM Tomas Kalibera wrote: > On 11/21/20 6:51 PM, Jan Gorecki wrote: > > Dear R-developers, > > > > Some of the more fat scripts (50+ GB mem used by R) that I am running, > > when they finish they

Re: [Rd] .Internal(quit(...)): system call failed: Cannot allocate memory

2020-11-23 Thread Tomas Kalibera
On 11/21/20 6:51 PM, Jan Gorecki wrote: Dear R-developers, Some of the more fat scripts (50+ GB mem used by R) that I am running, when they finish they do quit with q("no", status=0) Quite often it happens that there is an extra stderr output produced at the very end which looks like this: Warn

[Rd] Different results from 'lm' for different 32-bit Windows versions

2020-11-23 Thread Andreas Fromkorth
Hello, I recently stumbled upon the fact that different 32-bit R Windows versions produce slightly different results when calling 'lm'. More precisely, this seems to be caused by a change in the transition from R 3.2.x to R 3.3.0. A minimal example, for reproducing this is "lm(y~x, data.frame(x