| setClass {methods} | R Documentation |
Create a class definition and return a generator function to create objects from the class. Typical usage will be of the style:
myClass <- setClass("myClass", slots= ...., contains =....)
where the first argument is the name of the new class and, if supplied, the arguments
slots= and contains= specify the slots
in the new class and existing classes from which the new class
should inherit. Calls to setClass() are normally found in the
source of a package; when the package is loaded the class will be
defined in the package's namespace. Assigning the generator
function with the name of the class is convenient for users, but
not a requirement.
setClass(Class, representation, prototype, contains=character(),
validity, access, where, version, sealed, package,
S3methods = FALSE, slots)
Class |
character string name for the class. |
slots |
The names and classes for the slots in the new class. This argument
must be supplied by name, The argument must be vector with a names attribute, the names being those of the slots in
the new class. Each element of the vector specifies an
existing class; the corresponding slot must be from this class
or a subclass of it. Usually, this is a character vector
naming the classes. It's also legal for the elements of the
vector to be class representation objects, as returned by As a limiting
case, the argument may be an unnamed character
vector; the elements are taken as slot names and all slots have
the unrestricted class |
contains |
A vector specifying existing classes from which
this class should inherit. The new class will have all the slots
of the superclasses, with the same requirements on the classes
of these slots. This argument
must be supplied by name, See the section ‘Virtual Classes’ for the special
superclass |
prototype, where, validity, sealed, package |
These arguments are currently allowed, but either they are unlikely to be useful or there are modern alternatives that are preferred.
|
representation, access, version, S3methods |
All these arguments are deprecated from version 3.0.0 of R and should be avoided.
|
A generator function suitable for creating objects from the class is
returned, invisibly. A call to this function generates a call to
new for the class. The call takes any number of arguments,
which will be passed on to the initialize method. If no
initialize method is defined for the class or one of its
superclasses, the default method expects named arguments with the
name of one of the slots and unnamed arguments that are objects from
one of the contained classes.
Typically the generator function is assigned the name of the class,
for programming clarity. This is not a requirement and objects
from the class can also be generated directly from
new. The advantages of the generator function are a
slightly simpler and clearer call, and that the call will contain
the package name of the class (eliminating any ambiguity if two
classes from different packages have the same name).
If the class is virtual, an attempt to generate an object from
either the generator or new()
will result in an error.
The two essential arguments other than the class name are
slots and contains, defining the explicit slots
and the inheritance (superclasses). Together, these arguments define
all the information in an object from this class; that is, the names
of all the slots and the classes required for each of them.
The name of the class determines which methods apply directly to objects from this class. The superclass information specifies which methods apply indirectly, through inheritance. See Methods_Details for inheritance in method selection.
The slots in a class definition will be the union of all the slots
specified directly by slots and all the slots in all
the contained classes.
There can only be one slot with a given name.
A class may override the definition of a slot with a given name, but
only if the newly specified class is a subclass of the
inherited one.
For example, if the contained class had a slot a with class
"ANY", then a subclass could specify a with class
"numeric",
but if the original specification for the slot was class
"character", the new call to setClass would generate an error.
Slot names "class" and "Class" are not allowed.
There are other slot names with a special meaning; these names start with
the "." character. To be safe, you should define all of
your own slots with names starting with an alphabetic character.
Some inherited classes will be treated specially—object types, S3 classes and a few special cases—whether inherited directly or indirectly. See the next three sections.
Classes exist for which no actual objects can be created, the virtual classes.
The most common and useful form of virtual class is the class
union, a virtual class that is defined in a call to
setClassUnion() rather than a call to
setClass().
This call lists the members of the union—subclasses
that extend the new class.
Methods that are written with the class union in the signature
are eligible for use with objects from any of the member classes.
Class
unions can include as members classes whose
definition is otherwise sealed, including basic R data types.
Calls to setClass() will also create a virtual class,
either when only the Class argument is supplied (no slots
or superclasses) or when the contains= argument includes
the special class name "VIRTUAL".
In the latter case, a
virtual class may include
slots to provide some common behavior without fully defining
the object—see the class traceable for an
example.
Note that "VIRTUAL" does not carry over to subclasses; a
class that contains a virtual class is not itself automatically virtual.
In addition to containing other S4 classes, a class definition can
contain either an S3 class (see the next section) or a built-in R pseudo-class—one
of the R
object types or one of the special R pseudo-classes "matrix" and
"array".
A class can contain at most one of the object types, directly or indirectly.
When it does, that contained class determines the “data part”
of the class.
This appears as a pseudo-slot, ".Data" and can be treated as a
slot but actually determines
the type of objects from this slot.
Objects from the new class try to inherit the built in
behavior of the contained type.
In the case of normal R data types, including vectors, functions and
expressions, the implementation is relatively straightforward.
For any object x from the class,
typeof(x) will be the contained basic type; and a special
pseudo-slot, .Data, will be shown with the corresponding class.
See the "numWithId" example below.
Classes may also inherit from "vector", "matrix" or
"array".
The data part of these objects can be any vector data type.
For an object from any class that does not contain one of these
types or classes,
typeof(x) will be "S4".
Some R data types do not behave normally, in the sense that they are
non-local references or other objects that are not duplicated.
Examples include those corresponding to classes "environment", "externalptr", and "name".
These can not be the types for objects with user-defined
classes (either S4 or S3) because setting an attribute overwrites the
object in all contexts.
It is possible to define a class that inherits from such types,
through an indirect mechanism that stores the inherited object in a
reserved slot, ".xData".
See the
example for class "stampedEnv" below.
An object from such a class does not have a ".Data" pseudo-slot.
For most computations, these classes behave transparently as if they
inherited directly from the anomalous type.
S3 method dispatch and the relevant as.type()
functions should behave correctly, but code that uses the type of the
object directly will not.
For example, as.environment(e1) would work as expected with the
"stampedEnv" class, but typeof(e1) is "S4".
Old-style S3 classes have no formal definition. Objects are “from” the class when their class attribute contains the character string considered to be the class name.
Using such classes with formal classes and methods is necessarily a
risky business, since there are no guarantees about the content of the
objects or about consistency of inherited methods.
Given that, it is still possible to define a class that inherits from
an S3 class, providing that class has been registered as an old class
(see setOldClass).
Broadly speaking, both S3 and S4 method dispatch try to behave
sensibly with respect to inheritance in either system.
Given an S4 object, S3 method dispatch and the inherits
function should use the S4 inheritance information.
Given an S3 object, an S4 generic function will dispatch S4 methods
using the S3 inheritance, provided that inheritance has been declared via
setOldClass. For details, see setOldClass
and Section 10.8 of the reference.
Class definitions normally belong to packages (but can be defined in
the global environment as well, by evaluating the expression on the
command line or in a file sourced from the command line).
The corresponding package name is part of the class definition; that
is, part of the classRepresentation object holding that
definition. Thus, two classes with the same name can exist in
different packages, for most purposes.
When a class name is supplied for a slot or a superclass in a call to
setClass, a
corresponding class definition will be found, looking from the
namespace of the current package, assuming the call in question appears directly in the source for the
package, as it should to avoid ambiguity.
The class definition
must be already defined in this package, in the imports directives of
the package's DESCRIPTION and
NAMESPACE files or in the basic classes defined by the methods package.
(The ‘methods’ package must be included in the imports directives
for any package that uses
S4 methods and classes, to satisfy the
"CMD check" utility.)
If a package imports two classes of the same name from separate packages, the packageSlot
of the name argument needs to be set to the package name of the
particular class.
This should be a rare occurrence.
Chambers, John M. (2016) Extending R, Chapman & Hall. (Chapters 9 and 10.)
Classes_Details for a general discussion of classes,
Methods_Details for an analogous discussion of methods,
makeClassRepresentation
## A simple class with two slots
track <- setClass("track", slots = c(x="numeric", y="numeric"))
## an object from the class
t1 <- track(x = 1:10, y = 1:10 + rnorm(10))
## A class extending the previous, adding one more slot
trackCurve <- setClass("trackCurve",
slots = c(smooth = "numeric"),
contains = "track")
## an object containing a superclass object
t1s <- trackCurve(t1, smooth = 1:10)
## A class similar to "trackCurve", but with different structure
## allowing matrices for the "y" and "smooth" slots
setClass("trackMultiCurve",
slots = c(x="numeric", y="matrix", smooth="matrix"),
prototype = list(x=numeric(), y=matrix(0,0,0),
smooth= matrix(0,0,0)))
## A class that extends the built-in data type "numeric"
numWithId <- setClass("numWithId", slots = c(id = "character"),
contains = "numeric")
numWithId(1:3, id = "An Example")
## inherit from reference object of type "environment"
stampedEnv <- setClass("stampedEnv", contains = "environment",
slots = c(update = "POSIXct"))
setMethod("[[<-", c("stampedEnv", "character", "missing"),
function(x, i, j, ..., value) {
ev <- as(x, "environment")
ev[[i]] <- value #update the object in the environment
x@update <- Sys.time() # and the update time
x})
e1 <- stampedEnv(update = Sys.time())
e1[["noise"]] <- rnorm(10)