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.

debkeepr: Analysis of Non-Decimal Currencies and Double-Entry Bookkeeping

Analysis of historical non-decimal currencies and value systems that use tripartite or tetrapartite systems such as pounds, shillings, and pence. It introduces new vector classes to represent non-decimal currencies, making them compatible with numeric classes, and provides functions to work with these classes in data frames in the context of double-entry bookkeeping.

Version: 0.1.1
Depends: R (≥ 3.5)
Imports: cli (≥ 3.4.0), dplyr (≥ 1.0.0), magrittr, methods, rlang (≥ 1.1.0), tibble (≥ 3.0.0), vctrs (≥ 0.5.2), zeallot
Suggests: covr, ggplot2, ggraph, igraph, knitr, rmarkdown, roxygen2, scales (≥ 1.1.0), testthat (≥ 3.1.3)
Published: 2023-03-22
DOI: 10.32614/CRAN.package.debkeepr
Author: Jesse Sadler ORCID iD [aut, cre, cph]
Maintainer: Jesse Sadler <jrsadler at icloud.com>
BugReports: https://github.com/jessesadler/debkeepr/issues
License: MIT + file LICENSE
URL: https://github.com/jessesadler/debkeepr, https://jessesadler.github.io/debkeepr/
NeedsCompilation: no
Materials: README NEWS
CRAN checks: debkeepr results

Documentation:

Reference manual: debkeepr.pdf
Vignettes: Getting Started with debkeepr
Analysis of Richard Dafforne's Journal and Ledger
Transactions in Richard Dafforne's Journal

Downloads:

Package source: debkeepr_0.1.1.tar.gz
Windows binaries: r-devel: debkeepr_0.1.1.zip, r-release: debkeepr_0.1.1.zip, r-oldrel: debkeepr_0.1.1.zip
macOS binaries: r-release (arm64): debkeepr_0.1.1.tgz, r-oldrel (arm64): debkeepr_0.1.1.tgz, r-release (x86_64): debkeepr_0.1.1.tgz, r-oldrel (x86_64): debkeepr_0.1.1.tgz

Linking:

Please use the canonical form https://CRAN.R-project.org/package=debkeepr 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.