[Rd] Altrep and translations (was "[R] Description of error is untranslated when ....")

R-core *and* at first just in a separate branch before being merged in to the main (r-devel) branch. OTOH: There may be good reasons for translations lookup being brittle in case of altrep error messages .. and hence left off purposely? Martin -- Martin Maechler ETH Zurich and R Core Team

Re: [Rd] R 4.4.0 has version of Matrix 1.7-0, but it's not available on CRAN

> Gábor Csárdi > on Fri, 26 Apr 2024 11:55:36 +0200 writes: > I don't know if this is a bug, but it is certainly weird. AFAICT R > 4.4.0 has Matrix 1.7-0. Yes, it *is* available from CRAN: You can see it when looking into the 4.4.0/ , specifically the

Re: [Rd] [External] Re: Repeated library() of one package with different include.only= entries

e *without* tryCatch() as I think the user should choose their own line of action in such cases ... on the help page would then be appropriate. Martin > On Thu, Apr 11, 2024 at 7:37 AM wrote: >> On Thu, 11 Apr 2024, Duncan Murdoch wrote: >> >> >

Re: [Rd] Repeated library() of one package with different include.only= entries

been exercised a lot yet, and limitations as you found them haven't been noticed yet, or at least not noticed on the public R mailing lists, nor otherwise by R-core (?). Your implicitly proposed new feature (or even *changed* default behavior) seems to mak

Re: [R-pkg-devel] Matrix 1.7-0 to be released in March with ABI-breaking SuiteSparse update

n 4.4.0 beta (2024-04-10 r86393) -- "Puppy Cup" Best regards, Martin -- Martin Maechler ETH Zurich and R Core Team > On Mon, 12 Feb 2024, at 6:36 PM, Mikael Jagan wrote: >> Dear users and binary repository maintainers, >> >> We are preparing

Re: [Rd] `as.data.frame.matrix()` can produce a data frame without a `names` attribute

>>>>> Martin Maechler >>>>> on Fri, 22 Mar 2024 11:17:34 +0100 writes: >>>>> Davis Vaughan via R-devel >>>>> on Thu, 21 Mar 2024 15:10:29 -0400 writes: >> Hi all, >> I recently learned that it is pos

Re: [Rd] `as.data.frame.matrix()` can produce a data frame without a `names` attribute

> Davis Vaughan via R-devel > on Thu, 21 Mar 2024 15:10:29 -0400 writes: > Hi all, > I recently learned that it is possible for > `as.data.frame.matrix()` to produce a data frame with 0 > columns that is also entirely missing a `names` attribute, > and I think

Re: [Rd] Spurious warning in as.data.frame.factor()

>>>>> Martin Maechler >>>>> on Fri, 15 Mar 2024 11:24:22 +0100 writes: >>>>> Ivan Krylov >>>>> on Thu, 14 Mar 2024 14:17:38 +0300 writes: >> On Thu, 14 Mar 2024 10:41:54 +0100 >> Martin Maechler wrote

Re: [Rd] Spurious warning in as.data.frame.factor()

>>>>> Ivan Krylov >>>>> on Thu, 14 Mar 2024 14:17:38 +0300 writes: > On Thu, 14 Mar 2024 10:41:54 +0100 > Martin Maechler wrote: >> Anybody trying S7 examples and see if they work w/o producing >> wrong warnings? &g

Re: [Rd] Spurious warning in as.data.frame.factor()

> В Tue, 12 Mar 2024 12:33:17 -0700 > Hervé Pagès пишет: > > The acrobatics that as.data.frame.factor() is going thru in order to > > recognize a direct call don't play nice if as.data.frame() is an S4 > > generic: > >     df <- as.data.frame(factor(11:12)) > > > >    

Re: [R-pkg-devel] [External] [External] RcmdrPlugin.HH_1.1-48.tar.gz

> Duncan Murdoch > on Thu, 7 Mar 2024 05:08:40 -0500 writes: > On 07/03/2024 4:16 a.m., Ivan Krylov wrote: >> On Wed, 6 Mar 2024 13:46:55 -0500 Duncan Murdoch >> wrote: >> >>> is this just a more or less harmless error, thinking >>> that the dot needs

Re: [R-pkg-devel] [External] [External] RcmdrPlugin.HH_1.1-48.tar.gz

