Tony Plate wrote:
here's my two cents:
- require names on parameters, rather than order
- construct calls and use eval() rather than do.call() (then you can
manipulate list(...) without the ugh factor of do.call() -- though is
do.call() any different to eval() in R? -- I know in S-PLUS that the
On Wed, 13 Aug 2008, Tony Plate wrote:
Ben Bolker wrote:
I'm looking for advice on manipulating parameters that
are going to be passed through to another function.
Specifically, I am working on my version of "mle",
which is a wrapper for optim (among other optimizers).
I would prefer not
Ben Bolker wrote:
I'm looking for advice on manipulating parameters that
are going to be passed through to another function.
Specifically, I am working on my version of "mle",
which is a wrapper for optim (among other optimizers).
I would prefer not to replicate the entire argument
list of
f Ben Bolker
> Sent: Wednesday, August 13, 2008 11:46 AM
> To: r-devel@r-project.org
> Subject: [Rd] messing with ...
>
>
>I'm looking for advice on manipulating parameters that are
> going to be passed through to another function.
>
>Specifically, I am wor
I'm looking for advice on manipulating parameters that
are going to be passed through to another function.
Specifically, I am working on my version of "mle",
which is a wrapper for optim (among other optimizers).
I would prefer not to replicate the entire argument
list of optim(), so I'm usi
