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.

RequireR

Peter van den Berg

2017-01-02

The requireR package can be used to modularize your code. Using requireR, your system components can be separated and combined easier. The requireR packages is inspired by the JavaScript library ‘RequireJS’http://requirejs.org/.

Files will become selfcontained. Modules can contain private variables and functions, and only communicate via their interface variables.

The global environment can stay clean. (almost) no variables end up in the global environment, so no more name collisions or related problems.

Depedencies are always explicified. Each file contains all its dependencies, so you directly see where the file is dependent on.

A typical use case is the following:

#hello.R
requireR(function() {
  "hello"
})

## [1] "hello"

#world.R
requireR(function() {
  "world"
})

## [1] "world"

requireR(
  "hello.R",
  "world.R",
  function(hello, world) {
    paste(hello, world)
})

## [1] "hello world"

As you can see, all code is wrapped within the requireR function. The variables ‘hello’ and ‘world’ can only be used within the wrapped function, and do not end up in the global scope.

You can also use requireR within your module-less code (although this is not recommended)

hello <- requireR("hello.R")
world <- requireR("world.R")
paste(hello, world)

## [1] "hello world"

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.