similar to: Attributes of 1st argument in ...

When the 'by' function forms subsets, are the rows in the same order as they are in the original data frame? For example, I want to use 'by' to calculate cumulative sums of a value 'v' by date 'd' for different levels of a factor 'f': >

Hello: I am building R 2.15.1 from source on a Windows 7 machine with the x64 toolset, MixTeX, and InnoSetup per http://cran.r-project.org/bin/windows/Rtools/. I obtained the source for 2.15.1 via svn from https://svn.r-project.org/R/branches/R-2-15-branch/. This is my first try building R from source. The build seems to go far, then terminates with "undefined exports: .M.classEnv" from

Sirs: My validity function did not run when my class contains="matrix". But if I first define the class with contains="numeric", then define it again with contains="matrix", validity runs. Here's the session: > f <- function(object) "BAD CLASS" # force error to > setClass("A", contains="matrix", validity=f) [1]

Hello:I am trying to match the value 0.3 in the sequence seq(.2,.3). I get > 0.3 %in% seq(from=.2,to=.3) [1] FALSE Yet > 0.3 %in% c(.2,.3) [1] TRUE For arbitrary sequences, this "invisible .3" has been problematic. What is the best way to work around this? Thank you. Dan [[alternative HTML version deleted]]

On 02/03/2020 3:24 a.m., Martin Maechler wrote: >>>>>> robin hankin >>>>>> on Sun, 1 Mar 2020 09:26:24 +1300 writes: > > > Thanks guys, I guess I should have referred to FAQ 7.31 > > (which I am indeed very familiar with) to avoid > > misunderstanding. I have always used dput() to clarify > > 7.31-type

Thanks guys, I guess I should have referred to FAQ 7.31 (which I am indeed very familiar with) to avoid misunderstanding. I have always used dput() to clarify 7.31-type issues. The description in ?dput implies [to me at any rate] that there will be no floating-point roundoff in its output. I hadn't realised that 'deparsing' as discussed in dput.Rd includes precision roundoff issues.

Dear List, I'm struggling with the signature writing cbind/rbind functions for a S4 class. First of all, I'm very happy that it is now possible to dispatch on ... I follow the example for "paste" in ?dotMethods, which works as far as this: ### start example setClass ("cbtest", representation = representation (data = "data.frame"),

Hi, The following function works, but is there a neater way to write it? f = function(x,...) { # return a character vector of the arguments passed in after 'x' gsub(" ","",unlist(strsplit(deparse(substitute(list(...))),"[(,)]")))[-1] } > f(x,a,b,c*d) [1] "a" "b" "c*d" > Thanks. [[alternative HTML

Hi, All: ????? How can I get the names of all the arguments in dots(...)? ????? I'm able to get the name of the first argument but not the second: deparseDots <- function(...){ ? deparse(substitute(...)) } a <- 1 b <- 2 deparseDots(a, b) [1] "a" ????? I'd like to get c('a', 'b'). ????? Thanks, ????? Spencer Graves > sessionInfo() R

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 error ??? ## Error in (function (..., collapse = NULL)? : ??? ##?? cannot coerce type 'builtin' to vector of type 'character' ??? ##

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 calls. 2. What is the best way to view these non-standard calls. I agree that issue 2. requires further thought and discussion under a

On 21/02/18 11:36, Spencer Graves wrote: > Hi, All: > > > ????? How can I get the names of all the arguments in dots(...)? > > > ????? I'm able to get the name of the first argument but not the second: > > > > deparseDots <- function(...){ > ? deparse(substitute(...)) > } > a <- 1 > b <- 2 > deparseDots(a, b) > [1]

We also have a few other suggestions and wishes about backtrace storage and display on the one hand, and display of constructed calls on the other hand. Perhaps it would be better to open a different wishlist item for traceback() to keep the discussions focused? FWIW I think deparsing backtraces lazily is a great idea. Displaying 1 line per call by default in interactive sessions, while being

Hi all, Why I am getting, Error: evaluation nested too deeply: infinite recursion / options(expressions=)? Thanks in advance! func <- Vectorize(function(x, a, sad, trunc=0, ...) { result <- function(x) { f1 <- function(n) { dcom <- paste("d", deparse(substitute(sad)), sep="") dots <- c(as.name("n"), list(...)) f <-

I downloaded R v2.1.1 earlier this morning to compile under Fedora Core 4. It compiled without incident, but 'make check' failed. Below is the relevant part of its report. Is this a known problem? I used a locally compiled version of GCC v4.0.0 that reports [kent at d89h102 R-2.1.1]$ gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.0.0/configure

On 20/02/2018 5:47 PM, Rolf Turner wrote: > On 21/02/18 11:36, Spencer Graves wrote: >> Hi, All: >> >> >> ????? How can I get the names of all the arguments in dots(...)? >> >> >> ????? I'm able to get the name of the first argument but not the second: >> >> >> >> deparseDots <- function(...){ >> ?

Hi Tim, I have also asked a similar question a couple of months ago, and someone else did the same recently, maybe on r-devel. We received no "official" response, but Deepayan Sarkar (R Core Team member) claimed that: " There is no documented reason for this to work (AFAIK), so again, I would guess this is a side-effect of the implementation, and not a API feature you should

Has the CentOS logo disappeared from CentOS-7? I thought the logo in CentOS-6 was very pleasant. Also I liked the way in which one increasing circle inside another showed how the boot was progressing. The dots going round and round in Microsoft fashion in CentOS-7 is a retrograde step, I think. One always has the fear it might continue forever. -- Timothy Murphy gayleard /at/ eircom.net School

There seems to be a bug arising when using multiple S4 generics with "..." as the signature. The following code works as expected: ############################################################## > setGeneric("rbind", function(..., deparse.level=1) standardGeneric("rbind"), + signature = "...") Creating a generic for "rbind" in

My points: - The 'withCallingHandlers' construct that is used in current 'stopifnot' code has no effect. Without it, the warning message is the same. The overridden warning is not raised. The original warning stays. - Overriding call in error and warning to 'cl.i' doesn't always give better outcome. The original call may be "narrower" than 'cl.i'. I