Package development process: Difference between revisions

Revision as of 23:59, 8 September 2010

Revision as of 02:43, 11 September 2010

Line 23:

| title = Creating R Packages, Using CRAN, R-Forge, And Local R Archive Networks And Subversion (SVN) Repositories

| url =http://cran.r-project.org/doc/contrib/Graves+DoraiRaj-RPackageDevelopment.pdf| }}

</ref> checks for errors of various types. ExamplesThis includedincludes inchecking for syntax errors on both the documentation filesmarkup language and the code as well as comparing the arguments between documentation and code. Examples in the documentation are tested and produce error messages if they fail. This can be used as a primitive form of [[unit testing]]; more formal unit tests and [[regression testing]] can be included in a "tests" subdirectory. This can improve software development productivity by making it easier to find bugs as the code is being developed. In addition, the documentation makes it easier to share code with others. It also makes it easier for a developer to use code written months or even years earlier. Packages contributed to the R software repository CRAN (the Comprehensive R Archive Network) <ref> {{ cite web

| title=The Comprehensive R Archive Network | url =http://cran.r-project.org}} </ref> and under development in the [[Apache Subversion|Subversion]] repository R-Forge <ref> {{ cite web | title = R-Forge | url=http://r-forge.r-project.org}} </ref> are repeatedly compiled on different platforms under different versions of the core R language. The results are made available to package maintainers. In this way, package contributors become aware of problems they might otherwise never encounter themselves, because they otherwise would not have easy access to those alternative test results.