\Header{checkFF}{Check Foreign Function Calls}
\keyword{programming}{checkFF}
\keyword{utilities}{checkFF}
\begin{Description}\relax
Performs checks on calls to compiled code from R code.  Currently only
whether the interface functions such as \code{.C} and \code{.Fortran}
are called with argument \code{PACKAGE} specified, which is highly
recommended to avoid name clashes in foreign function calls.\end{Description}
\begin{Usage}
\begin{verbatim}
checkFF(package, dir, file, lib.loc = NULL,
        verbose = getOption("verbose"))
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{package}] a character string naming an installed package.  If
given, the installed R code of the package is checked.
\item[\code{dir}] a character string specifying the path to a package's root
source directory.  This should contain the subdirectory \code{R}
(for R code).  Only used if \code{package} is not given.
\item[\code{file}] the name of a file containing R code to be checked.  Used
if neither \code{package} nor \code{dir} are given.
\item[\code{lib.loc}] a character vector of directory names of \R{} libraries,
or \code{NULL}.  The default value of \code{NULL} corresponds to all
libraries currently known.  The specified library trees are used to
to search for \code{package}.
\item[\code{verbose}] a logical.  If \code{TRUE}, additional diagnostics are
printed.
\end{ldescription}
\end{Arguments}
\begin{SeeAlso}\relax
\code{\Link{.C}},
\code{\Link{.Fortran}};
\code{\Link{Foreign}}.\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
checkFF(package = "ts", verbose = TRUE)
\end{ExampleCode}
\end{Examples}

