search for: gaslam

On 27 November 2016 at 13:20, Duncan Murdoch wrote: | On 27/11/2016 11:34 AM, brodie gaslam via R-devel wrote: | > Minor issue, but the following changed as of R3.3.2 from: | > | > > a <- function() b() | > > a() | > Error in a() : could not find function "b" | > | > To (at least in R Under development (unstable) (2016-11-20 r71670)): |...

Minor issue, but the following changed as of R3.3.2 from: > a <- function() b() > a() Error in a() : could not find function "b" To (at least in R Under development (unstable) (2016-11-20 r71670)): Error in b() : could not find function "b" Notice the "Error in **b**() :" part. The original error message seems more correct to me, although

Thanks Brodie, that's some nice detective work. If someone wanted to grant me access to Bugzilla, I'll be happy to post the bug and patch there (with your permission Brodie?) and help this bug get fixed. Mike. On Tue., 25 Sep. 2018, 10:53 pm brodie gaslam, <brodie.gaslam at yahoo.com> wrote: > > > For what it's worth the following patch fixes that particular problem on > my system. I have not checked very carefully to make sure this does not > cause other problems, but at a high level it seems to make sense. In this >...

...tml] >> >> The following package was uploaded to CRAN: >> =========================================== >> >> Package Information: >> Package: crayon >> Version: 1.3.4 >> Title: Colored Terminal Output >> Author(s): G?bor Cs?rdi [aut, cre], Brodie Gaslam [ctb] >> Maintainer: G?bor Cs?rdi <mailto:csardi.gabor at gmail.com> >> Suggests: mockery, rstudioapi, testthat, withr >> Description: Colored terminal output on terminals that support 'ANSI' >>??? color and highlight codes. It also works in 'Emacs' ...

> On Fri, 2017-10-20 at 14:01 +0000, brodie gaslam via R-devel wrote: > > I'm thinking of this passage: > > > > > Logical values are sent as 0 (FALSE), 1 (TRUE) or INT_MIN = > > > -2147483648 (NA, but only if NAOK is true), and the compiled code > > > should return one of these three values. (Non-zero va...

On 1/7/20 06:13, brodie gaslam via R-devel wrote: ... > Happy new decade. *** caught segfault *** conflicting decade boundaries Traceback: 1: new_decade <- 2020:2029 2: previous_decade <- 2011:2020 3: previous_previous_decade <- 2001:2010 4: current_millenium <- 2001:3000 5: previous_millenium <-...

...ws PR#17833. * Using tcltk widgets no longer crashes R on Windows. * source(*, echo=TRUE) no longer fails in some cases with empty lines; reported by Bill Dunlap in PR#17769. * on.exit() now correctly matches named arguments, thanks to PR#17815 (including patch) by Brodie Gaslam. * regexpr(*, perl=TRUE) no longer returns incorrect positions into text containing characters outside of the Unicode Basic Multilingual Plane on Windows. -- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark...

On 7/24/23 4:10 AM, Duncan Murdoch wrote: > On 23/07/2023 9:01 p.m., Brodie Gaslam wrote: >> >> >> On 7/23/23 4:29 PM, Duncan Murdoch wrote: >>> The help page for `?gsub` says (in the context of performance >>> considerations): >>> >>> >>> "... just one UTF-8 string will force all the matching to be done in >&...

I noticed some problems that cropped in the latest versions of R-devel (2016-11-08 r71639 in my case) for one of my packages. I _think_ I have narrowed it down to the changes to what gets byte-compiled by default. The following example run illustrates the problem I'm having: compiler::enableJIT(0) fun <- function(x) local(as.list(parent.frame(2))) fun(1) ## $x ## [1] 1 ##

One of the things I often wish R would work with: When calling print() explicitly --- as I do not so rarely, e.g., specifying digits = <nd> --- it sometimes seems awkward that from the printing options() , one can specify 'digits' and it has default digits = NULL which is documented to be equivalent to digits = getOption("digits"), but one cannot specify 'width'

