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.

lrequire for R

In the fashion of ‘node.js’ https://nodejs.org/, requires a file, sourcing into the current environment only the variables explicitly specified in the module.exports or exports list variable. If the file was already sourced, the result of the earlier sourcing is returned to the caller.

Installation

From CRAN:

install.packages("lrequire")

From GitHub:

devtools::install_github("rickwargo/lrequire")

Introduction

lrequire enables division of labor in R routines, only exposing variables that are necessary. lrequire-ing scripts keeps the enviornment clean and free of unused and unwanted variables. It also saves on execution time, as it caches the results from an earlier lrequire. The caching behaviour can be either suspended or it can re-source files that have been changed since the last cache of the file.

Example

Given the following unit file, named sample.R:

this = list(
  ten=      10,
  me=       "Rick",
  square=   function(x) { return (x*x) }
)

will.not.expose <- TRUE
this$power <- function(x, y) { return (x^y) }

module.exports = this

lrequire it and make use of it’s outputs.

vals <- lrequire(sample)

print(paste("The square of 8 is ", vals$square(8)))

Upon lrequire-ing sample.R, only the this list will be exposed and assigned to the variable vals. It will have the following assignments:

• vals$ten
• vals$me
• vals$square
• vals$power

Note that vals$ten and vals$me are simple variables while both vals$square and vals$power are functions.

The next time the file is lrequire’d, the file will not be sourced - the cached value will be returned. To disable caching, pass do.caching = FALSE as a parameter to the lrequire() statement. Alternatively, set the variable module.change_code to 1 prior to the file being cached so any subsequent changes to the file, after it was cached, will cause it to be re-sourced.

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.