manual:chapter5:listproc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
manual:chapter5:listproc [2019/10/17 15:23]
jojo1973 [Group 5: One-argument, one-result commands] Fixed examples 		manual:chapter5:listproc [2019/11/03 06:36] (current)
jojo1973 [Group 9: Quirky commands]
Line 89: Line 89:
  
 In the first form, parallel elements are combined by the command: <code> In the first form, parallel elements are combined by the command: <code>
-{ 1 2 3 } +2:                     { 1 2 3 } 
-{ 4 5 6 }+1:                     { 4 5 6 } 
 +……………………………………………………………………………………
 % %
 </code> returns ''{ .04 .1 .18 }''. </code> returns ''{ .04 .1 .18 }''.
  
 In the second form, the level 1 object is combined with each element in the level 2 list in succession: <code> In the second form, the level 1 object is combined with each element in the level 2 list in succession: <code>
-{ 1 2 3 } +2:                     { 1 2 3 } 
-30+1:                            30 
 +……………………………………………………………………………………
 %CH %CH
 </code> returns ''{ 2900 1400 900 }''. </code> returns ''{ 2900 1400 900 }''.
  
 In the third form, the level 2 object is combined with each element of the level 1 list in succession: <code> In the third form, the level 2 object is combined with each element of the level 1 list in succession: <code>
-50 +2:                            50 
-{ 1 2 3 }+1:                     { 1 2 3 } 
 +……………………………………………………………………………………
 %T %T
 </code> returns ''{ 2 4 6 }''. </code> returns ''{ 2 4 6 }''.
Line 111: Line 114:
 ==== Group 8: Multiple-result commands ==== ==== Group 8: Multiple-result commands ====
 Any command that allows parallel processing, but produces multiple results from its input data, will return its results as a single list. For example,<code> Any command that allows parallel processing, but produces multiple results from its input data, will return its results as a single list. For example,<code>
-{ 1 2 3 } +2:                     { 1 2 3 } 
-{ 4 5 6 }+1:                     { 4 5 6 } 
 +……………………………………………………………………………………
 R→C R→C
 +</code> produces, as expected ''{ (1, 4) (2, 5) (3, 6) }'', but<code>
 +1:      { (1, 4) (2, 5) (3, 6) }
 +……………………………………………………………………………………
 C→R C→R
 </code> produces ''{ 1 4 2 5 3 6 }'' rather than the more expected ''{ 1 2 3 } { 4 5 6 }''. </code> produces ''{ 1 4 2 5 3 6 }'' rather than the more expected ''{ 1 2 3 } { 4 5 6 }''.
Line 129: Line 136:
 » »
 </code> </code>
 +
 Taking ''{ 1 4 2 5 3 6 }'' from above as the result of ''C→R'' (a command which should return two results),<code> Taking ''{ 1 4 2 5 3 6 }'' from above as the result of ''C→R'' (a command which should return two results),<code>
-2+2:               { 1 4 2 5 3 6 } 
 +1:                             2 
 +……………………………………………………………………………………
 UNMIX UNMIX
 </code> gives ''{ 1 2 3 } { 4 5 6 }''. </code> gives ''{ 1 2 3 } { 4 5 6 }''.
Line 138: Line 148:
  
   * ''DELALARM''. This command can take a list of arguments. Note, however, that deletions from early in the alarm list will change the alarm indices of the later alarm entries. Thus, if there are only three alarms, <code>   * ''DELALARM''. This command can take a list of arguments. Note, however, that deletions from early in the alarm list will change the alarm indices of the later alarm entries. Thus, if there are only three alarms, <code>
-{ 1 3 }+1:                       { 1 3 } 
 +……………………………………………………………………………………
 DELALARM DELALARM
 </code> will cause an error, whereas <code> </code> will cause an error, whereas <code>
-{ 3 1 }+1:                       { 3 1 } 
 +……………………………………………………………………………………
 DELALARM DELALARM
 </code>will not. </code>will not.
   * ''DOERR''. This command forces an error state that causes all running programs and commands to halt. Thus even though providing the command with a list argument will cause the command to perform parallel processing, the first error state will cause the command to abort and none of the rest of the list arguments will be used.   * ''DOERR''. This command forces an error state that causes all running programs and commands to halt. Thus even though providing the command with a list argument will cause the command to perform parallel processing, the first error state will cause the command to abort and none of the rest of the list arguments will be used.
-  * ''RESTORE''. This command performs a system warmstart after installing the backup object into memory. All functions are terminated at that time. Thus, only the first backup object in a list will be restored. FIXME+  * ''USBRESTORE''. This command performs a system warmstart after installing the backup object into memory. All functions are terminated at that time. Thus, only the first backup object in a list will be restored. FIXME
  
 ==== Using DOLIST for parallel processing ==== ==== Using DOLIST for parallel processing ====
  • manual/chapter5/listproc.1571351029.txt.gz
  • Last modified: 2019/10/17 15:23
  • by jojo1973