Re: [netrexx-pipelines] Upgraded SPEC stage

[J L. T. <jlt...@ma...>]

	Wonderful!  Thank you so very much!

Leslie

On 2022-12-21 12:38:58 Jeff Hennick wrote:
> I have just uploaded an updated SPEC 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.)
>
> 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. The big
> addition is FIELDS, now in addition to characters and words.  And
> WORDSEPARATOR and FIELDSEPARATOR, 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. These contrived
> examples are from specs_tests_9.njp:
>
> -- specs wordseparator multichar multiseps?
>     literal @#one@#@#@#two@#@#three@#four |
>     specs wordseparator @# w2 1 |
>     cons
>
> The output is two.
> And
> -- specs multi fieldseparator multichar multiseps?
>     literal $@#$one$@#@#@#two@#@#$three$@#four |
>     specs fieldseparator @# f5 1 fieldseparator $ f5 nw |
>     cons
>
> With output of two three.
>
>
>
>
> And, NetRexx Pipelines has the two newish stages for rearranging content:
> PARSE and GREP / REGEX.

--