||
) Logical OperatorContinues next operation only if previous operation fails
When in the normal run mode (see “schedulers” link below) this will only run the command on the right hand side if the command on the left hand side does not error. Neither STDOUT nor STDERR are piped.
This has no effect in try
nor trypipe
run modes because they automatically apply stricter error handling. See detail below.
Second command does not run because the first command doesn’t error:
» out: one || out: two
one
Second command does run because the first command produces an error:
» err: one || out: two
one
two
This has no effect in try
nor trypipe
run modes because they automatically apply stricter error handling. You can achive a similiar behavior in try
with the following code:
try {
err: one -> !if { out: two }
}
There is no workaround for trypipe
.
?
) Token: Pipes STDERR from the left hand command to STDIN of the right hand commanderr
: Print a line to the STDERRout
: Print a string to the STDOUT with a trailing new line charactertry
: Handles errors inside a block of codetrypipe
: Checks state of each function in a pipeline and exits block on errorThis 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 Mon Feb 13 09:18:06 UTC 2023 against commit f339958f33995895c1d997efcdbb8408d2c8d45f8b5f934.
Current version is which has been verified against 13950 tests cases.