> On Friday, May 15, 2020, 12:13:04 PM EDT, Dirk Eddelbuettel <edd at debian.org> wrote: > On 15 May 2020 at 15:41, Martin Maechler wrote: > | <whining> > | > |??? Why does nobody anymore? help R development by working with > |??? "R-devel", or at least then the alpha, beta and the "RC" > |??? (Release Candidate) versions that we release daily

Hi there, using cbind with a numeric and raw argument produces an incorrect result. I've posted some details below, kind regards, Mike. e.g. > cbind(0, as.raw(0)) [,1] [,2] [1,] 0 6.950136e-310 A longer example shows that the result is not a rounding error, is not consistent, and repeated applications get different results. > cbind(0, as.raw(1:10))

I've found over time that R documentation that comes off as terse at first blush is usually revealed to be precise, concise, and complete on close reading.? I'm sure this is also true of `?findInterval`, but for whatever reason my brain simply refuses to extract meaning from it. Part of the problem may be that we interact with the function via a compressed form of the bounds of the

Currently S3 objects nested in generic vectors cause the tag buffer to be reset.? This feels sub-optimal for those objects that don't have a print method: > list(a=list(b='hello')) $a $a$b???????????????? ### <<<< notice "$a$b" [1] "hello" > list(a=structure(list(b='hello'), class='world')) $a $b?????????????????? ###

> On Wednesday, May 20, 2020, 7:00:09 AM EDT, peter dalgaard <pdalgd at gmail.com> wrote: > > Expected, see FAQ 7.31. > > You just can't trust == on FP operations. Notice also Additionally, since you're implementing a "mean" function you are testing against R's mean, you might want to consider that R uses a two-pass calculation[1] to reduce floating

On Tue, Jan 7, 2020 at 6:14 AM brodie gaslam via R-devel <r-devel at r-project.org> wrote: > > For whatever my 2c are worth I think this would be nice. I'm still uncomfortable at having to call `options` in my package `diffobj` to set output width. Adding a few more cents: It might be worth considering "who" shoul...

...d this to the wishlist item. This all needs to be looked > at together, and nothing is likely to happen until after > vacation/conference season. It will disappear from everyone's radar > if it is just in R_devel. > > Best, > > luke > > On Sun, 14 Jul 2019, brodie gaslam wrote: > >> Luke, thanks for considering the issue. I would like to >> try to separate the problem into two parts, as I _think_ >> your comments address primarily part 2 below: >> >> 1. How can we avoid significant and possibly crippling >> stalls on err...

...-tierney at uiowa.edu> wrote: This is probably best viewed in the context of other issue with displaying calls, such as issues arising from calls constructed in non-standard evaluation contexts. Might be good to move to a wishlist item in bugzilla. Best, luke On Sat, 13 Jul 2019, brodie gaslam via R-devel wrote: > When large calls cause errors R may stall for extended periods.? This > is particularly likely to happen with `do.call`, as in this example > with a 24 second stall: > > ??? x <- runif(1e7) > ??? system.time(do.call(paste0, list(abs, x)))? # intentional er...

Better to add this to the wishlist item. This all needs to be looked at together, and nothing is likely to happen until after vacation/conference season. It will disappear from everyone's radar if it is just in R_devel. Best, luke On Sun, 14 Jul 2019, brodie gaslam wrote: > Luke, thanks for considering the issue.? I would like to > try to separate the problem into two parts, as I _think_ > your comments address primarily part 2 below: > > 1. How can we avoid significant and possibly crippling > ?? stalls on error with these non-standard cal...

I think there is a memory bug in `substr` that is triggered by a UTF-8 corner case: an incomplete UTF-8 byte sequence at the end of a string.? With a valgrind level 2 instrumented build of R-devel I get: > string <- "abc\xEE"??? # \xEE indicates the start of a 3 byte UTF-8 sequence > Encoding(string) <- "UTF-8" > substr(string, 1, 10) ==15375== Invalid read of