> Richard M Heiberger > on Wed, 6 Mar 2024 17:10:50 + writes: > Thank you, I will do that reversion in a few days. (good; I'm sorry I did not see this, before I replied to Joshua's) > Before I do, I want to ask if the default export generated by R CMD build should be

Re: [R-pkg-devel] [External] RcmdrPlugin.HH_1.1-48.tar.gz

> Joshua Ulrich > on Wed, 6 Mar 2024 10:57:28 -0600 writes: > On Wed, Mar 6, 2024 at 1:03 AM Richard M. Heiberger > wrote: >> >> Thank you Duncan, Jeff, Ivan. >> >> I did all that Duncan and Jeff suggested, plus a bit more >> that appeared to be

Re: [Rd] `sort` hanging without R_CheckUserInterrupt()

> Aidan Lakshman > on Wed, 21 Feb 2024 15:10:35 -0500 writes: > Hi everyone, > Just a quick question/problem I encountered, wanted to make sure this is known behavior. Running `sort` on a long vector can take quite a bit of time, and I found today that there don’t seem to

Re: [Rd] Bug in comparison of language objects?

which may have been the intention). > Duncan Murdoch I agree ... (and more do). Thank you for adding it as formal report to R's bugzilla, https://bugs.r-project.org/show_bug.cgi?id=18676 Unfortunately, it triggers something in the (byte) compiler test suite, and (also/hence) will probabl

Re: [Rd] round.Date and trunc.Date not working / implemented

> Jiří Moravec > on Wed, 7 Feb 2024 10:23:15 +1300 writes: > This is my first time working with dates, so if the answer is "Duh, work > with POSIXt", please ignore it. > Why is not `round.Date` and `trunc.Date` "implemented" for `Date`? > Is this because `Date` is

Re: [Rd] [Feature Request] Hide API Key in download.file() / R's libcurl

> Simon Urbanek > on Sun, 4 Feb 2024 10:33:34 +1300 writes: > Any reason why you didn't use quiet=TRUE to suppress that > output? He wrote 'quite' instead of 'quiet' {see cited below '1. quite=1'} and probably never tried the correct spelling ... > There is no

Re: [Rd] [External] Re: zapsmall(x) for scalar x

.d = -5) # the same zapShow(c(x2, 999), mFUN = mF_rob) # same *rounding* as w/ Inf zapShow(c(x2, 999), mFUN = mF_rob, min.d = 3) # the same zapShow(c(x2, 999), mFUN = mF_rob, min.d = 8) # small diff ##--- } > On Mon, Dec 18, 2023, 05:47 Serguei Sokol via R-devel > wrote: > Le 1

Re: [Rd] [External] Re: zapsmall(x) for scalar x

> Serguei Sokol via R-devel > on Mon, 18 Dec 2023 10:29:02 +0100 writes: > Le 17/12/2023 à 18:26, Barry Rowlingson a écrit : >> I think what's been missed is that zapsmall works relative to the absolute >> largest value in the vector. Hence if there's only one >>

[R-pkg-devel] Wrong mailing list: Could the 100 byte path length limit be lifted?

evel, not at all R-package-devel, but be more accurate in what you are talking about, only between the line I could read that it is about some variants of using 'tar'. Best regards, Martin --- Martin Maechler ETH Zurich and R Core team __ R-packag

Re: [R-pkg-devel] Check warning around sprintf: Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system

> Serguei Sokol > on Mon, 20 Nov 2023 10:04:10 +0100 writes: > Le 19/11/2023 à 02:07, Iris Simmons a écrit : >> Yes, the reason for the error is the use of sprintf. You can instead use >> snprintf where n is the maximum number of bytes to write, including the >>

Re: [Rd] [R] Why Rprofile.site is not built with manual installation of R devel in linux?

> Jeff Newmiller via R-help > on Thu, 09 Nov 2023 12:08:07 -0800 writes: > No clue. Tip: R-devel is the mailing list for anything > related to development versions of R. Off-topic here. Yes. Alternatively, as he uses Debian, there's the R-SIG-Debian mailing list, too. -->

Re: [Rd] c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?

for the 'x == NA_LOGICAL' case to_convert_ to NA_complex_. >> >> Yes; "of course" ... still, I did not answer your main question, >> as you did ask +/- if c() should not get an adjustment to the >> new as.complex() |--> (Re = NA, Im = 0) >> behavio

Re: [Rd] c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?

