On 05/03/2017 12:04 PM, Hervé Pagès wrote:
Not sure why the performance penalty of nonstandard evaluation would
be more of a concern here than for something like switch().
which is actually a primitive. So it seems that there is at least
another way to go than 'dots <- match.call(expand.dots=FA
Not sure why the performance penalty of nonstandard evaluation would
be more of a concern here than for something like switch().
If that can't/won't be fixed, what about fixing the man page so it's
in sync with the current behavior?
Thanks,
H.
On 05/03/2017 02:26 AM, peter dalgaard wrote:
The
Now fixed in R-devel revision 72650.
Duncan Murdoch
On 02/05/2017 4:11 AM, Duncan Murdoch wrote:
On 01/05/2017 8:49 PM, Jack Kelley wrote:
Thanks for looking into this.
A few notes regarding all the UTF encodings on Windows 10 ...
This all stems from the ancient bad decision by Microsoft to
Ximin Luo:
> [..]
>
> I've attached a patch (applies to both 3.3.3 and 3.4) that fixes this issue;
> however I know it's not perfect and would welcome feedback on how to make it
> acceptable to the R project.
>
Hi all, attached is an updated version of the patch.
We've tested this on our jenk
The first line of stopifnot is
n <- length(ll <- list(...))
which takes ALL arguments and forms a list of them. This implies evaluation, so
explains the effect that you see.
To do it differently, you would have to do something like
dots <- match.call(expand.dots=FALSE)$...
and then ex
