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
> 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
