Menu
▾
▴
Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes
|
From: Jeff H. <Je...@Je...> - 2022-06-25 23:15:05
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Great ideas. Thank you.</p>
<p>The potential problem I see with undelimited strings here is all
the key words become"reserved" as any can end the clause before
it. Is there any combination that it might cause a problem?</p>
<p>This is the first I have heard of a problem with XLATE/TRANSLATE,
except that the various code pages are not supported "yet." (I
don't see much use, in the NetRexx world, for all the EBCDIC pages
that CMS supports.)<br>
</p>
<p>These are the tests it currently passes:</p>
<p>
<blockquote type="cite">-- xlate xrange char ?<br>
-- xlate xrange char char char?<br>
-- xlate ?<br>
-- xlate xrange char char char (overlap)?<br>
-- xlate xrange (multiple overlap)?<br>
-- xlate pairs reversed ?<br>
-- xlate xrange short-xrange ?<br>
-- xlate short-xrange xrange ? </blockquote>
What am I missing?</p>
<p>Jeff<br>
</p>
<div class="moz-cite-prefix">On 6/25/2022 6:30 PM, <a class="moz-txt-link-abbreviated" href="mailto:hp...@we...">hp...@we...</a>
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9f6...@we...">Hi Jeff!
<br>
<br>
Am 25.06.2022 um 05:56 schrieb Jeff Hennick:
<br>
<blockquote type="cite">[...]
<br>
<blockquote type="cite">
<blockquote type="cite">Pipeline stage options could use some
more, optional, "fluff
<br>
words," that would limit the need for external
comments/documentation.
<br>
</blockquote>
</blockquote>
<br>
Sorry for my miscommunication. I do NOT advocate for fluffy
stage names, at all.
<br>
</blockquote>
<br>
Well, as I misconceived it my comments are completely wrong.
<br>
<br>
<blockquote type="cite">The additional fluffy things that I do
suggest are for pipelines that will have
<br>
to be read by a human, maybe the author or not, some time in the
future, are in
<br>
the options. CMS Pipelines stages can be very terse, which is
very good for one
<br>
time pipes.
<br>
<br>
What I have in mind are like this stage: [RRT view of 'change']
<br>
</blockquote>
<br>
Thank you, now I see, your "fluff words" are 'filler', or more
<br>
general 'grammatical particles'. Filler may be omitted without
<br>
changing the predication. Yes, I remember, even the HP71-BASIC
<br>
knows one or two of those, in execution just NOPs.
<br>
<br>
Well, the idea is not new to communicate with the machine in
<br>
natural human language (which is English in any case, no other
<br>
language is more natural and more human, Siri will confirm it).
<br>
Fullscreen-CMS once made some promising steps in this direction
<br>
(pop window cmsout), and crawled back a bit in next release
<br>
(window pop cmsout).
<br>
<br>
<blockquote type="cite">Now, those of us that grew up on or with
XEDIT have no problem with just the
<br>
delimited changeString format, but for "normal" people, having
the optional
<br>
words FROM, TO, and FOR make it much more understandable,
although they add
<br>
nothing to working of the stage, and I personally would not use
them in a
<br>
one-off pipe. They are, implied, defaults, so do not break any
existing pipes
<br>
without them.
<br>
</blockquote>
<br>
FROM, TO, and FOR (I suggest also WITHIN and AND) would for sure
<br>
make more sense if by using them the sequence of the arguments
<br>
would become irrelevant _and_ the strings don't necessarily need
<br>
to be delimited strings:
<br>
<br>
Change within 3-8 and w2.3 for x to a from b /* got it? */
<br>
<br>
Nice, but would you please be so kind and fix XLATE first? ;)
<br>
<br>
Best,
<br>
M.
<br>
<br>
<br>
_______________________________________________
<br>
netrexx-pipelines mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:net...@li...">net...@li...</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines">https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines</a>
<br>
</blockquote>
</body>
</html>
|
