, March 13, 2008 2:01 PM
To: Ravi Varadhan
Cc: r-help@r-project.org
Subject: Re: [R] Use of ellipses ... in argument list of optim(),
integrate(), etc.
There is an entry in the NEWS file for 2.6.0:
CHANGES IN R VERSION 2.6.0
SIGNIFICANT USER-VISIBLE CHANGES
o integrate(), nlm
There is an entry in the NEWS file for 2.6.0:
CHANGES IN R VERSION 2.6.0
SIGNIFICANT USER-VISIBLE CHANGES
o integrate(), nlm(), nlminb(), optim(), optimize() and uniroot()
now have '...' much earlier in their argument list. This
reduces the chances of unin
Ravi Varadhan wrote:
> Hi,
>
> I have noticed that there is a change in the use of ellipses or . in R
> versions 2.6.1 and later. In versions 2.5.1 and earlier, the . were always
> at the end of the argument list, but in 2.6.1 they are placed after the main
> arguments and before method control a
13, 2008 1:09 PM
To: Ravi Varadhan
Cc: r-help@r-project.org
Subject: Re: [R] Use of ellipses ... in argument list of optim(),
integrate(), etc.
From the NEWS file:
CHANGES IN R VERSION 2.6.0
SIGNIFICANT USER-VISIBLE CHANGES
o integrate(), nlm(), nlminb(), optim(), optimize() and uniroot
From the NEWS file:
CHANGES IN R VERSION 2.6.0
SIGNIFICANT USER-VISIBLE CHANGES
o integrate(), nlm(), nlminb(), optim(), optimize() and uniroot()
now have '...' much earlier in their argument list. This reduces the
chances of unintentional partial matching but means that the later
arg
Hi,
I have noticed that there is a change in the use of ellipses or . in R
versions 2.6.1 and later. In versions 2.5.1 and earlier, the . were always
at the end of the argument list, but in 2.6.1 they are placed after the main
arguments and before method control arguments. This results in the
6 matches
Mail list logo