From: Jeff H. <Je...@Je...> - 2022-12-21 18:55:29
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body> <p>I have just uploaded an updated <b>SPEC</b> stage. It will be included in the next release of NetRexx. (The source is now available from SourceForge, but since it uses advanced features it can only be compiled by rebuilding the full NetRexx jars. Doable.)<br> </p> <p>This fixes a known bug with X2C/C2X. (I had used the NetRexx builtin, but it works with a singe character, not a string like classic Rexx.) Also fixed, I hope, was the proper way to handle multiple input streams.</p> <p>The big addition is <b>FIELDS</b>, now in addition to characters and words. And <b>WORDSEPARATOR</b> and <b>FIELDSEPARATOR</b>, and their abbreviations. As an extension to the CMS separators, which are limited to a single character, NetRexx Pipelines now also supports multi-character separators. These are specified by a "QWord." This is a simple single word, which is optionally surrounded by quote marks, single or double. Quotes are necessary if the "word" includes a SPACE, or begins with a quote mark.</p> <p>These contrived examples are from <b>specs_tests_9.njp</b>: <br> </p> <font face="monospace">-- specs wordseparator multichar multiseps?<br> literal @#one@#@#@#two@#@#three@#four |<br> specs wordseparator @# w2 1 |<br> cons</font><br> <p>The output is <b>two</b>.</p> <p>And</p> <font face="monospace">-- specs multi fieldseparator multichar multiseps?</font><br> <font face="monospace"> literal $@#$one$@#@#@#two@#@#$three$@#four |</font><br> <font face="monospace"> specs fieldseparator @# f5 1 fieldseparator $ f5 nw |</font><br> <font face="monospace"> cons <br> </font> <p>With output of <b>two three</b>.</p> <p><br> </p> <p><img src="cid:par...@Je..." alt=""></p> <p><img src="cid:par...@Je..." alt=""></p> <p><img src="cid:par...@Je..." alt=""></p> <p><img src="cid:par...@Je..." alt=""></p> <p><img src="cid:par...@Je..." alt=""></p> <p><br> </p> <p>And, NetRexx Pipelines has the two newish stages for rearranging content: <b>PARSE</b> and <b>GREP / REGEX</b>.<br> <font face="monospace"></font></p> </body> </html> |