trypipeerr)Checks state of each function in a pipeline and exits block on error
trypipeerr checks the state of each function and exits
the block if any of them fail. Where trypipeerr differs
from regular tryerr blocks is trypipeerr will
check every process along the pipeline as well as the terminating
function (which tryerr only validates against). The
downside to this is that piped functions can no longer run in
parallel.
trypipeerr { code-block } -> <stdout>
<stdin> -> trypipeerr { -> code-block } -> <stdout>trypipeerr {
out "Hello, World!" -> grep: "non-existent string" -> cat
out "This command will be ignored"
}Formated pager (less) where the pager isn’t called if
the formatter (pretty) fails (eg input isn’t valid
JSON):
func pless {
-> trypipeerr { -> pretty -> less }
}A failure is determined by:
You can see which run mode your functions are executing under via the
fid-list command.
catch): Handles the exception code raised by
try or trypipeunsafe): Execute a block of code, always returning a
zero exit numberfid-list): Lists all running functions within the
current Murex sessionrunmode): Alter the scheduler’s behaviour at higher
scoping levelif):
Conditional statement to execute different blocks of code depending on
the result of the conditiontrypipe): Checks for non-zero exits of each function
in a pipelinetryerr): Handles errors inside a block of codeswitch): Blocks of cascading conditionalstry):
Handles non-zero exits inside a block of codeThis document was generated from builtins/core/structs/tryerr_doc.yaml.
This site's content is rebuilt automatically from murex's source code after each merge to the master branch. Downloadable murex binaries are also built with the website.
Last built on Wed Jan 15 23:07:50 UTC 2025 against commit b4c4296b4c429617fd41527ea0efef33c52c15ef2b64972.
Current version is 6.4.2063 (develop) which has been verified against tests cases.