Description Usage Arguments Details Value See Also Examples
You very likely don't need to read this— add.flatdoc.to
is usually called automatically for you, by fixr( ..., new.doc=TRUE)
. It adds skeleton flat-format documentation to a function, suitable for conversion to Rd-format using doc2Rd
. The result should pass RCMD CHECK (but won't be much use until you actually edit the documentation).
1 2 | # See *Examples* for practical usage
add.flatdoc.to(x, char.x = NULL, pkg=NULL, env=NULL, convert.to.source=FALSE)
|
x |
unquoted function name, sought in |
char.x |
[string] function name |
pkg |
[string] name of maintained package where |
env |
[environment] where to get |
convert.to.source |
[logical] if TRUE and |
You don't have to write Rd-compatible documentation from the outset. You can write documentation that's as free-form as you wish, and there's no need to use add.flatdoc.to
to do it– you can write the doco directly in your text editor provided that you can source
the resultant melange OK (see fixr
). I find add.flatdoc.to
useful, though, because I can never remember the headings or mild layout conventions of doc2Rd
and Rd-format itself.
A function with attribute doc
containing the flat-format documentation.
1 2 3 4 5 | myfun <- function( ...) ...
myfun <- add.flatdoc.to( myfun)
# 'fixr( myfun)' will now allow editing of code & doco together
# Or, in a maintained package:
# ..mypack$myfun <<- add.flatdoc.to( myfun, pkg='mypack')
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.