Hi Leslie,
Yes, it seems that ’specs’ keeps growing and growing. The good news is that in
our implementation Jeff did a separate part for inputRange and if it works
there, it should work everywhere.
For clarity, I did not try this because at the moment, I did what I would do in
Rexx.
René.
>
René,
I see that in this pipeline you use reverse with specs to trim trailing
parts of your
records. I understand that the nrx specs stage does not yet completely emulate
the CMS
specs stage, but I hope that as it is improved it will fully support CMS-type
inputRange
notation.
Thank you. I too would not want this to hold up progress towards v5.0
On Sat, 18 Jun 2022 at 13:05, Michael Lueck
wrote:
> Greetings Harmander,
>
> Personally since Classic Rexx on say OS/2 is so antiquated these days, I
> think the line has long been crossed for quickly executing untouched
> Cl
Greetings Harmander,
Personally since Classic Rexx on say OS/2 is so antiquated these days, I think
the line has long been crossed for quickly executing untouched Classic Rexx
programs on current ooRexx.
At least that is my vote... when porting Classic Rexx to ooRexx, expect some
code changes
Terry,
One issue which came up in this context a long while back was that at
some stage in the development of v5.0, the classic Rexx file input
statements linein, charin 'had a performance hit' (they became much slower
than their ooRexx counterparts).
That problem doesn't appear to have been as ye
On 2022-06-17 15:53:37 Sanford Geiger wrote:
> I agree that 5.0 is way overdue for GA. The only possible holdup that I can
> think of is full support for all of OLE. Do we have such support?
>
It would be nice if there was documented support for GUI on non-Windows
platforms (i.e.
any of the Rexx n
