trypipe)Checks for non-zero exits of each function in a pipeline
trypipe checks the state of each function and exits the block if any of them fail. Where trypipe differs from regular try blocks is trypipe will check every process along the pipeline as well as the terminating function (which try only validates against). The downside to this is that piped functions can no longer run in parallel.
trypipe { code-block } -> <stdout>
<stdin> -> trypipe { -> code-block } -> <stdout>trypipe {
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 {
-> trypipe { -> 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 conditiontrypipeerr): Checks state of each function in a pipeline and exits block on errortryerr): 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/try_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 Sep 18 21:18:57 UTC 2024 against commit c037883c03788357164e9846c84d9f777251495d9452a8e.
Current version is 6.3.4225 (develop) which has been verified against tests cases.