Erich,
On 24.01.2022 15:03, Erich Steinböck wrote:
> METAVERSION was already changed to 42 for 5.0
METAVERSION gets changed each time the compiled image changes structurally as
the comment "// gets
updated when internal form changes" clearly states, it is not dependent on a
change in the official
ooRexx version number. Just look at the changes to METAVERSION since February
20th, 2008:
svn log --diff interpreter/classes/support/ProgramMetaData.hpp
> no double patch please
This is not a "double patch".
---
You may be unaware of the fact that there are application developers out in the
market who have been
taking advantage of ooRexx 5.0 features and distribute their programs in
compiled form to protect
their source code. One very important reason being that ooRexx 5.0 fixes errors
that are present in
ooRexx 4.2. Also, ooRexx 5.0 is faster than ooRexx 4.2. And for some the new
features of ooRexx 5.0
are so compelling that they take advantage of them for the benefit of their
applications.
[This observation - ooRexx 5.0 being used for application development in the
field - and the
increase in overall quality of ooRexx 5.0 compared to 4.2 has been the
motivation to suggest to
create a release of 5.0 ASAP to open the doors for ooRexx 5.0 into companies
that do not allow
software dubbed as "beta".]
If compiled images are attempted to be run that are not valid then the ooRexx
interpreter must not
run them and issue an error to make the application developer and user aware of
this fact. This is
only possible by increasing the METAVERSION/image version indicator to inhibit
executing ooRexx
programs that got compiled with ooRexx 5.0 between April 30th 2019 and November
27th 2021 (the image
format changed with r12326 on November 28th 2021 and thus became incompatible
with earlier versions).
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
