> John Chambers
> on Sat, 10 Sep 2016 09:16:38 -0700 writes:
> (Brief reply, I'm traveling but as per below, this is on my radar right
now so wanted to comment.)
> Two points regarding "dotsMethods".
> 1. To clarify the limitation. It's not that all the arguments have
One option would be to use the same strategy that we use for cbind()
and rbind(), i.e., if dispatch fails, call a binary generic, c2(),
recursively. Could do the same for pmin() and pmax().
Michael
On Sat, Sep 10, 2016 at 8:27 AM, Martin Maechler
wrote:
> I have been asked (by Roger; thank you
> Suharto Anggono Suharto Anggono
> on Sat, 10 Sep 2016 02:36:54 + writes:
> Looking at the code of function 'table' in R devel r71227, I see that the
part "remove NA level if it was added only for excluded in factor(a,
exclude=.)" is not quite right.
> In
> is.na(a)
(Brief reply, I'm traveling but as per below, this is on my radar right now so
wanted to comment.)
Two points regarding "dotsMethods".
1. To clarify the limitation. It's not that all the arguments have to be of
the same class, but there must be one class that they belong to or subclass.
(So
I have been asked (by Roger; thank you for the good question,
and I hope it's fine to answer to the public) :
> with Pi a sparse matrix and x,y, and ones
> compatible n-vectors — when I do:
>> c(t(x) %*% Pi %*% ones, t(ones) %*% Pi %*% y )
> [[1]] 1 x 1
