Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
dev env vars
The following environment variables can impact Rakudo's behavior:
Defaults to 65536; the default number of characters to read on an IO::Handle
Set to 1, will disable multiline input for the REPL
If present, the print_exception routine will use a class of that name to process the exception for output. Rakudo currently ships with Exceptions::JSON (invoked by setting this variable to "JSON"), to override the default output.
This specifies the location of the history file used by the line editor; the
This specifies the preferred line editor to use; valid values are
none. A value of
none is useful if you want to avoid
the recommendation message upon REPL startup.
If set to 1, diagnostic information about the precompilation process is emitted.
If you're using the MoarVM backend for Rakudo, the following variables also have an impact:
Disables all dynamic optimization
Make threads pause while dynamic optimization work is performed; this effectively makes the optimization work take place synchronously rather than in the background, which means bugs will manifest themselves more predictably.
Run dynamic optimization even for cold frames. Useful in conjunction with MVM_SPESH_BLOCKING for stress-testing the dynamic optimizer.
Disables on-stack replacement
Disables JITting to machine code
Specifies a dynamic optimizer log file
Specifies a JIT-compiler log file
Specifies a directory for JIT bytecode dumps
Log unprotected cross-thread object writes to stderr
Specifies a line coverage log file
When set to 1, line coverage is not de-duplicated, and it must be started with a call to
When set to 2, line coverage is not de-duplicated, but starts without requiring a call to
Line coverage can be stopped/restarted with calls to