On 9/29/2016 2:49 AM, Rob van der Heij wrote:
> I do recognize the situations where your suggestion could simplify the
> pipeline. For such if/then/else constructs I sometimes use IF (mainly in
> the limited space of the command line):
>
> .. | a: if drop | sort | a: | ..
I keep wondering why IF is restricted to one alternate stream. It seems
like it could be just as useful with stages like DEAL that write to many
streams:
... | a: if deal | insert 'header '
| a: | insert ' sub1 '
| a: | insert ' sub2 '
| a: | insert 'footer '
| a: | ...
I vaguely remember long ago trying to formalize the way the novice user
often expects a label to name a connection rather than a stage, but I'm
not finding the discussion in the old CFORUM archive. I was thinking I
had once written something called MANIFOLD that just added a bunch of
short-through pipelines, but all I'm finding is Rod Davis's MANIFOLD
REXX that he used to create a more generalized DROPNTAKE.
¬R
(Finally resolved the problem with my ISP with receiving mail sent from
IBM to the list--it turned out that the shuttling of mail within IBM's
Connections Cloud on top of the bounces through LISTSERV at Marist had
exceeded their max hop count, and they've increased it now. Rob's
message wound up with a total of 20 Received: headers including the ones
added at the receiving end.)
