Using the base
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" ,R.oo setConstructorS3 R.methodsS3::setMethodS3
or S4 setMethod calls in order to link the documentation of those properly.
Lines of R source code in a character vector - note that any
the environment in which the code has been evaluated before. This is e.g. iportant to make sure that we can evaluate expressions like signature definitions for methods
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:
Ordinary assignment of value/function;
Definition of S4 class;
Definition of a method of a S4 generic;
Definition of S3 class using R.oo package;
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.
R.methodsS3::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 S3generic is linked to the
first defining instances, subsequent definitions of that S3generic
also link back to the first defining instance.
Returns an invisible list of .DocLink objects.
Toby Dylan Hocking <firstname.lastname@example.org> [aut, cre], Keith Ponting [aut], Thomas Wutzler [aut], Philippe Grosjean [aut], Markus Müller [aut], R Core Team [ctb, cph]