\Header{hdf5}{Interface to the HDF5 Library}
\alias{hdf5save}{hdf5}
\alias{hdf5load}{hdf5}
\keyword{file}{hdf5}
\begin{Usage}
\begin{verbatim}
hdf5save(file, ...)
hdf5load(file, load=TRUE)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\texttt{file}] the name of the file in which the objects will be stored.
\item[\texttt{...}] the names of the objects to be saved.
\item[\texttt{load}] a logical value.  If \texttt{FALSE}, a character vector
containing the names of the objects in the file is returned.
If \texttt{TRUE} (the default), the objects are returned as the
components of a named list.
\end{ldescription}
\end{Arguments}
\begin{Description}
\texttt{hdf5save} and \texttt{hd5fload} provide an experimental interface
to version 5 of the NCSA HDF library.  \texttt{hdf5save} writes a
representation of \R\ objects to the specified file in a form which
can be read by software which understands the HDF5 format.
The objects can be read back from the file at a later
date by using the function \texttt{hdf5load}.

Not all R types are supported and it probably doesn't make sense to
put some of them into an HDF file (e.g. closures).  However, lists,
strings, vectors, and matrices work.  Lists map to HDF groups.
Vectors and matrices map to datasets.

This capability is only available on machines which have the HDF5
library.\end{Description}
\begin{Author}
Marcus G. Daniels \email{mgd@santafe.edu}.\end{Author}
\begin{References}
\url{http://hdf.ncsa.uiuc.edu}\end{References}
\begin{SeeAlso}
\texttt{\Link{save}}, \texttt{\Link{load}}.\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}

hdf5save("examp.hdf", pi, letters, ls)
str(hdf5load("examp.hdf"))

\end{ExampleCode}
\end{Examples}

