tryerr)Handles errors inside a block of code
tryerr forces a different execution behavior where a failed process at the end of a pipeline will cause the block to terminate regardless of any functions that might follow.
It’s usage is similar to try blocks in other languages (eg Java) but a closer functional example would be set -e in Bash.
To maintain concurrency within the pipeline, tryerr will only check the last function in any given pipeline (ie series of functions joined via |, ->, or similar operators). If you need the entire pipeline checked then use trypipe.
tryerr { code-block } -> <stdout>
<stdin> -> tryerr { -> code-block } -> <stdout>tryerr {
out "Hello, World!" -> grep: "non-existent string"
out "This command will be ignored"
}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 pipelinetrypipeerr): Checks state of each function in a pipeline and exits block on errorswitch): 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 Sat Nov 23 00:50:15 UTC 2024 against commit 69c17da69c17da3bd9db98ca508f6a03a402f074ee24cec.
Current version is 6.4.0375 (develop) which has been verified against tests cases.