\HeaderA{new}{Generate an Object from a Class}{new}
\aliasA{initialize}{new}{initialize}
\keyword{programming}{new}
\keyword{classes}{new}
\begin{Description}\relax
Given the name or the definition of a class, plus optionally data
to be included in the object, \code{new} returns an object from that
class.
\end{Description}
\begin{Usage}
\begin{verbatim}
new(Class, ...)

initialize(.Object, ...)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{Class}] Either the name of a class (the usual case) or the
object describing the class (e.g., the value returned by
\code{getClass}).
\item[\code{...}] Data to include in the new object.  Named arguments
correspond to slots in the class definition. Unnamed arguments must
be objects from classes that this class extends.
\item[\code{.Object}] An object:  see the Details section.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
The function \code{new} begins by copying the prototype object from
the class definition.  Then information is inserted according to the
\code{...} arguments, if any.  As of version 2.4 of R, the type of
the prototype object, and therefore of all objects returned by
\code{new()}, is \code{"S4"} except for classes that extend
one of the basic types, where the prototype has that basic type.  User
functions that depend on \code{\LinkA{typeof}{typeof}(object)} should be
careful to handle \code{"S4"} as a possible type.

The interpretation of the \code{...} arguments can be specialized to
particular classes, if an appropriate method has been defined for the
generic function \code{"initialize"}.  The \code{new} function calls
\code{initialize} with the object generated from the prototype as the
\code{.Object} argument to \code{initialize}.

By default, unnamed arguments in the \code{...} are interpreted as
objects from a superclass, and named arguments are interpreted as
objects to be assigned into the correspondingly named slots.  Thus,
explicit slots override inherited information for the same slot,
regardless of the order in which the arguments appear.

The \code{initialize} methods do not have to have \code{...} as
their second argument (see the examples).  Initialize methods are
often written when the natural parameters describing the new object
are not the names of the slots.  If you do define such a method,
note the implications for future subclasses of your class.  If these
have additional slots, and your \code{initialize} method has
\code{...} as a formal argument, then your method should pass such
arguments along via \code{\LinkA{callNextMethod}{callNextMethod}}.  If your method
does not have this argument, then either a subclass must have its
own method or else the added slots must be specified by users in
some way other than as arguments to \code{new}.

For examples of \code{initialize} methods, see
\code{\LinkA{initialize-methods}{initialize.Rdash.methods}} for existing methods for
classes \code{"traceable"} and \code{"environment"}, among others.

Methods for \code{initialize} can be inherited only by simple
inheritance, since it is a requirement that the method return an
object from the target class.  See the
\code{simpleInheritanceOnly} argument to \code{\LinkA{setGeneric}{setGeneric}} and
the discussion in \code{\LinkA{setIs}{setIs}} for the general concept.

Note that the basic vector classes, \code{"numeric"}, etc. are
implicitly defined, so one can use \code{new} for these classes.
\end{Details}
\begin{References}\relax
Chambers, John M. (2008)
\emph{Software for Data Analysis: Programming with R}
Springer.  (For the R version.)

Chambers, John M. (1998)
\emph{Programming with Data}
Springer (For the original S4 version.)
\end{References}
\begin{SeeAlso}\relax
\LinkA{Classes}{Classes} for an overview of defining class, and
\code{\LinkA{setOldClass}{setOldClass}} for the relation to S3 classes.
\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
## using the definition of class "track" from Classes



## a new object with two slots specified
t1 <- new("track", x = seq_along(ydata), y = ydata)

# a new object including an object from a superclass, plus a slot
t2 <- new("trackCurve", t1, smooth = ysmooth)

### define a method for initialize, to ensure that new objects have
### equal-length x and y slots.

setMethod("initialize",
          "track",
          function(.Object, x = numeric(0), y = numeric(0)) {
            if(nargs() > 1) {
              if(length(x) != length(y))
                stop("specified x and y of different lengths")
              .Object@x <- x
              .Object@y <- y
            }
            .Object
          })

### the next example will cause an error (x will be numeric(0)),
### because we didn't build in defaults for x,
### although we could with a more elaborate method for initialize

try(new("track", y = sort(stats::rnorm(10))))

## a better way to implement the previous initialize method.
## Why?  By using callNextMethod to call the default initialize method
## we don't inhibit classes that extend "track" from using the general
## form of the new() function.  In the previous version, they could only
## use x and y as arguments to new, unless they wrote their own
## initialize method.

setMethod("initialize", "track", function(.Object, ...) {
    .Object <- callNextMethod()
    if(length(.Object@x) != length(.Object@y))
     stop("specified x and y of different lengths")
    .Object
  })

\end{ExampleCode}
\end{Examples}