lid open question. ... contrary to what I wrote yesterday; sorry for that "answering a different question". Martin > On Mon, Nov 6, 2023 at 3:08 AM Martin Maechler > wrote: >> >>>>> Michael Chirico >> >>>>> on Sun, 5 Nov 2

Re: [Rd] c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?

> peter dalgaard > on Mon, 6 Nov 2023 11:59:51 +0100 writes: > Hmm, it is not actually at odds with help(c), it is just that the autocoercion works different that it used to, so that > as.complex(NA) == as.complex(NA_real) == NA_real_+0i) > which now differs from >

Re: [Rd] c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?

> Michael Chirico > on Sun, 5 Nov 2023 09:41:42 -0800 writes: > This is another follow-up to the thread from September > "Recent changes to as.complex(NA_real_)". > A test in data.table was broken by the changes for NA > coercion to complex; the breakage essentially

Re: [Rd] 'R CMD INSTALL' keeps going on despite serious errors, and returns exit code 0

> Hervé Pagès > on Fri, 3 Nov 2023 15:10:40 -0700 writes: > Hi list, > Here is an example: >     hpages@XPS15:~$ R CMD INSTALL CoreGx     * installing >     hpages@XPS15:~$ R CMD INSTALL CoreGx >     * installing to library

Re: [R-pkg-devel] Package bioOED has been removed from CRAN just for personal reasons

an to continue to provide substandard service to the people with whom I work because I perpetrated the same mistake in an environment in which no one questioned so effectively my errors. -- Spencer Graves (in a discussion on whether answers on R-help should be more polite) R-help (December 2004) > sg Martin -- Martin Maechler ETH Zurich and R Core team __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Matrix and Mac OS

> Uwe Ligges > on Wed, 1 Nov 2023 06:26:23 +0100 writes: > On 01.11.2023 03:51, Mikael Jagan wrote: >> Thanks.  It seems that we were mistaken in our feeling (IIRC) that it would >> be "OK" to implicitly require '--no-manual' on versions of R from 3.5.0 to >> 4.2.1,

[Rd] warnings() in R-devel: inherits from "warnings" - summary(warnings())

practically all warnings Best regards, Martin -- Martin Maechler ETH Zurich and R Core team __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] dim<-() changed in R-devel; no longer removing "dimnames" when doing dim(x) <- dim(x)

> outermost (ineffective) dimensions: >> x <- array(1:6, dim=c(2,3,1), dimnames=list(c("A", "B"), c("x","y", "z"), "T")) >> S4Arrays:::set_dim(x, 2:3) > x y z > A 1 3 5 > B 2 4 6

Re: [Rd] dim<-() changed in R-devel; no longer removing "dimnames" when doing dim(x) <- dim(x)

