search for: dot_002ddot_002ddot

...function. I?m particularly interested in accessing the environment in which each contribution to ... can be evaluated. So far, I?m using tricks involving passing down the sys.calls() and sys.frames() down to the C function. The documentation in http://cran.r-project.org/doc/manuals/R-ints.html#Dot_002ddot_002ddot-arguments did not help me a lot. Romain

...: don't use ...() and pretend that you never discovered it in the first place. Use match.call() instead, as suggested by Serguei. [Disclaimer: I have no idea what is actually going on, so these are just guesses. There are some hints at https://cran.r-project.org/doc/manuals/r-devel/R-ints.html#Dot_002ddot_002ddot-arguments if you want to folllow up.] " Cheers, Denes On 10/6/20 8:38 AM, Tim Taylor wrote: > I probably need to be more specific. What confuses me is not the use > of substitute, but the parenthesis after the dots. It clearly works > and I can make guesses as to why but it is...

I probably need to be more specific. What confuses me is not the use of substitute, but the parenthesis after the dots. It clearly works and I can make guesses as to why but it is definitely not obvious. The following function gives the same final result but I can understand what is happening. dots <- function (...) { exprs <- substitute(list(...)) as.list(exprs[-1]) } In the

It seems like there is no obvious way in the documentation to convert the expressions in the dots argument to a list without evaluating them. Say, if you want to have a function that prints all its arguments: > foo(abc$de, fg[h], i) abc$de fg[h] i ...then converting them to a list would be helpful. Using substitute(...) was the first thing I tried, but that only gives the *first *argument in