Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes

[<hp...@we...>]

>> On 3 Jun 2022, at 04:53, hp...@we... wrote:
>> ((Reply to a mail I missed))
>>>> [...]
>
> The Pipelines Guide shows some examples of how nrws is an apt environment for pipeline experimentation. The main nrws documentation is in the Programming Guide. [...]

I found no way to change the colour of the 'nrws>' prompt to the
left and the additional info on the RHS. It's dark blue on black
and for me just not existent. Even if I change the background of
the cmd window this two fields insist on their own background
colour: black.

>>> nrws> say hello                                                        initial 1
>>> 2 +++ say hello;
>>>   +++     ^^^^^
>>>   +++ Error: Result of this expression cannot be just a type; it must have a va
>>> lue
>
> In NetRexx, there is no literal value of an undeclared string. If you look at the first VM manuals, those were all over them, and they disappeared from the examples and a ’signal on novalue’ was introduced. Following that trend they were removed from NetRexx.

Fair enough -- seems a tendency I missed. Sorry.

>> BTW, the nrws description uses every now and then the term "home
>> directory", once even "top level home directory". May I assume
>> this is the same as I set at some point during installation
>> procedure in the NETREXX_HOME system variable (and the top level
>> home directory to be the same)?
> No, this is your home directory, I think in windows referred to as %HOME%.

Stackoverflow unveils: "Home" on Windows is %userprofile%
Was asked more than 10 years ago. Tested with nrws -- works.

>> ...and so on. Did you read along "the Book" about varset at
>> http://vm.marist.edu/~pipeline/pipeline.pdf ?
>> I know it's dated, but -- hobbyist I am -- I'm removed from
>> Pipelines evolution ever since the Runtime Library Distribution
>> was updated for the last time.
>>
> Not yet, but I will today. Seems like a handy addition.

Sure, there are other ways to read defaults from disk, for example
read an INI file and _interpret_ it line by line. Offers the
optional risk of "bad" REXX clauses in it. Setting variables only
is less jeopardy.

>>> So that does more or less what you want already - the source redirect <, the nlocate works. If you want we can make a varset stage, I think we don’t have that at the moment but it cannot be too hard.
>>
>> No, we should go all-in, if NetRexx Pipelines does not have a
>> varset stage yet it is a good test (for me to learn and for
>> NetRexx to point out) how to add those 'on the fly', analogous to
>> CMS Pipelines (filetype REXX). [...]

I have to weaken my request a bit by adding 'if possible and
purposive'. At least I also had to adopt my "CMS-pipe-thinking" to
the limited capabilities and many pitfalls of OS/2 Pipelines. So
my only goal of this change-over to NetRexx Pipelines is nothing
but running VilMA and -- if installation of NetRexx is as simple
as /younameit/ -- maybe publishing it.

>> Well, I hope NetRexx Pipelines allows home-made stages like this.
>
> Yes, certainly. The source of all the stages is in NetRexx. Did you check out the source from Github or SourceForge (I keep it in two places because it limits the exposure from outages).

Found https://github.com/rvjansen/netrexx-site but no source of
stages in there.

> We keep all the stages in src/org/netrexx/njpipes/stages. Most are put together by Jeff Hennick so I hope he’ll join this conversation sometime.

Clicking on 'Files' in SourceForge shows:
  "This project has no files."
Then ... at last, found it. Nice :)

So this is the only option users may add their DIY stages?

/M.