similar to: summary.default & is.recursive (PR#221)

I'm moving this part of an on-going discussion to r-devel because I think I've uncovered a bug: >summary.default : How is yours different from R's (I didn't try to find out) > If it has an advantage you should post to R-devel as a proposal I did propose it along time ago, but ... The fix was for a bug that Splus 3.2 and 3.3 have. It does not work properly with lists

A slightly revised version of my DSE package for multi-variate time series analysis is now available at <www.bank-banque-canada.ca/pgilbert>. This version works with R 0.90.1 (and not with R 90.0 or earlier versions). It can also be installed with install.packages(c("syskern", "tframe", "dse"),

A slightly revised version of my DSE package for multi-variate time series analysis is now available at <www.bank-banque-canada.ca/pgilbert>. This version works with R 0.90.1 (and not with R 90.0 or earlier versions). It can also be installed with install.packages(c("syskern", "tframe", "dse"),

On Sat, Oct 15, 2016 at 2:00 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Michael Lawrence <lawrence.michael at gene.com> >>>>>> on Wed, 12 Oct 2016 15:21:13 -0700 writes: > > > Thanks, this was what I expected. There is a desire to > > eliminate the usage of pairlist from user code, which > >

Thanks, this was what I expected. There is a desire to eliminate the usage of pairlist from user code, which suggests the alternative of allowing for function arguments to be stored in lists. That's a much deeper change though. On Wed, Oct 12, 2016 at 12:31 PM, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: > Michael, thanks for this info. > > I've stumbled upon

Hi Henrik, It would help to understand your use case for pairlists. Thanks, Michael On Wed, Oct 12, 2016 at 9:40 AM, Michael Lawrence <michafla at gene.com> wrote: > The coercion is probably the most viable workaround for now, as it's > consistent with what happens internally for calls. All pairlists/calls > are converted to list for subassignment, but only calls are

Dear list, I think I just stumbled across a bug in either 'relist()' and/or 'as.relistable()'. It seems that 'pairlists' can only be un- and relisted as long as they're not nested: Good: a <- as.relistable(as.pairlist(list(a=1, b=2))) a <- unlist(a) relist(a)# Works Bad: a <- as.relistable(as.pairlist(list(a=1, b=2, c=list(c.1=1, c.2=2)))) a <- unlist(a)

> -----Original Message----- > From: Luke Tierney [mailto:luke at stat.uiowa.edu] > R does not provide a pairlist data structure. This creates a dilemma > when translating some list-based xlispstat code, or, more > importantly, when implementing an algorithm for which parilists are > the natural data structure to use. > ... > Pairlists were and still are used internally

I would like to create a vector of pairlist (flag, binary_value) like: (variable ="TrendOff", value = 0) (variable ="MOdwt", value = 1) (variable ? "ZeroPadding", value =1) ................................................ I tried the following syntax but the emcompassing list (that I called "flags") is not made up of pairlists. Instead it

Hi, A common idiom in the R sources is to convert objects between LANGSXP and LISTSXP by using SET_TYPEOF. However, this is soon going to be disallowed in packages. From what I can see, there isn't currently a direct way to convert between these two object types using the available API. At the R level, one can convert calls to pairlists with: >

Hi, ?pairlist gives no explanation about what exactly is the difference between a pairlist and a list (except that a pairlist of length 0 is 'NULL'). So, what's a pairlist? class(.Options) [1] "pairlist" Some strange things about the "pairlist" type: > showClass("pairlist") Error in getClass(Class) : "pairlist" is not a defined class

Hi, I seem to not be able to assign NULL to an element of a pairlist without causing it to be coerced to a plain list. For example: > x <- pairlist(1, 2) > class(x) [1] "pairlist" > x[1] <- list(NULL) > class(x) [1] "list" This actually true for all [()<- assignments regardless of list value, e.g. > x <- pairlist(1, 2) > x[1] <- list(0) [1]

Hello, Sorry a second time again, Maybe I have to add that I'm running R under Windows 2000/XP, and that the download works properly under 1.062 but not under 1.070. Diethelm >Date: Tue, 10 Jun 2003 19:25:33 +0200 >To: r-devel@stat.math.ethz.ch >From: Diethelm Wuertz <wuertz@itp.phys.ethz.ch> >Subject: dse package - load failure >Cc: pgilbert@bank-banque-canada.ca

Inspired by the exchange between Rolf Turner and Wacek Kusnierczyk, I thought I'd clear up for myself the exact relationship among the various sequence concepts in R, including not only generic vectors (lists) and atomic vectors, but also pairlists, factor sequences, date/time sequences, and difftime sequences. I tabulated type of sequence vs. property to see if I could make sense of all

Inspired by the exchange between Rolf Turner and Wacek Kusnierczyk, I thought I'd clear up for myself the exact relationship among the various sequence concepts in R, including not only generic vectors (lists) and atomic vectors, but also pairlists, factor sequences, date/time sequences, and difftime sequences. I tabulated type of sequence vs. property to see if I could make sense of all

And a last post from Paul Gilbert. Thanks to all! This disscusion was really beneficial for me! -----Original Message----- From: Paul Gilbert [mailto:pgilbert at bank-banque-canada.ca] Sent: sre 2005-06-08 21:01 To: Gorjanc Gregor Subject: Re: [R] Random seed problem in MCMC coupling of chains Gorjanc Gregor wrote: > Thanks to Paul and Gabor for additional tips/examples. Actually, I find

Tested in R 2.8.1 Windows > ff <- formals(function(x)1) > ff1 <- as.list(function(x)1)[1] # ff1 acts the same as ff in the examples below, but is a list rather than a pairlist > dput( ff , control=c("warnIncomplete")) list(x = ) This string is not parsable, but dput does not give a warning as specified. > dput( ff ,

the help page says: 'is.list' returns 'TRUE' iff its argument is a 'list' _or_ a 'pairlist' of 'length' > 0, whereas 'is.pairlist' only returns 'TRUE' in the latter case. does the "latter case" mean a 'pairlist' of 'length' > 0? but > is.pairlist(pairlist()) [1] TRUE > length(pairlist())

This code which has worked for years in R but fails under R-devel: > R.version.string [1] "R Under development (unstable) (2012-07-25 r59963)" > > n <- 3 > f <- function(x) {} > formals(f) <- rep(formals(f), n) ## Error in rep(formals(f), n) : replication of pairlists is defunct The message suggests that the change was intentional. Why was this functionality

Reading the body of function 'AnswerType' in bind.c, called from 'do_c' and 'do_unlist', I notice that EXPRSXP and VECSXP are handled identically in the recurse = TRUE case. A corollary is that c(recursive = TRUE) and unlist(recursive = TRUE) treat expression vectors like expression(a, b) as lists of symbols and calls. And since they treat symbols and calls as