For what I understand so far : For set, you can add some verification of object internal coherance. The initialize make verification when you create your object, aSlotName<- can make some verification when you change your slot.
For get, you can build some more elabored method than just getting a slot. For example getSlotA can get the value of a slot wich is a list for some convenience and return a matrix. Or it can get matrix A using some columne name define in slot B. Or it can get the first colonm of A only... Christophe > I don't know of any '"non official list" of what method a new S4 object > should have' - such a list would have to depend on what the object > represents. If it represents the output of fitting a model, then methods > for 'residuals', 'fitted' and 'coefficients' would probably be nice. > > Also, out of curiosity, what do your methods for `get' and `set' for each > slot look like? Is there any advantage to using such methods over using > > slot(objectOfYourClass, "aSlotName") # for get, and > slot(objectOfYourClass, "aSlotName") <- aValue # for set > > On Sat, 23 Feb 2008, Christophe Genolini wrote: > > >> Hi the list, >> >> I am defining a new class. Shortly, I will submit a package with it. >> Before, I would like to know if there is a kind of "non official list" >> of what method a new S4 object should have. >> More precisely, personally, I use 'print', 'summary' and 'plot' a lot. >> So for my new class, I define these 3 methods and of course, a get and a >> set for each slot. What else? Is there some other methods that a R user >> can reasonably expect? Some "minimum basic tools"... >> >> Thanks >> >> Christophe >> >> >> [[alternative HTML version deleted]] >> >> ______________________________________________ >> R-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel >> >> > > [[alternative HTML version deleted]] ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
