search for: ellipsis

Hi Everyone, When I have a load of functions which have various arguments passed via the ellipsis argument it keeps on assigning them as symbol making them unusable to the function. My current work around involves using do.call but this is rather cumbersome. Does anyone know why it suddenly changes the types to symbol and if there is a way to get the actual data pointed to by the symbol? (I h...

Hi, I'm confused about the use of ellipsis in function arguments. I'm trying to write a wrapper for plot to automate the combination of plot() and points() calls for a data.frame. Some arguments seem to get passed through to the inner plot, while others cause an error: Error in eval(expr, envir, enclos) : ..1 used in an incorrect c...

...(~ RHEL-4), kernel-2.6.9-11.EL, samba-client-3.0.10-1.4E, rsync-2.6.3-1, LANG=en_US.UTF-8. NT4 shares are mounted on the server and rsynced to local disk. This setup is working pretty well, however on the NT box there are some files with names containing odd characters like accented characters and ellipsis. I'm a bit at a loss as to the correct settings of the smbmount iocharset and codepage parameters to use, and whether the display charset and unix charset options in smb.conf are relevant to the mounts. I've setup a test share. An ls in smbclient gives me the correct output in a gnome-term...

...14 [ 6,] 3 8 14 [ 7,] 1 7 15 [ 8,] 1 8 15 [ 9,] 2 7 15 [10,] 2 8 15 [11,] 3 7 15 [12,] 3 8 15 </fantasy> One object is to have b <- c(0,1) and then ntuple(b,b,b,b,b,b,b,b) will generate all 256 distinct bytes. I tried to use the ellipsis argument "..." with no success (because it takes only named arguments). Any help anyone? While I'm writing, my meshgrid() below works as per octave's, but it's a bit clunky. Is there anything better? This is the only thing I've found so far that Octave can do that I ca...

...nel.barchart(x, y, ...) } )) } I get: barchart(a ~ b, data = x, groups = c, panel = function(x, y, ...) { panel.barchart(x, y, a ~ b, data = x, groups = c) }) I'm not sure if this is the cause of above error but this would mean that the ellipsis in panel.barchart gets wrongly expanded with the contents of the arguments given to f.barchart and not the panel function. Is there a way to avoid this problem? How can I make the function work? I use R 2.10.1 @ win32. Regards, Tom

Thanks all, this was very helpful. Peter's finding - dots2() below - is indeed interesting - I'd be curious to learn what goes on there. The different alternatives perform approximately the same; dots1 <- function(...) as.list(substitute(list(...)))[-1L] dots2 <- function(...) as.list(substitute(...())) dots3 <- function(...) match.call(expand.dots = FALSE)[["..."]]

Hi In addition to the inconsistency in make.names(), the text in ?Reserved seems incomplete: "Reserved words outside quotes are always parsed to be references to the objects linked to in the ?Description?, and hence they are not allowed as syntactic names (see make.names). They **are** allowed as non-syntactic names, e.g. inside backtick quotes." `..1` and `...` are allowed for

I want to see all str(demo1); 'data.frame': 24 obs. of 4 variables: $ id : int 1 1 1 2 2 2 3 3 3 4 ... $ group: int 1 1 1 1 1 1 1 1 1 1 ... $ pulse: int 10 10 10 10 10 10 10 10 10 10 ... $ time : int 1 2 3 1 2 3 1 2 3 1 ... summary(demo2bis); id.group.pulse.time 1 1 10 1: 1 1 1 10 2: 1 1 1 10 3: 1 1 2 15 1:

Hello If I have a function aFunction <- function(data, alpha, ...) { transform(alpha, ...) rowMeans(data) > alpha } f <- function(data, selection, ...) { selected <- selection(data, ...) plot(data[selected, ], ...) } f(aDataset, aFunction, alpha = 10, pch = 19, transform = sqrt) and selection calls another function, which has ... and that function calls other

Hi: I have a function as follows: my.plot <- function( x, y = NULL, ... ) { plot( x, y, cex.axis=0.5, ...) } Set up the variables: x <- 1:10; y <- x; tdf <- data.frame( x, y ); main.str <- "test" I will exercise the function in two ways: > my.plot( y ~ x, tdf, main = "test" ) This works fine > my.plot( y ~ x, tdf, main = main.str ) Error in

Hi. For any number of *known* arguments, we can do: one <- function(a) list(a = substitute(a)) two <- function(a, b) list(a = substitute(a), b = substitute(b)) and so on. But how do I achieve the same when I have: dots <- function(...) list(???) I want to implement this such that I can do: > exprs <- dots(1+2) > str(exprs) List of 1 $ : language 1 + 2 as well as: >

Interestingly, as.list(substitute(...())) also works. On Sun, Aug 12, 2018 at 1:16 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 12/08/2018 4:00 PM, Henrik Bengtsson wrote: >> >> Hi. For any number of *known* arguments, we can do: >> >> one <- function(a) list(a = substitute(a)) >> two <- function(a, b) list(a = substitute(a), b =

Since you're already using bang-bang ;) library(rlang) dots1 <- function(...) as.list(substitute(list(...)))[-1L] dots2 <- function(...) as.list(substitute(...())) dots3 <- function(...) match.call(expand.dots = FALSE)[["..."]] dots4 <- function(...) exprs(...) bench::mark( dots1(1+2, "a", rnorm(3), stop("bang!")), dots2(1+2, "a",

...lent search facility, I am no wiser as to how R recognizes an incomplete command line and politely raises its hand for more. The help page for parse gives no indication that it does anything more than spit the dummy when fed an incomplete command line, but something in there must recognize such ellipsis. Any hints? Jim

...lent search facility, I am no wiser as to how R recognizes an incomplete command line and politely raises its hand for more. The help page for parse gives no indication that it does anything more than spit the dummy when fed an incomplete command line, but something in there must recognize such ellipsis. Any hints? Jim

...u 8.04 In the "Properties" window for a Flash object, there is a button labelled "Save media as". There are three issues with this label: 1. Just clicking the button by itself doesn't save the media; you need to specify the destination. Therefore the label should end in an ellipsis. 2. Button labels should use title capitalization, e.g. "Save Media As...". 3. The "Save As?" wording is normally used only when there is a separate "Save" command that updates the existing file. Here there isn't such a command, so the "As" isn't nece...

...nge(mpg)) > arrows(3, 15, 4, 30) > })) I think you meant panel.first, not plot.first. At least I cannot find any mention of plot.first in the R source code. In this example, plot.first ends up being an argument of an internal call from plot.default() to plot.window(), which evaluates its ellipsis arguments. If your plot.first expression returned a non-NULL value, you would also have received a warning: plot.window(0:1, 0:1, plot.first = message('hello')) # hello plot.window(0:1, 0:1, plot.first = 123) # Warning message: # In plot.window(0:1, 0:1, plot.first = 123) : # "plot....

...: : with 2 lines, with : : : colons on the left. 5 | Illust. | An illustration | new line, would this do? : : and I think you : Is it parseable? : : know what I mean. The colon at each empty cell looks like vertical ellipsis, that makes it pretty legible Adding a 'wrappable' cell definition would go a long way to make it perfect.

I'm experiencing some confusion with the ellipsis argument (...). In my .Rprofile, I have the following functions: stderr <- function(x, ...) { sqrt( var(x, ...) / length(x) ) } se <- stderr I can use tapply to calculate some means: > tapply( Diameter, factor(Region), mean, na.rm=TRUE ) I II...

Dear R Core Team, I learnt approx. two years ago in this mailing list that one can use the following "trick" to get a (dotted pair)list of the ellipsis arguments inside a function: `substitute(...())` Now my problem is that I can not find any occurrence of this call within the R source - the most frequent solution there is `substitute(list(...))[-1L] ` I would like to know if: 1) substitute(...()) is a trick or a feature in the language; 2)...