> Henrik Bengtsson > on Sun, 29 Oct 2023 10:42:19 -0700 writes: > Hello, > the fix of PR18612 > (https://bugs.r-project.org/show_bug.cgi?id=18612) in > r85380 > (https://github.com/wch/r-source/commit/2653cc6203fce4c48874111c75bbccac3ac4e803) > caused a

Re: [Rd] as.character.Date() strips names in R 4.3.2 beta, bug?

about this if just simply at ?as.character.Date Best regards, Martin -- Martin Maechler ETH Zurich and R Core team __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [R-pkg-devel] Question regarding listing base and recommended packages programmatically and efficiently

>>>>> Henrik Bengtsson >>>>> on Sat, 14 Oct 2023 10:37:14 -0700 writes: > On Sat, Oct 14, 2023 at 5:25 AM Martin Maechler > wrote: >> >> >>>>> Ivan Krylov >> >>>>> on Thu, 12

Re: [R-pkg-devel] Question regarding listing base and recommended packages programmatically and efficiently

> list.files() is faster than that. The above is another issue that we've wanted to improve, as some of you are aware, notably thinking about caching the result .. there has been work on this during the R Sprint @ Warwick a couple of weeks ago, ==> https://github.com/r-devel/r-project-sp

Re: [R-pkg-devel] Question about Clang 17 Error

> Reed A Cartwright > on Wed, 11 Oct 2023 22:25:35 -0700 writes: > Okay, I'll reach out to the CRAN team shortly. > I wanted to run it by the group here first because my interactions with the > CRAN team haven't always been positive and I need to make sure that I'm not

Re: [Rd] About FlexiBLAS in the R-admin docs

R's sources, the latest version hence is always https://svn.r-project.org/R/trunk/doc/manual/R-admin.texi (or "almost always current" at one of its github mirrors ..) Best regards, Martin -- Martin Maechler ETH Zurich and R Core team >> Date: Wed, 27 Sep 2023 15:14:4

Re: [Rd] Subset has No Examples for Vector Data

> Rui Barradas > on Tue, 10 Oct 2023 12:17:19 +0100 writes: > Às 11:00 de 10/10/2023, Dario Strbenac via R-devel escreveu: >> Hello, >> >> Could the documentation page for subset gain an example of how to use it for something other than a data frame or matrix? I

Re: [Rd] as(, "dgTMatrix")' is deprecated.

> Duncan Murdoch > on Tue, 3 Oct 2023 12:59:10 -0400 writes: > On 03/10/2023 12:50 p.m., Koenker, Roger W wrote: >> I’ve been getting this warning for a while now (about >> five years if memory serves) and I’m finally tired of it, >> but also too tired to track it

Re: [Rd] Recent changes to as.complex(NA_real_)

>>>>> Martin Maechler >>>>> on Thu, 28 Sep 2023 12:11:27 +0200 writes: >>>>> Gregory R Warnes >>>>> on Sat, 23 Sep 2023 13:22:35 -0400 writes: > > It sounds like we need to add arguments (with sensible > >

Re: [Rd] Recent changes to as.complex(NA_real_)

> Gregory R Warnes > on Sat, 23 Sep 2023 13:22:35 -0400 writes: > It sounds like we need to add arguments (with sensible > defaults) to complex(), Re(), Im(), is.na.complex() etc to > allow the user to specify the desired behavior. I don't think I'd like such extra

Re: [Rd] Minor bug with stats::isoreg

> Ivan Krylov > on Thu, 28 Sep 2023 00:59:57 +0300 writes: > В Wed, 27 Sep 2023 13:49:58 -0700 Travers Ching > пишет: >> Calling isoreg with an Inf value causes a segmentation >> fault, tested on R 4.3.1 and R 4.2. A reproducible >> example is:

Re: [Bioc-devel] [Rd] is.atomic(NULL) will become FALSE

es already sooner. Best regards, Martin -- Martin Maechler ETH Zurich and R Core team ___ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel

Re: [R-pkg-devel] [Rd] is.atomic(NULL) will become FALSE

I've sent a longish post to the R-devel mailing list with this topic here: https://stat.ethz.ch/pipermail/r-devel/2023-September/082892.html In the mean time, the plan is to effectuate the change in R-devel (the in-development version of R) on Sep.28, ~ 9:30 CEST ( =UTC+2) Martin

[Rd] is.atomic(NULL) will become FALSE

urrent versions of R and will "automatically" continue to work correctly in future versions of R where is.atomic(NULL) will no longer be true. We hope this will help programming safe-ness *and* make learning and teaching of R more consistent. Enjoy using R! Martin -- Martin Maechle

Re: [Rd] Recent changes to as.complex(NA_real_)

>>>>> Hervé Pagès >>>>> on Sat, 23 Sep 2023 16:52:21 -0700 writes: > Hi Martin, > On 9/23/23 06:43, Martin Maechler wrote: >>>>>>> Hervé Pagès >>>>>>> on Fri, 22 Sep 2023 16:55:05 -0700 writes:

Re: [Rd] NROW and NCOL on NULL

> Simone Giannerini > on Sun, 24 Sep 2023 16:57:00 +0200 writes: > Thank you for your comment, On Sat, Sep 23, 2023 at > 9:51 PM Ben Bolker wrote: >> >> This is certainly worth discussing, but there's always a >> heavy burden of back-compatibility; how much

Re: [Rd] Recent changes to as.complex(NA_real_)

nn hypothesis), and typically vice versa. With your proposal, for a (potentially large) vector of complex numbers, after Re(z) <- 1/2 I could no longer rely on Re(z) == 1/2, because it would be wrong for those z where (the imaginary part/ the number) was NA/NaN. Also, in a similar

Re: [Rd] Recent changes to as.complex(NA_real_)

> Mikael Jagan > on Thu, 21 Sep 2023 00:47:39 -0400 writes: > Revisiting this thread from April: > https://stat.ethz.ch/pipermail/r-devel/2023-April/082545.html > where the decision (not yet backported) was made for > as.complex(NA_real_) to give NA_complex_

Re: [Rd] proposal: 'dev.capabilities()' can also query Unicode capabilities of current graphics device

> Trevor Davis > on Thu, 31 Aug 2023 13:49:03 -0700 writes: > Hi, > It would be nice if `grDevices::dev.capabilities()` could also be used to > query whether the current graphics device supports Unicode. In such a case > I'd expect it to return `FALSE` if `pdf()`

[Rd] FYI: daily R source tarballs from ETH: *.xz instead of *.bz2)

