Re: [Rd] False positive note about ambiguous dispatch

2012-10-02 Thread John Chambers
The as() function does some non-standard stuff, and it appears in this example to set up methods for coerce() in a way that fools the disambiguation code (which is newer than the as() code, I think). Pending a rewrite of as() (not imminent) the Note has been deactivated for the coerce()

Re: [Rd] False positive note about ambiguous dispatch

2012-10-02 Thread Hervé Pagès
Thanks you. H. On 10/02/2012 01:56 PM, John Chambers wrote: The as() function does some non-standard stuff, and it appears in this example to set up methods for coerce() in a way that fools the disambiguation code (which is newer than the as() code, I think). Pending a rewrite of as() (not

[Rd] False positive note about ambiguous dispatch

2012-10-01 Thread Hervé Pagès
Hi, In the situation below the note issued by the dispatch algo doesn't seem right: setClass(A, representation(stuff=complex)) setAs(ANY, A, function(from) new(A, stuff=as.complex(from))) as(6, A) An object of class A Slot stuff: [1] 6+0i as(6L, A) Note: Method with