On Fri, Feb 19, 2010 at 4:44 AM, Paul Hiemstra wrote:
> Jyotirmoy Bhattacharya wrote:
>>
>> I could not find any documentation of how dot-dot-dot works when used
>> as an argument in a function call (rather than as a formal argument in
>> a definition). I would appreciate some references to the ru
> I could not find any documentation of how dot-dot-dot works when used
> as an argument in a function call (rather than as a formal argument in
> a definition).
You might also be interested in other thread regarding this problem:
http://groups.google.com/group/r-help-archive/msg/5c6ea5eb593337b4
Jyotirmoy Bhattacharya wrote:
I could not find any documentation of how dot-dot-dot works when used
as an argument in a function call (rather than as a formal argument in
a definition). I would appreciate some references to the rules
governing situations like:
f1<-function(x,y,...){
print(x)
}
It likely has to do with the fact that barchart uses unevaluated
arguments. Look at its source by entering its name without arguments:
barchart
This does work:
library(lattice)
f.barchart2 <- function(...) eval.parent(substitute(barchart(...)))
x <- data.frame(a = c(1,1,2,2), b = c(1,2,3,4), d
I could not find any documentation of how dot-dot-dot works when used
as an argument in a function call (rather than as a formal argument in
a definition). I would appreciate some references to the rules
governing situations like:
f1<-function(x,y,...){
print(x)
}
f2<-function(...){
f1(...)
}
5 matches
Mail list logo
