||
Or 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 achieve a similar behavior in try
with the following code:
try {
err one -> !if { out two }
}
There is no workaround for trypipe
.
&&
And Logical Operator: Continues next operation if previous operation passes?:
Elvis Operator: Returns the right operand if the left operand is falsy (expression)?
stderr Pipe: Pipes stderr from the left hand command to stdin of the right hand command (DEPRECATED)err
: Print a line to the stderrout
: Print a string to the stdout with a trailing new line charactertry
: Handles non-zero exits inside a block of codetrypipe
: Checks for non-zero exits of each function in a pipelineThis document was generated from gen/parser/logical_ops_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 Thu Aug 15 14:38:34 UTC 2024 against commit 50ed9d650ed9d6df391240d3c2c02e623636e508dfcdad1.
Current version is 6.2.4000 which has been verified against tests cases.