Special variables reserved by Murex
In Murex, there are five different classes of variables:
- Local variables (scope limited to a function et al)
- Module variables (scoped to a module)
- Global variables (available to every function within Murex but not shared with processes outside of the Murex's runtime)
- Environmental variables (available to every function and process -- internal and external to Murex)
- Reserved variables
Reserved variables are data that are available to any code running within Murex and exposed as a variable.
Because reserved variables are dynamic properties of the runtime environment, they can only be queried and not set:
» set SELF="foobar" Error in `set` (0,1): cannot set a reserved variable: SELF
- Modules and Packages: An introduction to Murex modules and packages
- Numeric (str): Variables who's name is a positive integer, eg
- Pipeline: Overview of what a "pipeline" is
- Variable and Config Scoping: How scoping works within Murex
ARGV(json): Array of the command name and parameters within a given scope
COLUMNS(int): Character width of terminal
HOSTNAME(str): Hostname of the current machine
MUREX_ARGV(json): Array of the command name and parameters passed to the current shell
SELF(json): Meta information about the running scope.
SHELL(str): Path of current shell
export: Define an environmental variable and set it's value
global: Define a global variable and set it's value
set: Define a local variable and set it's value
This document was generated from gen/user-guide/reserved_vars_doc.yaml.