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 at 8:42 AM René Jansen <rvjan...@xs4all.nl> wrote:

> 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 the NetRexx architecture board some years ago where Mike Cowlishaw did
> not budge. Out of respect for him I kept the NetRexx numbering like this;
> NetRexx 3.09 will be released very soon.
>
> The argument is that decimal version numbers can be easily compared. IBM
> never changed this for mainframe Rexx.
>
> best regards,
>
> René.
>
> On 15 Mar 2020, at 13:19, Rony G. Flatscher <rony.flatsc...@wu.ac.at>
> wrote:
>
>
> 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
>
> https://www.ibm.com/support/pages/vrmf-maintenance-stream-delivery-vehicle-terminology-explanation
>
>
> Wow, very helpful, thank you very much Enrico!
>
> On the other side the *ix is a bit murkier due also to the confusion about
> library versioning
>
> The terms used by CMAKE are
>
> PROJECT_VERSION
> PROJECT_VERSION_MAJOR
> PROJECT_VERSION_MINOR
> PROJECT_VERSION_PATCH
> PROJECT_VERSION_TWEAK
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to