SCM Repository

[inlinedocs] View of /pkg/inlinedocs/man/
ViewVC logotype

View of /pkg/inlinedocs/man/

Parent Directory Parent Directory | Revision Log Revision Log

Revision 353 - (download) (as text) (annotate)
Mon Apr 9 12:44:43 2012 UTC (7 years, 4 months ago) by tdhock
File size: 1629 byte(s)
doc bugfix for some \code blocks
\title{S4 class inline documentation}
\description{Using the same conventions as for functions, definitions of S4 classes
in the form \code{setClass("classname",\dots)} are also located and
scanned for inline comments.}
  \item{}{DocLink object as created by \code{\link{extract.file.parse}}.
Note that \code{source} statements are \emph{ignored} when scanning for
class definitions.}
\details{Extraction of S4 class documentation is currently limited to expressions
within the source code which have first line starting with
\code{setClass("classname"}. These are located from the source file
(allowing also for white space around the \code{setClass} and \code{(}).
Note that \code{"classname"} must be a quoted character string;
expressions returning such a string are not matched.

For class definitions, the slots (elements of the
\code{representation} list) fill the role of function
arguments, so may be documented by \code{##<<} comments on
the same line or \code{### } comments at the beginning of the
following line.

If there is no explicit title on the first line of setClass, then
one is made up from the class name.

The class definition skeleton includes an \code{Objects from the Class}
section, to which any \code{##details<<} documentation chunks are
written. It is given a vanilla content if there are no specific
\code{##details<<} documentation chunks.}

\author{Inlinedocs development team
ViewVC Help
Powered by ViewVC 1.0.0  
Thanks to:
Vienna University of Economics and Business Powered By FusionForge