I also am not sure exactly what the OP wants and even less sure of what he
needs...
But a possible answer is that a canonical way to do this is just to pass
down the ... list in the definition and specifying a named list of
arguments in the call (as has already been mentioned).
e.g. consider:
On 28/05/2015 1:40 PM, Luca Cerone wrote:
Hi everybody,
this is probably a silly question, but I can't find a way to recognize
the names that are passed
to variables in ellipsis.
For example, say I have a core function that receives some extra
parameters through ...
e.g.
f -
On May 28, 2015, at 11:03 AM, Duncan Murdoch wrote:
On 28/05/2015 1:40 PM, Luca Cerone wrote:
Hi everybody,
this is probably a silly question, but I can't find a way to recognize
the names that are passed
to variables in ellipsis.
For example, say I have a core function that receives
Hi everybody,
this is probably a silly question, but I can't find a way to recognize
the names that are passed
to variables in ellipsis.
For example, say I have a core function that receives some extra
parameters through ...
e.g.
f - function(...) {
params - c(...)
#dothehardworkhere
On 28/05/2015 1:40 PM, Luca Cerone wrote:
Hi everybody,
this is probably a silly question, but I can't find a way to recognize
the names that are passed
to variables in ellipsis.
For example, say I have a core function that receives some extra
parameters through ...
e.g.
f - function(...) {
Thanks a lot to all of you for the help!
Duncan's solution is what I was looking for!
In my examples I assumed that if f(...) is called by g then the names
I use in g were transferred to f, which is not true.
But calling f as Duncan explained ( g - function(x,y) f(x=x,y=y) )
solves the issue!
6 matches
Mail list logo
