[Rd] How to correctly write a package?

From: Vladimir Eremeev <wl2776_at_gmail.com>
Date: Mon, 28 May 2007 08:34:27 -0700 (PDT)

I am writing a package.

Please, study the sequence of my actions below, and comment, what's incorrect.
The package contains pure R code.

  1. At the one level up from the package directory, from the system command prompt: R CMD build --binary ac9

This produces the file ac9_0.1.zip (The package name is ac9, and the package's DESCRIPTION file says its version is 0.1)

2. Then I run Rgui in the other directory and "Install package(s) from local zip files"

3. Issue the following commands in the command of Rgui from step 2 :

 [calls to functions from the package]

4. If I see errors, I quit Rgui from step 2, then change (hopefully) properly the source package code, and
go to step 1.

What would happen if I don't quit Rgui from the step 2? Would it reload the new function definitions?

Is there any other methods to refine a packaged code, which experienced package writers use in their routine work?

I have created package source using package.skeleton, and have documented the functions.
Updating of the function body and re-use of the package.skeleton with force=TRUE overwrites the documentation files. This disallows often use of
this function, or requires keeping the backup copy of the package sources.

View this message in context: http://www.nabble.com/How-to-correctly-write-a-package--tf3828586.html#a10837938
Sent from the R devel mailing list archive at Nabble.com.

R-devel_at_r-project.org mailing list
Received on Mon 28 May 2007 - 15:38:50 GMT

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Mon 28 May 2007 - 21:34:19 GMT.

Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-devel. Please read the posting guide before posting to the list.