This has essentially nothing to do with methods, but rather with the
treatment of missing arguments.
Consider:
> foo <- function(x,...)bar(x,...)
> bar <- function(x, y=12, z, ...) {cat(missing(y), "\n"); cat(y, "\n")}
This is the same argument-matching as your example, since the generic
and
Jeffrey Horner wrote:
> Jeffrey Horner wrote:
>> Duncan Murdoch wrote:
>>> On 6/14/2007 10:49 AM, Jeffrey Horner wrote:
Hi,
Here's a patch to the readChar manual page (R-trunk as of today)
that better clarifies readChar's return value.
>>> Your update is not right. For exampl
Prof. Ripley,
I had a feeling I was going a little too deep into the R source code
in order to pull out these functions. I particularly like these La_*
functions calling the LAPACK routines, because they have so much of
the error checking already built-in. I can just copy the code over,
and hope
On Fri, 15 Jun 2007, [EMAIL PROTECTED] wrote:
> Prof. Ripley,
>
> I had a feeling I was going a little too deep into the R source code
> in order to pull out these functions. I particularly like these La_*
> functions calling the LAPACK routines, because they have so much of
> the error checking
Hello,
I have come across a troubling problem in which my call to crossprod
will occasionally produce NaNs. That is, a proper matrix cross-product
will be produced except that some of the matrix elements will
arbitrarily be NaN. For my purposes, this is extremely bad. On several
different R sessio
John Chambers wrote:
> This has essentially nothing to do with methods, but rather with the
> treatment of missing arguments.
>
> Consider:
>> foo <- function(x,...)bar(x,...)
>> bar <- function(x, y=12, z, ...) {cat(missing(y), "\n"); cat(y, "\n")}
>
> This is the same argument-matching as your
