Continues 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
.
- Error String (
err
): Print a line to the stderr - Output String (
out
): Print a string to the stdout with a trailing new line character - Pipe Fail (
trypipe
): Checks for non-zero exits of each function in a pipeline - Pipeline: Overview of what a "pipeline" is
- Schedulers: Overview of the different schedulers (or 'run modes') in Murex
- Try Block (
try
): Handles non-zero exits inside a block of code &&
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)
This document was generated from gen/parser/logical_ops_doc.yaml.