From: Marc R. <re...@gm...> - 2023-01-04 15:24:30
|
I always found it strange that NetRexx Pipelines did not accept its source from stdin, counter-intuitive on *nix. I've updated runner.nrx to do just that. Previously, when executing org.netrexx.njpipes.pipes.runner without an argument, a message 'specify a pipeline' was given. Now, it will read the pipeline from stdin. Also, a -h option was added, and the parsing of the pipeline options - between () - have been sanitised. bin/pipe does not have to readline anymore, as runner does it now. This allows addressing pipelines directly : << $ cat pipetest.nrx address system 'pipe "(sep ! end %) literal one ! cons%"' 'echo "literal two | cons" | pipe' 'echo "literal three | cons" >pipein.txt' 'pipe -f pipein.txt' address pipe '(pipetest sep ! end ") literal four ! cons"' address pipe '(pipetest sep ! end ") literal five ! cons"' '(pipetest sep | end ?)'- -- split lines 'literal six |'- -- write comments after - 'cons ?' '(pipetest sep | end ?)'- ' literal seven '- '| cons' $ nrc -exec pipetest NetRexx portable processor 4.05-alpha build 2,078-20230104-1557 Copyright (c) RexxLA, 2011,2022. All rights reserved. Parts Copyright (c) IBM Corporation, 1995,2008. Program pipetest.nrx ===== Exec: pipetest ===== one two three four five six seven Processing of 'pipetest.nrx' complete >> Mileage on Windows may vary.. Marc |