SCM

SCM Repository

[inlinedocs] View of /pkg/inlinedocs/man/extract.file.parse.Rd
ViewVC logotype

View of /pkg/inlinedocs/man/extract.file.parse.Rd

Parent Directory Parent Directory | Revision Log Revision Log


Revision 122 - (download) (as text) (annotate)
Sat Aug 28 21:36:48 2010 UTC (8 years, 11 months ago) by tomaschwutz
File size: 1943 byte(s)
implemented Claudia's suggestion about the assignment function of example code to attribute ex:
added function inlinedocExample<- in file package.skeleton.dx.R with specifying the example already using this mechanism
added testfile attrExamples.R

in addition added suppressWarnings() around the call to package.skeleton, because it always gave a warning of non-exisiting package with my Windows version of R 10.1.
\name{extract.file.parse}
\alias{extract.file.parse}
\title{File content analysis}
\description{Using the base \code{\link{parse}} function, analyse the file to link
preceding "prefix" comments to each active chunk. Those comments form
the default description for that chunk. The analysis also looks for
S4 class "setClass" calls and R.oo setConstructorS3 and setMethodS3
calls in order to link the documentation of those properly.}
\usage{
extract.file.parse(code)
}
\arguments{
  \item{code}{Lines of R source code in a character vector - note that any
nested \code{source} statements are \emph{ignored} when scanning
for class definitions.}
}
\details{If the definition chunk does not contain a
description, any immediately preceding sequence consecutive
"prefix" lines will be used instead.

Class and method definitions can take several forms,
determined by expression type: \describe{
\item{assignment (<-)}{Ordinary assignment of value/function;}
\item{setClass}{Definition of S4 class;}
\item{setConstructorS3}{Definition of S3 class using R.oo package;}
\item{setMethodS3}{Definition of method for S3 class using R.oo package.}}
Additionally, the value may be a name of a function defined elsewhere,
in which case the documentation should be copied from that other definition.
This is handled using the concept of documentation links.

The \code{setMethodS3} calls introduce additional
complexity: they will define an additional S3 generic (which
needs documentation to avoid warnings at package build time)
unless one already exists. This also is handled by "linking"
documentation. A previously unseen generic is linked to the
first defining instances, subsequent definitions of that generic
also link back to the first defining instance.}
\value{Returns an invisible list of .DocLink objects.}

\author{Inlinedocs development team <inlinedocs-support@lists.r-forge.r-project.org>}






root@r-forge.r-project.org
ViewVC Help
Powered by ViewVC 1.0.0  
Thanks to:
Vienna University of Economics and Business Powered By FusionForge