Not that I am really interested in this, but for your information: CMS and TSO
Rexx traditionally has had a decimal version number: 3.40, 3.48. 4.02.
This is without reason: its inventor is more involved with decimal arithmetic
than the man in the street. There was a semi-heated discussion in
Thanks for pointing that out. The NetRexx discussion was about product release
number, i.e. the number that the translator tells you in the logo. The code
states ‘language level’ indeed, but as far as I can go back this was never
different from the product release level. (It was a product only
On 14.03.2020 21:51, Enrico Sorichetti via Oorexx-devel wrote:
> There is a clash in the nomenclature used by IBM software development
> And the one used in the *ix word
>
> The IBM terminology is explained here
>
That is the language level, not a product release level. ooRexx also has a
language level that is decimal in form, but that is only updated when there
is a change to the language handled by the interpreter. Bug fixes would
never bump that, nor would new class libraries.
Rick
On Sun, Mar 15, 2020
Probably that’ the reason why on zOS
Parse version v
Say v
Reports
REXX370 3.48 01 May 1992
Disregarding the Version whatever of the product ( TSO extensions )
Which delivers the rexx interpreter
E
> On 15 Mar 2020, at 13:45, Rick McGuire wrote:
>
> That is the language level, not
Not sure whether I get locked out of the University hence committing the rexxpg
work.
The OS/2 remainders of CMD-files and all upercase filenames should be gone and
match what is in
"samples" e.g. A lot of work went into formatting (emphasizing,
code/literal/filename).
One area needs
