There may be a misunderstanding here: the stem support and the syntax for using it should not be
touched, but remain in place.
The suggestion is about extending the stem syntax to at least arrays, preferably to all ordered
collections for output and error output, with the ability to create the array (or indicated ordered
collection) objects for the variables which should receive the output.
(1) Keeping the stem support and syntax intact. The following example will place the stdout lines to
"stemOut.", the stderr lines to "stemErr.":
ADDRESS SYSTEM some_command WITH OUTPUT stem stemOut. ERROR stem stemErr.
(2) The suggestion proposes to use the above syntax for arrays (preferably for any of the ordered
collections, that may be used) as well and if the variables "arrOut" and "arrErr" do not exist,
create them before executing the statement, like:
ADDRESS SYSTEM some_command WITH OUTPUT array arrOut ERROR array arrErr
A general support for any orderable collections (list, queue, ...) would then use the same syntax as
well, just the type option would change accordingly, e.g.:
ADDRESS SYSTEM some_command WITH OUTPUT list listOut ERROR list listErr
3) Currently, if one wishes to use the arrays (or orderable collection) to receive the output lines
one has to code:
arrOut=.array~new
arrErr=.array~new
ADDRESS SYSTEM some_command WITH OUTPUT USING (arrOut) ERROR USING (arrErr)
Following the stem syntax would ease coding for the Rexx programmers, folding three statements of
(3) into one, cf. (2) above.
---rony
On 14.07.2022 19:15, Sanford Geiger wrote:
I also have tens of thousands of lines of code using stems spanning over 30-40
years. I only use the objects when I absolutely have to, such as OLE. Please
leave the stems alone.
Thank you,
Sandy Geiger
-----Original Message-----
From: Mike Cowlishaw<m...@speleotrove.com>
Sent: Thursday, July 14, 2022 12:56 PM
To: 'Open Object Rexx Developer Mailing
List'<oorexx-devel@lists.sourceforge.net>
Subject: Re: [Oorexx-devel] Ad address...with
I agree; I don't see why the .stem variant should be
easier than any other, especially since stems are hardly ever
used with the more modern rexx constructs (e.g. loop x over y).
I don't think it should be made harder: I have tens of thousands of lines of
Rexx code, some over 40 years old, and mostly still use stems out of habit
if they suffice. So please keep stems easy to use and fast ... :-).
Mike
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
