For documentation we use a system that generates Rd files from special
comments in the code. (inlinedocs).
It is crucial to be able to get the defining source code for objects like
methods to extract the comments from it.
Here is an R session that shows how this works for several kinds of methods
Thank You very much. This is a great help.
I would never ever have thought of either unRematchDefinition or getSrcref.
I will incorporate this new insight and report about any further
discoveries (or problems leading to them ;-))
Thanks again
Markus
2014/1/8 Duncan Murdoch
> On 14-01-07 2:40 P
For the purpose of automatic documentation, I want to parse a NAMESPACE
file of the package to be documented.
I want to know the contents:
exportedClasses , exportedMethods and so on
to be able to hide the part of the documentation not exposed in the
NAMESPACE file.
Up to now I am parsing the fi
Cool
It works ;-)
Thanks a lot.
2014/1/21 Peter Meilstrup
> Try the function parseNamespaceFile in base. Not documented but its
> output should be understandable.
>
> Peter
>
> On Tue, Jan 21, 2014 at 5:41 AM, Markus Müller
> wrote:
> > For the purpose of automatic documentation, I want to pa