[Rd] [Wishlist] a 'PackageDevelopment' Task View
dutangc at gmail.com
Sun Jul 27 09:33:02 CEST 2014
Let me suggest to follow the table of contents of http://cran.r-project.org/doc/manuals/r-release/R-exts.html
For example, you could use the following TOC:
1 - Creating R pkg
2 - Writing documentation and vignettes
3 - Profiling code
4 - Debugging, spell checking
5 - Foreign languages interfaces
6 - GUI and other frond-ends
7 - Unit testing
8 - Benchmarking
9 - Automation
Maybe 7 and 8 could be merged?
LMM, UdM, Le Mans, France
Le 26 juil. 2014 à 17:04, Luca Braglia <lbraglia at gmail.com> a écrit :
> 2014-07-25 14:29 GMT+02:00 Duncan Murdoch <murdoch.duncan at gmail.com>:
>> On 25/07/2014 8:05 AM, Luca Braglia wrote:
>>> Hello everybody,
>>> as a young/unexperienced R package developer (only a few, mainly
>>> for personal use) i was thinking it could be very useful having a
>>> "meta" task view for all package-development related
>>> packages and/or function.
>>> Something like ...
>>> - utils::package.skeleton, pkgKitten, Rcpp::Rcpp.package.skeleton
>>> Foreign languages interfaces:
>>> - Rcpp
>>> - roxygen2
>>> - utils::Rprof
>>> - profr
>>> - proftools
>>> Unit test
>>> - RUnit
>>> - testthat
>>> Spell checking
>>> - tools::aspell_package_* functions
>>> - devtools
>>> and so on.
>>> These are only the ones i (use or know) & (remember), but for
>>> sure there is already a lot of useful code in this area and
>>> having a summary (by more experienced developers) of which good
>>> tools are available would be *very* useful, IMHO.
>>> How about it?
>> Sounds like a good idea. You should do it.
>> Download the "ctv" package, and read the vignette for instructions.
>> Duncan Murdoch
> Fine, I've set up a github repo here
> and a first thread about task view structure here
> Contribution (via e-mail or github) are, of course, really welcome.
> Cheers, Luca
> R-devel at r-project.org mailing list
More information about the R-devel