module and require not available

[71104]

They should be available when running from the REPL, but they aren't (not sure why).

This is secondary if the main use of the language is to transpile to JavaScript.

[71104]

Neither Math's methods are...

[71104]

They might be available through global, which in turn is not currently available due to #27.

[71104]

Now that #27 is fixed global is available but module and require are not.

[71104]

This one strikes back.

Eventually, the solution adopted to make module and require available to the global scope (when running Lambda programs in the interpreter) was to invoke eval with the variable name.

This had the nasty side effect of making lots of other internal variables available to the global scope of Lambda programs: all the Lambda namespace and all the variables available in the specific point of the Lambda interpreter code where eval was invoked.

This has been reverted by 2f66282, and now module and require are no longer accessible.

These two variables are defined in a very weird way in Node.js, and the only solution here is to provide an ad hoc solution, i.e. making them explicitly available when running in interpreter mode.

[71104]

module and require are still indirectly accessible through process.mainModule and process.mainModule.require, respectively.

[71104]

5d316a9 introduces a command line switch n that enables "NodeJS mode". In NodeJS mode the interpreter has types and unmarshalled values for module and require.

Note that, for convenience, require requires only one string argument rather than this and an array of arguments, like other native closures. Example:

~/lambda$ npm start -- -n
> let fs = require 'fs' in fs.readdirSync {'.'}
{'.git', '.gitattributes', '.gitignore', 'Doxyfile', 'Gulpfile.js', 'LICENSE', 'README.md', 'bin', 'doc', 'node_modules', 'package.json', 'src', 'test'}
>