diff options
author | Kaz Kylheku <kaz@kylheku.com> | 2023-01-02 12:32:23 -0800 |
---|---|---|
committer | Kaz Kylheku <kaz@kylheku.com> | 2023-01-02 12:32:23 -0800 |
commit | 57dbbc33be97dbfafe5151b136a623b702cb3fa1 (patch) | |
tree | 6cbe9e04ce4d4af714f6c1ad97e2b11496915f31 /txr.1 | |
parent | 63b3110fcda127de8156075879d24ad16c85f0c2 (diff) | |
download | txr-57dbbc33be97dbfafe5151b136a623b702cb3fa1.tar.gz txr-57dbbc33be97dbfafe5151b136a623b702cb3fa1.tar.bz2 txr-57dbbc33be97dbfafe5151b136a623b702cb3fa1.zip |
doc: awk: mention res in clause descriptions.
* txr.1: In the description of the condition-action clause
processing, mention the new res variable. Some additional
improvements in neighboring text.
Diffstat (limited to 'txr.1')
-rw-r--r-- | txr.1 | 20 |
1 files changed, 14 insertions, 6 deletions
@@ -67922,14 +67922,22 @@ is other than a function or regular expression, it is taken directly to be the truth value. If the condition is true, then its associated .meta action -forms are evaluated. Either way, processing passes to the next condition -clause (unless an explicit step is taken in one of the -.metn action s -to prevent this, for instance by invoking the +forms are evaluated. These forms have access to the truth value via the +.code res +variable, which is freshly bound for each execution of the +.meta action +forms of that specific clause. +For each input record, all condition-action clauses are processed in the order +they appear, regardless of which of them have a true action, +except in cases when some +.meta action +invokes the .code next -and +or .code next-file -macros). +macro, or abandons the execution of the +.code awk +macro entirely via a non-local exit. When an input source runs out of records, .code awk switches to the next input source. When there are no more input sources, |