Displaying 3 results from an estimated 3 matches for "do_docall".
Did you mean:
do_dotcall
2010 Nov 02
2
on the usage of do.call
...enquote <- function(x) as.call(list(as.name("quote"),
x))
args <- lapply(args, enquote)
}
.Internal(do.call(what, args, envir))
}
<environment: namespace:base>
>
In <src>/main/names.c, the function do.call is linked to the C function
do_docall (line 499). (.Internal calls the good function line 1194.)
And the do_docall function is defined in <src>/main/coerce.c line 2217 and
declared as
SEXP attribute_hidden do_docall(SEXP call, SEXP op, SEXP args, SEXP rho)
in Internal.h.
The problem is that I do not guess the exact meaning of...
1999 Apr 21
1
do.call() mangles expressions in arguments (PR#174)
> f<-function(x)x
> f(expression(print("Oops")))
expression(print("Oops"))
> do.call("f",list(expression(print("Oops"))))
[1] "Oops"
Something in the do_docall code causes an extra eval of the
argument. Causes trouble with math expressions in labels in
boxplot (do.call("title",...))
--please do not edit the information below--
Version:
platform = i586-unknown-linux
arch = i586
os = linux
system = i586, linux
status = Patched (unreleased...
2000 Dec 18
1
1.2.0 segfault
...4bb078) at eval.c:317
---Type <return> to continue, or q <return> to quit---
#22 0x5a730 in Rf_applyClosure (call=0x4bbc94, op=0x2d32e0, arglist=0x4bbd04,
rho=0x2d36ec, suppliedenv=0x1b5300) at eval.c:501
#23 0x5a340 in Rf_eval (e=0x4bbc94, rho=0x2d36ec) at eval.c:352
#24 0x38940 in do_docall (call=0x4bbc94, op=0x3, args=0xbcd8b4, rho=0x4bc678)
at coerce.c:1692
#25 0x7d32c in do_internal (call=0x17f5f0, op=0x1cd010, args=0x4bc6b0,
env=0x4bc678) at names.c:925
#26 0x5a114 in Rf_eval (e=0x1e488c, rho=0x4bc678) at eval.c:317
#27 0x5a730 in Rf_applyClosure (call=0x9d1c5c, op=0x1e47a...