A quick notice for anyone who uses cron-like scripts to get R source tarballs from the ETH R/daily/ s: I've finally switched to replace *.bz2 by *.xz which does save quite a bit of bandwidth. Currently, you can see the 2 day old *.bz2 (and their sizes) and compare with the new *.xz one

Re: [Rd] Concerns with SVD -- and the Matrix Exponential

ite matrices with arbitrary symmetric matrices. > but those statements are contradicting with the statements > discussed in your email. I don't think so. I think we all agreed (John Nash, me, Aidan Lakshman), even though focussing on different aspects of your partly incorrect claims. Mar

Re: [Rd] Heads up about documentation-related reports

> Elio Campitelli > on Mon, 14 Aug 2023 17:42:42 -0300 writes: > For the upcoming R Sprint I'm proposing a project to improve documentation > . That's good, thank you. However, do concentrate

Re: [Rd] R 4.3: Change in behaviour of as.character.POSIXt for datetime values with midnight time

character(c(0.5, 0.75, pi)) [1] "0.5" "0.75" "3.14159265358979" whereas format() does not (ensuring resulting strings of the same nchar(.)): > format( c(0.5, 0.75, pi)) [1] "0.50" "0.75" "3.14

Re: [Rd] R 4.3: Change in behaviour of as.character.POSIXt for datetime values with midnight time

