On Wed, Feb 22, 2012 at 3:34 PM, Joshua Wiley wrote:
> Barry, is this a test/example only or would you plan on keeping
> something like that on your site even if it is not adopted for cran
> task views? If it is not adopted elsewhere and you are willing to
> maintain it, I would like to link to
This issue ties loosely into other recent S4 topics on this board.
The methods package defines a number of implicit generics for linear
algebra related functions (rcond, norm, backsolve) that, when used,
interfere with base package operations. Here is the cut-and-paste
version of the code the
On Mon, Feb 27, 2012 at 9:19 AM, Martin Maechler
wrote:
>> Jeffrey Ryan
>> on Mon, 27 Feb 2012 07:39:32 -0600 writes:
>
> > Doesn't this also mean that if Matrix is loaded first,
> > det() will be calling Matrix::determinant, which could be
> > quite surprising change in beha
> Jeffrey Ryan
> on Mon, 27 Feb 2012 07:39:32 -0600 writes:
> Doesn't this also mean that if Matrix is loaded first,
> det() will be calling Matrix::determinant, which could be
> quite surprising change in behavior from expectation?
> This seems rather dangerous and
Doesn't this also mean that if Matrix is loaded first, det() will be
calling Matrix::determinant, which could be quite surprising change in
behavior from expectation?
This seems rather dangerous and 'untrustworthy' to me - unless I am
missing some other hidden mechanism involved here.
I haven't r
Ben Bolker gmail.com> writes:
Bump? (Quoting with "> " removed to make Gmane happy)
I've since realized that it will be harder to use the
built-in $simulate methods in my application than I thought,
but I'm still curious about this issue (and might still be
able to use them with a slight ha
> Matthew Dowle
> on Mon, 27 Feb 2012 09:59:43 + writes:
> Hello,
> Regarding this in R-devel/NEWS/New features :
> o 'library(pkg)' no longer warns about a conflict with a
> function from 'package:base' if the function is an
> identical copy of the base one
Hello,
Regarding this in R-devel/NEWS/New features :
o library(pkg) no longer warns about a conflict with a function from
package:base if the function is an identical copy of the base one but
with a different environment.
Why would one want an identical copy in a different environment? I'm
I think the message is accurate [*]: you do however need to have a clear
understanding of the scoping issues involved, and no message is going to
give you that.
In short, implicit generics are converted (or not) into explicit
functions to be dumped during the dump-for-lazy-loading phase of R C
