Thanks to all!
Nicola
2011/12/16 Martin Maechler
> > David Scott
> > on Fri, 16 Dec 2011 22:51:11 +1300 writes:
>
>> One easy way is to list the undocumented files in
>> pkg-internal.Rd. From the Writing R Extensions manual:
>
>> Note that all user-level objects in a pa
> David Scott
> on Fri, 16 Dec 2011 22:51:11 +1300 writes:
> One easy way is to list the undocumented files in
> pkg-internal.Rd. From the Writing R Extensions manual:
> Note that all user-level objects in a package should be
> documented; if a package pkg contains us
One easy way is to list the undocumented files in pkg-internal.Rd. From
the Writing R Extensions manual:
Note that all user-level objects in a package should be documented; if a
package pkg contains user-level objects which are for “internal” use
only, it should provide a file pkg-internal.Rd
Why not use package.skeleton() to construct empty help files?
But if you're determined to change the function names instead, grep and sed are
very useful tools for that sort of thing. (The OS versions, not the R grep()).
Sarah
On Thu, Dec 15, 2011 at 7:01 AM, Nicola Sturaro Sommacal
wrote:
> Hi
Use namespaces and only export the functions at the user level. The
rest will be hidden in the namespace and doesn't require a help page.
See 'Package Namespaces' in the manual Writing R Extensions.
Cheers
On Thu, Dec 15, 2011 at 1:01 PM, Nicola Sturaro Sommacal
wrote:
> Hi!
>
> I am building a
Nicola Sturaro Sommacal nicolasturaro.com> writes:
>
> Hi!
>
> I am building a package. This package will not submitted to CRAN.
>
> I write the help files for the most important functions of my package, I
> cannot write it for all functions. This may sounds strange, but so there!
>
> I know
Hi!
I am building a package. This package will not submitted to CRAN.
I write the help files for the most important functions of my package, I
cannot write it for all functions. This may sounds strange, but so there!
I know that all user-level functions should be documented, so I have to
move my
