RcppTOML 0.1.1
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
Following up on the somewhat important RcppTOML 0.1.0 releaseas which brought RcppTOML to Windows, we have a first minor update 0.1.1. Two things changed: once again updated upstream code from Chase Geigle‘s cpptoml which now supports Date types too, and we added the ability to parse TOML from strings as opposed to only from files.
TOML is a file format that is most suitable for configurations, as it is meant to be edited by humans but read by computers. It emphasizes strong readability for humans while at the same time supporting strong typing as well as immediate and clear error reports. On small typos you get parse errors, rather than silently corrupted garbage. Much preferable to any and all of XML, JSON or YAML — though sadly these may be too ubiquitous now.
TOML is making good inroads with newer and more flexible projects such as the Hugo static blog compiler, or the Cargo system of Crates (aka “packages”) for the Rust language.
Changes in version 0.1.1 (2017-xx-yy)
Synchronized multiple times with ccptoml upstream adding support for local datetime and local date and more (PR #9, #10, PR #11)
Dates are now first class types, some support for local versus UTC times was added (though it may be adviseable to stick with UTC)
Parsing from (R) character variables is now supported as well
Output from
print.toml
no longer prints extra newlines
Courtesy of CRANberries, there is a diffstat report for this release.
More information and examples are on the RcppTOML page. Issues and bugreports should go to the GitHub issue tracker.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.