Rev 21759 | Rev 42333 | Go to most recent revision | Blame | Compare with Previous | Last modification | View Log | Download | RSS feed
\name{undoc}\alias{undoc}\alias{print.undoc}\title{Find Undocumented Objects}\usage{undoc(package, dir, lib.loc = NULL)}\description{Finds the objects in a package which are undocumented, in the sensethat they are visible to the user (or data objects or S4 classesprovided by the package), but no documentation entry exists.}\arguments{\item{package}{a character string naming an installed package.}\item{dir}{a character string specifying the path to a package's rootsource directory. This must contain the subdirectory \file{man}with \R documentation sources (in Rd format), and at least one ofthe \file{R} or \file{data} subdirectories with \R code or dataobjects, respectively.}\item{lib.loc}{a character vector of directory names of \R libraries,or \code{NULL}. The default value of \code{NULL} corresponds to alllibraries currently known. The specified library trees are used toto search for \code{package}.}}\details{This function is useful for package maintainers mostly. In principle,\emph{all} user level \R objects should be documented; note howeverthat the precise rules for documenting methods of generic functionsare still under discussion.}\value{An object of class \code{"undoc"} which is a list of character vectorscontaining the names of the undocumented objects split according todocumentation type. This representation is still experimental, andmight change in future versions.There is a \code{print} method for nicely displaying the informationcontained in such objects.}\seealso{\code{\link{codoc}}, \code{\link{QC}}}\examples{undoc("tools") # Undocumented objects in 'tools'}\keyword{documentation}