On Thu, Oct 6, 2011 at 1:19 PM, Terry Therneau wrote:
>
> On Thu, 2011-10-06 at 10:00 -0400, Kasper Daniel Hansen wrote:
>> if you're using two packages that both define a diag function/method
>> you absolutely _have_ to resolve this using your NAMESPACE. [Update:
>> I see both are methods. I ac
On Thu, 2011-10-06 at 10:00 -0400, Kasper Daniel Hansen wrote:
> if you're using two packages that both define a diag function/method
> you absolutely _have_ to resolve this using your NAMESPACE. [Update:
> I see both are methods. I actually don't know what happens when you
> have the same gener
Terry,
if you're using two packages that both define a diag function/method
you absolutely _have_ to resolve this using your NAMESPACE. [Update:
I see both are methods. I actually don't know what happens when you
have the same generic in both packages]
And yes, there is both an importClassesFro
The current coxme code has functions that depend on bdsmatrix and others
that depend on Matrix, both those pacakges define S4 methods for diag.
When loaded, the message appears:
replacing previous import ‘diag’ when loading ‘Matrix’
Questions:
1. Do I need to worry about this? If so, what c
