Re: [netrexx-pipelines] Ad ooRexx scopes, ... (Re: Migrate OS/2 pipelines to NetRexx Pipes

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

On 2022-06-18 04:49:56 hp...@we... wrote:
> Hi Jeff!
>
> Am 18.06.2022 um 00:56 schrieb Jeff Hennick:
> > The WORDS option of the SPECs stage is supported in NetRexx Pipelines.
> >  FIELDS, and the SEPERATORs are not yet.  (WORDS uses a simple PARSE, but
> > using a non-SPACE separator will require more code, probably PARSE in a
> > loop.)
>
> More code for sure, but PARSE in a loop? How about masking blanks,
> if there are more word-separators mask them too, change the fs to
> blank, parse "words" as you are used to, and undo all masking.
> Drawback: chars used for masking must not exist in input, else you
> have a problem. But, IMO, it's worth it, otherwise, how do you
> handle CSV files?
	Assuming one is processing text, any of these ASCII codes can be used to translate white 
space characters; they're hardly ever used for anything:
 1C FS FileSeparator
 1D GS Group Separator
 1E RS Record Separator
 1F US Unit Separator

Leslie
-- 
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
java version "18" 2022-03-22
NetRexx portable processor 4.03-GA build 260-20220503-1730