uot;} : Currently, this would be "something like" unlist(lapply(x, as.POSIXlt)) well, and then you need to jump a hoop additionally. If you want POSIXct, like this : .POSIXct(unlist(lapply( * , as.POSIXct For your example ch <- c("1975-01-0

Re: [Rd] Improving user-friendliness of S4 dispatch failure when mis-naming arguments?

you only check in case of English ...}. > but I don't suppose a full patch would be dramatically different from the > above. I agree: The patch looks to make sense to me, too, while I'm not entirely sure about the extra call. = FALSE (which I of course understand you'd prefer for t

Re: [Rd] hist(..., log="y")

> Ott Toomet > on Sat, 5 Aug 2023 23:49:38 -0700 writes: > Sorry if this topic has been discussed earlier. > Currently, hist(..., log="y") fails with >> hist(rexp(1000, 1), log="y") > Warning messages: 1: In plot.window(xlim, ylim, "", ...) : > nonfinite axis=2

Re: [Rd] Concerns with SVD -- and the Matrix Exponential

> J C Nash > on Sun, 16 Jul 2023 13:30:57 -0400 writes: > Better check your definitions of SVD -- there are several > forms, but all I am aware of (and I wrote a couple of the > codes in the early 1970s for the SVD) have positive > singular values. > JN Indeed.

Re: [Rd] [R] Errors in "An introduction to R"

> Ivan Krylov > on Mon, 10 Jul 2023 18:37:30 +0300 writes: > Dear Jarkko, Thank you for spotting these problems and > suggesting fixes for them! I am forwarding your e-mail to > the R-devel mailing list (removing the R-help list, which > is for different kind of R

Re: [R-pkg-devel] Is it a wrong assumption that ${R_HOME}/lib always exists?

ora/Redhat-only "flexiblas" approach, with which I can nicely switch the versions of BLAS and Lapack libraries that R works with from within R. As that version of R is not "shared", i.e., no libR.so , *and* gets both its BLAS and Lapack libraries from "external" (not from

Re: [Rd] logic tweak needed for as.data.frame. deprecation warning

> Mikael Jagan > on Thu, 6 Jul 2023 11:32:00 -0400 writes: > Continuing the thread started on R-package-devel, here: > https://stat.ethz.ch/pipermail/r-package-devel/2023q3/009307.html > The logic of the now soft-deprecated as.data.frame., >>

Re: [R-pkg-devel] Warning 'as.data.frame.POSIXct()' is deprecated

re a question for R-devel though. Indeed. ... and so I've sent a long reply to you, Enrico, Vincent *AND* the R-devel mailing list. In its archives you see it here https://stat.ethz.ch/pipermail/r-devel/2023-July/082725.html With thanks to Vincent, Tim, Enrico, (and Mikael who started

Re: [Rd] Warning 'as.data.frame.POSIXct()' is deprecated

l, ...) >> if (!optional) >> names(value) <- deparse1(substitute(x)) >> value >> } >> >> >> Kind regards >> Enrico Indeed, thank you, Enrico! That's another such case, that my "hack" (see above) overlook

Re: [Rd] Installation of R-4.3.1 with intel 2022

> Giuseppe Calò > on Thu, 22 Jun 2023 16:30:03 +0200 writes: > yes I think it is caused by the absence of matther in glibc. To compile R with icc I disabled matther (with gcc matherr is self disabled). Is it safe to keep it disabled matherr? Others, e.g., Tomas, is much more

Re: [Rd] New behavior when running script in package directory?

> Mikael Jagan > on Wed, 21 Jun 2023 12:41:02 -0400 writes: > Surely this behaviour is just a case of ESS being "too clever", sourcing > *.R files in special way when it detects that a file belongs to a package > (loading dependencies automatically, etc.)? > The

Re: [Rd] Installation of R-4.3.1 with intel 2022

> Giuseppe Calò > on Thu, 22 Jun 2023 14:52:00 +0200 writes: > Hello Martin, this is output > R version 4.3.1 (2023-06-16) -- "Beagle Scouts" > Copyright (C) 2023 The R Foundation for Statistical Computing > Platform: x86_64-pc-linux-gnu (64-bit) [.]

Re: [Rd] Installation of R-4.3.1 with intel 2022

: int 8 > $ sizeof.time_t: int 8 > $ longdouble.eps : num 1.08e-19 > $ longdouble.neg.eps : num 5.42e-20 > $ longdouble.digits: int 64 > $ longdouble.rounding : int 5 > $ longdouble.guard : int 0 > $ l

Re: [Rd] Installation of R-4.3.1 with intel 2022

sessionInfo(), the output of str(.Machine) maybe interesting. Once I'd see these, I might have to ask further questions (possibly off-mailinglist), so it'd be good if you keep the R "installation" in '/juno/opt/sources/R/R-4.3.1-intel21/ for minor "experiments

Re: [Rd] codetools wrongly complains about lazy evaluation in S4 methods

>>>>> Martin Maechler >>>>> on Fri, 16 Jun 2023 11:41:12 +0200 writes: >>>>> Mikael Jagan >>>>> on Thu, 15 Jun 2023 22:00:45 -0400 writes: >> On 2023-06-15 5:25 pm, Hervé Pagès wrote: >>> Oh but I se

Re: [Rd] codetools wrongly complains about lazy evaluation in S4 methods

> Mikael Jagan > on Thu, 15 Jun 2023 22:00:45 -0400 writes: > On 2023-06-15 5:25 pm, Hervé Pagès wrote: >> Oh but I see now that you've already tried this in your >> R/AllGenerics.R, sorry for missing that, yes, this one: setGeneric("qr.X", function(qr,

Re: [Rd] infelicity in `na.print = ""` for numeric columns of data frames/formatting numeric values

> Ben Bolker > on Sat, 3 Jun 2023 13:06:41 -0400 writes: > format(c(1:2, NA)) gives the last value as "NA" rather than > preserving it as NA, even if na.encode = FALSE (which does the > 'expected' thing for character vectors, but not numeric vectors). > This was

Re: [Rd] bug in na.contiguous? Doesn't give the first tied stretch if it is at the start

> Georgi Boshnakov > on Thu, 1 Jun 2023 22:00:39 + writes: > Hi. > The description of na.contiguous says: > "Find the longest consecutive stretch of non-missing values in a > time series object. (In the event of a tie, the first such > stretch.)" > But

Re: [Rd] why does [A-Z] include 'T' in an Estonian locale?

> Ben Bolker > on Tue, 30 May 2023 11:45:20 -0400 writes: > Inspired by this old Stack Overflow question > https://stackoverflow.com/questions/19765610/when-does-locale-affect-rs-regular-expressions > I was wondering why this is TRUE: > Sys.setlocale("LC_ALL",

Re: [R-pkg-devel] help fixing CRAN package sos-now fails on GitHub

> Duncan Murdoch > on Mon, 22 May 2023 15:38:10 -0400 writes: > On 22/05/2023 3:07 p.m., Ivan Krylov wrote: >> I fed your vignette to R CMD Sweave, and here's the >> relevant fragment from the resulting *.tex file: >> >>> This returned a {\tt "findFn"} object

Re: [Rd] range() for Date and POSIXct could respect `finite = TRUE`

so that R developers of other similar classes could also easily make range(*, finite=TRUE) "work" for their class objects. Martin > On Fri, May 19, 2023 at 8:30 AM Martin Maechler > wrote: >> >>>>> Bill Dunlap >> >>>>

Re: [Bioc-devel] issue with .local() hack used in S4 methods

> Hervé Pagès > on Fri, 19 May 2023 11:43:50 -0700 writes: > Hi, > Just ran across this: >     foo <- function(x, ..., z=22) z >     setMethod("foo", "character", function(x, y=-5, z=22) y) >     # Creating a generic function from function ‘foo’ in the global

Re: [Rd] range() for Date and POSIXct could respect `finite = TRUE`

, character *and* raw, the latter really debatable - but *not* in this thread). So, allows.infinite(x) would *not* vectorize but return TRUE or FALSE (and typically not NA ..), in some sense being a property of class(x) only. > On Thu, May 11, 2023 at 1:49 AM Martin Maechler > wr

Re: [R-pkg-devel] Intrinsic UTF-8 use in aspired CRAN package

> Schuhmacher, Dominic > on Wed, 17 May 2023 12:05:49 + writes: > Dear list, I have a package > https://github.com/dschuhmacher/kanjistat whose very > purpose depends on working with Japanese kanji characters > (in UTF-8 encoding). Such characters appear vitally

Re: [Rd] range() for Date and POSIXct could respect `finite = TRUE`

hich is TRUE where x[i] is not NA/NaN/+Inf/-Inf .. *and* is.infinite := Negate(is.finite){or vice versa if you prefer}. I agree that this may be useful somewhat more generally than just for range() methods. What do others think? Martin > On Thu, May 4, 2023 at 5:29 AM Martin Maechl

Re: [R-pkg-devel] Please install cmake on macOS builders

>>>>> Martin Maechler >>>>> on Wed, 10 May 2023 21:31:29 +0200 writes: >>>>> Dirk Eddelbuettel >>>>> on Wed, 10 May 2023 07:01:37 -0500 writes: >> Simon, >> Explicitly declaring &g

Re: [R-pkg-devel] Please install cmake on macOS builders

k > -- > dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- Martin Maechler ETH Zurich and R Core team __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [Bioc-devel] BiocManager::install

velopers need a lot of stamina if their package depends (directly or recursively) on a Bioc package which is really unfortunate and tends to put the Bioconductor project in a shady light it really has not deserved at all! Martin -- Martin Maechler ETH Zurich and R Core team >> Il g

Re: [Rd] save.image Non-responsive to Interrupt

interrupt happens. For example, transfers >> between a > client and a server are no longer atomic at >> this level, which means we > might end up in a corrupt >> state. This may, for instance, happen to > database >> transactions, and PSOCK pa

Re: [Rd] range() for Date and POSIXct could respect `finite = TRUE`

ke classes to provide their own range() method as a 1-liner *and* be future-consistent with the default method.. > On Sat, Apr 29, 2023 at 4:47 PM Martin Maechler > wrote: >> >> >>>>> Davis Vaughan via R-devel >> >>>>>

Re: [Rd] save.image Non-responsive to Interrupt

> Ivan Krylov > on Tue, 2 May 2023 14:59:36 +0300 writes: > В Sat, 29 Apr 2023 00:00:02 + > Dario Strbenac via R-devel пишет: >> Could save.image() be redesigned so that it promptly responds to >> Ctrl+C? It prevents the command line from being used for a number

Re: [Rd] range() for Date and POSIXct could respect `finite = TRUE`

> Davis Vaughan via R-devel > on Fri, 28 Apr 2023 11:12:27 -0400 writes: > Hi all, > I noticed that `range.default()` has a nice `finite = > TRUE` argument, but it doesn't actually apply to Date or > POSIXct due to how `is.numeric()` works. Well, I think it would /

Re: [Rd] Possible inconsistency between `as.complex(NA_real_)` and the docs

> Hi all, > > Surprisingly (at least to me), `as.complex(NA_real_)` results in > `complex(real = NA_real_, imaginary = 0)` rather than `NA_complex_`. Well, the logic here is really the mathematical equivalence: if you turn a real number x in to a complex one, say z, then z = x + i * 0 ,

Re: [Rd] Confusion about ks.test() handling of ties and exact vs approximate results

> Karolis Koncevičius > on Fri, 21 Apr 2023 11:32:41 +0300 writes: > Hello, > Today I was investigating ks.test() with two numerical arguments (x and y) and was left a bit confused about the policy behind handling ties. > I might be missing something, so sorry in

Re: [Rd] Error message for infinite probability parameters in rbinom() and rmultinom()

> Christophe Dutang > on Sat, 8 Apr 2023 14:21:53 +0200 writes: > Dear all, > Using rmultinom() in a stochastic model, I found this function returns an error message 'NA in probability' for an infinite probability. > Maybe, a more precise message will be helpful when

Re: [Rd] Query: Could documentation include modernized references?

ests. And maybe don't do any > until you hear from a member of R Core that they're > willing to participate in this, because they certainly > don't accept all suggestions. > Duncan Murdoch Thanks a lot, Duncan, for this (as usual fro

Re: [Rd] make file.rename return invisible

y safe use (in scripts run automatically, ..) should happen inside if (!file.rename(a,b)) stop("Could not successfully rename ", a, " to ", b) anyway... and indeed it's much much less confusing for people debugging such code that functions behave normally, i.e., the user

Re: [Rd] Multiple Assignment built into the R Interpreter?

> Sebastian Martin Krantz > on Sat, 11 Mar 2023 11:04:54 +0200 writes: [] > But maybe this has already been discussed here and already > decided against. In that case, a way to browse R-devel > archives to find out would be nice. > Best regards, >

Re: [Rd] confusing all.equal output

>>>>> peter dalgaard >>>>> on Thu, 2 Mar 2023 19:47:59 +0100 writes: > I believe the wording goes back to Martin Maechler many > moons ago (AFAICT towards the end of the last millennium.) > We might leave it to him to change it?

Re: [Rd] transform.data.frame() ignores unnamed arguments when no named argument is provided

is often not really feasible anyway ..), but somewhat experienced useRs should know about options(warn = 1) # or options(warn = 2) # plus options(error = recover) # or tryCatch( ..., warning = ..) or {even more} Martin -- Martin Maechler ETH Zurich and R Core team __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Compilation Error when DEBUG_approx Toggled on in RISC-V

> Jane He > on Thu, 23 Feb 2023 15:33:23 -0800 writes: > Hi all, > While compiling R to RISC-V64 architecture and debugging in R's C source > codes, I think I have found a small bug. Can anyone please verify whether > it is a real bug? > The possible bug lies in

Re: [R-pkg-devel] Package submission rejected as it fails checks on Debian

> Spencer Graves > on Tue, 21 Feb 2023 05:25:39 -0600 writes: > On 2/21/23 2:34 AM, Vasileios Nikolaidis wrote: >> Yes, with all this I can think where I may have messed up. So thanks for >> the help, at least it verified it is indeed an issue with the code. As >>

Re: [Rd] uniroot violates bounds?

>>>>> Martin Maechler on Mon, 20 Feb 2023 19:25:02 +0100 writes: >>>>> Serguei Sokol via R-devel >>>>> on Mon, 20 Feb 2023 10:59:22 +0100 writes: >> Le 18/02/2023 à 21:44, J C Nash a écrit : >>> I wrote first cut at u

Re: [Rd] uniroot violates bounds?

> Serguei Sokol via R-devel > on Mon, 20 Feb 2023 10:59:22 +0100 writes: > Le 18/02/2023 à 21:44, J C Nash a écrit : >> I wrote first cut at unirootR for Martin M and he revised and put in >> Rmpfr. >> >> The following extends Ben's example, but adds the unirootR

Re: [Rd] Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '' if an environment variable contains \xFF

> Tomas Kalibera > on Tue, 31 Jan 2023 10:53:21 +0100 writes: > On 1/31/23 09:48, Ivan Krylov wrote: >> Can we use the "bytes" encoding for such environment variables invalid >> in the current locale? The following patch preserves CE_NATIVE for >> strings valid in the

Re: [Rd] memory leak in png()

> Tim Taylor > on Tue, 17 Jan 2023 13:39:01 + writes: > On 17/01/2023 13:06, Duncan Murdoch wrote: >> I don't have a valgrind-capable version of R, but I'd be interested to >> see whether this is a one-time loss, or repeated.  That is, do you get a >> much

  1   2   3   4   5   6   7   8   9   10   >