similar to: (PR#7326)(inappropriate) manipulation of expression objects

> version _ platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status Under development (unstable) major 2 minor 1.0 year 2004 month 10 day 25 language R > > foo <- expression(alpha, beta, gamma) > foo[2] expression(beta) > foo[2] <- NA > foo ## or str(foo) Segmentation fault (Same behaviour in R 1.9.1)

On an azure centos VM, I can reproduce this bug which reports either: *** caught segfault *** address 0x70000006a, cause 'memory not mapped' (crash) Or incompatible types (from builtin to integer) in subassignment type fix (no crash) Like Gabriel, I could not reproduce the bug on a mac laptop. Both R versions 3.5.1. Travers On Wed, Feb 27, 2019 at 9:08 AM William Dunlap via R-devel

>From the R FAQ Bug reports on contributed packages should be sent first to the package maintainer, and only submitted to the R-bugs repository by package maintainers, mentioning the package in the subject line. and you are NOT the listed maintainer. Do learn to read FAQs before causing unnecessary work for other people (as the R posting guide asks). Please do as the FAQ asks. On

Valgrind (without gctorture) reports memory misuse: % R --debugger=valgrind --debugger-args="--leak-check=full --num-callers=18" ... > x <- 1:200000 > y <- rep(letters[1:5], length(x) / 5L) > for (i in 1:1000) { + # x[y == 'a'] <- x[y == 'b'] + x <- `[<-`(x, y == 'a', x[y == 'b']) + cat(i, '') + } 1 2 3 4 5 6 7 8 9 10

On Fri, 5 Apr 2024 08:15:20 -0400 June Choe <jchoe001 at gmail.com> wrote: > When assigning a list to an out of bounds index (ex: the next, n+1 > index), it errors the same but now changes the values of the vector > to NULL: > > ``` > x <- expression(a,b,c) > x[[4]] <- list() # Error > x > #> expression(NULL, NULL, NULL) > ``` > > Curiously,

On Fri, 5 Apr 2024, Ivan Krylov via R-devel wrote: > On Fri, 5 Apr 2024 08:15:20 -0400 > June Choe <jchoe001 at gmail.com> wrote: > >> When assigning a list to an out of bounds index (ex: the next, n+1 >> index), it errors the same but now changes the values of the vector >> to NULL: >> >> ``` >> x <- expression(a,b,c) >> x[[4]] <-

Hi all, I have a very high dimensional data and apparently there are several columns that contain similar information (some columns are equal). I want to form a matrix/data frame consisting of unique columns. Does anyone have an efficient way of getting out these columns. A small section of the data frame is given below. Thanks for helping. Stephen. > newdata [,1] [,2] [,3] [,4] [,5]

On Fri, Jun 14, 2019 at 6:42 PM Richard M. Heiberger <rmh at temple.edu> wrote: > > This is still not repaired in > R version 3.6.0 Patched (2019-05-17 r76528) > > library(latticeExtra) > > a <- xyplot(1 ~ 1) > > c(a,a) > Warning message: > In formals(fun) : argument is not a function > > Can we have it in R-3.6.1 that Peter just announced? Sorry

On 14/06/2019 9:12 a.m., Richard M. Heiberger wrote: > This is still not repaired in > R version 3.6.0 Patched (2019-05-17 r76528) >> library(latticeExtra) >> a <- xyplot(1 ~ 1) >> c(a,a) > Warning message: > In formals(fun) : argument is not a function > > Can we have it in R-3.6.1 that Peter just announced? That looks like a bug in the latticeExtra

This problem is still present in > version _ platform x86_64-w64-mingw32 arch x86_64 os mingw32 system x86_64, mingw32 status Under development (unstable) major 4 minor 0.0 year 2019 month 12 day 03 svn rev 77513 language R version.string R Under development (unstable)

We've seen the integer overflow problem in ks.test before, easily solved. The help page says x and y must be numeric, so this is user error. I've added tests to the code. Why do people file bug reports without reading the help/man page? On Tue, 14 Jan 2003 bates@stat.wisc.edu wrote: > This was filed as a bug report on the Debian r-base package. It is > more properly a bug

On Fri, Mar 23, 2018 at 7:58 AM, Richard M. Heiberger <rmh at temple.edu> wrote: > The warning message in the last line of this email is incorrect. > This is behavior which Duncan Murdoch labeled a bug in > https://stat.ethz.ch/pipermail/r-help/2017-December/450494.html Yes, sorry, this has been fixed in the r-forge sources for a while now, but I haven't had the time to

> From: rossini@blindglobe.net (A.J. Rossini) > Date: 01 Nov 2000 07:47:21 -0800 [...] > Thanks for the pointer to stack/unstack -- now, having been reminded, > I think I'd seen these float through on the list (still doesn't solve > the missing modeling routines (parametric GLMMs, some of the > econometrics stuff -- does R _easily_ do 3SLS?), but they'll appear >

Do not use R-bugs for reports on compatibility of obselete versiond of packages with unreleased versions of R! You did not give the RODBC version no. The current version, 1.1-3, is compatible with R-devel. 1.1-2 was not (alongside a dozen or so CRAN packages). The only bugs here are in the report. On Thu, 24 Feb 2005 david.whiting@ncl.ac.uk wrote: > Full_Name: David Whiting >

Thank you very much It works perfectly well Have a wonderful day |---------+----------------------------> | | ripley at stats.ox.a| | | c.uk | | | | | | 04/28/03 12:58 PM| | | | |---------+---------------------------->

Thanks, That fixed the problem. Jarek -----Original Message----- From: ripley at stats.ox.ac.uk [mailto:ripley at stats.ox.ac.uk] Sent: Friday, July 15, 2005 11:11 AM To: Tuszynski, Jaroslaw W. Cc: r-devel at stat.math.ethz.ch Subject: Re: [R] Passing character strings from C code to R Reading the posting guide would have shown you that R-help was quite inappropriate, so I have moved this to

After the discussion a while back about how sort inconsistently handles attributes such as dim's, I have taken a closer look and found yet more anomalies. That suggested trying out the principle that sort() should preserve only names (and sort those). Now, sort(partial=) was preserving names and NOT sorting them, and since it was included for efficiency I decided it should just drop

Previously, I've posted queries about this, and thanks to postings and messages in response have recently had some success, to the extent that there is now a package called nlmrt on the R-forge project https://r-forge.r-project.org/R/?group_id=395 for solving nonlinear least squares problems that include small or zero residual problems via a Marquardt method using a call that mirrors the nls()

This is still not repaired in R version 3.6.0 Patched (2019-05-17 r76528) > library(latticeExtra) > a <- xyplot(1 ~ 1) > c(a,a) Warning message: In formals(fun) : argument is not a function Can we have it in R-3.6.1 that Peter just announced? Rich On Mon, Apr 2, 2018 at 4:08 AM Deepayan Sarkar <deepayan.sarkar at gmail.com> wrote: > > On Fri, Mar 23, 2018 at 7:58 AM,

Apart from the inconsistencies, there are two clear bugs here: 1) miscalculating the number of values needed, in the matrix case. E.g. > AA[idx, 1] <- B[1:4] Error in "[<-"(`*tmp*`, idx, 1, value = B[1:4]) : number of items to replace is not a multiple of replacement length although only 4 values are replaced by AA[idx, 1] <- B. 2) the behaviour of the 3D case.