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.
Access to the internal R serialization code is provided for use by other packages at the C function level by using the registration of native function mechanism. Client packages simply include a single header file RApiSerializeAPI.h provided by this package. This packages builds on the Rhpc package by Ei-ji Nakama and Junji Nakano which also includes a (partial) copy of the file src/main/serialize.c from R itself. The R Core group is the original author of the serialization code made available by this package.
| Version: | 0.1.2 |
| Published: | 2022-08-25 |
| Author: | Dirk Eddelbuettel, Ei-ji Nakama, Junji Nakano, and R Core (original code) |
| Maintainer: | Dirk Eddelbuettel <edd at debian.org> |
| BugReports: | https://github.com/eddelbuettel/rapiserialize/issues |
| License: | GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
| URL: | https://github.com/eddelbuettel/rapiserialize, https://dirk.eddelbuettel.com/code/rapiserialize.html |
| NeedsCompilation: | yes |
| Materials: | README NEWS ChangeLog |
| CRAN checks: | RApiSerialize results |
| Reference manual: | RApiSerialize.pdf |
| Package source: | RApiSerialize_0.1.2.tar.gz |
| Windows binaries: | r-devel: RApiSerialize_0.1.2.zip, r-release: RApiSerialize_0.1.2.zip, r-oldrel: RApiSerialize_0.1.2.zip |
| macOS binaries: | r-release (arm64): RApiSerialize_0.1.2.tgz, r-oldrel (arm64): RApiSerialize_0.1.2.tgz, r-release (x86_64): RApiSerialize_0.1.2.tgz, r-oldrel (x86_64): RApiSerialize_0.1.2.tgz |
| Old sources: | RApiSerialize archive |
| Reverse imports: | qs, RcppRedis |
| Reverse linking to: | qs, RcppRedis |
Please use the canonical form https://CRAN.R-project.org/package=RApiSerialize 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.