Content deleted Content added
Ahhwhereami (talk | contribs) Grammar fix. The intro section needs to be rewritten though. Tags: Mobile edit Mobile web edit Advanced mobile edit |
Jellymanpro (talk | contribs) No edit summary |
||
Line 25:
| title = Creating R Packages, Using CRAN, R-Forge, And Local R Archive Networks And Subversion (SVN) Repositories
| url =https://cran.r-project.org/doc/contrib/Graves+DoraiRaj-RPackageDevelopment.pdf}}
</ref> checks for errors of various types. This includes checking for syntax errors on both the documentation markup [[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. 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. Routine checks are made of packages contributed to the Comprehensive R Archive Network (CRAN) and under development in the companion open-source collaborative development web site, R-Forge. These checks compile the packages repeatedly 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.
An interesting research question would be to compare the quality of contributions to different [[software repository|software repositories]] and try to relate that to features of the language and accompanying package development process. This could include trying to compare the rate of growth of contributed software to the degree of formality and enforcement of standards for documentation, testing, and coding.
| |||