\Header{dump}{Text Representations of R Objects}
\keyword{file}{dump}
\keyword{connection}{dump}
\begin{Description}\relax
This function takes a vector of names of \R{} objects and produces
text representations of the objects on a file or connection.
A \code{dump} file can be \code{\Link{source}}d into another
\R{} (or S) session.\end{Description}
\begin{Usage}
\begin{verbatim}
dump(list, file="dumpdata.R", append=FALSE)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{list}] character. The names of one or more \R{} objects to be dumped.
\item[\code{file}] either a character string naming a file or a
connection. \code{""} indicates output to the console.
\item[\code{append}] if \code{TRUE}, output will be appended to
\code{file}; otherwise, it will overwrite the contents of
\code{file}.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
At present the implementation of \code{dump} is very
incomplete and it really only works for functions and
simple vectors.

The function \code{\Link{save}} is designed to be used for
transporting \R{} data between machines.\end{Details}
\begin{SeeAlso}\relax
\code{\Link{dput}}, \code{\Link{dget}},\code{\Link{write}}.\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
x <- 1; y <- 1:10
dump(ls(patt='^[xyz]'), "xyz.Rdmped")
unlink("xyz.Rdmped")
\end{ExampleCode}
\end{Examples}

