Dario Strbenac
2014-Oct-07 08:00 UTC
[Rd] S4 Method Dispatch for Class Defined as Attribute
Hello, I am writing an interface to some functions from the CRAN package pamr, which is poorly written. I have a S4 method I declared with setMethod. I'd like to provide a signature of "pamrtrained" which is the class of object that training creates. The last two lines of code of pamr.train are : class(junk) = "pamrtrained" junk How can I dispatch on these kinds of objects, other than making the signature be "ANY" and checking the class inside the S4 method ? Might these kinds of class assignments be deprecated in a future version of R ? -------------------------------------- Dario Strbenac PhD Student University of Sydney Camperdown NSW 2050 Australia
Sven E. Templer
2014-Oct-07 09:01 UTC
[Rd] S4 Method Dispatch for Class Defined as Attribute
Is setOldClass the solution? e.g. x <- list() class(x) <- "foo" setGeneric("bar", function(x) "bar generic") setOldClass("foo") setMethod("bar", "foo", function(x) "bar foo") bar(x) On 7 October 2014 10:00, Dario Strbenac <dstr7320 at uni.sydney.edu.au> wrote:> Hello, > > I am writing an interface to some functions from the CRAN package pamr, which is poorly written. > > I have a S4 method I declared with setMethod. I'd like to provide a signature of "pamrtrained" which is the class of object that training creates. The last two lines of code of pamr.train are : > > class(junk) = "pamrtrained" > junk > > How can I dispatch on these kinds of objects, other than making the signature be "ANY" and checking the class inside the S4 method ? Might these kinds of class assignments be deprecated in a future version of R ? > > -------------------------------------- > Dario Strbenac > PhD Student > University of Sydney > Camperdown NSW 2050 > Australia > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel