The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

cleanr: Helps You to Code Cleaner

Check your R code for some of the most common layout flaws. Many tried to teach us how to write code less dreadful, be it implicitly as B. W. Kernighan and D. M. Ritchie (1988) <ISBN:0-13-110362-8> in 'The C Programming Language' did, be it explicitly as R.C. Martin (2008) <ISBN:0-13-235088-2> in 'Clean Code: A Handbook of Agile Software Craftsmanship' did. So we should check our code for files too long or wide, functions with too many lines, too wide lines, too many arguments or too many levels of nesting. Note: This is not a static code analyzer like pylint or the like. Checkout <https://cran.r-project.org/package=lintr> instead.

Version: 1.4.0
Depends: R (≥ 3.3.0)
Imports: checkmate, fritools, pkgload, rprojroot
Suggests: devtools, rasciidoc, rmarkdown, RUnit, testthat, usethis
Published: 2023-06-16
DOI: 10.32614/CRAN.package.cleanr
Author: Andreas Dominik Cullmann [aut, cre]
Maintainer: Andreas Dominik Cullmann <fvafrcu at mailbox.org>
License: BSD_2_clause + file LICENSE
URL: https://gitlab.com/fvafrcu/cleanr
NeedsCompilation: no
Materials: README NEWS
CRAN checks: cleanr results

Documentation:

Reference manual: cleanr.pdf
Vignettes: An Introduction to cleanr

Downloads:

Package source: cleanr_1.4.0.tar.gz
Windows binaries: r-devel: cleanr_1.4.0.zip, r-release: cleanr_1.4.0.zip, r-oldrel: cleanr_1.4.0.zip
macOS binaries: r-release (arm64): cleanr_1.4.0.tgz, r-oldrel (arm64): cleanr_1.4.0.tgz, r-release (x86_64): cleanr_1.4.0.tgz, r-oldrel (x86_64): cleanr_1.4.0.tgz
Old sources: cleanr archive

Reverse dependencies:

Reverse suggests: fakemake, packager

Linking:

Please use the canonical form https://CRAN.R-project.org/package=cleanr to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.